During Sprint Reviews, I’ve observed teams showcasing the results of purely technical work. Sometimes the resolution of a defect caused by some form of technical debt (“we noticed that we were making too many service calls”); or something related to development infrastructure (“we had to switch to a new testing framework”.) In such cases, the presentation frequently jumps quickly into a description of what was done showing, for example, the before and after behaviour connected to the defect or the results produced with a testing framework.
Potential problems with this are that business stakeholders attending the meeting:
- might be left wondering what this means to them
- feel unable to provide any feedback
- and in the worst case scenario, might feel they’ve wasted their time attending the Review.
A team might ask themselves, “what is the reason for us to have purely technical items in our Product Backlog?” But leaving that aside, the perils of losing stakeholder engagement during the Sprint Review could be mitigated by framing the presentation around the following questions:
- How is the world better now that we’ve fixed this defect?
- What’s the impact on the users and the business?
- What specific new capability does this technical work allow the team to do now for the business they serve (that they couldn’t do before)?
Submitted by Fernando Cuenca