Info-Tech members who are moving to Agile are frequently unsure what the role of project managers (PMs) and the project management office (PMO) is in an Agile environment. Any organization that is used to following traditional (Waterfall) project management practices will need to make some sideways adjustments in support of Agile or risk losing the benefits it would otherwise bring.
Note: This is a companion piece to Explaining Agile to Management and Your PMO (How to Foster Their Buy-In and Support) – consider reading it first for a better understanding of Agile benefits and how it differs from Waterfall. For the purposes of this tech brief, we will limit ourselves to organizations that are large enough to have an established and traditional project management process in place (typically Waterfall or Phase-gate) and want to understand the altered role PMs and PMOs play on an Agile project.
Let’s begin by saying that Waterfall and Agile are not simply two sides of the same coin. They are very different approaches, and so they must be project managed very differently. To do otherwise is folly. As an example, any organization that imposes a rigid Waterfall project gating process on an Agile project risks erasing any benefits the organization may have realized from Agile, up to and including risking failure of the project. Your organization’s project management approach will need to adjust in a way that is supportive of Agile’s strengths if you hope to succeed with it.
These required adjustments can be most simply described by comparing/contrasting the high-level responsibilities of PMs and PMOs under Waterfall and Agile as shown below:
What follows are generalized explanations and recommendations about how the role of PMs and PMOs should be altered to support an Agile environment (it is not presented as an exhaustive or complete explanation of the changes required). Organizations are encouraged to adopt and adapt these changes to their individual circumstances. For more specific guidance about how to apply this to your organization, arrange for an Analyst Call with an Info-Tech representative.
Strictly speaking, there is no defined role for a PM in Agile projects. Agile methodologies (like Scrum) rely on self-organizing cross-functional teams who are empowered by the organization to make key project decisions and to problem solve as they go. Scrum teams consist of a Product Owner, Scrum Master, and Development Team, and they deliver projects without following a detailed project plan like those commonly used in Waterfall projects. Together, the Product Owner and Scrum Master roles fulfill a majority of the functions that would normally be done by a PM. However, organizations can and should still assign a project manager to Agile projects, albeit with modified responsibilities.
In a Waterfall project, the PM plays a key leadership role in delivery by orchestrating the activities of all project team members through a detailed project plan. On an Agile project, the PM’s role is diminished but is still vital to the overall success of the project. Instead of providing leadership, a PM on an Agile project plays a role in supporting and monitoring the project and acts as an escalation point to the PMO and senior management (as a side note, don’t make the mistake of substituting either the Product Owner or Scrum Master with a project manager – their skills and responsibilities differ significantly).
Here is a little more detail about the PM role in Agile:
One of the primary responsibilities of your PMO is to provide governance and oversight of project activities. This is typically accomplished by use of a traditional (think Waterfall or Phase-gate) project gating process (PGP). But it is important to know that a traditional PGP will not work for an Agile project because it relies on a rigid linear approach that is at odds with the Agile approach. In fact, forcing an Agile project to follow a traditional PGP will, with almost absolute certainty, cause it to fail.
To avoid this risk, an organization’s PGP must be repurposed for Agile projects. Thankfully, this can be done without changing the PMO’s primary governance and oversight role. For Agile projects, this can be accomplished by altering your PGP to focus on verifying that the project is following good Agile practices instead of good Waterfall practices.
Here is a little more detail about how to adjust the PMO/PGP role in Agile:
Making these PM/PMO role adjustments will help to raise your organization’s probability of success with Agile adoption while ensuring effective and appropriate project oversight takes place (which is the primary reason for having PMs and PMOs after all!). Once again, for more specific guidance about how to apply this approach to your organization, arrange for an Analyst Call with an Info-Tech representative.
COVID-19 has forced software companies and their suppliers to refocus efforts around prioritizing systems and workflows that are nearly 100% digital in nature. As a result, Info-Tech has observed the quick emergence of six market themes that are highly relevant post COVID-19. This note series will profile key vendors and how they fit into the post-COVID-19 world.
COVID-19 has forced software companies and their suppliers to refocus efforts around prioritizing systems and workflows that are nearly 100% digital in nature. As a result, Info-Tech has observed the quick emergence of six market themes that are highly relevant after COVID-19. This note series will profile key vendors and how they fit into the post-COVID-19 world.
IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.
Is it true that everything that can go wrong will go wrong? Don’t bet on it to not.
While Microsoft is not a prominent player in the RPA space now with its Power Automate solution, compared to Blue Prism, UiPath, and Automate Anywhere, its latest acquisition of Softomotive, maker of WinAutomation, demonstrates Microsoft’s dedication to mature and expand its RPA offerings.
Test data management tools offer you the ability to provision, mask, and govern the access and use of your test data, alleviating these manual, laborious and error-prone tasks from your testing, operations, and DBA teams.
When trying to implement Agile as a defined process, Scrum turned BAs or other roles into order takers with the title “product owner.” This undermines the entire value proposition of product management.
Agile systems delivery (implemented through Scrum) is quickly becoming an accepted norm in IT. But using Scrum successfully in an organization requires a deep understanding of how it works and why. For example, many of our members don’t understand the importance of selecting a Product Owner who has three ears.
Reeling from the pandemic response executed by governments all the over world, companies are accelerating their implementation of low-cost automation. That bodes well for UiPath – a leader in RPA aiming to go public this year.