agile-portfolio-management

Agile Portfolio Management In A Nutshell

Agile Portfolio Management (AgilePfM) is a high-level change management framework that ensures that business change strategy remains under continuous review. AgilePfM reviews changes in a business environment and then coordinates similar changes within the business itself.

Understanding Agile Portfolio Management

Agile Business Change philosophy states that “best value emerges when business changes are aligned to clear business goals, deliver frequently and are powered by the effective leadership of fully engaged, autonomously collaborative teams”.

To facilitate this alignment, AgilePfM reviews changes in a business environment and then coordinates similar changes within the business itself. It also ensures that change is articulated through the setting of strategic goals. These goals then provide a foundation for approving, prioritizing, and governing subsequent work.

However, organizations may nevertheless struggle with change at the portfolio level. More traditional practices such as annual budgeting and inflexible strategy definition can stifle the effectiveness of agile delivery. In the most severe instances, this rigidity can negate the benefits of agile principles entirely.

To address this conflict, AgilePfM encourages agility at the project and program level while allowing organizations to maximize value from portfolio investments.

The four-step portfolio process of AgilePfM

  1. Confirm portfolio drivers. What is driving high-level outcomes? How do they relate to vision, goals, or objectives? It’s also important to consider the role of culture and leadership.
  2. Confirm portfolio foundations. Here, the business must establish strategic alignment criteria using certain key performance indicators. These KPIs might include profit, volume, or customer satisfaction metrics. 
  3. Deliver change. This may include agile budgeting in combination with continuous idea management and portfolio prioritization. Whatever the change initiative, it must be coordinated and planned for appropriately. In other words, the change must deliver incremental value to the organization as quickly as possible.
  4. Keep it current. AgilePfM encourages the periodic reassessment of strategy and portfolio alignment by measuring ROI for the KPIs established in the previous step. ROI should also be calculated after high-impact events have occurred.

Agile governance and portfolio-specific rules

In managing change at the portfolio level, organizations must adhere to a suite of general and more specific rules.

Agile governance rules

  • Value must drive priority (do the right things).
  • Quality should never be compromised (do the things right).
  • Decide with initiatives. Do not manage them.
  • Give clear and considered direction.
  • Stay informed.

Agile portfolio rules

  • If it is in the portfolio, then it must be in the strategy.
  • If there is no strategy, stop! Do not proceed with AgilePfM without one.
  • Constantly review the portfolio and adjust when required. Do not perform one-off exercises.
  • Concentrate on prioritizing, blending, and balancing with a near-term horizon of no more than a few months ahead.

Key takeaways

  • Agile Portfolio Management is a high-level change management framework that favors continuous change strategy review.
  • Agile Portfolio Management allows businesses to incorporate agile practices at the traditionally rigid portfolio level. Processes that may become less rigid include budgetary planning and strategy definition.
  • Agile Portfolio Management is governed by general agile governance rules and more specific rules that guide agile practices at the portfolio level. In the latter set of rules, business strategies must be holistic and continually reviewed no more than a few months ahead.

Related Business Concepts

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.
test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.
feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.
extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.
dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.
timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.
rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.
mvc-framework
The MVC framework is a predictable software design pattern separated into three main components and suitable for many programming languages. The goal of the MVC framework is to help structure the code-base and separate application concerns into three components: View, Model, and Controller.
agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.
devsecops
DevSecOps is a set of disciplines combining development, security, and operations. It is a philosophy that helps software development businesses deliver innovative products quickly without sacrificing security. This allows potential security issues to be identified during the development process – and not after the product has been released in line with the emergence of continuous software development practices.

Read Next: Business AnalysisCompetitor Analysis, Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Main Free Guides:

Scroll to Top
FourWeekMBA
[class^="wpforms-"]
[class^="wpforms-"]