A build’s path from ticket to store
Six lanes. Work does not move on until its gate is met. Durations are indicative ranges, not guarantees.
01
Intake
Ticket triage, scope, risks, acceptance criteria
1–3 daysGATE ✓02
Design
Flows, prototype, component states
1–3 weeksGATE ✓03
Build
2-week sprints, a build at the end of each
iterativeGATE ✓04
Verify
Device matrix, regression, accessibility
every sprintGATE ✓05
Publish
Metadata, review, staged rollout
1–2 weeksGATE ✓06
Watch
Crash reports, hotfixes
as agreedGATE ✓
ILLUSTRATIVE STOCK PHOTOGates we never skip
A gate is a yes/no checkable condition. If it fails, the release stops and a blocker appears on the desk.
- No open critical-severity defects
- Crash-free session rate of the previous version known and compared
- Privacy declarations match actual data collection
- Rollback plan tested on staging