A precursor to Scrum is practicing iterative development of any kind.
- Fixed iterations of not longer than six [weeks]1
- Working software at the end of each iteration
- Start iterations without requiring a “complete” specification
- Testing during rather than at the end of iterations
Jeff states, “this rules out about half of (self-identified) Scrum teams.”
The minimum to foster self-directed development teams working to clear business priorities using the tracking mechanisms of Scrum.
- Got a product owner? A single, empowered person who works directly with the team to determine what to build.
- Does the product owner have a product feature backlog? Is that backlog prioritized by business value? Is it estimated by the team?
- Track work with a burndown? From that, can you derive a velocity?
- Hands off during an iteration? “Nokia has a rule that you can’t have a project manager interfering with the team in the middle of an iteration because that stops the self organization.”
Jeff’s been saying for years that if you don’t have a backlog, you don’t have Scrum.
The first thing we lost in the acquisition process was our product owner. From there the rest deteriorates. Without a strong, empowered product owner the backlog becomes arbitrary and so does planning work against that backlog. See what that does to talented developers used to fueling themselves on intrinsic motivation.
It will be at least as hard to re-build these practices as it was to build them in the first place. The work of the new year and perhaps many years to come…
1 corrected from six
months to six weeks.