Sprint Planning & Estimation

Tickets that are ready before planning, an estimation method the team trusts, sprint commitments sized to real capacity and forecasts given as ranges rather than promises.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Sprint Planning & Estimation, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Sprint Planning & Estimation

Breaking work into tickets, estimating effort, committing to sprints and improving predictability without turning estimates into promises.

  1. Sprint length and planning day decision
  2. Definition of ready for incoming tickets
  3. Team definition of done everyone signs
  4. One ordered backlog with a single owner
  5. Ticket template with acceptance criteria
  6. Choosing the estimation unit for the team
  7. Reference stories for relative sizing
  8. Velocity baseline from the last six sprints
  9. Team capacity calendar for leave and on-call
  10. Weekly backlog refinement session
  11. Timeboxed sprint planning meeting
  12. Mid-sprint scope and risk check
  13. Sprint review that compares plan with outcome
  14. Retrospective focused on predictability
  15. Carry-over log for unfinished tickets
  16. Unplanned work and interrupt tracking
  17. Monthly roadmap forecast refresh
  18. Estimate accuracy review
  19. Stale ticket sweep for backlog hygiene
  20. Splitting stories into thin vertical slices
  21. Planning poker that avoids anchoring
  22. Acceptance criteria written as examples
  23. Timeboxed spikes for unknown work
  24. Monte Carlo forecasting from throughput
  25. Three-point estimates for larger pieces of work
  26. Reading burn-up and cumulative flow charts
  27. Story points versus no-estimates trial
  28. Scrum or Kanban decision for the team
  29. Sprint goals written as one outcome
  30. Capacity buffer policy for interrupts
  31. Board columns that match the real workflow
  32. Ticket size cap for sprint work
  33. Policy on estimating bugs and chores
  34. First sprint under the new planning process
  35. Quarterly planning session for the team
  36. Date commitment conversation with stakeholders
  37. Holiday period sprint plan
  38. Story mapping workshop for a new epic
  39. Lightweight planning for a team of two or three
  40. Asynchronous refinement across time zones
  41. Calibrating a new engineer's estimates
  42. Estimating your own work under a deadline
  43. Fixed-price bid estimate for client work
  44. Merging two teams' backlogs and velocity
  45. Cross-team dependency board for planning
  46. Multi-team programme forecast
  47. Estimating research and machine learning work
  48. Cost of delay and WSJF backlog ordering
  49. Cycle time percentiles as a service expectation
  50. Calibration training for ranged estimates

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Sprint length and planning day decision

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Teams that drift between one, two and three week sprints never build a velocity worth reading, because every number is measured against a different yardstick.

First tasks

  • Count how many sprint lengths the team has used in the last six months
  • Propose one length and one planning day in the team channel
  • Book recurring planning, review and retrospective slots for six sprints
  • Mark public holidays and freeze weeks against each sprint

Definition of ready for incoming tickets

Half the time lost in planning goes on tickets nobody can estimate: no acceptance criteria, an open design question, a dependency on another team. A short definition of ready, checked during refinement, keeps those tickets out of the sprint until they can be sized and started on day one.

First tasks

  • Pull ten tickets that stalled or were sent back in the last two sprints
  • Note what was missing from each when work started
  • Draft five to seven ready conditions from those gaps
  • Agree the checklist with the product owner and pin it in the tracker

Team definition of done everyone signs

When one engineer counts a ticket as done at merge and another waits for production, velocity measures nothing and carry-over hides in plain sight. Writing a single definition of done covering code review, tests, documentation and deployment makes every point the team reports mean the same thing.

First tasks

  • Ask each engineer when they consider a ticket finished
  • Write one definition that covers review, tests, docs and deployment
  • Link the definition from the sprint board header
  • Reread the definition of done with the team and update it @recurring(quarterly)

Make it yours.

Install Sprint Planning & Estimation, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.