Sprint review. Let's talk about this event. So we have a good illustration here and we see a lot more people's, some of them are sitting there are staying and listening. And there is one guy who actually explaining something and demonstrating something. So that's where we'll take example on how sprint review could be maintained. Now let's talk about this event in more details.

So sprint review is a scrum a Wednesday, it's usually the last one hour for every week of sprint. So for example, if you have to experience then you can consider up to two hearts for this event, and for house for a monster sprint. During this event, scrum team and other stakeholders inspect the outcome of the sprint and figure out what to do next. Sprint review should help at the end of every sprint sells it was an generic rule for sprint review and its purpose. Let's learn more about this one. And let's start exploring these now.

So let's talk about your turistic scrum team and stakeholders are down this event. So entire scrum team and all the stakeholders are welcome and actually it's good if the attendees around scrum team and stakeholders inspects outcome of sprint and figure out what to do next. So it's considered that Tim finish finished a number of product backlog items, and scrum team as well as stakeholder starts inspecting what was delivered these process normally leads to change towards a product backlog order and preliminary preparation of Wolfers an expert. So while scrum team and stakeholders florins are deliverables, zil. So thinking on the for their plan actual as they're sinking what to do next. And if for whatever reason some product backlog items was not finished is actually returning back to the product backlog and prioritize accordingly.

So it's all about this statement. Sprint review is not the same as a sprint demo demonstration could be a part of sprint review, but not always, and for example, technical improvement. So what we're trying to say here is that sprint review is standalone Armenian standalone words grammar and demo could be a part of this event. And also when you understand the demo is optional, sometimes it could take place but if Diem for whatever reason could not demonstrate Sampson's they can explain this in other way. For example, Show the performance improvements to Ron Sampson or actually explain how this was delivered to prove that it was done. So, demo is optional part.

That's how we can consider it. So let's talk more about this they went down let's review the true statements on this printer you and it's true that sprint review should lead to the updated order of product backlog based on zero knowledge of the increment. So once again, let's imagine the situations that we actually joined sprint review, and we see how do you actually explore in the sprint product backlog items shows their explorations items that were committed to the sprint and challenging them where whether they were delivered out for example, As a considers that one item was not truly delivered for example, it's doesn't work as expected. It's also like that they return this item back to the product backlog and prioritize it accordingly. So that's how it can lead to the updated order or the product backlog. As this statement is all about this let's move on the next statement is as it sprint reviews it time walks to one with maximum length of four hours.

We already talked about this and that's absolutely true. It's true that sprint review went is they went where guests are welcome. So it's absolutely correct. And sprint reviews on obviously went were us are welcome now. Anyone who interested could join this event. So where have you come on to statement about this?

Well, now let's talk about False. So it's false, that demo is mandatory for every sprint. So once again, Sprint reviews the Wentworth team actually explain what was done and confirming these in different ways. And one of them is to confirm something by demonstrating it. But of course, if for whatever reason someone is not ready to demonstrate something or don't want to demonstrate something, because well his reason, for example, this could be technical improvement, which cannot be demonstrated. But it can be measured, for example, as they can skip the demonstration parts.

So demonstration is a part of sprint review, but this part is not mandatory. So it's foul statement. If we say that it's mandatory. Let's move on. It's false. That demo should be driven only by the product owner or Scrum Master.

So it's another false statement. And demo could be Driving by product owner or Scrum Master. In exceptional cases, I would say so but in most cases, members of development team usually demonstrate something or actually could demonstrate something. But of course, we should never say that this should be done by product owner or Scrum Master only. This statement is absolutely false. So we reviewed the purpose of sprint review out the main characteristics of this event.

Let's move on and let's discuss other Scrum wet