PM process

From UG

Revision as of 19:04, 8 July 2010 (edit) Alex (Talk | contribs) (→Major steps) ← Older edit		Revision as of 19:15, 8 July 2010 (edit) (undo) Alex (Talk | contribs) Newer edit →
Line 9:		Line 9:
	* 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'''		'''BA/SA phase'''
Line 30:		Line 26:
	'''Post Mortem'''		'''Post Mortem'''
	* organise project post mortem - analysis of bad and good		* 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

---

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

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