Archive for the ‘Velocity’ Category

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

Don’t Estimate Stories In Sprint Planning

6 comments

This is part three in a series on estimating. Part one was “Don’t Estimate Software Defects” and Part two was “Don’t Estimate Spikes”. I don’t estimate stories in sprint planning. Nor do I re-estimate stories in sprint planning. I estimate stories in a separate estimating meeting and usually at least a couple sprints in advance, […]

read more

A Lesson In Process Improvement

1 comments

Regardless of your organization and goals, everyone is trying to do things better.  I commonly hear about management asking its people to do more faster, often with less. One major mistake I see time and time again are organizations trying to do things faster before really understanding their own processes.  If you don’t stop and really […]

read more

Getting Predictable

2 comments

Over the past few weeks, I’ve made two assertions about new agile teams. First… teams need to get good at calling their shots. To me, that means that over time, a well-formed, stable team should get good at being able to predict what they will get done over the course of the next iteration. Second… […]

read more

How Big Is Your Bucket?

6 comments

A few posts back, I asked if an agile team should be expected to call their shots. In other words, should we expect that over time, an agile team should be able to accurately predict what they’ll be able to deliver at the end of the iteration? My assertion was that predictability at the iteration […]

read more