Don’t Look Back in Anger: Blameless Sprint Retrospectives

It’s all about culture.

Photo by Dark Rider on Unsplash

While working at a startup, we pretty much followed the Agile Scrum process. It is normal for companies to take a glance at the Agile Manifesto and implement a flexible Scrum process to ensure that quality software is developed.

Ceremonies

Sprint Backlog Refinement - The backlog represents the work that needs to be completed in order for the software to be developed. This includes Epics that can be broken down later into more manageable chunks

Sprint Planning Meeting - Each two week section of work answered the question “What are we going to work on” in collaboration between the product owner and development team

Daily Stand-up Meeting - Every day the group (under the stewardship of a Scrum Master) would cover the work that they have done, and what they would do during the next day.

Sprint Review Meeting - Held at the end of a sprint to demonstrate the newly built functionality. This delivered feedback from the stakeholders and product owner about the software artefact.

But wait, there is one missing part

Sprint Retrospective Meeting- Retrospective meetings focus on what went well, and what didn’t.