3 min read
- Introduction
- Instructions for running the retrospective
- 1. Preparation
- 2. Team Gathering
- 3. Setting the stage
- 4. Reflection
- 5. Sharing
- 6. Identifying Action Items
- 7. Following up
- Final thoughts
Introduction
The Four Ls retrospective is a simple but effective method for a team to reflect on their previous sprint and identify areas for improvement. The method is built around four key questions:
- What did we learn?
- What did we like?
- What did we lack?
- What did we long for?
By focusing on these specific areas, the team can gain a deeper understanding of what went well and what did not, and develop actionable steps to improve in the next sprint.
Instructions for running the retrospective
1. Preparation
Before the retrospective, make a decision as a team on the time period you will be reflecting on and prepare four areas on a whiteboard labeled "Learned", "Liked", "Lacked", and "Longed for”. For remote teams, you can use a shared document on Notion/ Trello /Confluence.
You can use the 4Ls Retrospective Template for Notion.
2. Team Gathering
The retrospective is usually run by the Scrum Master, but all members of the team should be encouraged to participate.
3. Setting the stage
At the start of the meeting, inform your team of the following:
- We're taking the time to talk about how we worked in order to see where we can improve.
- We're coming into this meeting with the understanding that everyone did their best given their knowledge and tools.
- This meeting is a secure environment. Nothing shared will be used against anyone.
- We're here to learn, not to punish.
4. Reflection
Explain the four lists to the team: Loved, Longed For, Loathed and Learned.
What you loved about your work during that time period. This is something you want to continue doing or do more of in the future.
Something you wish you had. More people, more time, or more coffee. Nothing is off-limits.
What made life more difficult back then. What are you hoping never happens again?
What you've learned from your successes and failures.
Set a timer for 10-15 minutes for team members to reflect on the previous sprint and write down their thoughts on the Four Ls (learned, liked, lacked, and longed for). Setting a time limit assists team members in focusing and prioritising their thoughts, ensuring that everyone has an opportunity to share and that the retrospective meeting does not run over.
5. Sharing
When the time for reflection is up, the team can begin sharing their thoughts. Beginning with the "Learned" category, team members can share one item at a time, and the Scrum Master can record it on the corresponding area of the whiteboard or in the 4Ls Retrospective Template. After that, the team should move on to the next category, "Liked," and so on until all four categories have been discussed.
6. Identifying Action Items
Once all of the ideas have been shared and written down, the team should go over the items in each category and identify action items to improve. Here are some suggestions
- Take one action to get something off the LOATHED list.
- Take one action to amplify something from the LOVED list.
- Use the LONGED FOR and LEARNED lists to help shape the ideas for next steps.
These actions should be specific, measurable, and attainable, and they should be assigned to specific team members with a completion deadline.
Commit to tracking action progress on a regular basis, such as at team meetings or the next 4Ls.
7. Following up
The Scrum Master should arrange for a follow-up meeting to check on the status of the action items and ensure that they are completed.
Final thoughts
The Four Ls retrospective is an excellent way for teams to gain a more in-depth understanding of what occurred during the sprint and identify areas for improvement. It encourages team members to be critical of their work and allows the team to identify and implement concrete steps for improvement. It is also simple to implement and understand, making it a valuable tool for any team using an Agile development framework.
