Can you recall the last time you saw a promo of your favorite movie or TV series? How did you felt on that moment? – I believe the emotions stretch from anticipating to enthusiasm. But, why we behave like this? – Well, first, the natural notion that “someone” has thought of us (producer or movie studios). Second, by seeing this promo we are gaining confident that the movie/series will actually take place on near future. No more rumors over network. Movie studios are actually working on this. Third, usually, promo’s gains back our expectations. Meaning that, the new coming will be as good as the current movie/series – not less. If promo will lose this expectation, no user will be expected to view this movie/series. Scrum as a method should also provide such promos in which called demo.
In general, demo has some magic connectivity between R&D or QA department into Product management & marketing departments. Let’s take a real life example:
Product manager ask R&D to develop a new feature. R&D is setting the best plan they could for achieving such feature. R&D estimate feature developing should take about 6 months with 10 team members. Now, PM raise few questions:
1) How will I know, that this feature is actually get into progress or will be increment?
2) Assuming, adjustment will need to take place, when I will be able review this feature before go to market?
As such, think of demo as a promo. In this case, PM will gain the notion that R&D is aligned with product departments – R&D is not developing something “else”. In addition, PM will gain the confident about this feature, meaning that reducing the feature risk; hence all relevant departments will set the correct expectation levels.
The best practice for ta demo, is setting a short demo by the end of each sprint. In some companies, sprint can be taking a week while on other companies a month. So, it is also depend upon the following question: “Can the end-user actually view the change in this feature by the end of the current sprint?” –alternatively, the developed feature, can’t be actually view since it is an infrastructure. But, end user could have the notion that new feature is supportive of service or product. The demo should include all relevant stakeholders, sometimes even the end users (Who know better than the end user?).
Now, the scrum just need to set the when & where.