PM process
From UG
(Difference between revisions)
(→Ongoing Activities) |
|||
Line 33: | Line 33: | ||
* update Chief PM (once a week) | * update Chief PM (once a week) | ||
* resolve conflicts, delays, risks, issues, etc | * resolve conflicts, delays, risks, issues, etc | ||
+ | * if proj plan has changed - distribute updated |
Revision as of 19:22, 8 July 2010
Contents |
Phases
Init
- project gets assigned to PM by Chief PM
- meet with Chief PM
- create initial version of Proj Plan
- research subject matter
BA/SA
- 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
- 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)
Close
- organise project post mortem - analysis of bad and good
Ongoing Activities
- get regular project status updates from team (2 times a week)
- update Chief PM (once a week)
- resolve conflicts, delays, risks, issues, etc
- if proj plan has changed - distribute updated