Project Management

Please login or join to subscribe to this thread

Do we need a PMO in Agile?

linkedin twitter facebook   Agile   Governance   Organizational Project Management   Scrum  
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia
Many advocate for the replacement of Project Managers with Scrum Masters.
What tipe of PMO, if there is still a PMO, will Agile bring?
Sort By:
< 1 2 >
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia
Mar 14, 2019 9:08 AM
Replying to Wade Harshman
...
The typical answer is no, there's no PMO in an Agile organization. In a nutshell, the argument follows this pattern: Projects are temporary endeavors undertaken to perform some sort of change (new product, service, or result). Agile organizations view change as constant, with no defined end. Therefore, there are no "projects" for anyone to manage, so there is no need for a PMO.

Having said that, there are plenty of Agile organizations that keep project managers. I've witnessed plenty of examples. In contrast to the traditional construction or aerospace PMs that we like to show in full control, an agile PM might be an assistant to a product owner or help coordinate organizational change. I like Kiron's answer here, that a PMO can exist so long as it offers value to the organization (and that should be true regardless of whether the organization is agile or not).

PMI has been working hard to adapt as more and more organizations shift to an agile culture. Frankly, there are a lot of things we still get wrong and we have a lot of catching up to do. For example, you're right that a lot of people advocate for moving PMs into scrum master positions, but this is a common mistake. The two positions are not related, and while an individual PM might be able to make the transition, it really is a type of career change away from project management.

I'm happy that project managers are making the effort to adapt to Agile, but I hope that we don't lose sight of the things we already do well because we're chasing after something else.
Thank you Wade. I don't know where in Agile it's the mandate for 'no defined end'. Incremental and iterative doesn't mean that at some point there is no end. All products and services have a lifespan. Projects are just iterations that deliver one or more increments. Real Agile should deliver multiple increments, to the users, during the project. Each Release/Version of a product can be considered a project when the end is the go live. Done correctly Agile should minimise the traditional Project Closure Phase.
Anything, including Agile, should exists as long as it adds value to the organisation.
I agree that PM and SM are complementary roles in a project and I don't understand how people can promote the replacement of PMs with SMs and then ask the SM to to exactly the same tasks as the PM, usually at a lower pay.
I agree that we should not throw the baby out with the bathwater and retain the useful knowledge and experience that project management discipline has.
I am one of the few who transitioned to planned project management from Agile. I was (sort of) lucky to use Agile patterns in mid 80s. I believe that using planned approach can improve the benefits of agility, if done right, and experience needs time. It can't be acquired in the training class.
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia
Mar 14, 2019 9:57 AM
Replying to Sergio Luis Conte
...
Do you need a PMO with Lean? Do you need a PMO with Six Sigma? Do you need a PMO with any enterprise strategy approach you decide to take? The same for Agile. Is not a matter of strategy.
Thank you Sergio. Excellent question, I will use in my next webinar about the role of the PMO in the Agile Enterprise (with credits).
If Lean Six Sigma, focused on eliminating waste, didn't recommend the removal of the PMO, if the computerisation didn't eliminate the need for a PMO, why Agile won't need a PMO.
I worked in (small) software companies, implemented XP and Scrum and delivered without any formal project management framework. But..
When the company grew we had to define a strategy, we had to plan, we had to introduce governance.
In mid 80's, when I probably worked in the most Agile environment, we had to obtain funding for our research. There was no PMO, but a body that made sure that whatever we do with the money has a justification. Unlike in a commercial environment, sometimes all we proved was that an idea it's not feasible, although it looked good and smart.
I don't see the need of governance disappearing in Agile, nor the need for support. I've seen many new names for the PMO but it seems that everybody agrees that there is a need for something beyond the Scrum or Project Team.
...
1 reply by Sergio Luis Conte
Mar 15, 2019 4:53 AM
Sergio Luis Conte
...
We are using Agile and we have a governance process in place. In fact, out process is based on stage gate approach and if you see https://www.stage-gate.com/ you will see adaptations to Agile. To have or not to have a PMO is not tied to the approach. It is tied to strategy where organizations define the functions/process and then is time to decide where those functions/process will be located. For example, by creating a new business unit called PMO.
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia
Mar 14, 2019 11:19 AM
Replying to Vincent Guerard
...
Stelian,

What is the role of the PMO?

In most case, you would want a PMO to cover all type of project management methods.
Thsnk you Vincent.That's a good question too. Can an Agile Enterprise function and survive as a collection of Scrum Teams? Whatever the role of the PMO is, it should fulfil a need. Sometimes the need is just to produce monthly RAG reports. I believe that anyone and anything should add value and a PMO can add a lot of value. Maybe as a Servant Leader.
avatar
Stelian ROMAN Project Manager| MicroSafety Carlingford, New South Wales, Australia
Mar 14, 2019 2:05 PM
Replying to Ema Garcia
...
When transitioning from traditional waterfall to Agile, I recommend creation of an Agile Center of Excellence (ACoE). This becomes the command post for governance, training, and Agile maturity within your organization.
Thank you Emma. The name is irrelevant. The PMO is already a center of excellence, for predictive framework. I believe that instead of discarding it it's more beneficial for the organisation to enhance it adding adaptive frameworks to their portfolio.
I strongly disagree with the term 'command post' and in some degree with the responsibility for training. Centralised training can be as bad as dogmatic Agile.
Each team should be able to and self-organise. Imposing a certain framework and a certain way to do things is not Agile.
BTW, the "traditional" waterfall was very Agile. The paper published by Royce in 1970 includes an option for a process that is very similar with some Agile frameworks. There are many Agile, or pretending to be Agile, teams, using a Requirements, Develop, Test, Implement swim-lines board, having a handover to QA (actually QC) or depicting the scrum iteration as a succession of mini-waterfalls: plan, develop, test, release.
In conclusion, I agree with a center of excellence but a center of excellence that can see beyond a team of 7.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Mar 14, 2019 7:04 PM
Replying to Stelian ROMAN
...
Thank you Sergio. Excellent question, I will use in my next webinar about the role of the PMO in the Agile Enterprise (with credits).
If Lean Six Sigma, focused on eliminating waste, didn't recommend the removal of the PMO, if the computerisation didn't eliminate the need for a PMO, why Agile won't need a PMO.
I worked in (small) software companies, implemented XP and Scrum and delivered without any formal project management framework. But..
When the company grew we had to define a strategy, we had to plan, we had to introduce governance.
In mid 80's, when I probably worked in the most Agile environment, we had to obtain funding for our research. There was no PMO, but a body that made sure that whatever we do with the money has a justification. Unlike in a commercial environment, sometimes all we proved was that an idea it's not feasible, although it looked good and smart.
I don't see the need of governance disappearing in Agile, nor the need for support. I've seen many new names for the PMO but it seems that everybody agrees that there is a need for something beyond the Scrum or Project Team.
We are using Agile and we have a governance process in place. In fact, out process is based on stage gate approach and if you see https://www.stage-gate.com/ you will see adaptations to Agile. To have or not to have a PMO is not tied to the approach. It is tied to strategy where organizations define the functions/process and then is time to decide where those functions/process will be located. For example, by creating a new business unit called PMO.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Smoking is one of the leading causes of statistics."

- Fletcher Knebel

ADVERTISEMENT

Sponsors