Sprint Planning: A Complete Guide for Teams That Ship Every Week
How a weekly team leaves planning with a goal, a capacity number, and a backlog it can actually finish.
Sprint planning, capacity, goals and what to do with unfinished work.
How a weekly team leaves planning with a goal, a capacity number, and a backlog it can actually finish.
Five sprint retrospective formats, a 45-minute timing plan, and a worked example that ends with owners and dates.
Sprint rollover stays honest when you return unfinished work, re-estimate what is left, and stop counting points you already claimed.
Which agile sprint meetings to keep, how long each one should take, and a one-week schedule for a five-person team.
A four-step method for scrum capacity planning that turns real availability into a sprint commitment you can defend.
Scrum velocity is a trailing average of finished work, useful for the next sprint and silent on dates, quality, and whether the team improved.
A timed sprint planning meeting agenda that covers capacity, the sprint goal, story selection, risks, and a spoken commitment in one hour.
A one-sentence sprint goal your team can still repeat on day six, with a formula, a worked example, and four tests.
What a smaller team can take from PI planning: shared objectives, a capacity check, and named dependencies, without a two-day release-train event.
A step-by-step Jira sprint planning sequence, from creating the sprint to the commitment, plus the gaps the board does not close.
The sprint backlog is this sprint's commitment. The product backlog is everything else still worth doing, in priority order.
A sprint planning template that covers capacity, a sprint goal, and a commitment your team can still explain on day six.
Sprint poker is a short, silent vote on effort so a team agrees a number before anyone debates the story.
We are opening workspaces to a few teams at a time, especially teams that build several applications and already code with Claude Code or Codex. Tell us what you build and we set it up with you.