The demo is an important part of the Sprint Review ceremony. However, there is a lot of contention who should run the demo, and how much preparation should go into it. Here are a few ideas to help make your demos more effective without decreasing efficiency.
I’m going to start off by saying that I know Scrum and metrics don’t necessarily get along. But I will also acknowledge that it’s a necessary evil in most cases. And in a lot of cases it doesn’t have to be evil. Metrics are simply: a method of measuring something. In Scrum, we measure a lot of things. We measure the size of our work items, we measure the effort or time it takes to complete them. We measure our accuracy. All of this is in our quest to become predictable as a team and to improve (and we need to start with a baseline measurement to know if we’ve improved). But when others start taking notice of our metrics, that’s when things get tricky.
The Pomodoro Technique is something I started reading about when I began doing Agile. It’s all about timeboxing and how it can be used to efficiently manage everyday things by “elliminating the anxiety of time” and “enhancing focus and concentration”. The technique specifically counts time in “Pomodoros” – 25 minute timeboxes in which to concentrate on only one task. Here I describe how to use this technique for Agile meetings and personal productivity.