Trial lock

This Research is for Members Only

Not a member? Unlock a free sample of our research now!

Already a member?

Sign in now

Project Portfolio Management icon

Manage an Agile Portfolio

Improve project oversight without imposing old-school command-and-control.

Unlock a Free Sample

View Storyboard

Solution Set Storyboard Thumbnail

Your Challenge

  • Agile renders traditional project portfolio metrics useless. The main steering lever used to be end dates; with Agile, the main lever is scope.
  • Executives and business stakeholders still expect traditional commitments and deadlines, not “sprints” and “velocity.”
  • Project portfolio management (PPM) could barely stay current with traditional projects on a quarterly basis - the challenge is even greater with Agile projects that change every two weeks.
  • Further complicating things, Agile will not completely replace traditional or waterfall projects. Most portfolios include a mix of projects.

Our Advice

Critical Insight

  • The traditional portfolio has defined success based on the quality of prediction: who will deliver what, when, and at what cost? The long-term value of the work was less important than the accuracy of those predications.
  • Project agility should help drive business agility, assuming that the portfolio is itself Agile.
  • Portfolio management and project management are separate concerns. The portfolio management methodology needs to interface with projects (and vice versa) but they have distinct goals, terminology, and methodology.

Impact and Result

  • Increase frequency of current reporting to at least biweekly using an Agile Portfolio Dashboard.
  • Tailor the process to your organization with either an “engaged” or “abstracted” approach. The engaged approach requires stakeholders to frequently interact with project teams to manage and refine scope. The abstracted approach is more traditional, with projects steered largely through high-level budgeting and resource allocation.

Research & Tools

1. Make the case for managing an Agile portfolio

Determine the value of building an Agile portfolio and make a go/no-go decision.

2. Assess the current state of the project portfolio

Assess the value of an Agile portfolio and prepare to develop one suited to your organization.

3. Establish a strategy and SOP for Agile portfolio management

Engage stakeholders and teams to define Agile portfolio processes that suit their needs and preferences.

4. Build and implement an Agile portfolio dashboard

Develop processes and tools to facilitate visibility required for effective, agile decision making.

5. Manage and optimize the Agile project portfolio

Use and continuously improve the Agile portfolio to realize greater value and make more strategically effective decisions.

Guided Implementations

This guided implementation is a five call advisory process.

Call #1 - Scoping call to determine timing and personnel

Confirm this is the best blueprint for your project. Set a time frame and other expectations for the guided implementation.

Call #2 - Assess current state

Define your current state based on PPM and Agile maturity. Assess the value of an Agile portfolio and prepare to develop one suited to your organization.

Call #3 - Establish a strategy and SOP for Agile PPM

Define key inputs, outputs, and metrics such as sprint value. Develop terms of engagement between the PMO, stakeholders, and project teams.

Call #4 - Build an Agile portfolio dashboard

Determine the “who, what, where, when, and how” of reporting project and portfolio status to various stakeholders.

Call #5 - Optimize the Agile project portfolio

Measure and build on success in the form of frequency of current reporting, average sprint value, and reclaimed capacity.

Onsite Workshop

Discuss This Workshop

Book Your Workshop

Onsite workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn't enough, we offer low-cost onsite delivery of our project workshops. We take you through every phase of your project and ensure that you have a roadmap in place to complete your project successfully.

Module 1: Assess the Current State of the Project Portfolio

The Purpose

  • Customize the Agile Portfolio development process to your organization.
  • Align different types of projects within a unified portfolio.
  • Estimate the value to help make the case for developing an Agile Portfolio.
  • Define the best roles and engagement strategies for individual stakeholders as you transition to an Agile Portfolio. 

Key Benefits Achieved

  • Ensure sustainable adoption and success of the Agile Portfolio.
  • Bolster the business case for building an Agile Portfolio.
  • Increase stakeholder and team buy-in.




Conduct an audit of project methodologies in use


Conduct an Agile Portfolio Profile Assessment by comparing Agile, Traditional, and Unstructured projects

  • Map of the composition of the project portfolio

Review the portfolio profile to begin formulating a target level of project heterogeneity and stakeholder engagement


Identify gaps and levers for aligning different types of projects within a unified portfolio

  • Analysis of project agility and PPM formality

Estimate the potential value of the Agile Portfolio


Create a stakeholder map

  • A stakeholder map

Document the current decision-making paradigm

Module 2: Establish a Strategy and SOP for Agile Portfolio Management

The Purpose

  • Improve stakeholder satisfaction by defining and reconciling stakeholder needs, preferences, and expectations.
  • Maximize stakeholder buy-in and alignment around unified portfolio metrics and processes. 

Key Benefits Achieved

  • Improved stakeholder satisfaction.
  • Maximized stakeholder buy-in and alignment.




Define the purpose and goals of the Agile Portfolio based on drivers of business & portfolio agility


Review & discuss stakeholder requirements and from the Agile Portfolio

  • Agile Portfolio Stakeholder Survey

Reconcile stakeholder requirements with current state to prioritize gaps & levers


Develop a universal scorecard


Define inputs, outputs, and other supporting processes


Formalize and agree on standard terms and definitions of your portfolio methodology


Formalize key roles and responsibilities


Identify potential sources of resistance and support

  • Agile Portfolio Communications Plan Template

Module 3: Build and Implement an Agile Portfolio Dashboard

The Purpose

  • Objectively and transparently approve, reject, and prioritize projects.
  • Prioritize work to start and stop on a sprint-by-sprint basis.
  • Maintain high frequency of accurate reporting.
  • Assess and report the realization of project benefits.

Key Benefits Achieved

  • Improve timeliness and accuracy of project portfolio reporting.
  • Make better, faster decisions about when to start and stop work on different projects.
  • Increase stakeholder satisfaction.




Review the value scorecard and confirm stakeholder approval


Test the scorecard by evaluating a list of proposed projects


Review project value before deciding whether to approve or reject them for the project backlog


Use the sprint value and need scores to prioritize work to start/stop in individual sprints


Decide what to start/stop for an individual sprint based on results of the Sprint Prioritization


Develop a management dashboard for reporting on the organization’s capacity for more projects

  • Sprint Prioritization Dashboard
  • Project Portfolio Capacity Dashboard

Develop a benefits dashboard for monitoring the long-term attainment of value

  • Project Value Dashboard
  • Agile Portfolio Benefits Dashboard

Module 4: Manage and Optimize the Agile Project Portfolio

The Purpose

  • Measure success of the Agile Portfolio.
  • Identify opportunities to improve Agile Portfolio processes and dashboard.

Key Benefits Achieved

  • Increase average sprint value.
  • Continue to reclaim project capacity.




Validate the Agile Portfolio Strategy and SOP using scenarios based on active or planned projects in the portfolio


Review measured value estimates from Step 1 to complete to the Agile Portfolio Scorecard

  • Agile Portfolio Scorecard

Search Code: 74687
Published: April 21, 2014
Last Revised: October 3, 2014