At the risk of becoming overly link heavy in recent posts, I want to highlight two sources for trouble-shooting scrum implementations. The first is from Mike Griffiths’ Introducing Agile methods to Organizations: Mistakes to Avoid” (part 1, part 2, part 3). These meaty articles share plenty of wisdom.
The second is from the ScrumAlliance. They have a wiki to share scrum experience. In a recent addition, they have succinctly started to expand on a Toward A Catalog Of Scrum Smells by Mike Cohn:
Catalog of Scrum Smells
- Loss of Rhythm
- Talking Chickens
- Missing Pigs
- Status not clear from Daily Scrums
- Lack of Progress Part One: Failing in Backlog Management
- Persistent Signatures
- ScrumMaster Assigns Work
- The Daily Scrum is For the ScrumMaster
- Specialized Job Roles
- Testers will not integrate with Team
- Reluctance to estimate Backlog Items
- Is It Really Done
- Nothing Ever Changes Around Here
- No One Wants to Attend Retrospectives
- Executive Pressure
- Missing Sprint Commitment
- Technical Debt
- Not Acting Like a Team
- No Engineering Practices
- Gorilla in the Room
Let me know if you have any others to share.
Horizon Line Group 