Stage 03
Agile Development Process
Weekly demos, visible progress, CI gates that hold.
Approach stage 03: Agile Development ProcessWhy it matters
Why this stage earns its keep.
no big-bang surprises
working software every week
cheap course-corrects
scope moves with evidence
predictable velocity
burn visible anytime
quality gates hold
red blocks, always
Step by step
How it runs.
Sprint zero
env + CI + contracts first
Sprint planning
DoR gate before entry
Build
WIP limits, trunk-based
Friday demo
working software or not done
Retro
one experiment, not a vent
Release
canary + rollback ready
Deliverables
What you walk away with.
- working increment each sprint
- changelog
- demo recordings
- burn report
- velocity trend
- ADR log
- release notes
- rollback plan
Who's involved
The people on the stage.
- Engineers2-6
- Tech Lead1
- PM1
- QA0.5
Controls
Quality & risk.
- CI green to merge; red blocks everything
- peer review required; no self-merges
- DoR gate before sprint entry
- demo or it didn't happen
- trunk-based with feature flags
FAQ
Questions, answered.
Sprint length?
1-2 weeks by cadence; weekly demos always.
Can we join standups?
Always invited - async first, video optional.
How are priorities decided?
Risk + leverage scoring, visible in the board.
Scope changes mid-sprint?
Change orders with visible trade-offs, never silent.
How do you handle blockers?
Async daily + escalation within 24h.
Agile Development Process applied to your project.
Tell us where you are — we'll run the stage that gets you unstuck.