6. Metrics

Burn-down

It answers the question: How much work is left to do? It is a visual representation of the pending work in the Sprint. It shows the amount of remaining work (in hours, story points, etc.) over time.

Burn-down chart

The X axis represents the days of the Sprint, while the Y axis represents the amount of remaining work. As the team completes tasks, the line on the chart goes down, showing progress toward the completion of the Sprint.

Burn-up

It answers the question: How are we progressing with respect to the changing scope? There are projects where the amount of work can change during the Sprint due to new requests or changes in requirements. The Burn-up shows both the completed work and the total scope of the project.

Burn-up chart

The X axis represents time (days, weeks...), while the Y axis represents the amount of work (story points, hours, etc.). There are two lines: one showing the completed work and another showing the total scope of the project. This allows you to see how the team is progressing in relation to changes in scope.

Cumulative flow

It answers the question: Where are the bottlenecks? It is a visual representation of the workflow across different stages of the development process. It shows the amount of work in each stage (for example, "To do", "In progress", "Done") over time.

Cumulative Flow Diagram

The X axis represents time, while the Y axis represents the amount of work in each stage (To do, in progress, testing, finished...). The colored areas show the amount of work in each stage, allowing you to identify bottlenecks and areas where the workflow can be improved.

Cone of Uncertainty

It answers the question: When will we finish the project? It is a visual representation of the uncertainty in time and effort estimates throughout the project's life cycle. It shows how uncertainty decreases as the project advances and more information is gathered.

Cone of Uncertainty

The X axis represents the project's time, while the Y axis represents the level of uncertainty. At the start of the project, uncertainty is high due to the lack of information. As the project advances, more information is gathered and uncertainty decreases.

This work is under a Attribution-NonCommercial-NoDerivatives 4.0 International license.

Desafíos de programación atemporales y multiparadigmáticos

Desafíos de programación atemporales y multiparadigmáticos

Te encuentras ante un librillo de actividades, divididas en 2 niveles de dificultad. Te enfrentarás a los casos más comunes que te puedes encontrar en pruebas técnicas o aprender conceptos elementales de programación.

Buy the book

Will you buy me a coffee?

This is how I keep writing without ads or paywalls.

Comments

There are no comments yet.