Management Information and Metrics Agile Testing

Since the implementations are managed through a suitable SCM tool, it is possible to make use of the metadata that are generated and stored in the underlying database. The process includes the following high-level activities:

  • user story definition and validation,
  • iteration planning,
  • spike development,
  • development estimates,
  • iteration durations,
  • rework/new development,
  • acceptance, and
  • minor release.

We can make use of the data generated(manually input data or system data)to produce useful management information and metrics. For example, we know the number of developers in a team, the number of user stories, and the development estimates for each user story. Therefore, we can produce metrics to assist the iteration planning process by assessing the capacity versus utilization metrics.

Since we know the iteration start dates, iteration duration, and number of development days(actual/estimated), we can calculate the burn
rates(Heartbeat retrospective), iteration velocity, and project velocity.

All of this information can again be displayed to the appropriate stakeholders using the rich graphical user interface .Figure illustrates the new development versus rework; note how iteration 4 has a predominantly high level of rework. Development managers(Scrum masters)can use this information to assess the reasons why there is a rework peak: poor requirements, complex code, or a change in business requirements, for example.

Again, there are sufficient data within the SCM tool to assess the velocity(progress)of each iteration and the overall project. With the correct management of user story metadata, combined with SCM workflow, it is possible to determine these statistics.

Taking this a step further, we can use these data to visualize trends and make predictions;consider the graph in Figure.

The dashed line in the graph plots the velocity of each iteration, whereas the gray solid line provides the velocity of the overall project. By overlaying trend lines we can also make reasonable assumptions for the delivery of the current user stories– fluctuations in the iteration velocities may be attributable to changing, or additional, requirements.

Graphical display of user story attributes.

Graphical display of user story attributes

Graphical display of rework ratio.

Graphical display of rework ratio

Graph of iteration and project velocity.

Graph of iteration and project velocity



Face Book Twitter Google Plus Instagram Youtube Linkedin Myspace Pinterest Soundcloud Wikipedia

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Agile Testing Topics