PM process
From UG
(Difference between revisions)
(→Major steps) |
|||
| (5 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Software Development Processes]] | [[Category:Software Development Processes]] | ||
| - | == | + | == Intro == |
| - | + | === Lead PM === | |
| - | * project gets assigned to PM by | + | |
| - | * meet with | + | === End of the week updates === |
| + | PM sends weekly update to Lead PM on their projects. | ||
| + | |||
| + | Lead PM sends weekly update to the President, cc others. | ||
| + | |||
| + | === Meeting notes === | ||
| + | |||
| + | == Phases == | ||
| + | |||
| + | ===Init=== | ||
| + | * project gets assigned to PM by Lead PM through Mantis | ||
| + | * meet with Lead PM | ||
* create initial version of Proj Plan | * create initial version of Proj Plan | ||
* research subject matter | * research subject matter | ||
| - | + | ===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 28: | ||
| - | + | ===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 36: | ||
* 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 | ||
| + | * if proj plan has changed - distribute updated | ||
| + | |||
| + | == Standard methods == | ||
| + | |||
| + | === Communication === | ||
| + | |||
| + | All communication is done through: | ||
| + | |||
| + | * mantis | ||
| + | * Skype | ||
| + | * email (everyone must check min 2 times a day and reply or at least confirm e-mail received same day) | ||
Current revision as of 14:52, 16 July 2010
Contents |
[edit] Intro
[edit] Lead PM
[edit] End of the week updates
PM sends weekly update to Lead PM on their projects.
Lead PM sends weekly update to the President, cc others.
[edit] Meeting notes
[edit] Phases
[edit] Init
- project gets assigned to PM by Lead PM through Mantis
- meet with Lead PM
- create initial version of Proj Plan
- research subject matter
[edit] 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
[edit] 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)
[edit] Close
- organise project post mortem - analysis of bad and good
[edit] 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
[edit] Standard methods
[edit] Communication
All communication is done through:
- mantis
- Skype
- email (everyone must check min 2 times a day and reply or at least confirm e-mail received same day)
