Key takeaways
- Sprints are fixed periods with committed work. Review at the end.
- Stories = user value. Points = relative effort. Velocity = predictable output.
- Prioritise, unblock, and review. That's your role.
Sprint planning can feel like a foreign language. Stories, points, velocity—what does it all mean? Here's a plain-English guide for founders who need to work with dev teams.
What a sprint is
A fixed period—usually 2 weeks—where the team commits to a set of work. At the end, you have something to review. It's a rhythm that keeps progress visible and predictable.
Stories and tasks
A story is a unit of work from the user's perspective: 'As a customer, I want to reset my password so I can log in again.' Tasks are the technical steps to get there. Stories get estimated; tasks get done.
Points and velocity
Points are relative estimates of effort—not hours. A 2-point task is roughly twice as big as a 1-point task. Velocity is how many points the team typically completes per sprint. It helps you plan.
What you need to do
- Prioritise the backlog—what matters most?
- Be available for questions—blockers need quick answers
- Review at the end of each sprint—feedback shapes the next one
FAQs
Two weeks is common. Shorter for fast-moving teams; longer for complex work. Consistency matters more than the length.
It happens. Incomplete work goes back to the backlog. Don't extend the sprint—keep the rhythm.