Sprint Planning

Sprint planning with AI agents on the team: how to handle capacity, estimates and the sprint goal when coding agents take Jira tickets, and why human review becomes the constraint.

Focus factor in Scrum converts available person-days into a realistic sprint commitment. How to calculate it, where it misleads, and how to replace it with per-person capacity in Jira.

A sprint planning tool does not make the meeting better — it makes the meeting shorter, by settling capacity and readiness before anyone joins the call. What to demand from one.

A sprint planning template is only as good as its capacity field. The five fields every template needs, why 80% capacity is a trap, and how to run it in Jira.

An AI scrum master can carry the mechanical half of the sprint cycle. Here is the split between what to automate in Jira and what a human still has to own.

When one senior developer or the Scrum Master assigns the points, the number survives but the information does not. Who should estimate story points, and why the disagreement is the valuable part.

Sprint length was a settled argument for a decade. AI-assisted delivery has reopened it. What sprint length is actually for, what shortening really costs, and the test that beats the debate.