Does Every User Story Need to Be Small? - Mike Cohn
whatshot 7 snips
Dec 11, 2024
Explore the critical role of user story size in Agile planning. Smaller stories can streamline project management, but larger ones have their advantages in early stages. Discover how consolidating user stories can keep the backlog manageable when launching new products. Learn the importance of empowering the Product Owner, emphasizing balanced responsibilities that enhance team efficiency. Dive into strategies for refining stories, allowing for size adjustment as projects evolve.
07:36
forum Ask episode
web_stories AI Snips
view_agenda Chapters
auto_awesome Transcript
info_circle Episode notes
volunteer_activism ADVICE
Small User Stories
Make user stories small, like t-shirt sizes, for easier consumption.
This improves sprint planning and forecasting and reduces work overflow.
insights INSIGHT
Large Stories for Future Sprints
Not all stories can be small initially, especially those planned for future sprints.
It's okay to have larger stories for items further out on the horizon where details are still unknown.
question_answer ANECDOTE
Example of Reporting Story
Mike Cohn uses the example of a new product with a set of reports.
Initially, one large reporting story is sufficient, avoiding premature detailed breakdowns.
Get the Snipd Podcast app to discover more snips from this episode
Small user stories are essential to success with agile. When it’s time to bring stories into an iteration, I always want them to be small. But larger stories have their place as well–especially for something you're not going to work on imminently. Suppose you have just begun work on a new product that will include a set of reports. Because this is a new product, there is nothing to be gained by writing a bunch of small user stories around each one of those reports at this point, especially since you don't yet even know all of the reports that will be needed. At this stage of the project, having one big reporting story rather than a bunch of little ones keeps the size of the backlog more manageable. You'll have one entry in your tool instead of 15 or 20. That's much easier to manage. Further, if you do write all the small user stories, one per report, it gives the impression that you've thought of everything. Early in a project, that's probably not true. New reports will be identified and some that are asked for initially may not be necessary. Don’t fall into the trap of thinking every story needs to be small from the beginning. They don’t. Instead, plan for stories to shrink in size and grow in detail as they move closer to being brought into a sprint. For most teams, this will happen during the product backlog refinement meeting one or two sprints before the iteration planning where they’ll be considered. Letting timing dictate story size will help you succeed with user stories and with agile.
The Agile Daily Standup - AgileDad