The Agile PMO Game Theory
A Project Management Office can act as an obstacle to agile projects. This can take the form of asking for inappropriate planning detail by not recognizing the likelihood of changes, or asking for conformance to templates that are not even used on an agile project. For these reasons, PMOs often get a bad reputation on agile teams. But it need not be that way--they can also add tremendous support and be a great help.
First, let’s look at what a PMO actually does--or what they should do, since implementations and services vary. In the September 2010 issue of the Project Management Journal (the PMI’s research publication), there was a nice definition of PMO roles:
- Monitor and control project performance
- Develop and implement standard methodologies, processes and tools
- Develop the competency of project personnel, including training and mentoring
- Multi-project management, including program and portfolio management, coordination and allocation of resources between projects
- Strategic management, including participation in strategic planning and benefits management
- Organizational learning, including the management of lessons learned, audits and monitoring of PMO performance
- Management of customer interfaces
- Recruit, select and evaluate project managers
- Execute specialized tasks for project managers (e.g.
Please login or register below to read the rest of the article.