Study guide
9.4 Agile Budgeting, Contracts & Governance
Professional Scrum Master II PSM II
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview, Empiricism & Advanced Framework Mechanics
1.1 PSM II Assessment Architecture, Scoring, and Advanced Mindset 1.2 Empiricism in Complex Environments 1.3 Living the Scrum Values Under Pressure
2 Chapter 2: Scrum Accountabilities & Team Self-Management
2.1 The Three Accountabilities in Deep Context 2.2 Fostering Self-Managing & Cross-Functional Teams 2.3 Anti-Patterns in Accountabilities
3 Chapter 3: The 8 Stances of the Scrum Master
3.1 Core Enabling Stances: Servant Leader & Manager 3.2 Developing Stances: Teacher, Mentor & Coach 3.3 Delivery Stances: Facilitator & Impediment Remover 3.4 Transformational Stance: Change Agent & Ineffective Stances
4 Chapter 4: Advanced Team Dynamics & Psychological Safety
4.1 Building Psychological Safety & Trust 4.2 Navigating Team Development & Dysfunctions 4.3 Conflict Resolution & Liberating Structures
5 Chapter 5: Managing Products with Agility & Product Owner Coaching
5.1 Coaching the Product Owner on Vision & Product Goal 5.2 Product Backlog Health, Ordering & Splitting 5.3 Stakeholder Engagement & Collaboration Without Feature Factories
6 Chapter 6: Evidence-Based Management (EBM) & Agility Metrics
6.1 EBM Framework Architecture & Strategic Loop 6.2 Market Value: Current Value (CV) & Unrealized Value (UV) 6.3 Organizational Capability: Time-to-Market (T2M) & Ability to Innovate (A2I) 6.4 Designing Agility Metrics vs. Vanity Metrics
7 Chapter 7: Artifacts, Commitments & Definition of Done
7.1 The Three Commitments & Empirical Artifact Transparency 7.2 Crafting and Evolving the Definition of Done 7.3 Definition of Done in Regulated & Complex Environments 7.4 Managing Technical Risk, Technical Debt & Engineering Excellence
8 Chapter 8: Advanced Events & Facilitation in Practice
8.1 Advanced Sprint Planning & Meaningful Sprint Goals 8.2 The Daily Scrum & Sprint Review as Empirical Feedback Loops 8.3 Actionable Sprint Retrospectives & Continuous Improvement
9 Chapter 9: Scaling Scrum & Organizational Agility
9.1 Scaling Fundamentals & Nexus Framework 9.2 Nexus Events & Multi-Team Dependency Management 9.3 Organizational Design, Culture & Removing Impediments Beyond the Team 9.4 Agile Budgeting, Contracts & Governance
9.4 Agile Budgeting, Contracts & Governance
Key Takeaways Explain This Topic AI
Traditional annual budgeting locks enterprises into obsolete 12-month assumptions and incentivizes wasteful 'spend-it-or-lose-it' budget consumption.
Dynamic agile funding funds persistent, cross-functional teams rather than transient projects, releasing capital in value-driven tranches evaluated through EBM metrics.
Traditional fixed-price, fixed-scope contracts create adversarial vendor relationships, change-order disputes, and quality compromises under complex uncertainty.
Modern agile contracting models—such as Money for Nothing, Changes for Free, and Capped Time and Materials—align financial incentives around shared risk and empirical value.
Empirical governance replaces document stage gates with frequent inspection of Done Increments and evidence, changing traditional budget and procurement controls incrementally rather than all at once.
Last updated: October 2026
Agile Budgeting, Contracts & Governance
Note
Agility cannot survive in an organization whose financial and legal systems remain locked in 19th-century industrial paradigms. True organizational agility requires replacing rigid annual capital allocation with dynamic capacity funding, collaborative contracting, and living empirical governance.
The Failure of Traditional Annual Budgeting
Traditional enterprise budgeting operates on a rigid 12-to-18-month cycle. In the autumn of each year, business units write speculative 50-page business cases forecasting costs, revenues, and resource requirements for projects that will not even begin for another six months. Finance departments review these business cases, lock in fixed budgets, and allocate funds to temporary projects.
This predictive budgeting model collapses under the conditions of complex knowledge work, generating systemic dysfunctions:
The "Spend-It-or-Lose-It" Pathology: Departmental managers know that if they do not spend 100% of their allocated annual budget, finance will permanently reduce their baseline allocation in the next fiscal year. Consequently, in the fourth quarter, managers rush to authorize low-value, wasteful expenditures simply to exhaust remaining funds.
Funding Temporary Projects Instead of Stable Teams: Traditional accounting funds "projects" with defined start and end dates. When a project begins, a temporary team is assembled from various departments. When the project ends, the team is disbanded, scattering institutional knowledge, breaking psychological safety, and resetting the team development curve to zero.
Lock-In to Obsolete Hypotheses: Market realities, competitor moves, and customer preferences change rapidly. An annual budget locks capital into initiatives conceived up to 18 months earlier, making it politically and administratively difficult to pivot capital toward emerging opportunities.
Disincentivizing Early Completion: If an agile team delivers 90% of the desired business value in 3 months instead of the planned 12 months, traditional financial systems penalize them by canceling the remaining project budget and reallocating resources, rather than rewarding early value realization.
Dynamic and Incremental Funding: Beyond Budgeting in Practice
To overcome these failures, agile enterprises adopt principles from the Beyond Budgeting movement and modern venture capital:
1. Capacity Funding for Persistent Teams
Instead of funding temporary projects, agile organizations fund dedicated, persistent, cross-functional teams (or value streams). The cost of a stable Scrum Team is highly predictable:
Team Run Rate = Headcount × Blended Monthly Labor Cost + Fixed Tooling/Infrastructure Cost \text{Team Run Rate} = \text{Headcount} \times \text{Blended Monthly Labor Cost} + \text{Fixed Tooling/Infrastructure Cost} Team Run Rate = Headcount × Blended Monthly Labor Cost + Fixed Tooling/Infrastructure Cost
Because team capacity and cost are stable, the enterprise stops estimating project costs through speculative labor hour calculations. Instead, the organization prioritizes a single, ordered backlog of strategic initiatives and brings the highest-value work to the persistent team.
2. Venture Capital-Style (Tranche-Based) Incremental Funding
Rather than granting a multi-million-dollar annual budget upfront based on a speculative business case, leadership acts like an internal venture capital firm:
Seed Funding: An initiative receives a small initial tranche of funding (e.g., funding 3 Sprints) to build a prototype, test customer desirability, and validate core architectural assumptions.
Empirical Governance Reviews: At the conclusion of each funding tranche, leadership, the Product Owner, and stakeholders inspect the working Increment and review Evidence-Based Management (EBM) metrics:
Current Value (CV): Are active users adopting the feature? Is customer satisfaction improving?
Unrealized Value (UV): What remaining market potential justifies further investment?
Time-to-Market (T2M): How rapidly are new releases reaching production?
Ability to Innovate (A2I): What proportion of budget is spent on new capabilities versus defect maintenance?
Pivot, Persevere, or Stop: If the initiative demonstrates strong value metrics, the next funding tranche is authorized. If the hypothesis fails, leadership terminates the initiative early with minimal financial loss, redirecting surplus capital to high-potential opportunities.
Agile Contracting Models: Aligning Incentives Under Uncertainty
Procurement departments often attempt to force agile software development into traditional Fixed-Price / Fixed-Scope contracts. This creates an adversarial relationship between buyer and vendor:
The buyer writes rigid, exhaustive specifications to lock down scope.
The vendor inflates estimates by 50% to 100% to buffer against unforeseen risks.
During development, when requirements inevitably change, the relationship devolves into bitter "Change Order Wars." The vendor demands exorbitant fees for minor scope modifications, and quality is compromised to protect profit margins.
Agile contracts replace adversarial tension with shared risk, transparency, and empirical alignment:
Contract Model Mechanics Benefit to Client Benefit to Vendor
Time & Materials with Target Cost Collaborative baseline target cost and date. Cost overruns or underruns are shared (e.g., 50/50 split). Protection against runaway costs; shares savings if delivered under target. Guaranteed baseline costs covered; financial bonus for efficient delivery.
Capped Time & Materials Vendor bills hourly/daily rates up to a guaranteed maximum cost ceiling; scope is managed flexibly. Absolute cost ceiling; client can stop work early and pocket savings. Eliminates bidding wars; provides stable, transparent revenue stream.
Money for Nothing & Changes for Free Client swaps unstarted items of equal effort for free; client can terminate contract early for a partial fee. Free requirement adaptation; ability to exit early when sufficient value is achieved. Retains profit margin without spending labor on low-value scope; builds client trust.
Graduated Fixed Price Tiered hourly billing rates based on delivery timing (early delivery earns higher rates; delays reduce rates). Incentivizes rapid delivery and high throughput. Financial upside for superior performance and high technical excellence.
Deep Dive: "Money for Nothing and Changes for Free"
Formulated by Dr. Jeff Sutherland (co-creator of Scrum), this contracting model provides an ideal balance of flexibility and commercial safety:
Changes for Free:
At the beginning of any Sprint Planning session, the client can introduce new Product Backlog items or modify existing ones at zero additional charge .
The Ground Rule: For every new item added, the client must remove an unstarted item of equivalent estimated effort. The overall scope volume remains constant, accommodating emergent learning without contract amendments.
Money for Nothing:
In software, the final 20% of planned features often represent low-value edge cases that deliver negligible return on investment.
If the client determines that the core business value has been fully achieved early (e.g., after Sprint 6 of a planned 10-Sprint contract), the client has the contractual right to terminate the contract early .
The Financial Settlement: The client pays a negotiated early-termination fee—typically 20% of the remaining unbilled contract balance—and walks away with 100% of the working, tested software.
The Win-Win: The client saves 80% of remaining expenditures ($80,000 saved on a remaining $100,000 balance). The vendor immediately banks $20,000 in pure profit margin without spending any labor or overhead, freeing their engineering staff to take on new billing client engagements.
Governance Without Stage Gates
Funding and contracts are two of the three enterprise interfaces where traditional structures collide with Scrum; the third is governance. Empirical governance replaces document-based stage gates with frequent inspection of Done Increments:
Investment decisions at the Sprint Review cadence. Leaders inspect working software and evidence (EBM measures) at the end of each funding tranche and decide whether to persevere, pivot, or stop.
Compliance inside the Definition of Done. Regulatory, security, and audit requirements become part of the Definition of Done and are automated in the delivery pipeline, so every Increment carries its own evidence. Section 7.3 covers this in depth for regulated environments.
Evolve, don't abolish. Most organizations cannot drop annual budgeting or procurement rules in one step. The Scrum Master makes the cost of each traditional control transparent and helps leaders replace it incrementally—for example, keeping the annual budget but releasing it in quarterly tranches tied to inspected results.