As a SM , Is it advisable to conduct in-progress demo during on going sprint of 2 weeks?
As a Scrum Master , Is it advisable to conduct in-progress demo during on going sprint of 2 weeks?
Share
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I guess the key things are
– who is the demo for?
– what value is the demo creating?
The Sprint cycle/cadence is NOT a stage gate. The Sprint Review is about evaluating the product-market fit and (at a point) whether we should be moving to end-of-life this product and work on things that are more valuable. In that context any demonstration is to support that *strategic* evaluation by key stakeholders, looking at the competitive market and it’s likely evolution. That might be for the product, or for internal products the business as a whole.
To put it another way, we’re trying to avoid the product becoming a “heritage” system 10 years out, with so much complexity and functionality that it’s hard to learn (from a user or development side), has lots of stuff that is seldom used, and is based on an aging technology stack that is hard to replace.
In Extreme Programming (XP) you had an “onsite customer” who collaborated intimately with the team as the development was done, looking at what was being developed, answering design questions and so on. The best Product Owners I have worked with can fulfil this role as user-domain experts, to shape the development as it is taking place.
In that sense demonstrations are continually part of the work, and should be a happening fluidly all of the time….