Learn

How to run a sprint planning session

The most common failure is choosing work before checking capacity. A team that plans from a backlog without looking at the calendar commits to a sprint that is already impossible on day one.

What matters here

  • Check real capacity first, including leave
  • Review what carried over and why
  • Select work together, not by assignment
  • Agree what done means for each item
  • Write down what was not selected

Capacity before ambition

Count the days people actually have. Deduct leave, support duty and recurring meetings. The number that remains is the real budget, and starting from it prevents the ritual of overcommitment followed by apology.

Carry-over honesty

Look at what did not finish last time and ask why once. Recurring carry-over is a signal about estimation or interruptions, and ignoring it makes planning a formality.

Defining done

For each item, say what complete looks like: reviewed, tested, deployed, documented. Without that, review becomes a negotiation at the end of the sprint instead of a check.

Frequently asked questions

Keep reading

Turn talk into a plan

Capture a thought in plain language and let Prysm Note shape it into tasks and a timeline.

Try Prysm Note

Disclaimer

This page is general information, not professional, legal, financial or medical advice. It describes common ways of working and how Prysm Note approaches them. Software changes over time, so details may differ from what you see in the product. Any product, company or brand names that appear are the property of their respective owners and are used only for identification. We do not claim any endorsement or affiliation. Where we compare approaches, we aim to describe each one honestly, including where a different approach may suit you better. Try the tools that matter to you and judge for yourself.