PM process
From UG
(Difference between revisions)
(→Major steps) |
|||
| Line 1: | Line 1: | ||
[[Category:Software Development Processes]] | [[Category:Software Development Processes]] | ||
| - | == | + | == Phases == |
| - | + | ===Init=== | |
* project gets assigned to PM by Chief PM | * project gets assigned to PM by Chief PM | ||
* meet with Chief PM | * meet with Chief PM | ||
| Line 10: | Line 10: | ||
| - | + | ===BA/SA === | |
* assign BA/SA | * assign BA/SA | ||
* organize project kick off meeting (present plan, explain responsibilities, etc) | * organize project kick off meeting (present plan, explain responsibilities, etc) | ||
| Line 17: | Line 17: | ||
| - | + | ===Dev/QA/UAT === | |
* once initial BA work completed assign Dev Manager | * once initial BA work completed assign Dev Manager | ||
* have a meeting with Development Manger | * have a meeting with Development Manger | ||
| Line 25: | Line 25: | ||
* organize project kick off meeting (present plan, explain responsibilities, etc) | * 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) | * get regular project status updates from team (2 times a week) | ||
* update Chief PM (once a week) | * update Chief PM (once a week) | ||
* resolve conflicts, delays, risks, issues, etc | * resolve conflicts, delays, risks, issues, etc | ||
Revision as of 19:18, 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
