Define the Initiatives board and the Delivery boards (operations + engineering) purpose, structure, and process

[choldgraf]

Description

In a recent solution forum team meeting we asked the team to define the purpose and process around our Initiatives Board.

Initiatives Board link here

Why is this important

By defining a standardized process for this board, our team will have a shared understanding of the organization's priorities, which will help us focus discussion and refinement, as well as streamline our ability to choose actions and deliverables for sprints.

Definition of done

• Documented role and process for the Initiatives board
• No objections from #initiatives team.

Tasks

Beta Give feedback

1. Draft initial text for initiatives board purpose and structure
2. Conduct survey to understand the level of alignment on new purpose and structure
3. Share summary of findings of the survey #851
   +0
4. Feedback for draft language for initiatives board purpose and structure #817
   +0
   

   
5. Add initiatives and delivery board description #821
   +0
6. https://github.com/2i2c-org/meta/issues/956#issuecomment-2014379312
7. Rework the Partnerships Board to be the Operations Board #826
   +0
   
8. Define recurring dates and format for the first initiatives and operations board meetings #827
   8 of 8
   +0
   
9. Refine the initiatives board so that it matches our criteria for WIP and clarity #828
   1 of 6
   +0
   
10. Add community (formerly "upstream") projects to the Initiatives planning process #829
    +0
    
11. Harold shares his analysis of the surveys
12. https://github.com/2i2c-org/meta/issues/1397

[choldgraf]

In our retrospective meeting today we touched on the topic of "refining the initiatives board so that it has the right information needed for our group to discuss and prioritize initiatives". I just want to note that those are also the two remaining items in this initiative:

• Refine the initiatives board so that it matches our criteria for WIP and clarity #828
• Add community (formerly "upstream") projects to the Initiatives planning process #829

I think that we can consider this initiative complete once we think the board has been refined to a level that is "safe to try", and when @haroldcampbell has shared his analysis of the surveys. We'll always keep iterating, and this initiative was really about kicking off the process.

[colliand]

2024-05-07. Initiatives Planning. @choldgraf reports... this is another dangling issue. There are two pieces that remain open. Most of the check boxes are checked. Harold has a survey that everyone has taken and we need to review the results. This is in a waiting/blocked status. @jmunroe are we waiting for Harold to do work? Or what? @aprilmj thinks we've all completed the survey. Let's treat this as in progress. We'd like feedback from Harold. @choldgraf will follow up with Harold.

[choldgraf]

Initiatives planning 2024-05-21

• @aprilmj and @jmunroe will discuss Add community (formerly "upstream") projects to the Initiatives planning process #829 and how to set it on a pathway to completion