When is a story too big?

I hear it all the time. “There is no way to break this story down any smaller.” Believe me there is always a way. Find it. Or your velocity will be all messed up! and worse. Watch this video to learn how Testing suffers from big stories

By | 2011-04-04T12:15:34+00:00 April 4th, 2011|agile, agile fundamentals, Basics, story card, video blog, waterfall|2 Comments

About the Author:

2 Comments

  1. Sampath Prahalad July 5, 2012 at 9:49 am - Reply

    A real good explanation, Joseph. This really happens in real life where QA gets all the work at the end of the Sprint. Let me try this out.
    One question though.. With this exercise, won’t we end up having only user stories of sizes 2, 3 and a max of 5 in the Sprint? Good for everyone, I agree, but it puts that much more pressure on the product owner.
    Let me know what you think.

  2. […] The ability to split requirements into granular user stories so that they can be completed within a Sprint. An epic user story can be big and spread across Sprints, but each user story should be granular enough to be implemented within a Sprint. See related video blog here. […]

Leave A Comment