Posts Tagged ‘User Story’

Why you might struggle with Progressive Elaboration

0 comments

Progressive Elaboration is the process of breaking Epics down into User Stories and defining details of those stories over time as the stories move through release planning and get closer and closer to being added to a Sprint. I’ve been exploring why some organizations struggle to put this into practice. Context: I often work with largish […]

read more

Estimating Placeholder Stories is a Bad Practice

3 comments

Placeholder stories, in general, are a bad idea. Estimating placeholder stories to reserve capacity or to get credit is a very bad idea. Define “Placeholder Stories” Of course, all stories are “placeholders for a conversation”, but that’s not what I’m talking about here. I am also not talking about things like “Refactor the such-n-such class as we start work on […]

read more

How Many Stories Per Sprint? Rules of Thumb

0 comments

I’m often asked how many user stories you should have in a sprint and how big is too big for a story. People are looking for guidance. Stories per Sprint I’ve heard some coaches recommend “3-6 stories per iteration per developer”. That’s a bad rule of thumb. For a team of 7 developers you would […]

read more

Don’t Give Partial Credit

2 comments

What do you do with stories that don’t finish before the end of the sprint? Do we get partial credit? I’m asked that a lot. Everyone wants to know whether to split the story and what to do with the points. Don’t give partial credit for unfinished stories or make untestable splits. Don’t Bother Splitting […]

read more

Telling Executive Stories

0 comments

Delivery teams manage and deliver value supported by the tool user stories. These teams tell stories about who, what, why, and acceptability using standard form, “As a <persona>, I want <capability> so that <delivered value> occurs,” and behavior acceptance form, “Given < context>, when <action occurs>, then < consequence >.” These stories form the foundation […]

read more