It seems that no matter which side of the line you come down on, people feel very strongly about the way an organization should go about getting projects done. If you are in the PMO or Agile camp, historically, you haven’t seen eye to eye on which approach is best. Is it best to have a PMO? Is a strictly Agile solution the answer?
Many of those that think Agile is the way to go, believe that the PMO just gets in the way of productivity. Those that believe a PMO is the right answer often think that Agile is the wild west with a lack of process, governance, and clearly defined dates and outcomes.
Here’s the truth…
they are both right…
and they are both wrong.
In some cases, the PMO has become too process heavy and overbearing to be the high-IMPACT organization it was intended to be. In other cases, the Agile camp has started off with great intentions, but not stayed true to the spirit and intent of the approach, leading to a less productive, somewhat chaotic, team.
When done right, both the PMO and Agile teams can be highly productive IMPACT Engines that create high value outcomes for the organization. The key is in combining the why with the what and the how.
Finding common ground: The Why
Before we get into ways to see this from both perspectives, it’s important to take a step back and look at some commonalities between the two mindsets. Yes, that’s right. Let’s stop trying to make the case for why things won’t work and look at all the ways we can all just get along and combine forces to create a league of superheroes that can really Get. It. Done. (Yes, my son has me watching all the super hero TV series with him these days.)
The first question we must ask is always “What business problem are you trying to solve?” The answer to that question helps us understand why we are here and what value we can serve to the organization. Understanding your why statement makes it a lot easier to use our best thinking to develop a clear solution to address the business problem.
What we need to keep front and center in our thinking is this: both camps should be focused on the same end game – helping an organization get projects done the best way they know how. While that “know how” might be different for each perspective, the concept of the greater good must be paramount in our thinking and approach. We are ALL here to serve that goal of helping the organization create IMPACT.
If we are too caught up in the process being the end game, we are completely losing sight of this goal. Remember, process is the means not the end. Let us never forget, none of us are here if we don’t have projects to do in the first place and if we cannot get those projects done in a way that delivers high-IMPACT outcomes to our organization, we become irrelevant…all of us…regardless of which side of the project management fence we are on.
By putting our “us and them” mindset aside, we can figure out how we take that common goal and use our best combined thinking to come up with a solution that fits the organizational needs most effectively. While many of us get quite passionate about our favorite methodology, if we get too caught up in the way we are implementing our projects (to the point of being blind to other possible solutions), we might forget the why.
Getting straight on terminology: The What
To get to the highest-IMPACT outcomes together, we first need to level set on some terminology. Project Management is NOT the same as implementation methodology.
Project management is the application of processes, methods, knowledge, skills, and experience to achieve project objectives.
– Association of Project Management
Hmmm…sounds a lot like what we are all here to do, yes?
If you look at the project management best practice guides out there, you will see that there is a big emphasis on what you should do and the what is the same across all methodologies chosen for implementation. You “gotta” manage risk, schedule, scope, cost, communication, stakeholders, etc. Don’t we do that in every implementation methodology?
So, what makes us think that Agile isn’t project management? Isn’t it an approach for getting projects done? Do you manage risk in Agile? How about communication? And stakeholders?
Here’s a hint: EVERY implementation methodology that’s any good will address every aspect of project management “gottas,” while also giving you an approach to creating and delivering the outcomes. The differences we see aren’t with project management, but how we go about creating those outcomes– that’s implementation methodology.
Seems to me we have a lot of common ground so far…
Now let’s look at the PMO perspective.
Somewhere along the way, the PMO got stereotyped as the process heavy organization that is responsible for simply defining and executing on implementation methodology. While best practices (think project management) and implementation methodology are certainly a part of what a PMO can do to help create consistency and reliability in project delivery for an organization, that’s certainly only scratching the surface of what a PMO can do.
Oh, and by the way, who said a PMO is ONLY about “classic” waterfall implementation methodology? While many people think “waterfall” when they think PMO, I’ve seen many PMOs that apply a much more iterative framework for getting projects done. We also need to get clear that project management is not synonymous with waterfall either.
Working together to create IMPACT: The How
Instead of spending so much energy fighting to make our differences known, how about we focus on how we can collaborate to deliver IMPACT for the organization?
As many Agile experts will tell you, Agile isn’t the answer to every problem, all the time, just as a PMO isn’t always the answer either. What might be the best solution to deliver the highest possible IMPACT on projects is leveraging the best of both, or a hybrid approach.
A PMO can provide all sorts of services that can benefit any organization regardless of methodology chosen to implement projects. Here are some examples of services a PMO can provide that are not necessarily “covered” within the confines of a singular Agile project:
- Provide coaching, training and support on the implementation methodology of choice (the How)
- Act as an advocate for the use of best practices and methodology across the organization, as well as assisting with best fit implementation methodology selection for each project
- Provide governance and oversight to the portfolio, balancing shifting priorities, resource allocation, and conflicts
- Provide career development, mentoring and opportunities for growth for PM/Scrum Master
- Ensure project management (the What) is fully understood and at the forefront of thinking regardless of implementation methodology chosen
- Establish and collect project and portfolio metrics to ensure proper performance and high-IMPACT project outcomes
- Provide organizational change management support and guidance (the true differentiator between successful and failed projects – how well they bring people along with the change)
- Ensure properly educated and engaged stakeholders and sponsors
- Ensure process excellence and continuous improvement of approach and execution
- Provide strategic planning support and ensure strategic alignment of all projects
- Ensuring consistent adherence and application of the implementation methodology and best practices to increase reliability and predictability of project performance and ability to meet expected outcomes
If you have a team doing these things, then you have a PMO (project management office), whether you call it that or not. If you don’t, you may want to consider how engaging a team to perform these critical services can help ensure that the people doing the project work can focus on doing the project work. This alone can improve project throughput and productivity. Outsource what you are not best at so you can focus all energy on what you do best and then do that.
I believe the opportunities to leverage a PMO to help an organization deliver IMPACT are endless. I also believe implementing a more Agile-like approach to projects has some huge benefits.
Some of the benefits of an Agile implementation methodology are:
- Increased customer engagement, leading to a solution that has a higher likelihood of use. Higher likelihood of use means higher likelihood of creating intended IMPACT and return on investment (ROI).
- Increased project control. Yes, that’s right. Using Agile can increase your control and governance of the project work and deliverables.
- Faster ROI. You can get products, services, deliverables to market faster if you do it in stages, thereby reaping some benefits
- Reduced risk. With greater insight, oversight, and shorter cycles, you have a greater chance of minimizing risk realization and impacts.
- Higher deliverable quality through that increased engagement and more interactive requirements-solution development cycle.
- Greater agility. The ability to shift as the needs and requirements change is critical to ensuring we achieve that high-IMPACT outcome.
- Increased collaboration across the project team. Everyone is talking to everyone and everyone knows what’s going on. This is the heart of effective project communication.
- The techniques originally designed for software development apply to many types of projects such as process improvement initiatives, marketing projects, sales cycle improvements, etc. When the goal is improvement, there are many ways the “tweaking” approach can be useful in getting us to a highly tuned solution.
As you can see, there are plenty of benefits to be gained by leveraging the best of both worlds. We can leverage the PMO construct and team to handle many of the services that an organization requires to oversee an entire project portfolio, build competencies, manage tools and resources, and keep stakeholders engaged and effective through the change process. The project teams are then freed up to have a laser-focus on project delivery, using the best mechanisms for creating return on investment for each project undertaken.
The opportunity here for all of us is to work together to find the best fit solution for our organization. That’s where the magic will happen. That’s where you will create the biggest IMPACT.
Tell me your thoughts in the comments and let’s open a dialog. I would be excited to hear other opinions on this topic.
|Consider joining our LinkedIn Group to continue this conversation as well - CLICK HERE|
|We hope you will consider joining our Facebook Community as well. Click on the image to your left to visit and join, or you can CLICK HERE|
Reading this article qualifies you to submit a request for PDU’s from PMI.
This Article qualifies as follows:
PDU AMOUNT: .25 PDU’s
For more information on registering your PDU’s with PMI – CLICK HERE
At Project Management for Today, we encourage conversation; agree with us or disagree with us, it’s all still knowledge, and we are here to share knowledge. Take a moment to add to the conversation by leaving a comment. It’s an opportunity to engage in the conversation!
If you believe in what we are doing, take a minute to share our articles on your social networks such as LinkedIn and other sites. Use the buttons on the left side of the page.
This article features content from a “Contributing Author” to the Project Management for Today Community. This content is published on this site with the author’s explicit permission. As with all articles on this site, this article is protected by copyright. If you are interested in becoming a Contributing Author to this site, you can learn more by reading the information HERE
Laura Barnard has spent more than 24 years helping business leaders in a broad range of organizations, from nonprofits to global financial institutions, get the results they crave. She combines her deep experience in the PMO and Change Management space with her passion for helping people get things done to transform how organizations realize business strategy. She shares her experience and stories in her blog titled, “I wish I had me when I was you... ™”
Laura runs several training and coaching programs that help organizations and individuals deliver high-impact outcomes on their projects and drive organizational change. Laura is best known as “the PMO lady” for her extensive experience in building and running PMOs that Get. It. Done. while developing a high-performing team of IMPACT Drivers that become an invaluable asset to any organization.
Laura believes that project managers are uniquely positioned to help organizations have a greater impact. She is the Founder and President of Project Management for Change, a nonprofit organization whose mission is to raise the profile of the project management profession by showing the value of project management across the globe as the most effective enabling resource for delivering sustainable change in the nonprofit sector. Their signature event, the Project Management Day of Service (PMDoS)®, brings together thousands of project managers with hundreds of nonprofit leaders to change the world, one project at a time.
Laura served on nonprofit boards for more than 12 years including multiple Project Management Institute (PMI) chapters, Virginia International University and Goodwill Industries. She continues to support the evolution of Project Management globally in her role as advisory board member for several global firms, as well as continuing to bring high-IMPACT content to project management focused conferences and training programs. Laura has a Computer Science degree from Virginia Tech, a Project Management Institute (PMI), PMP certification, and a Prosci Change Management Practitioner certification.
You can learn more about Laura at IMPACTbyLaura.com.
Laura Barnard's Website- CLICK HERE