Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News Presentation: 10 Ways to Screw Up with Scrum and XP

Presentation: 10 Ways to Screw Up with Scrum and XP

In this presentation filmed during Agile 2008, Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is, or they don't hold retrospectives.

Watch: 10 Ways to Screw Up with Scrum and XP (1h 28min)

Henrik's 10 reasons to fail while doing Scrum are:

  1. Believing the hype. Someone might believe that Agile is something magic.
  2. Definition of Done. There are problems when developers don't have a definition of Done, or they know it but they don't obey it. An example for Done is:
    • Unit/Integration tested
    • Ready for acceptance test
    • Deployed on demo server
  3. Velocity. Some of the issues related to velocity: not knowing about it, not using it or misusing it.
  4. Retrospectives. Some teams do not hold retrospectives at the end of a sprint or no improvement proposals are made.
  5. Team commitment. The team might be under pressure to deliver, or they are under committing or over committing.
  6. Technical debt. Accumulating technical debt over time or ignoring it has a serious negative impact on a project.
  7. Teamwork. Members in a team should not work like they are by themselves.
  8. Product backlog. If the product owner does not keep a product backlog, the project will develop chaotically and unpredictably.
  9. Mergophobia. Code merging is not done regularly.
  10. Sprint backlog/task-board. A team without a sprint backlog does not have a clear view of the work to be done.

Rate this Article