Planning
Planning turns requirements into an executable cycle plan.
Outcomes
Typical outcomes from planning:
- Prioritised backlog and cycle scope
- Sequenced work with owners and dependencies
- Clear readiness criteria
- Confirmed delivery timeline
Planning applies prioritisation to turn candidate work into an executable cycle sequence.
Flow
flowchart TD
start((Start)) --> ticket-age-input[Ticket age input]
start --> capacity-input[Capacity input]
start --> priority-input[Priority input]
ticket-age-input --> cycle-scope-defined[Cycle scope defined]
capacity-input --> cycle-scope-defined
priority-input --> cycle-scope-defined
cycle-scope-defined --> scope-approved["Scope approved<br/>by validators"]
scope-approved --> team-works["Team works on cycle scope<br/>priority order"]
team-works --> development[Development]
development --> qa-testing[QA testing & fixes]
qa-testing --> staging-test[Staging test]
staging-test --> cycle-completed((Cycle completed))
team-works --> new-issue{New issue<br/>during cycle?}
new-issue -->|Yes| urgent-critical{Urgent?}
urgent-critical -->|Yes| add-current["Add to current cycle<br/>if capacity allows"]
urgent-critical -->|No| add-backlog["Add to backlog<br/>next cycle"]
new-issue -->|No| add-backlog
add-current --> development
cycle-completed --> start
add-backlog --> start
Cycle length
2 weeks, excluding public holidays.