Improving Software Development Using Scrum Model by Analyzing Up and Down Movements On The Sprint Burn Down Chart - Proposition for Better Alternatives.
Md. Junaid Arafeen, Saugata Bose · International Journal of Digital Content Technology and its Applications · 2009
Among various models, now a day, to address changing customer’s needs, commercial software developers intend to use iterative processes. Agile software development processes are built on the foundation of iterative development. One of the agile development processes is Scrum, which is an iterative incremental process of software development. Besides meeting varying needs of customer, timely delivery of product is important too. To predict when all of the work will be completed the developers use Burn Down Chart which represents work left to do vs. time. Theoretically, progression of time should leave less amount of task, the chart will look like straight line and the sprint will remain constant. However, in software industry, the irregularities on burn down chart are common which are the ups and downs occurring due to introducing new story points, new technology, wrong estimation of resources, cost and schedule. These reasons in turn affect the cost of the project, which in turn pull down the quality of the product because of failed to attain the defined sprint goal. To avoid such irregularities in development the better solution might be use of sprint burn up chart or modified Phil Goodwin and Russ Rufer’s burn down chart.