Agile Project Metrics
Agile projects and traditional projects are tracked differently. The key difference is that agile projects track outcomes; traditional projects track activities. Project managers who are new to agile are often unsure which measures are relevant to which stakeholders and how to interpret them, and how agile metrics tie back to some of the more familiar forms of project reporting. Dave Nicolette explains how agile projects are tracked, which metrics are useful to which audiences, and how to monitor project health, delivery effectiveness, and the quality and value of the results. Dave describes the reasons to choose particular metrics, how to use metrics for informational, diagnostic, and motivational purposes, and the time-sensitivity of metrics. Dave also explains the meaning and use of measures peculiar to agile methods, such as "velocity," "running tested features," "earned business value," and "burn charts". Bring your metrics questions and apply the information to your real-world situations.
Upcoming Events
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |
Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |