Though Scrum is seen as most successful in delivering a product, often Scrum itself fails due to various reasons. The Symptoms and Root Causes are discussed in this article. As per Wikipedia, failure generally refers to the state or condition of not meeting a desirable or intended objective. so what is failure in the context of Scrum? As per the Agile Manifesto’s Principles, our highest priority is to satisfy customer through early and continuous delivery of valuable software. So a failure in context of Scrum can be defined as – Unsatisfied customer because of late or sporadic delivery of valueless artifacts.
Large parentage of organizations are believed to fail in Scrum due to the following reasons:
- Not implementing the whole process
- The team is not co-located
- Compromise on the Product Owner / Scrum Master roles
- Compromise on the size of the team
But how do you identify that the Scrum project is failing? There is no one single cause but a combination of problem areas that are dependent on each other like. Broadly the problem areas an be classified into:
In each of the above area, there are different symptoms that can indicate that the Scrum Project is failing. when you encounter such symptoms its easy to jump in and do a quick patch but it will not last longer if the root cause is not addressed. So, we have divided into two categories i.e Symptoms and Root cause under each problem area to help you clearly differentiate between symptom and root cause and fix the problem.
*Visited 7890 times, 3 So far today*