As Halloween approaches we look for some agile horrors to watch out for:
Frankenstein Process: This is the methodology designed by committee that tries to combine iterative, empowered development with linear scheduling and command-and-control task assignment. Perhaps created in an attempt to satisfy the desires of competing groups, this half-goose, half-salmon abomination neither flies nor swims.
Agile practices are in a balanced network. Ruthless testing balances the need for comprehensive documentation; colocation, demos and daily stand-ups reduce the need for detailed status reporting. Changes made to this web of practices can easily create risks, gaps and duplications if they are not carefully considered.
Think candy apples, not pumpkin pie: Hybrid methods work best when there is a core of agile for the team to own and execute, surrounded by a wrapper of more traditional process to buffer and integrate into a less agile-aware environment. Don’t try and glom disparate process pieces together; it becomes a monster nobody loves or defends.
Zombie Projects: Some projects should just die, but won’t seem to. Doomed from the outset with unrealistic deadlines, overly ambitious scope or ill-equipped skills and support, everybody knows it will not end well--but nobody seems willing or able to kill it.
These death marches to eventual failure or
Please log in or sign up below to read the rest of the article.
"This planet has - or rather had - a problem, which was this: most of the people living on it were unhappy for pretty much of the time. Many solutions were suggested for this problem, but most of these were largely concerned with the movements of small green pieces of paper, which is odd because on the whole it wasn't the small green pieces of paper that were unhappy."
- Douglas Adams