Confirmed users
1,052
edits
Project Management/2011 Q4/Updates/Project Funnel - Short-Term Proposal: Difference between revisions
Jump to navigation
Jump to search
Project Management/2011 Q4/Updates/Project Funnel - Short-Term Proposal (view source)
Revision as of 22:55, 21 November 2011
, 21 November 2011→Example Timeline and Intake Phases
| Line 34: | Line 34: | ||
== Example Timeline and Intake Phases == | == Example Timeline and Intake Phases == | ||
* One month before quarter begins, mozpm sends email to all@ announcing "project submissions will start in two weeks, so start planning." | |||
* Over the next two weeks product owners, project/program managers, and leaders from the entire organization work with their teams to hone their project list and priorities. | |||
* Two weeks before quarter begins, mozpm sends email with link to the submission form, announcing that the window for submissions has begun and will end the day before quarter begins. | |||
* Product owners, project/program managers, and leaders from the entire organization have a two-week window to submit their projects. | |||
* First day of the quarter, mozpm sorts and organizes the results of the form submissions in a Google Doc spreadsheet. | |||
* mozpm removes duplicate projects and cleans up submitted data. 2-3 days | |||
* mozpm communicates to the organization the summaries and metrics of the submitted data by end of week. | |||
* (Steering committee? Directors?) perform a [[Project_Management/2011_Q4/Meetings/Background_Info#Project_Prioritization|project prioritization]] process on the submitted projects. 2 days. | |||
* (Steering committee? Directors?) review and adjust the list of projects that should be priority for the next quarter. 2 days. | |||
* Gather feedback from all Mozilla groups if all priority projects are technically possible within the defined period of time. | |||
* Adjust priorities based on what is possible given all of the internal constraints and feedback. | |||