If you are ever in the need to fold some paper airplanes for a training or something, you can use this page as inspiration đ

Just a site where I archive interesting reads I've encountered online
If you are ever in the need to fold some paper airplanes for a training or something, you can use this page as inspiration đ
Copied this post from: https://retromat.org/blog/best-retrospective-for-beginners/
Positive & True
Why: Create a positive vibe and give everyone an opportunity to speak.
How: Ask your neighbor a question that is tailored to get a response that is positive, true and about their own experiences, e.g.
Then your neighbor asks their neighbor on the other side the same question and so on until everyone has answered and asked.
This will give everyone a boost and lead to better results.
Learning Matrix combined with Lean Coffee
Why: Learning Matrix is a great multi-purpose method that
has âappreciation for othersâ built-in. I use it to gather topics and
then use Lean Coffee to structure and time box the conversations about
these topics. I rely on Lean Coffee a lot!
How: Show a flip chart with 4 quadrants labeled â:)â, â:(â, âIdea!â, and âAppreciationâ. Hand out sticky notes.
Worked Well, Do Differently
Why: Keep track of suggested action items
How: In preparation for the retrospective head 2 flip
charts with âWorked wellâ and âDo differently next timeâ respectively.
Write down suggestions for actions that people mention during Lean
Coffee. State clearly that these are only suggestions for now. The team
will vote on these later.
When all Lean Coffee time is talked up, ask if there are any more suggestions for actions. If so, let them write in silence for a few minutes â 1 idea per sticky note. Let everyone read out their notes and post them to the appropriate category. Lead a short discussion on what the top 20% beneficial ideas are. Vote on which action items to try by distributing dots or Xâs with a marker, e.g. 3 dots for each person to distribute. The top 2 or 3 become your action items.
AHA
Why: Demonstrate the usefulness of retrospectives by asking for lessons learned
How: Throw a ball (e.g. koosh ball) around the team to
uncover learning experiences. Give out a question at the beginning that
people answer when they catch the ball, such as:
Depending on the question it might uncover events that are bugging people. If any alarm bells go off, dig deeper.
You need at least 1 hour of time.
This article is copied from the email I’ve received from Corinna of Retromat. Subscribe to her newsletter here to get more of these useful tips.
A Scrum Master from the financial industry shared a problem with me:
“My gnarly problem is that I have one member of my team that doesnât
like to participate in our ceremonies. Her body language shows it, but
her words never do. She doesnât really talk during any of the
ceremonies, just tells our manager that she thinks they are a waste of
time.
I keep trying to play games and spice things up and Iâve tried the
boring, to the point method of: works well, not so well, and needs
improvement âŚ
I just canât get her to engage! Any help on this?”
This seems to be a very common problem. Iâve certainly had it. Here, I’ll try to keep a focus on retrospectives although it seems to be a larger problem.
In a live coaching situation there are loads of good questions to ask: How does the team react? Was there ever a retrospective during which she was engaged? What is she like outside of the retros?
Without knowing many of the specifics, here is some generic advice.
In general, Iâve stopped forcing people. As Marshall Rosenberg said, you cannot make people do anything. We certainly canât make them âbe agileâ. If she doesnât want to be there, she wonât engage. What would happen if she didnât have to come? How would that affect the team? How does it affect the team now that sheâs not engaging?
Iâve often seen teams invest a lot of energy trying to include someone who didnât really want to be part of it. Not everybody is cut out for agile. Not everybody can be won over. Thatâs okay. Time will tell if she wants to work in an agile team or not. Sometimes itâs best for everyone if someone leaves the team â As graciously as possible: Let everyone save face. Certainly no mobbing!
But weâre not there yet. Everybody deserves a fair chance and weâre trying to include someone.
She gave a reason for her disengagement, at least to the manager. And itâs a valid reason. Veronika Kotrba and Ralph Miarka taught me: âEverybody is the expert for their own situationâ. If she thinks itâs a waste of her time, then itâs a waste of her time. Period. The question is: What would make it worth her while?
What is your relationship like? Is that something that you can ask her? Without being defensive or reproachful? With a curious mindset because you would honestly like to know? That would be my preferred route. And you can phrase it very positively: âWhat would you want to have happen that would make the retrospective a good use of your time?â
If you feel like you cannot approach her directly, you could try Outcome Expectations. Maybe she will tell what would make a retrospective valuable to her.
In the Retromat
1) If people donât speak early on in a meeting it gives them silent permission to stay quiet. Itâs part of the duties of the âSet the Stageâ activity to give everyone the opportunity to speak within the first 5 minutes.
2) Youâve already mentioned body language. What about her position in the room relative to the other participants? A lack of involvement might manifest in sitting outside of the inner circle. Luckily positions also work the other way around: If I can coax a person to join the inner circle they will often also engage more.
When I start with a new team I often run ESVP in one of the first three retrospectives. Iâm fully prepared to let Prisoners go. Iâve only ever had Prisoners once (in a retro with 25 people). I invited them to change their minds and then gave a 5 minute coffee break to let them slip away quietly. (ESVP was anonymous, of course. I honestly canât remember if everyone came back or if the 2 prisoners stayed away.)
I assume your team is not that big and it would be obvious who the prisoner is anyway. Plus, youâve already worked with that team for a while. Thatâs why I wouldnât use ESVP here, unless you think it might surface some other, less obvious Prisoners.
ESVP is something you might consider for a future team.
Phew, thatâs it.
tl;dr Donât force her. Find out what would make it worth her time.
In this Scrum Tapas video, Professional Scrum Trainers Todd Miller and Ryan Ripley discuss what it means to be a Professional Scrum Master. Â They look at behaviors, qualities and a big focus on
Quick takeaway tips:
Your team adopted Agile to get betterâto accelerate delivery and improve performanceâbut now that youâve been at it for a few months, it doesnât feel like itâs fulfilling the promise. Youâre following the practices. Youâve got the routine down. You expected to transform to a new way of working, but itâs starting to feel like Agile is just a set of handcuffs, not the solution you were looking for.
Read the complete article here: https://www.excella.com/insights/9-signs-youre-struggling-with-agile-adoption
A nice Trello board from The Liberators that holds a lot of cool ideas to help you facilitate as a Scrum Master. Find it here: https://trello.com/b/oC3oBEvY/facilitation-toolbox
Reading time: 3 minutes
The right answer to the question about scope, budget, and deadline is not to go along with the line of thinking thatâs behind it. Instead, offer management a better way to manage the risks of a project. Offer them a visible and transparent process like Scrum that allows for frequent change and makes the progress of teams visible on a transparent backlog. Scrum will not magically make your project succeed, nor will it prevent mistakes and failures, but it will make them less costly because you can detect them more frequently as part of the iterative nature.
Read the complete article here: https://medium.com/the-liberators/the-agile-response-to-how-much-will-it-cost-and-when-will-it-be-done-86d907573871
As a Scrum Master, you have a responsibility to your teams, the product owner, and also the organization. Do more than regurgitate whatâs written in the Scrum Guide. Sure, know your sh*t, but donât be a jerk about it.
Learn. Grow. Share. Donât be stagnant. Donât be a Scrum bully. Read the full article here: https://medium.com/serious-scrum/dont-be-a-scrum-bully-d61d0fef022e
What does Pac-Man and prioritizing a backlog have in common? Read it in this great article: https://medium.com/serious-scrum/pac-man-and-priority-a-backlog-story-e31632eb3921
A great exercise for a better understanding of people is to capture what you know about them in personal maps.
Read all about them here: https://management30.com/practice/personal-maps/