Not every product or change needs a sprint demo

Demos are far from the only way to receive timely feedback.

Talking to stakeholders and end-users is a great way to get feedback on the product you’re building.

But how often should we meet with our stakeholders and end-users to get this feedback?

If you adhere to Scrum, this is accomplished via the Sprint Review at the end of each Sprint. Although in practice, it seems that many teams skip this event entirely. And of those that don’t skip it, it’s often an internal meeting, without any stakeholders present.

But is that the answer? We should get feedback once per sprint/iteration?

Demos/reviews are far from the only way to receive timely feedback.

In fact, for some types of products, demos would be a very slow way to receive feedback.

Share this

Related Content

"Agile" isn't about delivering every sprint

Frequently delivering software, but not considering feedback on how to improve, isn't agile.

It's retro day!

If you find that you can improve the way you're working, don't wait.

Vanity metrics

"Revenue is down this quarter, but on the bright side, our sprint numbers are accurate!" said noone ever.