{"id":5858,"date":"2020-04-17T13:31:40","date_gmt":"2020-04-17T11:31:40","guid":{"rendered":"https:\/\/teamdeck.io\/?p=5858"},"modified":"2024-09-04T16:03:43","modified_gmt":"2024-09-04T14:03:43","slug":"ideid-agiilsete-sprintide-tagasivaadete-jaoks","status":"publish","type":"post","link":"https:\/\/teamdeck.io\/et\/juhtimine\/ideid-agiilsete-sprintide-tagasivaadete-jaoks\/","title":{"rendered":"V\u00e4rsked agiilsed retrospektiivsed ideed: Meeskonna j\u00e4rgmise koosoleku jaoks: Muutke asju"},"content":{"rendered":"
Home<\/a><\/span> \u00bb Fresh Agile Retrospective Ideas: Change Things up for Your Next Team Meeting<\/span><\/span><\/div>\n\n

A scrum retrospective is a crucial meeting in your team’s calendar. It’s a chance to analyze the previous sprint and “create a plan for improvements to be enacted during the next sprint” (source:<\/span> the Scrum Guide<\/span><\/a>). If you want your team to perform better and your team members to feel better about their work, the retrospective is the meeting you should put much focus on.<\/span><\/p>\n

Since retrospectives happen regularly (between every Sprint Review and Sprint Planning), you have plenty of opportunities to inspire your team members to share their ideas for improvements. The downside of retrospectives happening quite often is that they can easily change into routine gatherings that people want just to sit through and survive.<\/span><\/p>\n

If your team has also been affected by the retrospective fatigue, or you don’t see tangible results of these meetings, you’ll find this blog post especially useful. We’ve collected a couple of ideas to refresh your agile retrospective ceremony and maximize the benefits for your team.<\/span><\/p>\n

\"Agile<\/p>\n

Shake up the usual parts of agile retrospectives<\/strong><\/h2>\n

We’re not reinventing the wheel here. A scrum retrospective has an established structure that doesn’t need to be taken apart in order to <\/span>make the meeting more productive.<\/span><\/a> You can, however, change the way you usually go about certain parts of the retrospective:<\/span><\/p>\n

Gather feedback\u00a0and gather data<\/strong><\/h3>\n

Collecting notes from different members of the team is an essential part of a scrum retrospective. The chances are that you’ve been using the same formula to gather feedback for a while. It could be a table with <\/span>start<\/span><\/i>, <\/span>stop<\/span><\/i>, <\/span>continue<\/span><\/i> columns, or the<\/span> sailboat<\/span><\/a> metaphor. They might have worked well at the beginning but, with time, got a little stale.<\/span><\/p>\n

You can freshen things up by essentially doing the same thing, but slightly changing the form of this exercise. It will feel fresh and might inspire your team to come up with new items:<\/span><\/p>\n