top of page

Scrum Has Your Back

Updated: Apr 23

Not in the Sprint

The transparency of the Scrum artifacts helps prevent miscommunications and empowers the Scrum team to decide on a reasonable amount of work each Sprint.  The Scrum framework helps ensure that work is visible, the Sprint goal is clear and attainable, and no one gets surprised by hidden expectations.


Take this story that a participant shared at a recent Professional Scrum Master course. A Scrum Team sat down for Sprint Planning. After consulting the Product Owner and a key stakeholder, it was agreed that a particular Product Backlog item could be put on the "back burner" in light of other priorities, and it was therefore not pulled into the Sprint. Case closed, right?


Fast forward to the final day of the Sprint. The same stakeholder consulted during Sprint Planning asked why the Product Backlog item in question wasn't done by the due date.  A quick glance at the Sprint Backlog helped everyone to remember what was planned for the Sprint - and what wasn't.  


Scrum ensures transparency. The Sprint Backlog isn’t just a to-do list; it’s a transparent, living artifact that contains the plan for the Sprint. If it’s not in there, it’s not part of the Sprint. 

So, if you ever feel like you’re drowning in shifting priorities or being pressured to take on more than you should, remember—Scrum has your back. It's not about blame. It's about what's the most valuable thing to do next.

 
 
bottom of page