D O W HATEVER W ORKS FOR Y OU
Uh-oh. It’s looks like Master Sensei wants to see whether you’re picking any of this stuff up. Better get on over to the dojo and see whether any of this stuff makes sense. Good luck!
Master Sensei and the aspiring warrior Welcome back, Student. I have prepared for you three lessons to test your mettle on several real-life iteration mechanic scenarios. Please read each carefully before answering.
Scenario #1: The Incomplete Story MASTER: One day, during an IPM, it became apparent that a story was only half complete. Wanting to show progress, the young project manager wanted to count half of the story’s points toward this iteration’s team velocity and then count the other half when the story was completed next iteration. Is this a good idea? STUDENT: Well, if the story is truly half done, I see no harm in accurately reflecting the state of the story by counting half the story’s points toward this iteration’s velocity and carrying over the other half to the next iteration. MASTER: Is that so? Answer me this. Can a farmer transport his rice on a wagon with one wheel? Can a man eat with but one chopstick? Can a customer go into production with half a feature? STUDENT:
No, Sensei?
MASTER: To the agile warrior there is no 1/2 , 3/4 done, or 4/5 done for a user story. The story is complete, or it is not. For that reason, the warrior only counts fully tested and completed stories toward his iteration’s velocity. Any uncompleted stories are carried over.
Report erratum this copy is (P1.0 printing, September 2010)
188