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 [...]
Changing requirements and implications on testing
Filed Under Analysis, Change, Impact, Requirements, Testing | Posted on February 4, 2009
An ideal software development cycle involves a process whereby the requirements are frozen pretty early and the entire cycle happens with those frozen requirements. And if requirements do need to change, then a major impact analysis needs to happen, and the change is thoroughly studied before any change is taken. However, in the real world [...]