![[Website Name]](https://www.managenovax.com/assets/images/logo.webp){kind=logo}
Your Cart
-
Your cart is empty.
All Materials
Category
User Stories & Sprint Planning
User stories provide a practical way to capture product requirements from the perspective of end users. These detailed study materials guide you through writing clear story statements, defining precise acceptance criteria, and splitting oversized requirements into deliverable increments. You will explore estimation techniques, backlog refinement discussions, capacity planning, and sprint preparation. The material also examines common mistakes, such as vague requirements, missing edge cases, and overloaded sprint goals. Designed for self-paced reading, this content equips you with structured methods to facilitate productive planning discussions, align team expectations, and ensure that upcoming work is well-understood and achievable.
Select Skill LevelWhat a user story is meant to capture and what it is not, writing acceptance criteria that can be tested, recognising a story that is too large, and preparing for a planning meeting.
A practical introduction for people asked to write user stories who are copying a template without knowing what it is for.
The level leaves you able to write a story a developer can start from, attach acceptance criteria that settle arguments rather than create them, and contribute usefully to sprint planning.
Splitting a story so each part still delivers something, story mapping to see the whole journey, relative sizing and its limits, capacity-based planning, and handling the story that always carries over.
For readers whose stories are now the main planning currency, and whose sprints depend on those stories being right.
You come away able to split work so every piece is worth delivering on its own, plan a sprint the team can realistically finish, and see the whole journey rather than a list of fragments.
Planning several sprints ahead without over-committing, coordinating stories that span teams, forecasting from historical data, and keeping detail proportionate to how far away the work is.
Written for people planning across teams or across a longer horizon, where a sprint is too short a unit to answer the question being asked.
You can forecast several sprints ahead with an honest confidence range, coordinate stories that cross team boundaries, and resist the demand for detail on work that is still months away.
The limits of story-based planning, when estimation stops paying for itself, alternatives such as flow-based approaches, and why velocity becomes harmful once it is reported upward.
The deepest treatment, questioning the practices themselves: what stories are good for, where they mislead, and what to use instead.
You can judge when story-based planning has stopped earning its cost, introduce an alternative without losing predictability, and refuse a metric that would distort how a team works.