PM process

From UG

Revision as of 19:35, 8 July 2010 (edit) Alex (Talk | contribs) (→Ongoing Activities) ← Older edit		Revision as of 19:36, 8 July 2010 (edit) (undo) Alex (Talk | contribs) (→Standard methods) Newer edit →
Line 36:		Line 36:
	== Standard methods ==		== Standard methods ==
		+
		+	=== Communication ===
	All communication is done through:		All communication is done through:

---

Revision as of 19:36, 8 July 2010

Contents 1 Phases 1.1 Init 1.2 BA/SA 1.3 Dev/QA/UAT 1.4 Close 2 Ongoing Activities 3 Standard methods 3.1 Communication

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

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)