Agile

If you’ve never experienced what a good Scrum Master does for a team, it’s easy to misunderstand the role as being administrative: scheduling team meetings, taking notes on impediments, nagging people to update the status of things. When that happens, it’s natural for decision makers to feel that the role of Scrum Master is not a real job, and therefore decide not to invest time or money into it. At that point, one of several anti-patterns typically happens. Here are the ones I see most often:

In this blog, we’ll explore the purpose of three core reports every Scrum Master should understand and use: burndown, burnup, and throughput. We’ll also explain how to read and create each chart.

Read more to learn about EPC, why we use it, and which three inspect and adapt loops are used within the cycle of the framework, once per sprint.

Looking for quick ways to improve your Scrum team and its processes? These two quick tips will show immediate improvements.