Program Management/ProjectPlanTemplate: Difference between revisions
(→People) |
|||
| Line 1: | Line 1: | ||
=Project Name= | =Project Name= | ||
problem statement | problem statement or why we do this project | ||
==Goal== | ==Goal== | ||
keep the goal statement as simple as possible and include criteria to make it clear when the project will be completed | keep the goal statement as simple as possible and include criteria to make it clear when the project will be completed. one way to think of this statement is, what is the benefit of completing this project? | ||
===Scope=== | ===Scope=== | ||
| Line 12: | Line 11: | ||
==Duration== | ==Duration== | ||
estimated project time | estimated project time | ||
==Projects== | ==Projects== | ||
list any sub-projects - depending on complexity you may want to create a project page for each sub-project | |||
===Sub-project=== | ===Sub-project=== | ||
at a minimum, a sub-project should have a name and description. it may also include a link to the project page or inline text for a simple sub-project. | |||
==Communication== | ==Communication== | ||
| Line 44: | Line 46: | ||
* minutes go here | * minutes go here | ||
|} | |} | ||
==People== | ==People== | ||
list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project | list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project | ||
| Line 82: | Line 85: | ||
==Milestones/Iterations/Tasks== | ==Milestones/Iterations/Tasks== | ||
high level milestones can be included in this page. more complex milestones and tracking information (typically bug lists) should be included on a milestone specific tracking page | |||
==Dependencies== | ==Dependencies== | ||
| Line 95: | Line 99: | ||
==References== | ==References== | ||
other references, very useful catch all category for existing links and text when cleaning up existing project pages | |||
Revision as of 20:24, 30 October 2012
Project Name
problem statement or why we do this project
Goal
keep the goal statement as simple as possible and include criteria to make it clear when the project will be completed. one way to think of this statement is, what is the benefit of completing this project?
Scope
list items that are both in and out of scope for the project
Duration
estimated project time
Projects
list any sub-projects - depending on complexity you may want to create a project page for each sub-project
Sub-project
at a minimum, a sub-project should have a name and description. it may also include a link to the project page or inline text for a simple sub-project.
Communication
| Communication Type | Mechanism | Audience |
|---|---|---|
| Announcements | dev-platform and dev-planning lists | all |
| General discussion | dev-platform list | devs |
| Meetings | meeting time
|
all |
| Meeting summaries | this wiki | all |
Press & Blog Posts
optional - you may want to capture press, blog posts, etc. about the project
Minutes and Progress Reports
| 2012 | |
|---|---|
| |
People
list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project
| Project Champion | |
| Program Management | |
| Product | |
| UX | |
| Engineering | primary devs working on project |
| Other Engineering | subject matter experts contributing to project |
| Accessibility | |
| Localization | |
| Services | |
| Incoming Bug Triage | |
| QA | |
| Security | |
| Privacy | |
| Releng | |
| Marketing | |
| Legal |
Milestones/Iterations/Tasks
high level milestones can be included in this page. more complex milestones and tracking information (typically bug lists) should be included on a milestone specific tracking page
Dependencies
feature, partner, resource, etc.
Risks
list risks in table below
| Risk ID | Description |
|---|---|
References
other references, very useful catch all category for existing links and text when cleaning up existing project pages