Presenting Undone Work
Imagine there are three days left in the sprint, and stakeholder expectations are very high for the increment that the development team is building. Issues have emerged during the sprint that have slowed the development team, but the whole Scrum team has collaborated to keep the sprint goal intact. It’s clear that, although the team will meet the sprint goal, some of the functionality the stakeholders were really excited about won’t be fully tested and integrated into all environments. The development team’s definition of done states that the code must be tested and integrated in order for it to be considered “done.” But given the pressure from stakeholders, the Scrum team decides to include the functionality in the sprint ...
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