AI sprint planning checklist

Use this checklist during backlog refinement or sprint planning when a ticket may involve AI-assisted coding, prompt iteration, code review, or generated test work.

Scrum masters and tech leads can use this page when ordinary story-point planning does not capture how much AI-assisted exploration, prompting, generation, and review the work may require.

Walk the team through outcome, acceptance criteria, context size, likely model interactions, review depth, and release risk before voting.

In Token Poker, ask participants to vote privately before reveal. A private vote reduces anchoring and makes it easier to see whether disagreement is about delivery effort, likely AI usage, or both.

Record the final story-point estimate, final token estimate, and the assumptions that changed during discussion. The assumptions are often more useful than the number because they show what the team needs to learn next.

If token estimates are high, ask whether the ticket needs extra discovery, smaller slices, clearer acceptance criteria, or a deliberate decision to spend more AI budget on the work.

The checklist is meant to create shared understanding, not to turn estimates into commitments or to claim AI will automatically shorten the work.

Competitor and tool comparisons should stay specific. Token Poker focuses on AI-aware planning poker; other tools may be a better fit when a team only needs classic story-point voting or has different workflow requirements.