PM process
From UG
(Difference between revisions)
(→Major steps) |
|||
| Line 14: | Line 14: | ||
* organize project kick off meeting (present plan, explain responsibilities, etc) | * organize project kick off meeting (present plan, explain responsibilities, etc) | ||
* create proj plan that covers BA/SA phase (with milestones and dates) | * create proj plan that covers BA/SA phase (with milestones and dates) | ||
| + | * '''Milestone: Review design with MO''' | ||
Revision as of 19:16, 8 July 2010
Major steps
Init
- project gets assigned to PM by Chief PM
- meet with Chief PM
- create initial version of Proj Plan
- research subject matter
BA/SA phase
- assign BA/SA
- organize project kick off meeting (present plan, explain responsibilities, etc)
- create proj plan that covers BA/SA phase (with milestones and dates)
- Milestone: Review design with MO
Dev/QA/UAT phase
- once initial BA work completed assign Dev Manager
- have a meeting with Development Manger
- create Work breakdown structure (with Development Manger)
- create preliminary proj plan for Dev/QA phase (with Development Manger)
- create team / resource allocation (with Development Manger)
- organize project kick off meeting (present plan, explain responsibilities, etc)
Post Mortem
- organise project post mortem - analysis of bad and good
Ongoing
- get regular project status updates from team (2 times a week)
- update Chief PM (once a week)
- resolve conflicts, delays, risks, issues, etc
