Learn about Scrum – Why does Scrum fail – There is the reluctance to allow the team to be self-empowered and modify some processes for their betterment
Filed Under Agile, Change, Empower, Scrum | Posted on July 2, 2010
In the previous post (Team not being ready), I talked about how in some cases, the team has not been properly positioned into Scrum, and as a result, have not understood the benefits; and in some cases, they are introduced to an implementation of Scrum without the required training or at a time of stress, [...]
Learn about Scrum – Why does Scrum fail – The team is just not ready for a change in their processes to handle Scrum
Filed Under Agile, Daily Scrum Meeting, Features, Scrum | Posted on June 27, 2010
In the previous post, I took a real life example of a team (Daily Scrum and ScrumMaster) where Scrum was getting implemented, and yet soon after the actual work started, we were finding that things were not going on schedule, and that there were a lot of issues about commitment from the team, analysis revealed [...]
Learn about Scrum – Why does Scrum fail – A case of not getting the Daily Scrum correct
Filed Under Daily Scrum Meeting, Problems, Product Owner, Scrum, Status | Posted on June 20, 2010
In this post (and in a few other posts), I am going to be writing about some of the reasons as to why Scrum could fail. A lot of Scrum practitioners claim that typically it is not Scrum that fails, it is the people implementing it who fail. In this particular case, it is certainly [...]
Scrum problems – Problems in writing proper user stories – What a Scrum User story is not meant to be – Part 2
Filed Under Agile, Features, Product Owner, Scrum | Posted on June 16, 2010
The previous article (Scrum stories being too generic) was about providing the required right level of detail in Scrum User Stories, in order to make it represent the User Workflow. In this article, we focus on what a User Story should not be, and though these may seem obvious when we think about these deeply, [...]
