Sprint demos are a measure of team health

The output of the sprint demo is the customer value delivered, but the goal of the session is very different.

Image for post
Image for post
Photo by Alex Litvin on Unsplash

I’ve been on teams that demo every sprint, teams that demo if they have something they think stakeholders will care about, and some that don’t demo at all.

I’ve come to realise that the value in the demo is not the opportunity to update stakeholders. It’s the contribution it makes to the health of the team.

Here are a series of ways that the demo helps assess and improve team health.

Sprint demos prove we’re regularly shipping value

Sprint demos are a team celebration

If your team doesn’t want to demo it may be a sign that they don’t see how the work fits into your strategy. Or, that the balance between informal internal sharing and stakeholder ‘presentation’ isn’t quite right.

Sprint demos enable all team members to share

Individual team members not regularly demoing could be an indicator of a wider issue.

Sprint demos are light touch stakeholder interactions

But, where they do it’s a fantastic way for the whole team to get to know them outside of more formal company presentations.

‘Informal’ is the key when setting expectations with stakeholders. Demos should be quick and easy, nobody wants to lose time every 2 weeks prepping a detailed slide deck.

I’m sure there are many more reasons I haven’t yet considered and listed here. The demo is an important part of the product cycle, and teams are better for the experience.

Written by

Product Managementing @redgate. Can also be found parenting / cycling / cricketing / allotmenting.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store