PM process

From UG

Contents 1 Intro 1.1 Lead PM 1.2 End of the week updates 1.3 Meeting notes 2 Phases 2.1 Init 2.2 BA/SA 2.3 Dev/QA/UAT 2.4 Close 3 Ongoing Activities 4 Standard methods 4.1 Communication

Intro

Lead PM

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
• 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)