Demo day is where the team prove it has delivered the user stories as “done done” at the end of the sprint, typically in a one hour session.
In theory the Product Owner should run through the finished deliverables to make sure they work.
Demo days are always a challenge for BI projects due to the the high level of technical complexity in the components being delivered. This coupled with the fact that the Product Owner is often a business focussed person, make it a challenge for the product owner to run components such as a data load routine.
One of the other challenges is often the time it takes to execute the components delivered. shear volume of []
[[need time to prep]]
[[differentiate between user story and developer story ]]
[[always have some content at the end]]
[[shows the effort the team has undertaken, a often it is hodden]]
[[explains sone of the concepts embedded in hat has been produced. I’ve how conformed entities have been matched]]
[[give everybody a sense of enagement]]
HH Demo Day Flow
The first thing we do in the demo day process is to bring up the vision statement that the sprint is operating under. This helps reiterate the agreed scope of the sprint, as the audience will probably have forgotten or not have been involved in defining the vision.
It also has an added benefit of socialising the format for a vision statement, which will help if any of the audience are part of a visioning session in the future.
The we run through demos of what has been delivered in the sprint.
[[ req, data , code, rules, content, doco at each stage]]
We don’t typically present any details of the number of points planned or delivered, or any of the team velocity reporting. This is to make sure the demo day is solely focussed on proving what has been deliverers, not the how or why. An hour is not a long time and in a three week sprint the team should have delivered enough value that squeezing it all in is always a challenge.
The other thing that is important to manage, is that the audience is not allowed to ask questions during the demo session. This again is to make sure we get through all the content in an hour and keep our promise of only taking an hour of the attendees time. We leave an extra hour of the teams time free after the session so that those who have questions can stay back after and ask them. This is normally also the time the team get great feedback on the great work they have done.