Building an Agile PMO (Project Management Office) for Organizational Efficiency
What is Agile PMO?
You know, with Agile Project Management Offices (PMOs), I feel like this is one of those topics that doesn’t get enough airtime. Am I right? But it’s actually a really fascinating concept that more folks should be talking about in the industry and they don’t, really. I guess Waterfall PMOs are still more popular than Agile, but it is certainly catching on.
I had world expert Jon Ward write my Agile PMOs chapter in my book “The PMO Lifecycle: Building, Running, and Shutting Down” (which you can conveniently purchase on Amazon) but realized I haven’t gone too deep on specifically Agile PMOs myself. I ran a pure Agile PMO when I was at a large software company several years back and helped bring in Agile in IT at that same company. So, I know Agile very well. I say a traditional PMO and an Agile PMO are really not that different from a traditional PMO, which we tend to call them Waterfall PMOs. There are lots we can talk about there, but for today, let’s just focus on Agile PMOs.
Sure, you could say something like “An Agile PMO is a framework for implementing Agile practices across an organization’s projects” and that would be technically correct. But really nailing down what an Agile PMO actually looks like in practice? Agile methodologies are very different than Waterfall, DevOps, Manufacturing, and so spending time and understanding the structure of an Agile PMO is critical. It is also important to understand that one Agile PMO at one company is going to vary greatly depending on the company, the leadership team’s philosophies, and how it meshes it a PM methodologies will also be different.
With over 30 years of hands-on experience in the Project Management field, including over 20 years dedicated to the PMO space across ten PMOs and four different companies, I’ve gained invaluable insights. Reflecting on my career, the diversity of experiences across those PMOs highlights the unique experiences I have had and when I ran my Agile PMO in the Marketing department at Microsoft, I gained a ton of experience in this space.
Throughout my career, I’ve seen Agile PMOs that are basically just lightweight governance bodies, and others that are these enormous, complex PMOs with Agile, Waterfall and Hybrid type projects. Some focus solely on promoting Agile principles, while others incorporate elements of more traditional project management too. What is interesting is that each PMO I ran always had strong project management practices included in them that helped in the execution. There’s no single, clean-cut way to a PMO regardless of the type, because every organization puts their own spin on it based on their unique needs and cultures.
What do you think? Do you agree?
Anyway, that’s just my initial thoughts with my many years in this PMO space I wanted to share before we got too far into this article. Let me know if you have your own experiences to share around Agile PMOs. Or if you just want to vent about something completely different, I’m all ears!
Before delving deeper into the article, I’d like to share a video I’ve created on my YouTube Channel that I believe you’ll find enjoyable. You can watch it here.
What did you think?
Alright, let’s return to the fundamentals and discuss building an Agile PMO.
What I want to do now is focus on creating an Agile PMO and what I have seen and done in the past. Let’s dive into the seven steps for creating an Agile PMO. These steps some best practices around Agile principles and practices I have used personally in my PMOs in the past.
Seven steps to an Agile PMO
Before diving into the first step of building an Agile PMO, it’s crucial to understand the benefits it offers compared to a traditional project management office. Here are just some comparisons from my perspective:
Raise awareness of the value of moving to an Agile mindset.
Introduce a consistent way of working that uses a formal framework (such as Scrum, Kanban, or SAFe).
Change the focus from reporting to learning to use daily stand ups and retrospective meetings to help teams inspect and adapt.
Introduce new roles and responsibilities that support the needs of Agile delivery teams, which may include business analysts, technical product owners, test engineers, and user experience designers.
Change from traditional project management tools such as Microsoft Project to tools like Jira that are better suited for Agile delivery and collaboration with remote team members.
Review governance and assurance processes to ensure they are fit for purpose in an Agile environment, including getting rid of unnecessary paperwork or steps in existing processes that add overhead but don’t provide value (lean principles at work).
Rewire how people within the organization interact with one another; this includes introducing new communication channels for teammates working remotely, including video conferencing software like Zoom or Google Meet so everyone feels connected on projects even if they’re not physically together in person
What do you think? Do you have other comparisons I have missed that you have seen before? Ok, let’s jump into step 1 which focused on the need to change the project deliver practices you are using today and look at using more of an Agile framework delivery model.
Step 1. Understand the need for change in project delivery
A good place to start is to ask yourself why traditional project management approaches are being challenged. It’s likely that your organization is facing one or more of the following challenges and feels like something is not working anymore. Let’s look at some of these areas:
Organizations are changing their business models – Shifting the focus of traditional project management from producing products and services as outputs to achieving outcomes. But as organizations shift their business models to embrace new digital-first thinking, it’s time for project management to change too. New tools like artificial intelligence and machine learning are creating new opportunities for businesses to create value for customers. And yet many organizations find themselves hamstrung in their ability to innovate by less than agile approaches to managing projects and delivery teams. This does not mean that effective project management is not necessary it is. However, it implies that we need to make adjustments to what we have been doing in the past.
Speed – As the pace of innovation increases and competitive threats become more common, speed to market has become critical in getting ideas turned into marketable products and in the hands of your customers as soon as possible. The traditional approach of carefully defining requirements up front before work begins may have made sense when change was slow, but today it creates unnecessary risk. I want to be careful here, because this is also where companies get in trouble as well, because when we don’t document any requirements or do a poor job there, we see problems down the line in testing and then eventually in the adoption phase. So, speed is good, but poor quality is not!
Talent – Employees are increasingly looking for jobs that offer them autonomy and opportunities for ongoing learning rather than just a paycheck at the end of each week. Those days are long gone, employees are starting to realize that work/life balance is critical and yes large pay checks are good, but at the pace of layoffs these companies are doing, employees are recognizing they don’t last forever. More and more we are seeing employees moving from one role to another and more and more we are seeing mass layoffs at high-tech companies that it has put both the employee and the company in a difficult position. However, as it relates to Agile, we are seeing employees thrive in this Agile environments and companies that embrace Agile are more likely able to keep their employees that much longer.
Ok, let’s look at step 2 now, which focus on a coaching and learning mindset. Many years ago when I was at Microsoft, they used to talk about growth mindset all the time. The one thing all that talk on Growth Mindset did for me was to make me realize I have always felt like I had to keep larning and growing and continue to learn wherever I could. Let’s dive into this now.
Step 2. Change the culture from a controlling and reporting mindset to a coaching and learning mindset
Your PMO team needs to understand Agile, what it is, and the benefits. They must be able to describe the difference between their role in an Agile PMO and their previous traditional PMO. Agile PMO roles and responsibilities differ from Waterfall responsibilities so critical to ensure that everyone is clear. They will need training in that new responsibilities and have always recommended that everyone start with ScrumMaster training as a starting place. We should not expect them to pick up this change of direction alone, as there is a lot to learning Agile and every bit of training helps.
It is also important that your PMO team understands they are part of the extended project team rather than “above” it. The Agile approach is based on teamwork – all members work together as equals towards shared goals and success. They must understand that all members of the extended team are on an equal footing, and they will learn from each other if you allow it. This means that the hierarchy within your organizations must remain external to your project teams so that it does not affect how people interact with each other during meetings or discussions. This is so important to get right and what I find is that when people are on so many projects, this is very hard to do. I would love to see us go back to single focused teams, but sadly I think that ship has sailed!
Ok, let’s dive into step 3, which goes deeper into that roles and responsibilities topic.
Step 3. Clarify Agile PMO Roles and Responsibilities
The third step is to clarify roles, responsibilities, and governance for Agile PMO. In an Agile PMO, the focus should be on decision making and not on project reporting. It is important to say project reporting can not be ignored, it just should not be the main focus, as it is not in an Agile project itself. The Agile PMO supports agile teams across the organization by providing a framework of practices, principles, and common language to help them make better decisions.
What does a typical Agile PMO organization structure look like exactly? Good question, have a look.
Are these roles exact for your PMO? No, but directionally, this is a great Agile PMO organizational structure that you could use as a starting point. This is what I have seen and used in my PMOs before and strongly suggest you use as well. Remember, your goal is to create an environment where teams can take full responsibility for their projects without fear of external interference.
Ok, now we have seen the roles used in an Agile. Let’s talk about methodologies and processes that you will need to adapt and adjust for your Agile delivery. Sometimes, yes, you are going to have to redesign some Agile processes or create some new ones if you don’t have them in place today.
Step 4. Re-design processes to enable Agile delivery
As noted, Agile delivery in any organization is difficult and it is going to take some time to adjust what you have today to your new Agile PMO, and that will take time. Before you dive in, sometimes, it is good to sit back and look at some processes you have today, and figure out what needs tweaking and adjusting. Here are some areas to watch out for in for your Agile PMO:
Processes should be designed to support the project delivery.
Processes should be designed to support the team.
Processes should be designed to support the customer.
Processes should be designed to support the business.
Processes should be designed to support the agile delivery methodology.
You might have more processes that need adjusting than listed here, and you might not understand where to start. Just look at what you have today and keep growing them based on these principles in mind. Does that make sense?
Ok, let’s move onto Agile PMO tools. Tools are critical for most PMOs. Let’s dive into the tools conversation now.
Step 5. Change reporting toolset to support Agile delivery
As noted, PMOs need tools and a great Agile PMO looks for tools that will support all processes across the organization. That means tools for delivery, governance, Agile development…etc. When I was at Microsoft, we clearly used Microsoft Agile development tools like Azure DevOps.
Let’s talk about some areas around PMO tools that you should consider:
Get your team trained on the new tools. This is critical because the PMO plays a big role in getting Agile teams trained on Agile tools. Don’t implement tools and be done with it, train your staff.
Work with the team to update project templates and processes for these new tools. Sometimes when you introduce new tools, it means implementing new development and project management process across the organization. So, understand Agile tools often are not installed and forgotten. There is often a ton of work to get setup for your organization.
Start using them immediately in all projects and let the teams work through what works and does not in these tools. For example, if you have a waterfall project that is just beginning, tell your team to use Agile tools instead of waterfall templates and see if it works. If it is just not a fit, then don’t, but try it and see what happens. It is a great learning for everyone and will get people familiar with the tools much quicker. This will allow them to become familiar with these toolsets, and it will give you data to determine what works well and what doesn’t work well.
PMO tools are one of my favorite topics and something I am hugely passionate about for many years now. As PMO leader, i have always felt like I needed to stay on top of the latest PMO tools out there and staying current in this skill set. Ok, let’s go into another favorite topic of mine and that is communications. I wrote a couple of books on project communications and it is a huge passion for me.
Step 6. Develop communications plan to promote and support Agile delivery methodology
If your company hasn’t used Agile before, a significant amount of education will be required to explain the concepts and benefits of using it. I have seen this before. Everyone wants to go Agile, but not many people know what that actually means. These constant communications will be an ongoing activity as new people join the organization or move into roles where they are supporting Agile teams and need to learn all about it.
Use a variety of media to communicate the information on what is an Agile PMO, what Agile means, how do you go about the adoption of Agile practices. Here are some areas you would include in an Agile Communication plan for your PMO:
Presentations
One-to-one discussions
Written material (i.e. documents, briefings, FAQs)
Consider who you need to communicate with and tailor the message to them in terms they will understand and appreciate. This means you may need to develop multiple communications targeting different audiences. For example:
Senior management – focus on how this is good for the business, i.e. increased alignment with customer needs, higher quality products and greater productivity
Middle management – focus on what is in it for them, i.e. improvements in staff engagement and motivation, better quality work output
Project managers – focus on what this means for them, i.e increased autonomy, less bureaucracy
- Team Members – Agile some agile teams might be brand new and so ensuring they have the information they need on the use of Agile on their projects is critical.
It can be quite helpful if you have some concrete examples of successful Agile projects that have been completed using these new approaches so that people can see proof that it works! When communicating about changes make, sure you cover off all the aspects of change management including:
Reason for change
How it will help?
What’s in it for me?
Ok, this is a huge passion for me. I could talk about communications for a while, but let’s move and now and talk about how to measure success in an Agile PMO. An Agile PMO must have points and areas that is can measure so you can focus on continuing move the bar of maturity. Let’s dive in now.
Step 7. Measure success in your Agile PMO
Measuring the success of your PMO is difficult, but critical. What’s the best way to measure success? This will depend on your business goals, your leadership expectations and some key principles that should be present for all measurements including:
Simple and easy to understand
Useful and meaningful
Relevant to the business
- Timely
Visible and accessible by all members of the organization
Reliable, consistent over time, and comparable
Does that make sense? You can go overboard quickly and create all these different ways to measure your PMO, but having too many will drive unacceptable behavior and having too few will not move the maturity bar fast enough. So, there is a balance there ever project management office will not be the same, and therefore your measurements can’t be the same as well.
I hope that helps, and those seven tips get you started in building your world class PMO.
Summary
As we summerize, we’ve covered a lot regarding the steps involved in building an Agile PMO, drawing from my personal experience and 30 year’s experience in the project management space. Here are the seven steps we covered:
Step 1. Understand the need for change in project delivery
Step 2. Change the culture from a controlling and reporting mindset to a coaching and learning mindset
Step 3. Clarify Agile PMO Roles & Responsibilities
Step 4. Re-design processes to enable Agile delivery
Step 5. Change reporting toolset to support Agile delivery
Step 6. Develop communications plan to promote and support Agile delivery methodology
Step 7. Measure success in your Agile PMO
Ultimately, more and more companies want to go “Agile” and it is becoming the methodology of choice for most product development companies. Where are you in your Agile journey? Do you have an Agile PMO already?
What do you think?
If you like this article, you will love this one Agile tools for projects. Or you can read this one on how to build a world class culture in your PMO.
Thanks!
Bill Dow, PMP
Relevant Tools/Resources from us:
Relevant YouTube Videos:
Connect with me on Socials
Want to see all my Products, Courses, Templates….? Check it out here:
https://store.dowpublishingllc.com/mainstore/
Facebook Business Page:
https://www.facebook.com/dowpublishingllc
Facebook Group for support/questions:
https://www.facebook.com/groups/pmoprojectmanagement/
Twitter:
https://twitter.com/dowpublishing
Instagram:
https://www.instagram.com/dowpublishing/
Join my newsletter:
https://forms.aweber.com/form/61/1095355561.htm
YouTube Channel Link:
https://youtube.com/c/Dowpublishingllc

