Stage Description Allowed Roles Can Move To What Happens next

0 Business High-level business ideas, requirements or PRDs. Tasks here are not PM, Product Owner Ready for Development Tasks are defined, clarified, and groomed before
ready for development. entering engineering scope.

1 Ready for Dev Tasks are fully groomed with clear acceptance criteria and are ready to PM, Developer In Development
Developers can start working. Once picked, tasks
be picked by devs. must be moved immediately to 'In Development'.

Once coding is done and local tests pass,

2 In Development Active coding stage. Feature is under implementation. Developer Peer Review or Blocked developer moves to Peer Review.

3 Peer Review Code is under peer review. Typically includes Git merge requests and In QA, or back to In Dev In QA, or back to In Dev
Tasks are defined, clarified, and groomed before
inline code comments. entering engineering scope.

4 DevOps Build Automated build stage triggered after Peer Review approval. Prepares CI/CD System, DevOps Engineer In QA
Tasks are defined, clarified, and groomed before
the environment for QA testing. entering engineering scope.

5 In QA QA validates functionality and acceptance criteria, and logs issues if Field Done or In Development Tasks are defined, clarified, and groomed before
any. entering engineering scope.

6 Done Task is fully complete, passes QA, merged to release branch or Field Archived Tasks are defined, clarified, and groomed before
deployed. entering engineering scope.

Tags Purpose When to use Allowed Roles Required Action Can Move To

Task is blocked due to external teams, '

When you re waiting on a party Note external party and what’s
1 Blocked - External vendors, clients, or unavailable outside your squad or org to Anyone (Dev, QA, PM) expected. Assign internal follow-up Cannot move until unblocked or
systems. respond or deliver. owner. manually overridden by PM.

Task is blocked due to internal delays

2 Blocked - Internal (missing access, design,
When an issue within the team/
org is stopping progress. Anyone (Dev, QA, PM) Log blocker clearly and tag internal
team or person responsible. Blocked until resolution or escalation.
dependencies, etc.).
Task is pending a stakeholder, design,
legal, or business review—not peer When work is paused until non - Anyone (Dev, QA, PM) Mention who is expected to review, Same column unless a review
3 Waiting on Review
code review. dev review/feedback is received. ETA, and next steps post-review. outcome demands movement (e.g.,
back to Business)

Task needs immediate attention due For high-priority fixes, customer Add reason in comments. May override Can skip normal flow with PM
4 Urgent
to business or production criticality. commitments, production bugs. PM, Tech Lead WIP if justified. Notify team. approval (e.g., from Ready → In Dev
→ QA)

Indicates task is build-ready and Immediately after peer review

5 QA Needed pending QA testing. and DevOps build success. Developer or DevOps Ensure build is stable, QA is notified. In QA

Task has unclear or missing During grooming, dev, or review Add specific question, tag PM or
6 Needs Clarification stages if blockers due to lack of Anyone tays in current column until clarified
requirements. clarity arise. relevant team for clarification. S

Task depends on another ticket or ’

When a task s progress is Link dependent task, monitor blocking tays in current column; visual cue
Dependency . Anyone S
7
system to proceed. contingent on another item task status, notify during standup. only

Task depends on another ticket or After QA pass and stakeholder Mark as release-ready, notify DevOps
8 Ready for Release system to proceed. approval. QA, DevOps or PM to include in next release. Release column or Done