As you adopt Agile principles it is important to understand the critical difference between Agile Project Management and Agile Portfolio Management—and that you can have one without the other.
Agile methodologies have become a compelling trend with a host of proponents touting their benefits of speed, innovation, and customer satisfaction. There is no doubt that Agile can indeed deliver such benefits, and many organizations are now looking at how they can apply Agile practices to help them tackle the new challenges created by the global pandemic and to realize those benefits. But not all projects are conducive to Agile, and it is important to select the methodology best suited for the project at hand. What is more important in times such as these is to adopt Agile Portfolio Management to promote better organizational agility and to ensure your portfolio of projects is aligned to the goals of the organization.
Agile Portfolio Management means that your portfolio is adaptable, well-maintained, and aligned. It ensures you have resources to complete the work you take on, and you are constantly re-evaluating which initiatives your dollars are going toward. Furthermore, it ensures that you have the ability to make the changes required to stay aligned with the goals of the business—even as those change.
Agile Project Management vs. Agile Portfolio Management
While companies are motivated to make the shift to an Agile model, it is important to first understand what that means for your unique organization and which areas will undergo the change. It is a common misconception that making projects agile will result in an agile portfolio, but it doesn’t quite work that way. A quick look at some areas where they differ:
|Agile Project Management||Agile Portfolio Management|
|Delivers projects better and faster||Delivers the best projects in a streamlined manner|
|Focuses on the right people for the right projects||Focuses on the right TEAMS and provides resource agility|
|Reduces risk and prioritizes stakeholder satisfaction||Ensures a properly prioritized project portfolio across all project types|
Agile Portfolio Management for Diverse Project Approaches
Once you understand Agile Portfolio Management and the implications at a high level, the next step is adopting this model. One of the key reasons that many organizations hesitate to implement Agile is the misperception that they must jump in with both feet and apply Agile practices across all areas of project and portfolio management—and that simply isn’t true. There are more options than a wholesale, instantaneous change, and in fact, you will be more effective with a phased approach across diverse projects.
If your organization can make a sweeping change to embrace Agile across all areas of project and portfolio management, excellent! For those who have concerns, rest assured—you can selectively apply your use of Agile and still see the benefits. Applying the Agile methodology to project management is not necessarily right for all businesses, because not all projects or industries can operate on an iterative, rapidly changing trajectory. Agile Portfolio Management, however, is something that most businesses can successfully implement, particularly in light of the current situation with the COVID-19 pandemic.
The ability for a business to pivot and quickly realign its investments based on timely, accurate data is more critical than it has ever been before. Across the enterprise, organizations are being forced to make drastic changes to their operations to protect their longevity. In the realm of portfolio management, this means reprioritizing project selection to emphasize those that strengthen the business and help it weather the challenges ahead. It also means empowering the Project Management Office (PMO) to say no to projects and back that decision with hard data.
In times of plenty, IT leadership doesn’t worry so much, and they’re willing to approve many, if not most, projects. However, effective portfolio management becomes especially relevant when the PMO has to start saying no. As the available resources and investment dollars shrink, the PMO needs hard data around capacity, value, and strategic alignment in order to prioritize a portfolio of projects and ultimately say no to some initiatives. As such, Agile Portfolio Management is the optimal methodology for maintaining a strong portfolio that delivers the greatest business value. Here are three key reasons why:
- Agile Portfolio Management centralizes all projects regardless of methodology. This means that even projects managed with more traditional methodologie, such as waterfall, can reside in an Agile portfolio. Centralization provides the PMO with the power to manage the entire spectrum of work from a single source and apply the correct methodology to each project
- It provides high visibility, data, and reporting. The PMO can see who is doing what on which project in real time, anytime. They can see the resource allocation to each project, the time spent, the progress, and the results and use that information to make sound decisions about present and future project selection. Again, it’s worth noting that Agile Portfolio Management does not mean all the projects managed under an Agile portfolio are Agile themselves—just that the portfolio is.
- Agile Portfolio Management supports the creation of a portfolio backlog. Because the PMO can centralize projects and see progress and results in real time, they are able to begin making strategic decisions about future projects and creating an effective pipeline of vetted work that is ready to go as soon as space opens up.
To put this more succinctly, Agile Portfolio Management makes it easier for the PMO and the stakeholders to closely monitor every aspect of the projects within that portfolio and use the information gained to make strategic decisions that support the longevity and security of the organization.
Overcoming Roadblocks to Agile Portfolio Management
Even as you take steps to transition to an Agile Portfolio Management model, there will be challenges you encounter. Here are a few that you should anticipate:
- Perceived Lack of Visibility: Many think Agile teams work in an organized chaos fashion and at the end deliver something of value, but the nitty gritty is hard to understand. With Agile Portfolio Management it is quite the opposite. Visibility is a key component, and understanding the true status of projects—Agile or otherwise—is inherent in this type of management structure.
- Cultural Biases: Some people just don’t work well in unstructured environments and can’t adapt. Again, this perceived roadblock is contradictory to actual Agile Portfolio Management working environments. Planning becomes even more important (though also more frequent), and work is not “chaotic” but “iterative” and pieced out into more manageable pieces.
- Can’t Mix Methodologies: While it is true it can be difficult to manage projects of different methodologies within the same portfolio, it is also incredibly important to do so. Having a complete picture of all project work and resources available across all project types is the only way to get a real understanding of capacity and demand. This critical element is arguably the determining factor of success for organizational agility.
- Unpredictable: Hearing this almost makes me laugh. Agile has really gotten a bad rap for delivering exploratory or innovative projects that are unpredictable in nature. That doesn’t mean managing using Agile will make the project unpredictable. Bringing Agile to the portfolio level actually makes the portfolio more predictable, because you know you’ll be measured against business value and investing in projects that are the best for the business rather than those that are most reliable.
- Replacing PMOs: This is another misperception of Agile that is wildly off base. Wide adoption of Agile is making the role of the PMO more important as investment in project management practices yields better project results and requires increased oversight.
Bringing It All Together
As you adopt Agile principles it is important to understand the critical difference between Agile Project Management and Agile Portfolio Management—and that you can have one without the other. Not all projects need to— or even should be—managed in an agile fashion to be able to achieve Agile Portfolio Management. Note again the key point that Agile can provide great visibility at the portfolio management level, despite how individual projects are managed. This top-down approach is what delivers so many benefits, such as funding and resource management, to Agile Portfolio Management. Best of all, this can be accomplished in a phased and methodical manner, delivering both short-term value and longer-term organizational transformation to withstand change.