PM process

From UG

(Difference between revisions)
Jump to: navigation, search
(Created page with 'Category:Software Development Processes == Major steps == * get project assigned by Chief PM * reasearch documentation * research subject matter * create Work breakdown str…')
(Major steps)
Line 3: Line 3:
== Major steps ==
== Major steps ==
-
* get project assigned by Chief PM
+
'''Init'''
-
* reasearch documentation
+
* project gets assigned to PM by Chief PM  
 +
* meet with Chief PM
 +
* create initial version of Proj Plan
* research subject matter
* research subject matter
 +
 +
'''Ongoing'''
 +
* get regular project status updates from team (2 times a week)
 +
* update Chief PM (once a week)
 +
* resolve conflicts, delays, risks, issues, etc
 +
 +
'''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)
 +
 +
 +
'''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 Work breakdown structure (with Development Manger)
-
* create preliminary proj plan (with Development Manger)
+
* create preliminary proj plan for '''Dev/QA phase''' (with Development Manger)
* create team / resource allocation (with Development Manger)
* create team / resource allocation (with Development Manger)
 +
* organize project kick off meeting (present plan, explain responsibilities, etc)
-
* organize project kick off meeting (present plan, explaine responsibilities, etc)
+
'''Post Mortem'''
-
* get project updates
+
* organise project post mortem - analysis of bad and good
-
* send project updates
+
-
* resolve conflicts, delays, risks, issues, etc
+
-
* organise project post mortem
+

Revision as of 19:04, 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

Ongoing

  • get regular project status updates from team (2 times a week)
  • update Chief PM (once a week)
  • resolve conflicts, delays, risks, issues, etc

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)


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
Personal tools