Project Management

Does your PMO hinder or help your agile transformation?

From the Easy in theory, difficult in practice Blog
by
My musings on project management, project portfolio management and change management. I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success. This blog contains articles which I've previously written and published as well as new content.

About this Blog

RSS

Recent Posts

Leading Through Crisis Means Leading Through Context

"It's the end. But the moment has been prepared for." - retirement lessons from the Doctor

Just because they are non-critical, doesn't mean they are not risky!

Just because they are non-critical, doesn't mean they are not risky!

How will YOU avoid these AI-related cognitive biases?

Categories

Agile, Artificial Intelligence, Career Development, Change Management, Communications Management, Decision Making, Governance, Hiring, Kanban, Lessons Learned, Personal Development, PMO, Portfolio Management, Project Management, Resource Management, Risk Management, Risk Management, Schedule Management, Scheduling, Tools

Date

linkedin twitter facebook Request to reuse this  

Categories: Agile, Change Management, PMO


An agile project management office might sound to some like an oxymoron, right?

This might be a reasonable assertion as many PMOs were first formed to provide oversight over a portfolio of projects and enforcing standards sounds like the antithesis to agility. But many successful PMOs have evolved beyond governance and control to helping their company reach higher levels of organizational project management maturity, and increasing agility should be complementary and not contradictory to this pursuit.

There are many ways in which PMOs can hamper progress towards greater agility including:

  • Enforcing standards over principles
  • Continuing to apply traditional funding models and prerequisites to agile investments
  • Obsessing over vanity metrics such as velocity or time to market rather than business value delivered or shipped features utilized
  • Evangelizing agile from the ivory tower instead of actively engaging with and supporting teams
  • Failing to inspect and adapt

So what can a PMO do to actively support an agile transformation?

  • Collecting chronic impediments from agile teams, curating and prioritizing them, and championing their elimination by the appropriate senior leaders
  • Having the courage to say "NO!" when a given context is not suitable for using an adaptive approach
  • Advocating for funding to incent early adopters to try new delivery approaches
  • Encouraging staff who possess the right expertise, behaviors and attitude to train and take on Agile Lead/Scrum Master or Product Owner roles with coaching support
  • Examining their own operational processes and leaning them out as much as possible
  • Shifting portfolio reporting from being a manual, onerous process to the automated consumption of information radiators
  • Migrating from an artifact-centric delivery approach to an information-centric model
  • Transforming heavy, gate-based governance to a metrics-driven, exception-based process
  • Working actively with functional managers, procurement, HR and other key stakeholders to change their project engagement models to be more support of adaptive approaches
  • Helping portfolio governance committees to make their investment selection, evaluation and prioritization processes more agile

An agile transformation provides the leadership of a PMO with a good opportunity to review their charter and service catalog - are these still relevant, and if not, what can be changed to ensure that the PMO is not identified as common impediment by agile teams!


Posted on: May 06, 2018 07:00 AM | Permalink

Comments (8)

Please login or join to subscribe to this item
avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Kiron, really great points listed. Each one of those has significant meaning; and effect! In the early phases of the maturity process, there is probably a transition from the first set of points to the second, though I suppose not without the I&A aspect!

avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Thanks Kiron, great stuff. It's a tricky one because what senior management require from the PMO is not always in line with actively supporting an agile transformation. Can you please elaborate on "transforming heavy, gate-based governance to a metrics-driven, exception-based process."

avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Thanks Andrew!

Sante - many traditional project governance models penalize the many to protect the organization from the few. A better approach is to use a holistic set of quantitative metrics (e.g. EVM, customer/stakeholder satisfaction) drive how much oversight is required so scrutiny is only placed on the few projects which are truly offside.

Kiron

avatar
Samuel Berroa de La Rosa Engineer.| Food processing / Construction Management Pa, United States
Change in the only constant and when it is to improve we have to embrace it..
Very good !!!
Thankss

avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Thanks Kiron.

avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Thanks Samuel!

avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
Good points, Kiron and thanks for sharing.

avatar
Cibin Thomas Reston, Va, United States
Thanks for sharing Kiron!!

Please Login/Register to leave a comment.

ADVERTISEMENTS

"If you think you've hit a false note, sing loud. When in doubt, sing loud."

- Robert Merrill

ADVERTISEMENT

Sponsors