10 Ways to Fail Despite Scrum and XP
My last sessions of the Agile 2008 conference was a light talk by Henrik Kniberg. He was a fun speaker to listen to and He presented a nice talk on the following anti-patterns and I pass them on to you, here.
- Believing the hype
- If a company is really not willing to change, methodologies will not help them.
- Management discussion:
- Let’s go Agile!
- Good idea. Where’s the installation CD?
- Definition of Done
- not having one
- not respecting one
- Not knowing your own
- Not using it to try and improve team performance
- Not using it to do release planning
- doesn’t happen
- no improvements recommended
- unwanted people at the meeting
- people not participating
- proposed changes no implemented
- Team commitment
- Team doesn’t track and learn
- Team doesn’t sit together
- Always under or over committing
- No slack or reserved capacity
- Technical debt
- “We don’t have time to write unit tests or refactor code”
- Lack of code coverage or inattention to it
- Having to find who wrote it to learn how it works
- Big bang rewrites
- Decreasing velocity as the system grows is a sign of technical debt
- Lack of automated tests
- “I finished my stuff”
- Fixed roles
- Personal backlogs or velocities
- Not helping each other
- Personal incentive models
- Implementing all stories in parallel
- Product Backlog and Product Owner problems Note: See APOP.
- No PBL
- Never ending stories
- PBL is not visible
- PO without domain knowledge
- PO sees PBLs as an annoying administrative responsibility
- PO thinks specs or MRDs are what the team needs to get the work done.
- PO surprised at sprint demo (smalls of not being involved with the team)
- PO being a bottleneck for communication or decision making
- Mergephobia – The irrational fear or merging code
- No “done” branch
- No checkin policies for testing
- Branching to avoid conflicting work in a codebase
- Taskboard abuse
- Doesn’t exist
- Too far from the team
- Too complicated
- Not used during daily scrum
- No burndown
- Not updated daily
- Not used to guide decisions
Bonus: Worrying too much.
6 thoughts on “10 Ways to Fail Despite Scrum and XP”
Surely an interesting summary, but could you explain what the abbreviations mean? (I am still a student)
Especially PO and PBL don’t make any sense to me
A thought-provoking insight on the pitfalls of agile methodologies implementations.
Is there a you-tube or video clip recording this presentation by Henrik Kniberg?
PO is “Product Owner.” It’s like a customer; the person who uses your application and tells you how it should work (i.e. what the requirements are).
PBL is “Product Backlog,” which is a proritized list of all the functionality that should (eventually?) go into the product. PM puts items on it, prioritizes it; the team takes chunks of it per sprint and implements it.
Comments are closed.