As part of the Scrum Tapas video series, Professional Scrum Trainer Martin Hinshelwood talks about why DevOps and Continuous Delivery fit nicely with Scrum as complimentary practices and techniques. 3:17 Minutes
sprint review is one time informal meeting where potentially shippable project is shown to stakeholders for review and feedback. how can we have review when having hourly / very frequent delivery ?
You can still review a set of deliveries. For example, if you are releasing hourly, would you go to all stakeholders each hour, likely not. You would generally have a group of items to review for context and for broader feedback. There also is nothing that says you cannot review more frequently, but at a minimum you need to look at what was done once per Sprint.
@scrum.org is correct. Your Sprint is a container for planning and not delivery. There is no reason why you cant do continuous delivery (maybe shipping every check-in to production), and then get your stakeholders together on your Sprint cadence to provide feedback on your work. Those stakeholders may also provide feedback on a continuous basis, however the Sprint Review is an explicit moment in time where your Scrum Team can solicit targeted feedback based on the current business conditions and the state of the Product Backlog and what you plan to work on next. The Sprint Review is the last moment in time that feedback provided can have an effect on the choice of what needs to be done next. Once you start the next Sprint you are committed to your Sprint Goal...
![โฮ่ง! (SUGOI) - LYKN [ OFFICIAL MV ]](http://i.ytimg.com/vi/nFp4zjAARFs/mqdefault.jpg)
sprint review is one time informal meeting where potentially shippable project is shown to stakeholders for review and feedback. how can we have review when having hourly / very frequent delivery ?
You can still review a set of deliveries. For example, if you are releasing hourly, would you go to all stakeholders each hour, likely not. You would generally have a group of items to review for context and for broader feedback. There also is nothing that says you cannot review more frequently, but at a minimum you need to look at what was done once per Sprint.
@scrum.org is correct. Your Sprint is a container for planning and not delivery. There is no reason why you cant do continuous delivery (maybe shipping every check-in to production), and then get your stakeholders together on your Sprint cadence to provide feedback on your work.
Those stakeholders may also provide feedback on a continuous basis, however the Sprint Review is an explicit moment in time where your Scrum Team can solicit targeted feedback based on the current business conditions and the state of the Product Backlog and what you plan to work on next.
The Sprint Review is the last moment in time that feedback provided can have an effect on the choice of what needs to be done next. Once you start the next Sprint you are committed to your Sprint Goal...