Update the working with us and initiative flow doc

Signed-off-by: Pierre-Yves Chibon <pingou@pingoured.fr>

modules/ROOT/pages/initiatives.adoc

@@ -11,16 +11,40 @@ The process to bring something to the attention of the CPE team consists of
 several steps:
 
 * Propose a new initiative; this proposal gives the “what” and “why” of the
-  work requested.
-* The team will review and discuss the proposal and determine whether it fits
-  its mission statement and thus if it is worth being pursued by the team, or
-  whether this work falls under the responsibility of someone else.
-* If the CPE team determines the proposal to be in line with the
-  xref:index.adoc[mission statement], the team will work together with the
-  submitter on figuring out the best approach to fulfill the request.
-* Based on the estimated amount of work, the initiatives currently in
-  progress, priorities, and return on investment, the CPE team decides whether
-  they can commit to this initiative, and if so, a rough timeline for it.
+  work requested and send it to the product owner.
+* The product owner reaches back and schedules some time with the requestor(s)
+  to go over the proposal to refine the details. We are looking to establish
+  why this initiative is important to do,what benefits it will bring to the
+  community, the technical details as the requestor sees them and their
+  estimated ‘need by’ date.
+* Once we have established these requirements, the product owner reviews the
+  request with the technical leads of the team to scope the effort the initiative
+  will require from the team to complete. These details include skill sets needed,
+  hardware, storage, automation, dependant services that could be impacted by
+  changes made & how long they think this would take to complete.
+* This information is then reshared with the requestor to verify and sign off on
+  and then reviewed by the CPE review team to be accepted or rejected to our backlog.
+* If rejected, the requestor is notified by the product owner.
+* If accepted the proposal is added to our backlog queue and is reviewed before
+  quarterly planning dates to be considered as an option.
+* Projects that are moved from the backlog queue to the consideration queue and
+  are not chosen for that quarter may still be progressed in the next quarter, or
+  depending on project sizes and timelines, may be picked up by the team on free
+  cycles if they choose to work on this
+* The team leads, team management team and all the stakeholders review all the
+  proposals for the quarterly planning session during which they prioritize a number
+  of initiatives for the coming quarter.
+* The management team forms the different project teams who will be working on the
+  different initiatives during the quarter.
+* As the quarter progresses, the product owner will reach out to the requestor(s)
+  to sync with them on the progress of the initiatives.
+
+
+.Initiatives flow
+[#img-initiative-flow]
+[caption="Figure 1: "]
+image::CPE_initiatives_flow.jpg[The initiative flow,500,500]
+
 
 === Writing Down a Requirements Document
 

modules/ROOT/pages/working_with_us.adoc

@@ -1,12 +1,24 @@
 :experimental:
 = Working with Community Platform Engineering
 
-This document explains the basic principles of working with the CPE team.
-These rules are necessary to allow the team to operate efficiently and to
-allow us to plan our work.
+This document explains how the CPE team works.
 
-The general rules are:
+We break down work requests that the team responds to into two categories, which we believe benefits both the CPE team and the communities we serve as they allow the team to operate efficiently and allow us to plan our work.
 
+* Initiatives handled by dedicated project teams
+  ** Initiatives are projects that require multiple team members to complete
+     over multiple weeks/months, in depth scoping and timelines
+  ** The process for submitting a new initiative is described in the
+     xref:initiatives.adoc[New Initiative workflow] document.
+
+* Work requests handled by the Infra & Releng Team
+  ** This team responds to 'lights on work' and requests that come in on an
+     ad hoc & regular basis such as:
+    *** BAU infra/releng requests
+    *** Bug fixes
+
+
+Some general best practices when working with us are:
 * Do not ping a single person
 +
 By doing this you reduce the number of people having access to your request