Sample sprint timeline
The timeline keeps the buyer focused on weekly proof instead of broad transformation theater.
Typical rhythm
Discovery locks scope first. Week one validates the data path. Week two makes the workflow usable. Later weeks harden and integrate.
- Day 0-2 scope lock
- Week 1 prototype
- Week 2 usable pilot
- Weeks 3-6 hardening and rollout
Why the timeline is written
The timeline is not a promise that every idea takes the same number of days. It is a control tool that keeps proof, risks, demos, and next decisions visible.
- Scope lock before build
- Early data/API validation
- Weekly demo rhythm
- Hardening only after proof
- Decision at the end
What changes by sprint type
A document automation sprint spends more time on samples and review queues. An API sprint spends more time on contracts and failure behavior. An LLM workflow spends more time on evaluation and guardrails.
- Document automation: samples and review
- API sprint: contracts and errors
- LLM workflow: evaluation and fallback
- App sprint: UX and user path
Preguntas frecuentes
- Is every sprint 2 weeks?
- No. Two weeks is useful for a first proof. Some scopes need 3-6 weeks when API integration, security, or multiple user roles are involved.
- What must happen before week one?
- Scope, data access, users, decision owner, and acceptance criteria need to be clear enough to start.
- When should hardening start?
- After the core path is proven. Hardening too early can polish the wrong workflow.