A firm is attempting to implement SAFe but maintains a budget that is allocated by project rather than by value stream. How does this conflict with the 'Leading the Change' domain?
Trap 1: It is an acceptable approach as long as projects are delivered on…
Project-based funding is fundamentally incompatible with SAFe's flow-based delivery. Even if projects are delivered on time, the organization continues to suffer from stop-start dynamics, wasted context-switching costs, and a lack of focus on long-term product viability, which ultimately limits the organization's ability to respond to market changes.
Trap 2: It increases visibility into spending for executive stakeholders.
While project budgets provide granular cost tracking, they do not provide visibility into the *value* created by that spend. Lean Portfolio Management offers better visibility by tracking value stream performance metrics. The goal of financial leadership should be value optimization, not just cost tracking for individual project work items.
Trap 3: It ensures that architecture is built for each individual project…
Building architecture independently for each project leads to technical debt and architectural drift, which is exactly what SAFe aims to prevent through the Architectural Runway. Project funding encourages 'quick and dirty' technical solutions to hit project deadlines, which ultimately increases the cost of future development and maintenance.
- A
It is an acceptable approach as long as projects are delivered on time.
Why it fails: Project-based funding is fundamentally incompatible with SAFe's flow-based delivery. Even if projects are delivered on time, the organization continues to suffer from stop-start dynamics, wasted context-switching costs, and a lack of focus on long-term product viability, which ultimately limits the organization's ability to respond to market changes.
- B
It forces teams to focus on output over outcomes.
Project funding incentivizes teams to focus on completing tasks or projects rather than delivering business value or customer outcomes. This leads to the 'project-to-project' trap, where teams are constantly re-formed, wasting time on team development cycles and preventing the formation of stable, high-performing value streams that are essential for continuous improvement.
- C
It increases visibility into spending for executive stakeholders.
Why it fails: While project budgets provide granular cost tracking, they do not provide visibility into the *value* created by that spend. Lean Portfolio Management offers better visibility by tracking value stream performance metrics. The goal of financial leadership should be value optimization, not just cost tracking for individual project work items.
- D
It ensures that architecture is built for each individual project independently.
Why it fails: Building architecture independently for each project leads to technical debt and architectural drift, which is exactly what SAFe aims to prevent through the Architectural Runway. Project funding encourages 'quick and dirty' technical solutions to hit project deadlines, which ultimately increases the cost of future development and maintenance.