Posts Tagged ‘Estimate’

What’s a spike, who should enter it, and how to word it?

0 comments

What’s a Spike? Who should create it? And what should it look like in VersionOne? (Or in Agile Central, Pivotal Tracker, HP AGM, Jira, or your ALM tool.) Excellent questions! I thought I’d share my thoughts on the topic: What’s a Spike? Sometimes a story is too large or overly complex. Perhaps the implementation or a 3rd party […]

read more

Always Looking Ahead

7 comments

I’m always looking ahead to the next planning or the next estimating meeting. I teach this behavior to my clients whenever I’m coaching a new ScrumMaster or Product Owner. I start off by involving them in what I’m doing, showing what needs to be done and by explaining my thinking. The teaching is very experiential, yet incomplete in […]

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

1 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

3 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