It is easy to lose track of Scrum principles and best practices. Inevitably, problems will then arise that will be perceived incorrectly as failures of Agile or Scrum itself. Do these Scrum anti-patterns affect your development process?
There's a saying in the Agile community - Agile is simple, but it's not easy. All too often Scrum teams cut corners or abuse the Scrum framework - they do the easy parts of Agile without doing the hard parts. These teams may see initial short term gains, but sooner or later, meet challenges, frustration, and in many instances, failure.