Posts Tagged ‘User Story’

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

Continuous Backlog Refinement

0 comments

Create your initial backlog, then stay on top of it. Here’s the how and why of Continuous Backlog Refinement. In my previous article, I talked about compressed backlog refinement in which a backlog is taken from crude to well-groomed in a matter of days through a series of intensive refinement meetings with the whole team. […]

read more

Compressed Backlog Refinement

0 comments

Lots has been written about backlog refinement (what we in the US used to call grooming), and a lot of it is good. There is lots to say about this practice. However, I’ve not seen any treatment on whether you should do it differently for your initial backlog. Therefore, I’m setting out in this post […]

read more