Preparing for a retrospective involves setting a clear agenda, gathering team metrics (like velocity or bugs), selecting a relevant format (e.g., Start, Stop, Continue), and creating a safe, open environment for feedback. Key preparation includes reviewing previous action items, defining the meeting’s, and ensuring all team members are prepared.
The 6 steps needed for a successful retrospective are:
What is the golden rule of retrospectives? To create a safe environment where team members can speak openly. It's essential to focus on continuous improvement rather than blame, ensuring that every voice is heard and valued.
Some questions you may want to ask during a sprint retrospective include:
One of the most common complaints about retrospectives is that people fail to bring up real issues or admit to their problems. If people aren't going, to be honest in a retrospective, the argument goes, they're a waste of time.
The "3-5-3 Scrum" is a simple framework to remember the core elements of Scrum: 3 Roles (Product Owner, Scrum Master, Developers), 5 Events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and the Sprint itself), and 3 Artifacts (Product Backlog, Sprint Backlog, and Increment). It serves as a quick checklist for teams to ensure they're covering the foundational practices for Agile development, promoting transparency, inspection, and adaptation.
Following are some common retrospective mistakes that can be made during a meeting and some tips you can use to effectively avoid them.
How to run a 4Ls Retrospective
These questions are vital to the retrospective process regardless of the nature or duration of the sprint.
Sprint Retrospective "Stop" Examples
Stop continuing to use an outdated tool that has proven to be inefficient. Stop spending too much time on non-priority tasks that do not directly contribute to project goals. Stop ignoring feedback from team members and stakeholders. Stop adding too many stories into the sprint.
Addressing Conflicts in Retrospective Meetings
Ask team members what they would like to start doing, what they'd like to stop doing, and what they want to continue doing. Those three questions will surface what the team thinks is working well, what isn't working, and potential solutions. You will likely have multiple retrospectives with the same team.
The 5 Cs of Scrum refer to the core values that guide behavior and decision-making in the Scrum framework: Commitment, Courage, Focus, Openness, and Respect, which empower the pillars of Transparency, Inspection, and Adaptation, fostering trust and successful product development. These values help teams navigate complex projects, encouraging individuals to commit to goals, have the courage to tackle tough problems, focus on sprint work, be open about challenges, and respect each other as capable individuals.
3 Pillars of a Retrospective
An icebreaker is a great way to get your team talking in a fun, easy, and engaging way. It helps everyone feel comfortable and sets a positive tone for your retrospective. This is an optional step. You can set up different types of icebreakers: A random icebreaker based on a category.
The purpose of the retrospective meeting is to: Evaluate how the last sprint, iteration, or work item went, specifically around the team dynamic, processes, and tools. Articulate and stack rank the items that went well, and those items that did not. Create and implement a plan for improving the way the team does work.
Retrospectives should be easy in theory. Just ask a few questions – What went well? What didn't go well? What did we learn?
The 3-5-3 rule in Agile (specifically Scrum) is a simple mnemonic for the core components of the framework: 3 Roles (Product Owner, Scrum Master, Development Team), 5 Events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and 3 Artifacts (Product Backlog, Sprint Backlog, Increment). It serves as a quick checklist for teams to ensure they are implementing Scrum correctly, promoting transparency, inspection, and adaptation for better value delivery.
To use the Fibonacci sequence in scrum, most teams do a round-robin or all-at-once assignment of a number. By holding up a number of fingers or a card with a number on it, an individual expresses which Fibonacci number corresponds with the scope of the work item.
In Scrum, two practices that are NOT allowed are Hardening Sprints and Release Sprints.