The goal of sprint planning is to ensure the Product Owner (PO), Developers, and Scrum Master are aligned on a plan for the upcoming sprint and collaboratively working toward the sprint goal. We’ll cover Scrum Guide’s sprint planning event topics.
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.
Creating tasks for each user story before implementation may seem like it is adding value and saving you time in the long run, but is it? Is it really? Or is it something you have always done without questioning its value?
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.
If you have a Scrum Alliance certification, your certification is good for two years. Then, you can renew your certification, a process that involves paying a renewal fee and collecting Scrum Education Units (SEUs) to prove your Scrum prowess. Read more to learn 5 tips for getting SEUs.
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.
We have created a checklist for Scrum Masters who are potentially stuck on one issue and unsure how to proceed.
Looking for quick ways to improve your Scrum team and its processes? These two quick tips will show immediate improvements.
A team that appears to be planning and executing sprints, but inside of the sprint timebox they still handle all of the phases of work as discrete, siloed steps is called Waterfalling the Sprint. Read to learn why it’s a problem and how to stop doing it.