This post is part of the series How SCRUM has became so much of an impediment.
Other posts in this series:
- How SCRUM has became so much of an impediment. (Current)
- The sprint.
To be honest, despite this post title, I have been quite enthusiastic about agile methods. They tend (on the paper) to give back to engineers the control of the engineering. One of the most heard buzzword during the latest years is : SCRUM. It sounded great :
- Short cycle of development.
- Engineering team can self organize.
- Engineers are protected from administrative work by a guy called “SCRUM Master”
- A single guy (the product owner) representing all users and/or customers to centralized requests.
It seems that people behind SCRUM have clearly understood the main issues that software developers are facing on a daily basis. In this serie of posts, I will take some key features of SCRUM and I will compare them to my experiences. Let’s see how well they perform when they are implemented. As the title suggest the result is far from the expectation but I hope these posts will help to analyse why SCRUM is generally a failure.
Continue reading this series: