You get to the end of your sprint and there is that are 2 incomplete stories left on the sprint backlog. Story A is judged to be 80% done, Story B was never even started. What do we do with these stories?
Options:
Story A
Story A was 80% complete. Incomplete work is not counted in the velocity because doing so allows the organization to consider work done that really isn’t.
Taking credit for unfinished work is the idea of Earned Value. Earned Value says because someone earned a salary for 3 days, the value of the final product or project went up accordingly. This is regardless of what the contributor did in those 3 days. This is obviously not a realistic notion given that Joe-Bob surfed the web for 2 of his 3 days.
Why do we re-estimate the work before putting it back into the backlog?
Re-estimate the story and put it back on the backlog.
Story B
Story B is simpler, but since it wasn’t even worked on why does it need to be re-estimated?
The real truth is that stories are often related, even though they are ideally independently deliverable. It is not only possible, but likely, that the team has learned more about the background of this work in the sprint that just finished. This means that a more accurate estimate is now likely.
No, you can’t take credit for partial work.
No, you can’t have credit for all originally estimated points in the sprint that finishes the job.
This model keeps things simple and keeps teams from gaming the numbers. Yes, I know successful teams that re-negotiate done. Yes, I know successful teams that split the story and only move part of it into the next iteration. I don’t agree that these practices are good, however. They relax the commitment made by the teams enough that the teams are basically allowed to get sloppy.
Keep it simple.
Remember Me
Disclaimer The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.