Sprint Retrospective. Let's talk about this Chroma went. So we see on this image a number of people, and they're sitting there discussing something. And the most noticeable part of this illustration is that they're sitting over as their own table. So this table gives people equal opportunity. So people are discussing something, actually scrum team discussing something.

And all the members of the scrum team have equal opportunities. This is fair discussion, and they appreciate each other. So that's all about this Scrum event. So let's learn more in details. So Sprint Retrospective, Scrum time walks around maximum three cars for a month sprint, whereas the scrum team has an opportunity to inspect itself and create a plan of improvements to be enacted during the next sprint. Sprint Retrospective should help as a variant of every sprint After the sprint review, so that was basic rule on the Sprint Retrospective.

Let's reuse the main characteristic of this era. Only scrum team attempt this at Northwest. Yes, Northwest bliss, it's internal and people could charge different opinions and assumptions that need to be limited to the scrum team. scrum team inspect, how's the last sprint went with regards to people relations process and tools. So that's actually the main purpose of the event. scrum team will rise of major items that went well and need to be continued and the items that requires attention and need to be improved.

So during the discussion, people of the team were actual members of the team arise in different issues and some of them are good, which need to be cultivated Need To Be Continued out the other need to be considered for improvements. That's another characteristic of this or And now let's our reviews the true statements on the Sprint Retrospective true statements that are valid forms of sweat. So the first thing is that Drew's is Sprint Retrospective is an internal event of scrum team. So once again, guests are not welcome, so only a scrum master product owner and entire development team should attend this event. It's true that the default agenda of every Sprint Retrospective is based on three major steps on Ally's horizon neck. So actually, all people should actively be involved into the discussion during this round, as they should charge their opinions on different things.

And and our team should analyze whether these things need to be considered as good or is there a read and need to be somehow committed as Part of improvement or part of plans that need to be changed somehow. So that's all about this statement. It's true that he observed too much things that requires attention as a result of Sprint Retrospective, it's good to focus on one or few major first. So that's absolutely correct. Sometimes after discussion, it could happen that tomorrow's it a number of issues, as it need to be fixes that need to be addressed. And of course, it's not possible to fix them all at once, because they more likely will fail, you'll start doing this.

So what can be suggested in this case is to select one or maybe two of the most major problems or things that need to be fixed and address them during an expert. And in that step by step way, Tim will figure out those things later. It's true that Sprint Retrospective is a time marks to end with maximum length of three cards. We already know that those grammar ones are time boxed Sprint Retrospective is one of them. So if you use multi sprint, you can allocate up to three cards. If you use two week sprints, and probably too hard 70 if you're using one week sprints and one hour should be enough for the discussion.

So wherever you eat, the things that were true statements about this around. Now let's talk about false statements in regards to loose grammar when it's false, that Sprint Retrospective is meant to punish low performers. Sometimes you can even see that it's went to fire people who perform bad so it's absolutely false statement. And that's absolutely not true. But of course during the discussion, people could share different Opinions including the performance of course, they could actually a price performance of a particular member or actually rise concerns about performance of one of the two members. So it's possible during the discussion, but of course, this should be done in polite manner and people who actually discusses such things should focus not on the personality but on the behavior that was produced by the person so network never darkness this person is bad.

Now we're never do this kind of mistakes. So if you would like to discuss something that's actually not very pleasant, you should discuss as they behave, but not the person directly. The main point here, out this statement is absolutely not correct. So we're huge. The Sprint Retrospective around and this event is considered as great internal Scrum or went for the team where they can inspect themselves. They can actually highlight the things that they're doing good and address the things that need to be considered for improvements.

And in that way they can always improve. So Sprint Retrospective is one of the most valuable events has actually bought. These one is internal. He went off the team, so it's spatial. So that was her view on this event we have finished or prescribed or in other words, canonical Scrum ones. Now let's talk about other events that could take place as well.