01 February 2014
Scrum comes with a set of new carefully chosen terms for roles in Software Development.
'Product Owner', the owner of the product, the budget and the one responisible.
Team member, not developer, architect or tester.
The terms are choosen to give a good idea what the role is about, mostly.
Lets look at sprint.
If you never bothered to look at a scrum book or took a training you might infer that
So far so good.
But it can also suggest that the involved go to an all out effort to finish the task they set out to do.
A sprinter wants to be first in this round, because there is no second.
Whether he can walk or talk afterwards is of no relevance,
it is over and he's won.
Here the analogy breaks.
A scrum team always has a next sprint.
If you (PO, manager or team member) organize sprints where massive overtime is acceptable,
you will end up with the follwing scheme:
The first days of sprint everybody just hangs around,
than the speed slowly picks up until evetybody is on overtime the last days before the sprint end.
The stories tend to be not well understood,
because they were discussed either during the time everybody is still exhausted,
or everybody is in hypermode and has no time for the next sprint.
The tasks tend to be rushed with a suboptimal quality.
Technical dept will mount because nobody thinks about tomorrow.
Everybody seams to be working so hard but the velocity drops.
If we want to think in sports term we should look at marathon runners.
How do you organize a run in \infinity many rounds
so that you never fall behind and are always in a good shape.
You can still sprint once in a while if it is necessary but without sacrificing the full race/ product / project.
Remember a profesional marathon runner can run at a speed that looks like sprinting
to an amteur pretty much forever.
But he does not exhaust himself in the middle of the race.