Our traditional PMO is struggling to find its place in the new Agile world. They are used to managing scope baseline, detailed planning, and resource allocation across multiple projects. How should the PMO adapt its role and structure to become an enabler of the Agile Transformation? Should it pivot toward Agile Governance, focusing on value streams and Portfolio Management, or primarily manage dependencies across multiple Scrum teams? What is the new value the PMO offers?
3 answers
The traditional PMO must pivot away from micro-managing individual project scope and instead focus on becoming an Agile Governance body centered around Portfolio Management and Value Streams. The new value the adapted PMO offers includes:
-
Portfolio Alignment: Ensuring all Scrum teams and Software Development efforts are aligned with the top strategic business priorities (Value Delivery).
-
Dependency Management: Proactively identifying and managing large, systemic dependencies and organizational risks that span multiple Agile teams.
-
Coaching & Standardization: Establishing the organization's standards for Agile metrics (like Velocity and Cycle Time) and providing coaching to Scrum Masters and Product Owners to ensure consistency and continuous improvement. This shifts the PMO from a policing function to an enabling one, supporting Sustainable Development across the enterprise.
Should the reformed PMO still be responsible for assigning people to Scrum teams, or does that responsibility belong entirely to the executive leadership (for strategic allocation) and the teams themselves (for self-organization)?
The PMO transforms into a function focused on Agile Governance and Portfolio Management. Its new value is ensuring alignment between Value Streams and strategic business goals, moving from micro-management of individual projects to macro-management of the entire Software Development portfolio.
Samantha is spot on. The PMO's primary role becomes helping the organization "think big" (portfolio) and letting the teams "manage small" (the Sprint), which is the essence of scalable Agile Transformation.
Ethan, the PMO should not assign individuals; that contradicts self-organizing teams. The PMO should facilitate the strategic allocation of funding and resources to the highest priority Value Streams (e.g., funding a "Customer Portal" team for a year). Executive leadership defines these strategic streams. The teams then determine their own composition and roles within that funding envelope, leveraging their expertise to foster motivated individuals and better team collaboration.