12.2 Dynamic Agile Portfolio Planning and Resource Allocation

12.2 Dynamic Agile Portfolio Planning and Resource Allocation

Quick Answer: Agile Portfolio Planning abandons traditional, predictive annual project budgeting in favor of dynamic, rolling, venture-capital-style funding loops guided by Beyond Budgeting principles. Instead of financing temporary, short-lived projects that assemble and disband teams, agile enterprises fund persistent, cross-functional value streams and stable Scrum Teams. Strategic investments are balanced across McKinsey's Three Horizons of Growth: Horizon 1 (protecting and optimizing the mature core cash flows, ~70% investment), Horizon 2 (scaling emerging, high-growth business models, ~20% investment), and Horizon 3 (incubating disruptive, exploratory bets, ~10% investment). Capital and team capacity are dynamically rebalanced across these horizons based on continuous inspection of Evidence-Based Management (EBM) Key Value Areas (CV, UV, T2M, A2I).

---

The Failure of Annual Project Budgeting in Complex Environments

For nearly a century, industrial enterprises have governed capital allocation through the Annual Budgeting Cycle. Every autumn, department heads and project managers construct elaborate 12-to-18-month forecasts detailing the scope, staffing, milestones, and expected return of proposed initiatives. Finance committees review these business cases, approve fixed budgets, and lock them in place for the fiscal year.

In complex software and technology environments, this predictive model introduces profound organizational failure modes:

+-----------------------------------------------------------------------------+
|              The Pathological Cycle of Annual Project Budgeting             |
+-----------------------------------------------------------------------------+
| 1. Speculative Crystal Ball Gazing  : Teams invent 12-month requirements.   |
| 2. Political Sandbagging & Padding  : Costs and timelines are inflated.     |
| 3. Fixed Scope / Fixed Cost Lock-in : Contractual commitments suppress Agility.|
| 4. "Spend It or Lose It" Behavior   : Wasteful spending to protect baselines.|
| 5. Delivering Validated Shelfware   : Teams ship features known to lack value|
|                                       simply because "it was budgeted."     |
+-----------------------------------------------------------------------------+

When unexpected market shifts occur—such as a competitor launching a breakthrough capability, an economic downturn, or changing consumer habits—teams locked into annual budgets cannot pivot. Changing direction requires submitting formal change requests through bureaucratic steering committees, taking months. Consequently, organizations spend millions delivering planned features that empirical evidence has already proven worthless.

The Beyond Budgeting Alternative

To overcome this pathology, agile organizations adopt the philosophy of the Beyond Budgeting Round Table (BBRT). Beyond Budgeting replaces rigid annual central planning with 12 adaptive leadership and governance principles, centering on:

• Rolling Forecasts: Replacing fixed fiscal-year deadlines with continuous, rolling 4-to-6-quarter strategic forecasts updated quarterly or monthly.
• Relative Targets vs. Fixed Contracts: Evaluating success against market benchmarks, customer outcomes, and peer performance rather than negotiated internal budget variances.
• Decentralized Decision-Making: Empowering front-line Product Owners and teams with operational autonomy to allocate resources dynamically within strategic guardrails.
• Event-Driven Funding Tranches: Releasing capital in small, incremental tranches tied to the validation of empirical hypotheses rather than annual lump sums.

---

Funding Stable Value Streams vs. Temporary Projects

A fundamental paradigm shift evaluated on the PSPO II assessment is the transition from Project-Centric Funding to Value-Stream-Centric Funding.

Why Bringing Work to Teams Beats Moving People to Work

When an enterprise manages by temporary projects, it continuously disrupts the social fabric of its teams. According to Bruce Tuckman's model of group development, newly formed teams must navigate Forming, Storming, Norming, and Performing. By the time a temporary project team reaches the "Performing" stage, the project concludes, the team is disbanded, and team members are scattered across new projects, resetting team performance back to zero.

Furthermore, temporary project structures create perverse incentives. Because developers know they will leave the project upon delivery, they are incentivized to bypass automated test suites, ignore refactoring, and introduce technical debt to meet the project deadline. The maintenance and operational fallout is dumped onto a separate, demoralized "run / maintenance" team.

In contrast, funding persistent Value Streams preserves high-performing Scrum Teams. The enterprise funds a dedicated cross-functional team (or Nexus of teams) with a predictable run rate (e.g., $150,000 per Sprint). The Product Owner's accountability is to continuously order the Product Backlog so that every Sprint's investment maximizes the return on that run rate. Work flows smoothly to the stable team, eliminating onboarding delays and instilling deep pride of product craftsmanship.

---

McKinsey's Three Horizons of Growth in Agile Portfolios

To avoid either stagnating into operational obsolescence or recklessly burning capital on unproven dreams, an enterprise must balance its product investments across different temporal and risk dimensions. The most widely adopted model for this balance is McKinsey's Three Horizons of Growth:

+-----------------------------------------------------------------------------+
|                 McKinsey's Three Horizons of Growth in EBM                  |
+-----------------------------------------------------------------------------+
| Horizon 1: Core Business       | Horizon 2: Emerging Growth | Horizon 3: Future Options   |
| - Defend & optimize mature     | - Scale proven bets        | - Seed exploratory probes   |
| - Peak Current Value (CV)      | - Accelerate CV capture    | - High Unrealized Value(UV) |
| - Low Unrealized Value (UV)    | - High Addressable UV      | - Extreme Uncertainty       |
| - Typical Allocation: ~70%     | - Typical Allocation: ~20% | - Typical Allocation: ~10%  |
+-----------------------------------------------------------------------------+

1. Horizon 1: Maintain and Defend the Core (The Cash Engine)

• Profile: Established, mature products that generate the majority of today's operating profits and cash flow. In EBM terms, these assets possess Peak Current Value (CV) and Low Unrealized Value (UV).
• Strategic Goal: Maximize profitability, customer retention, operational stability, and compliance while minimizing operational costs.
• Scrum Team Governance: Scrum Teams in Horizon 1 focus on streamlining user workflows, reducing infrastructure hosting costs, automating compliance, and paying down technical debt that impairs operational margins. Major new feature development is strictly limited.

2. Horizon 2: Scale Emerging Opportunities (The Growth Engines)

• Profile: Fast-growing products or business lines that have achieved validated product-market fit and are rapidly capturing market share. In EBM terms, they exhibit Accelerating Current Value (CV) and Large Addressable Unrealized Value (UV).
• Strategic Goal: Maximize market penetration, expand customer acquisition channels, scale infrastructure, and establish competitive moats before competitors dominate the space.
• Scrum Team Governance: Scrum Teams in Horizon 2 operate with aggressive scaling mandates. Product Owners prioritize non-functional scalability, seamless integration, and market expansion. Funding is substantial, aiming to turn Horizon 2 bets into the next generation's Horizon 1 cash cows.

3. Horizon 3: Transformative Exploratory Bets (The Options Lab)

• Profile: Highly speculative, disruptive initiatives, novel technologies, or unproven business models. In EBM terms, they feature Negligible Current Value (CV), Hypothetically Massive Unrealized Value (UV), and Maximum Uncertainty.
• Strategic Goal: Rapidly test hypotheses, prove or disprove feasibility, and discover viable future business models at minimal cost.
• Scrum Team Governance: Scrum Teams in Horizon 3 operate like early-stage startup founders. Product Owners embody the pure Experimenter stance. Teams are funded with micro-tranches (e.g., budget for 3-5 Sprints). Success is not evaluated by revenue or delivered story points, but by Validated Learning and Customer Satisfaction Gap reduction. If a Horizon 3 hypothesis fails validation, it is immediately abandoned, freeing capital for the next experiment.

[!IMPORTANT] The Classic Enterprise Portfolio Trap: Large enterprises frequently fall into the Horizon 1 Trap: they allocate 95% of their R&D budget to defending legacy Horizon 1 systems, spend 5% on Horizon 2, and starve Horizon 3 entirely. When a technological disruption arrives (e.g., cloud computing, AI, decentralized platforms), the enterprise has no viable options ready to deploy and collapses. Conversely, startups often commit the Horizon 3 Fantasy Trap: chasing multiple unproven ideas without ever scaling a viable Horizon 2 product into a profitable Horizon 1 engine.

---

Dynamic Capacity Rebalancing with Evidence-Based Management (EBM)

How do executives and Product Owners decide when to reallocate teams and funding across products and horizons? In an agile portfolio, this decision is never driven by politics, HiPPO (Highest Paid Person's Opinion), or static annual plans. It is governed empirically using the Four Key Value Areas (KVAs) of EBM:

                    +-----------------------------+
                    |    PORTFOLIO EBM TELEMETRY  |
                    +-----------------------------+
                                   |
        +--------------------------+--------------------------+
        |                          |                          |
        v                          v                          v
+---------------+          +---------------+          +---------------+
| CURRENT VALUE |          |  UNREALIZED   |          |    ABILITY    |
|     (CV)      |          |  VALUE (UV)   |          |  TO INNOVATE  |
| Is the cash   |          | Does the gap  |          |     (A2I)     |
| flow secure?  |          | justify more  |          | Is tech debt  |
| Retention OK? |          |  investment?  |          | choking us?   |
+-------+-------+          +-------+-------+          +-------+-------+
        |                          |                          |
        +--------------------------+--------------------------+
                                   v
                    +-----------------------------+
                    |  DYNAMIC PORTFOLIO ACTION   |
                    | - Shift team capacity       |
                    | - Release next tranche      |
                    | - Pivot / Kill investment   |
                    +-----------------------------+

The EBM Rebalancing Decision Matrix

Venture-Capital Funding Loops: The Sprint as a Funding Tranche

In dynamic agile portfolio management, the executive leadership team acts as an Internal Venture Capital Board. Instead of approving massive multi-million-dollar projects upfront, leadership meets with Product Owners on a regular cadence (e.g., quarterly or at the fulfillment of an Intermediate Goal / Product Goal) to inspect empirical evidence.

• Seed Funding: A Horizon 3 exploration receives a micro-tranche (e.g., 3 Sprints of funding for one Scrum Team) to create a proof-of-concept and test initial user demand.
• Series A (Validation): If the telemetry confirms customer interest and validates leading KVMs, the VC board approves funding for the next Intermediate Goal (e.g., 6 Sprints) to achieve an operational MVP.
• Series B / Scale (Horizon 2 Transition): Once product-market fit is empirically validated, the initiative graduates to Horizon 2, receiving dedicated, ongoing value-stream funding with multiple Scrum Teams.
• Defunding (The Empirical Pivot): If at any point the evidence disproves the hypothesis or shows that the market opportunity is insufficient, funding is halted without stigma. In agile management, killing a disproven idea early is celebrated as capital preservation.