How do we handle procurement lead times in agile delivery?
External lead-time constraintMake long-lead commitments visible early while keeping reversible details flexible. Use evidence to decide what must be ordered now and what can wait for further learning.
What to do now
- Identify long-lead items and decision dates
- Clarify the minimum information needed to commit
- Assess change and cancellation exposure
- Coordinate procurement with delivery learning
When to escalate
Escalate when
A delayed decision makes the required delivery window impossible.
Who decides
The delivery owner and relevant governance authority
Example
A team confirms hardware requirements early while continuing to refine configurable software behavior.
Mistake to avoid
Waiting for a sprint to begin before considering months-long procurement.
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 combine a fixed budget with evolving scope?Constraint-based adaptive delivery
- How do we manage fixed regulatory dates with iterative delivery?Fixed-date adaptive planning
- The procurement process will finish after the required start date. What can we do?Procurement lead-time mismatch
- Reviews take longer than the work itself. How can we plan better?Unplanned approval lead time