What is it?
Sprint is about to be completed, and now is the time for a retrospective to look back at what has happened and find out what needs to be improved.
Lets dig down with the team about the things that you’ve Liked, Learned, Lacked or Longed For.
Don’t forget, the team might talk about the below topics and not about the product itself
- Behaviors
- Tools
- Team Policies
- Processes & Scrum’s Events
A common pattern for retrospective facilitation can be,
- Ice Breaker
- Revealing the thoughts
- Finding Actions
- Giving Kudos
Why it is important?
Scrum Team gathers feedback each and every Sprint. One for the Product that is being created at the Sprint Review and one for the Team at the Sprint Retrospective.
Liked Learned & Lacked technique focuses on the Team’s current state and tries to find out what needs to be adapted without creating confusion and ensuring transparency in every team member’s eyes.
How can I do it?
- You can check the mural template out and create a copy.
- You can ask the team how they feel. Let them show their states by dragging the orange balls to the related smileys to create a team emotion chart.
- You can talk about if you see any patterns in the emotions chart. – Seems like we’re all tired/happy, etc.
- You can let the team talk if anybody needs to state something.
- You can drag the team to the bottom area, and let them pick a number, hide the number card, and let the team member answer the question below.
- Next, a team member selects a card and answers a question. This session continues until all the team members answer at least one question – You might want to change questions as you like.
- You can drag the team to the 4Ls area and explain What we Liked, What we Learned, What we Lacked, and What we Longed for.
- You can set the timer, give 5 minutes, enable the Private mode (this keeps authors anonymous), and explain to the team that they need to state clear and understandable sentences.
- After the time box has finished, you can ask the team if they need more time, and if so, wait a bit more. You can finish with ending the private mode.
- You can let the team read the stickies and try to organize the stickies into groups. There will be duplicates or similar stickies relating to the same things.
- You can start to talk about the groups (larger ones can be the first ones since they have more data in them) and ask if anybody wants to elaborate.
- You can ask what needs to be done to improve this.
- You can try to form an actionable commitment sentence. – We’re going to work/understand better, etc. is not going to work out, ask for How are you going to do that, how will you know when if we’ve achieved it, etc
- You can gather the Actions on the Blue stickies on the right-hand sight and let the team order them.
- You can warn the team to keep an eye on the focus and don’t let them commit to all of the items.
- After getting Objectives and Key Results from every team member about the commitments, you can move on to the Kudos part.
- You might want to start a Private mode if you have a shy team. If not, people might want to go vocal and say what they feel and give kudos to any team member about anything they want. You can let them hear what needs to be said or read whatever has been written about the kudos.
- Thank everyone, and ask how this session was.
