The product management team (aka PM team) is a subteam of Margo's Steering Committee. It's mission is to set technical directions aligned with project objectives, and to assure marketing enablement for Margo's deliverables. The product management team owns the roadmap planning and defines the requirements, both inputs for Margo's Technical Working Group.
In a spirit of openness, the roadmap and the collection of requirements are shared in public (read-only). Github Issues and Github Project view are used to structure these deliverables. The Specification Update Process can be used to make suggestions to the PM team.
- User Journey Steps - Deploy Workload At Scale - Step-by-step scenario
- Use the Project Dashboard to track the current status of requirements and roadmap planning
- Product Management collaboration space : MSTeams channel (Margo members only)
| Steps | Requirement Responsibility | Action | Assigned Label on Completion | Comments |
|---|---|---|---|---|
| 1 | PM member Submits Draft Requirement | Click here | PM-Requirement in Draft |
|
| 2 | PM Requirement Review | PM Group reviews submitted Requirements to gain consensus; once approved, the requirement Issue is assigned to the TWG (@ajcraig) for feedback | TWG - Feedback |
|
| 3 | TWG Feedback | TWG review the proposed requirement. | ||
| a. No Comments | No Comments: TWG accepts the requirement and is placed into the TWG requirement backlog. Move to Step 6 | TWG - Requirements Backlog |
||
| b. Comments raised | Reassigned to the PMG (@abbottjb) | PM - Reviewing TWG Feedback |
||
| 4. | PM Reviews TWG requirement Feedback | PM Group assesses the feedback and adjusts requirements accordingly - once approved, the requirement Issue is assigned to the TWG (@ajcraig) | TWG - Requirements Review |
|
| 5. | TWG Feedback | |||
| a. No Comments | TWG accepts the requirement and is placed into the TWG requirement backlog. Move to Step 6 | TWG - Requirements Backlog |
||
| b. Comments Raised | Reassigned to the PMG (@abbottjb) | PM - Reviewing TWG Feedback |
||
| 6. | TWG Initiate work on Requirement | TWG starts work on the requirement | TWG - Requirements in progress |
|
| 7. | Requirement Completed | |||
| a. Yes | Issue/PR assigned to the PMG for final review before the requirement is merged into the Spec baseline | PM - Requirement Final Review |
||
| b. No | Requires TWG feedback - Assign the issue to PWG (@abbottjb) - Move to Step 4 | PM - Reviewing TWG Feedback |