A Scrum Team inspects and adapts, and metrics give that inspection something real to work with. Used well, they help the team see its progress, spot problems early, and have honest conversations. Used badly, they turn into pressure or a way to compare teams. The Scrum Master helps the team choose measures that support learning rather than control.
You'll start with velocity and how to use it for forecasting without misusing it, then look at the burndown chart as a way to see progress toward the Sprint Goal. After that you'll see how a cumulative flow diagram shows work in progress and bottlenecks, and finish with Evidence-Based Management, which connects measures to value and continuous improvement.
With a clear view of metrics and improvement, you'll be ready for the next module, Tools, Scaling & Certification, where you look at the tools Scrum Masters use, how Scrum scales, and how to prepare for certification.
A quick explanation of the velocity metric, how a team can use it to plan, and how not to use it.
How a burndown chart shows a team’s progress toward its goal, and how to read it during a Sprint.
How to read a cumulative flow diagram and see the relationship between cycle time, work in progress, and throughput.
An introduction to Evidence-Based Management, why traditional measures fall short, and how measuring value helps a team keep improving.