Coach’s Corner
We’ve said this before and we’ll say it again: The development team owns the sprint backlog. The sprint backlog needs to be transparent so the dev team can properly inspect it and, if necessary, adapt their plan for achieving the sprint goal. Such transparency might feel scary to some development teams as they may still be used to the pre-Scrum ways of doing things—which probably didn’t involve as much transparency as Scrum requires. As Scrum masters, we can ease those fears by using transparency to promote changes that will improve the development team’s workflow, and by promising that we’ll work with management to tackle any impediments that are uncovered by the increased transparency. As we just mentioned, an approach that ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access