Agile Portfolio Management: Prioritizing Across Teams and Projects
Agile works well at the team level. But how do you prioritize when 5 teams need resources and 15 projects are competing? Agile portfolio management solves this.
The traditional problem
In the traditional portfolio model:
- Projects are approved annually
- Budget is fixed per project
- Teams are allocated by spreadsheet
- Priority changes take months
The world changes in weeks, but the portfolio changes in years.
Agile portfolio principles
1. Fund teams, not projects
Instead of “approving $500K for Project X,” fund the “Checkout Team” and let them deliver value continuously.
2. Re-evaluate priority each cycle
Every quarter (or sprint for smaller teams), re-evaluate:
- What has changed in the market?
- What new data do we have?
- Does the portfolio still make sense?
3. WIP limits at the portfolio level
Just as Kanban limits WIP at the team level, limit active projects in the portfolio:
“We have 8 teams. Maximum of 8 active projects simultaneously.”
4. Outcome metrics, not output metrics
Do not measure “how many features we delivered.” Measure “what business impact we generated.”
Portfolio decision tools
Cost of Delay
How much does it cost not to do something now?
“Not launching PIX checkout is costing R$50K/week in lost sales.”
Compare with other items:
| Item | Cost of Delay/week | Effort (points) | Cost of delay per point |
|---|---|---|---|
| PIX Checkout | R$50K | 21 | R$2,380 |
| iOS App v2 | R$20K | 34 | R$588 |
| Analytics Dashboard | R$5K | 8 | R$625 |
PIX Checkout is clearly the priority: highest return per point invested.
Weighted Shortest Job First (WSJF)
SAFe formula: WSJF = (Business Value + Time Criticality + Risk Reduction) / Effort
Items with higher WSJF are prioritized.
Risk vs. Return Matrix
| High return | Low return | |
|---|---|---|
| Low risk | DO NOW | Fill in if spare capacity |
| High risk | INVEST CAUTIOUSLY | AVOID |
Team allocation
Traditional approach (wrong)
Distribute people across projects: “Joao 50% on project A, 50% on project B.”
Results in context switching and a 20-40% loss in productivity.
Agile approach (right)
Teams are allocated to one product or initiative. If priority changes, the whole team shifts focus.
When shared allocation is necessary
- Platform teams serve multiple squads
- Specialists (security, data) share knowledge
- Operational support serving multiple products
In these cases, limit to 1-2 allocations per person, not 4-5.
Quarterly portfolio review
Recommended format:
- Results review — what impact did we generate last quarter?
- Market data — what changed?
- Re-prioritization — with the new data, what is most important?
- Allocation — are teams on the right projects?
- Decisions — start, stop, or continue initiatives
Conclusion
Agile portfolio is about funding delivery capacity, not approving static projects. Re-evaluate frequently, use data to prioritize, and limit work in progress at the highest level of the organization.