September 25, 2017.

5 ideas to improve your next Scrum Retrospective. As a result, the Scrum team comes up with a plan of improvements for a next Sprint. Reading Time: 6 minutes. They typically happen at the end of each sprint in Scrum, at regular intervals in kanban, or after something goes wrong in your organization. For example, for the Gather-The-Data step, you could use “What Went Well and What Went Wrong.” Now I hear you think… you know that activity! Use the Retrospective Exercises Toolbox to design your own Valuable Agile Retrospectives! AP) on it. In Scrum Framework, there a concept of a Sprint Retrospective meeting. Scrum Retrospective: Ideas and Examples. Depending on the scope and complexity of your work, team size, and/or length of time since the last retrospective, you may need to expand this up to an hour, or possibly even two hours. It is a self-inspection on how they are executing their tasks. Consider being on time for daily standups from the examples above. A quick note: ours was a lean 30-minute meeting. The Quick Retrospective dives straight in, asking the team direct questions about the sprint: what was good and what was bad, then capturing ideas and actions from the team. I vary retrospective techniques, it has happened more than once that I decided to change the approach while I was in the retrospective meeting, because another approach seemed more appropriate for the … A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. What Went Well / What Didn't Go Well setup in Retrium ‍ Step Two: To start the retrospective the facilitator should explain how the technique works. It’s a good starting point for new teams who are not experienced with retrospectives because it’s easy to understand and use. When you see action points, where a process adaption gets visible, or you spot an extension/change of your working agreements or a concrete to solve – add special marks (e.g.

I like multi-voting in a retrospective.

Good point! He or she should then tell the team the timebox for the retrospective (30-60 minutes, depending on the size of the team). Planning and executing an effective Scrum Retrospective is much easier said than done. For example, give each team member three votes to allocate as they wish (including all three votes to the same items). Many are more behavioral. Some examples are Root Cause Analysis, Timelines, Solution Focused, and the Perfection Game. Retrospective means to take a look back at events that already have taken place. Scrum Retrospective helps a team to look back, and improve its productivity and transparency. Home » Project management blog » Scrum Retrospective: Ideas and Examples.