Learn about Scrum – Why does Scrum fail – Dealing with a team that was hesitant, and it worked only after people actually were changed
Filed Under Challenge, Change, Daily Scrum Meeting, Scrum, Team | Posted on July 15, 2010
If you look at the title of this post, it does not mean that we convinced the people to change; it actually meant that in some cases, people were encouraged to leave for a different group, or when they decided to leave the company, they were not stopped. This seems rather drastic, but it turned [...]
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, [...]
Burn Down chart and a change in scope that impacts the burn down chart
Filed Under Agile, Change, Features, Scope, Scrum | Posted on March 11, 2010
In the previous post (Burn Down Chart), we talked about what a Burn Down Chart is, and how you can use it to get the current status of the project, while not using it as a way of judging the performance of the team. This is because there are many variable that can impact the [...]
Overview of Change Management – Software configuration management
Filed Under Change | Posted on September 18, 2009
Software configuration management is an umbrella activity that is applied throughout the software process. SCM identifies, controls, audits, and reports modifications that invariably occur while software is being developed and after it has been released to a customer. All information produced as part of software engineering becomes part of a software configuration. The configuration is [...]
