Sprint Retrospective Meeting – Ретроспектива в Scrum
Sprint Retrospective Meetings, as well as Sprint Reviews Meetings are held in the last day of a Sprint. But, the aim of a Sprint Reviews Meeting is bit different. While Sprint Review Meetings are used to take a look at the final product, Sprint Retrospective Meetings are held in order to analyze the results of the teamwork.
No matter how good a Scrum Team works, there is always a room for improvement. An experienced Scrum Team always keeps an eye for an opportunities to improve. That’s why Scrum has alloted a special time period, during which a Team can stop and think about their work and possible improvement.
Sprint Retrospective Meeting – is a useful event, so it shouldn’t be neglected. For example, imagine a process of changing oil in a car. An approximate interval for oil change is about 15 000 kilometers Otherwise, there is a possibility of loss of engine performance or even failure. Scrum Team also needs some kind of "oil change", in order to maintain the effectiveness of working process.
Most Scrum Teams hold Sprint Retrospective Meeting as soon as Sprint Review Meeting is over. The whole Development Team, as well as the Scrum Master and the Product Owner take part in it. But it should be mentioned, that a Product Owner’s presence is not always necessary. Sprint Retrospective Meetings don’t have strict time-limits, but there is an optimal formula: the duration of a Sprint Retrospective Meeting equals 45 minutes multiplied by the number of weeks in the finished Sprint. If you’ve had a 4-week Sprint, then your Sprint Retrospective Meeting should last 45 * 4 = 180 minutes (or 3 hours). Though, not every Team sticks to this formula and the meeting usually lasts for an hour, extended if necessary.
There are plenty of ways to hold such meetings and each company use several types of them. Several books have been written on this topic: Agile Retrospectives: Making Good Teams Great and Project Retrospectives: A Handbook for Team Reviews.
The most widely-spread and easy (but still effective) way to hold this meeting is Start-Stop-Continue method.
This method demands that each team-member should define a list of things his or her team should start doing, continue doing and which ones are unnecessary. So, a team-member divides his list of things into three groups:
- What to begin doing;
- What to stop doing;
- What to continue doing.
Afterwards, a Scrum Master collects the results, which he can do in various ways: he can suggests the members shouting their ideas out loud, or he can walk around the table and ask each person individually.
After this brainstorming a voting takes place, concerning the question that will be raised upon after the next Sprint. The remaining question will be discussed on the next Retrospective Meeting.
An example of a Sprint Retrospective Meeting during the online-store development.
After finishing the Sprint and holding the Sprint Reviews Meetings, the Team gathers in order to discuss the effectiveness of their work, evaluated by each one individually.
The Scrum Master asks each person individually in order to get answers.
- I think, that the team should start using more thorough testing lists
- I think, that the team should continue using the current Product Backlog, it is an optimal variant.
- I think, the team should stop using the current development environment. It’s very sluggish and it slows our progress.
- The team should definitely continue using the current system of version control and cloud saving. We worry less about the losses and concentrate on the work more.
As we may see, one can express his ideas concerning improvements in a variety of ways, because there are plenty of common points with the working process.
Scrum Master creates the wish-list and the voting takes place. First of all, the team decides which improvements should be implemented in the first place and which ones should be left for the next Sprint.