Browse Prior Art Database

Predictive Analysis for Agile Burndown Metrics Disclosure Number: IPCOM000198742D
Publication Date: 2010-Aug-13
Document File: 3 page(s) / 51K

Publishing Venue

The Prior Art Database


Predictive Analytics for Agile Burndown Metrics

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 3

Predictive Analysis for Agile Burndown Metrics

Disclosed is a process providing a capability in a metric that is typically as adaptive as the Agile ( methodology. The metric of the disclosed process relies on past



                                       redictive burn-down metric analyzes best and worst iterations of a team, as well as an average of several iterations, factors in anticipated changes, and determines various best-case and worst-case scenarios.

The most common metric for an Agile software development project is a burn-down metric . Typically, burn-down metric is focused on an iteration or sprint where work is accomplished over a short interval for example, a two-week period. For each day of the iteration, a formula for creating a burn down chart takes a total amount of work remaining to be done, subtracts work completed in the current day, resulting in a new amount of remaining work for the remainder of the iteration.

Another type of burn down chart used in Agile projects is extended to include an entire release (composed of multiple iterations). The same principle applies to the release burn down as to the iteration burn down. The work completed in each iteration is subtracted from the total remaining work at the end of each iteration, indicating progress along the path toward a full release. Whether used within or across iterations, the limitation of this burn down metric is that the metric focuses exclusively on past work performance. The current burn down metric fails to take into account actual ability of a team to produce, which can be influenced by a number of factors including adopting a new practice or improving a current practice as well as adding new team members. For example, assume a team has 100


oints worth of work to complete for a

                             oints per iteration. The team would require approximately five iterations to complete the work and ship the product. The following sample chart depicts workflow iterations to deliver the product.

given release and averages completion of 20

erformance and planned future change is typically used to more accurately predict future

erformance. The metric of the disclosed process referred to as a




Page 2 of 3

But, what if the team adds a new member? Obviously the ability of the team to complete work will be altered (and hopefully for the better). In this example, what happens when the team adopts a new practice and/or makes a significant change to a current practice. How can the team arrive at an understanding of the impact changes will have? Agile development is designed to be more flexible, anticipate problems sooner,...