Congratulations students, we reaches the final lesson of the chapter. It's gramma West. So let's make a quick summary on the scrum he wants. We know that as there is for first grabs, grammar wins, and we've spent way too much time to review them in details, but now let's do a quick summary. So, we have four prescribed words. The first one is a daily Scrum.

This event is time boxed, the duration is 15 minutes regardless of the size of the team. And the purpose is to understand the progress towards this printable bliss. Remember that this event is an internal event of development team. The second thing went to this point blank as the length is time boxed duration up to eight hours and when we are saying the towers we consider massive sprint. So if you have shorter Sprint's then you should spend Last time as if we're policies to set sprint goal create sprint backlog or at least backlog with a number of items to work for a couple of these. And of course development teams should have a plan how to reach the sprint goal.

The short is a sprint review. The sprint review is time boxed event duration up to 40 hours and when we are seen for hearts we consider monthly sprint. So once again if you have shorter Sprint's then you should spend less time and the purpose is to inspect the outcome of the sprint and decide what to do next. This event is considered to be open so gress stakeholders and who would like to learn more about the project could visit this event. And finally as for is Sprint Retrospective, is the length is time boxed duration up to three hours. And once again when we are saying three cars we consider a monthly sprint.

So for shorter sprint, consider to spend less time and the purpose is to analyze, how's the last sprint went and rise the plan of improvement. This event is considered to be an internal event of scrum team. And itself. Sprint is not an event duration for the sprint, usually from one week to four week or month to sprint. And the purpose is to create potentially releasable software. But this is not the event.

So, there are four prescribed events in Scrum, and all the other ones are welcome as long as they're productive. So we finish this chapter. And the final point is that all Scrum prescribed runs are opportunities for inspection and adaptation. Well, let's move And let's discuss the final chapter of this course is about Scrum prescribed artifacts.