How do we combine a fixed budget with evolving scope?
Constraint-based adaptive deliveryKeep the funding boundary explicit and prioritize usable outcomes within it. Make it clear which scope is essential and which remains an option, then review value and forecast regularly.
What to do now
- Confirm the fixed funding limit
- Identify indispensable outcomes
- Order remaining options by value and risk
- Stop or change direction before funds are exhausted
When to escalate
Escalate when
Essential outcomes cannot be delivered within the authorized funding.
Who decides
The delivery owner and relevant governance authority
Example
A team delivers core approval workflows first and considers optional reporting only after confirming remaining capacity.
Mistake to avoid
Promising fixed budget, fixed date, and unlimited evolving scope.
Prevent a repeat
Check whether governance decisions use real delivery evidence rather than forcing incompatible reporting rituals.
Suggested ApprovedFlow setup
- Projects
- Tasks
- Documents
- Approvals
Keep decision milestones and iterative task work connected, with explicit evidence required at each approved gate. See the platform
Related cases
- How do we manage fixed regulatory dates with iterative delivery?Fixed-date adaptive planning
- How do we handle procurement lead times in agile delivery?External lead-time constraint
- How can we manage scope when users discover needs during delivery?Evolving requirements
- A sponsor approves scope but not the extra budget. What should we do?Unfunded change approval