Common Questions About Sprint Review, Answered
Interested in doing a sprint review, but unsure what it is and how it works? We’ve answered some common questions about sprint reviews.
Interested in doing a sprint review, but unsure what it is and how it works? We’ve answered some common questions about sprint reviews.
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.
Software defects, also referred to as issues, bugs, observations, or oopsies (my personal favorite), are one of your largest sources of wasted time and money. Read more to learn what you can do to fix them fast.
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.
Learn about the CSM Journey and why A-CSM and CSP-SM were created.
Learn a few reasons that teams can’t seem to stabilize velocity and how to fix them.
Looking for quick ways to improve your Scrum team and its processes? These two quick tips will show immediate improvements.