PMO｜The PMO Rules of Engagement

Rules of Engagement are among the first elements the PMO office establishes. They outline clear expectations and define responsibilities for tasks anticipated in PMO management. This blog will provide an example of a PMO office's Rules of Engagement and discuss the considerations related to them.

General Guideline 
PMO Project Management operation will perform planning, task scheduling, status tracking, reports, escalations, delivery of features checks, documentation standardization review, and assist communication between stakeholders. PMO process generally contains:

• Weekly project status meeting with a report
• Sprint planning/grooming meeting 
• Daily/weekly standup meeting
• Each task is tracked with dev resources, priority, dependency, and deliverable timelines. 
• Track project roadmap, activities, and product changes

PMO project management operation does not engage in detailed requirement clarification, technical design decisions, solution task planning, testing content and execution discussions, technical risk mitigation, issue resolution, user training, production support transition, and technical approvals, including information security, network, platform, performance, and production release approvals.

All PMO-managed escalations require the dev team to perform due diligence and sign off before the escalation.

Detailed Explanation 

You may add more details as your PMO responsibility increases. ​