An Agile Release Train (ART) has been operating for six months with a traditional annual budgeting model. The Lean Portfolio Management group wants to shift to a more adaptive approach. During a portfolio sync, the LPM team asks which TWO practices are essential to enable faster adaptation to market changes while maintaining financial governance. (Choose two.)
Trap 1: Adopting a fixed annual budget with a 10% contingency reserve for…
A fixed annual budget with a contingency reserve still locks most funding for a year, limiting the ability to reallocate resources quickly. While a reserve provides some flexibility, it is not dynamic and does not support continuous re-evaluation of investments. This approach maintains the rigidity of annual cycles, which is the problem the LPM group wants to solve.
Trap 2: Establishing a quarterly portfolio review where Epics are evaluated…
While periodic reviews are part of LPM, they are not sufficient alone to enable faster adaptation. The key enabler is dynamic funding that can be adjusted continuously, not just at quarterly gates. Stopping Epics is a result of dynamic budgeting, but without flexible funding, the portfolio remains constrained by annual cycles. This option describes a practice but not an essential enabler for adaptation.
Trap 3: Requiring all Epics to be approved by the Portfolio Management…
Centralized approval of all Epics creates bottlenecks and delays, contradicting the goal of faster adaptation. Lean Portfolio Management advocates for decentralized decision-making with guardrails, allowing teams to self-manage within defined boundaries. This option centralizes control, which slows down response to market changes and undermines the agility the LPM group seeks.
- A
Adopting a fixed annual budget with a 10% contingency reserve for unexpected opportunities.
Why it fails: A fixed annual budget with a contingency reserve still locks most funding for a year, limiting the ability to reallocate resources quickly. While a reserve provides some flexibility, it is not dynamic and does not support continuous re-evaluation of investments. This approach maintains the rigidity of annual cycles, which is the problem the LPM group wants to solve.
- B
Moving from project-based funding to value stream funding, where persistent teams receive continuous funding.
Value stream funding provides stable, long-term funding to persistent teams, allowing them to focus on delivering value without the overhead of project initiation and closure. This enables faster response to market changes because teams can pivot within their value stream without seeking new project approvals. It is a core LPM practice that supports adaptability and continuous flow.
- C
Establishing a quarterly portfolio review where Epics are evaluated for continued investment and may be stopped early.
Why it fails: While periodic reviews are part of LPM, they are not sufficient alone to enable faster adaptation. The key enabler is dynamic funding that can be adjusted continuously, not just at quarterly gates. Stopping Epics is a result of dynamic budgeting, but without flexible funding, the portfolio remains constrained by annual cycles. This option describes a practice but not an essential enabler for adaptation.
- D
Implementing dynamic budgeting with guardrails and periodic re-evaluation of funding based on leading indicators.
Dynamic budgeting with guardrails allows funding to be adjusted as market conditions change, rather than being locked for a year. It maintains governance through predefined boundaries and regular reviews, enabling the portfolio to pivot quickly while still ensuring fiscal responsibility. This practice directly supports the Lean Portfolio Management principle of funding value streams, not projects.
- E
Requiring all Epics to be approved by the Portfolio Management office before any development work begins.
Why it fails: Centralized approval of all Epics creates bottlenecks and delays, contradicting the goal of faster adaptation. Lean Portfolio Management advocates for decentralized decision-making with guardrails, allowing teams to self-manage within defined boundaries. This option centralizes control, which slows down response to market changes and undermines the agility the LPM group seeks.