{"id":190,"date":"2021-04-07T18:39:08","date_gmt":"2021-04-07T15:39:08","guid":{"rendered":"https:\/\/hygger.io\/guides\/?p=190"},"modified":"2021-10-08T15:10:28","modified_gmt":"2021-10-08T12:10:28","slug":"retrospective-meeting","status":"publish","type":"post","link":"https:\/\/hygger.io\/guides\/agile\/scrum\/retrospective-meeting\/","title":{"rendered":"Retrospective Meeting"},"content":{"rendered":"

Anytime your team reflects on the past thinking about how to improve the future, you get real benefits. Such an agenda is considered a continuous improvement opportunity for a Scrum<\/a> team to review the good and the bad. And it is all about an Agile Retrospective Meeting<\/strong>.<\/p>\n

Whether you represent a technical and non-technical team, you can practice the Retrospective Scrum ceremony<\/a> on just about anything!<\/p>\n

\"Agile<\/p>\n

If done well, this meeting can highlight chances for change, generate essential improvements, and ultimately move your team in the right direction. If done poorly, a Retro can turn into a blame game.<\/span><\/p>\n

If you want to understand how you can use the Agile retrospective format as a vehicle to drive change, then put everything aside and keep reading this post thoroughly. Here we\u2019ll break down what a Retrospective definition is, what it is not, and share some tips to make this Scrum event as productive as possible.<\/span><\/p>\n

What Is an Agile Retrospective?<\/span><\/h2>\n

The key focus in the Agile philosophy is primarily on quickly getting releases and worrying about what will be next.\u00a0<\/span><\/p>\n

A Retrospective is a special Scrum ceremony that forces teams to pause and reflect on what transpired and discuss what worked and what didn\u2019t work during a project. It’s rather important to respect the format of this meeting as the key to an effective retrospective. Value comes from the dialogue rather than just from individual statements.<\/span><\/p>\n

The meeting requires the presence of a representative from each group. Each person gets floor time to share their view of the experience. It can also be marketing, sales, customer support, and operations representative.<\/span><\/p>\n

Attendees should be equally encouraged to bring up the positive aspects, not only the challenging ones. The Retrospective meeting is a safe space for bringing up contentious issues and contrarian views. It should be as productive and insightful as possible.<\/span><\/p>\n

The meeting is usually led by a product manager as he\/she represents the most cross-functional role in the company and has a broader view of what happened during the project. Third-party facilitators can also be involved to ensure everyone is treated equally and given a fair share of floor time.<\/span><\/p>\n

Also Known As<\/span><\/h4>\n

The term \u201cretrospective\u201d was popularized by Norm Kerth thanks to his book “Project Retrospectives” (2001).<\/span><\/p>\n

\"retrospective<\/a><\/p>\n

This term has gained popularity in the Agile world over better-known terms such as \u201cPost-mortem\u201d and \u201cDebriefing\u201d. You may also find such terms as \u201cIteration Retrospective\u201d or \u201cSprint Retro\u201d (less often – \u201cReflection Workshop\u201d).<\/span><\/p>\n

Retrospective Origins: What Are the Roots of the Term?<\/span><\/h3>\n