Scrum Masters must pay attention to how Scrum teams adhere to the Sprint Goal, how they collaborate with the Product Owner and other aspects that help teams perform.
In this episode, we talk about 5 different success metrics for Scrum Masters.
Featured Retrospective Format for the Week: The Sailboat Retrospective Format
Scrum Masters usually have multiple retrospective formats in their “back-pocket”. The Sailboat Retrospective format is one that is easy to setup (a flipchart and markers/post-its are enough), and can engage the team in a creative assessment of their ways of working.
About Nedeljko Damnjanovic
Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.
For Scrum Masters, success must include the team’s success. In this episode, we talk about the metrics and the type of feedback we must help teams collect, and how to use that to measure our Scrum Master success as well.
Featured Retrospective Format for the Week: I Like / I Wish and other games
Sometimes Scrum Masters must focus on helping teams feel at home, so that team members can discuss the issues that bother them. In this episode, we talk about how a CEO/CTO can derail a retrospective and what kind of games we can use to help teams focus on improving, even when managers are present in the retrospectives. The retrospective format we talk about is “I Like / I Wish”.
In this segment, we refer to Retromat, a service that helps you choose games/activities and plan your retrospective.
About Henrique Centieiro
Henrique is a Blockchain Product Manager (i.e. dealing with the blockchain related features/user stories of the product). He is passionate about teams and agile, using scrum to manage even his personal tasks.
Ajeet has come to value 4 specific ways to measure his impact as a Scrum Master. In this episode, we review these 4 benchmarks and how he uses them regularly to improve his approach.
Featured Retrospective Format of the Week: Well/Stop/Start retrospective format
In the Well/Stop/Start retrospective format (see a facilitation guide here), we have a simple format that can trigger important conversations. Especially when team members see each other’s contribution to those 3 categories.
This is a format that suits very well teams that are action-oriented, and have a high degress of collaboration already.
About Ajeet Singh
Ajeet is an IT professional with 17 years of delivery experience in application development, system integration and software testing. He’s served as a ScrumMaster for over 3.5 years for the clients of USA, UK and Australian geographies.
We like to keep our retrospectives fresh. We find it helps to reveal things we might not otherwise have found if we alter the format frequently. With this goal in mind, we follow a simple system:
Once a month we use our ”normal” retro format. Everyone in the team is familiar with this, and we can perform them quite quickly, with minimal prep work and explanation required. Basically, effective with very little admin.
Once a month we have our ”experimental” retrospective. A little more set-up time required, but a good opportunity for experimentation and explorations.
This is the story of one such retrospective.
Obviously, you can perform many Agile practices, but not be Agile. However, there are a lot of practices out there and sometimes teams can become focused solely on those that they are currently using, rather than looking at other tools they might bring to bear. This is where the Agile Practices Retrospective comes in.
In preparation for the retrospective, we created cards with various Agile practices as headlines, and a brief explanation of each listed on it. I also color coded them under various categories so they could be more easily identified from afar. Then we simply taped all these cards to a wall in their respective categories. There were about 50 cards in all.
With over 50 cards, there was a lot of information. We split into groups and started categorizing the cards under a new set of headings, it was made clear to all that they were not expected to read all the cards.
Doing (Working Well): Things we are currently doing, and quite happy with the way they currently work.
Doing (Could be better): Things we are currently practicing but could use improvement.
Not doing (By choice): Things we are not currently practicing, but have made a choice not to use in our context.
Not doing (Not tried): Things we are not doing, and have never really tried.
WTF!?!: We have no idea what this is, or what it means.
Deciding what to focus on
We obviously cannot talk about all these things. So, we used dot voting to decide what topics to focus on. Each team member was given 3 ”dots” for each of these types of vote:
We should start and or alter this practice in some way. (Indicated by a dot)
We would like to learn more about this practice. (Indicated by a +)
I also printed out simple list versions of the same information, as I knew it would be hard for everyone to gather around the board when deciding how to use their votes. Despite this, this was still not as successful as we would have hoped. Part of this is because we are actually two teams and our 3 customer representatives, so the whiteboard was too crowded. I feel this would go better with a single team.
Discussions and action points
We had open discussions and tried to create action points/experiments around the topics we had discussed. I will just give a very brief of what we arrived at:
Root Cause Analysis/ 5 Why’s
We even arrived at the fact that without formal tools, we are still quite good at root cause analysis. But perhaps a formal tool might reveal something we would have otherwise been unaware of.
Experiments: 1)Focus on using our discussion time during retrospectives (Generate Insight) to use more formal tools like 5 why’s.
2) When events are added to our timeline at daily stand-ups, then we should also consider doing a more in-depth analysis of those items.
Discussion: We felt that we very likely do have a product vision, and even a fair amount of impact mapping done for that, but this is not communicated to the entire team at a frequent enough rate. Also, we need to get better at following up these things.
Experiments: 1)Make the product vision more concrete and communicate it at a regular interval.
2)Follow the vision and impact map up at a regular interval.
Behaviour Driven Development (BDD):
Discussion: This is a discussion point we wanted to learn more about. So, the discussion was brief. We basically arrived at the fact that it was intriguing and we want to know more.
Experiments: 1)The two team members who know something on the subject will provide some links and a quick intro for everyone else.
2) Some of the team will experiment with these concepts in our ”Brain Day” next week.
This retrospective was reviewed well by the team, everyone generally liked it.
It was a fairly active retrospective, because of all the moving things around and working in teams, so the energy level remained high throughout.
Probably the best aspect of this retrospective was the addition of fresh concepts into the team, the idea to focus on things we wanted to learn more about was a good one. In the future, we would probably recommend only focusing on these things.
There was a fair amount of prep work involved in this one, although I consider it worth the investment, it wasn’t free. Hopefully, a bit cheaper for you, as we have provided the work we have done. Once again: https://tinyurl.com/l8loec6
It was too hard to get an overview with so many items, this may have been due to team size, and might have been possible to mitigate by having the team read the list beforehand.
Despite there being so many items, the list was not even close to exhaustive, and it was hard to leave off some practices that really should have been included.
Jeff is an Agile Coach who considers the discovery of Agile and Lean to be one of the most defining moments of his life and considers helping others to improve their working life not to simply be a job, but a social responsibility. As an Agile Coach, he has worked with driving Agile transformations in organizations both small and large.
Jeff is also involved in the Agile community and is one of the founding members of Gothenburg Sweden’s largest agile community at 1500+ members , and he also organizes the yearly conference www.brewingagile.org.
When Jeff discovered that Menlo Innovations (from the book Joy, Inc. by Richard Sheridan) was a drive away from his workplace, he got a few people together and started a journey that would change his view of how work should work. He decided that his work as a Scrum Master was about improving lives.
Featured Retrospective format: The Sailboat Retrospective
In the sailboat retrospective we use a metaphor to help the team identify the goal, the obstacles (the rocks), the drags on the team performance (the anchor) and the things that push us forward (sailing wind). Through metaphor we help the team explore ideas that they would otherwise skip in a more structured retrospective.
About Jeff Maleski
Jeff is passionate about working with and building up both individuals and teams using ideas from Jurgen Appelo’s Management 3.0 and Dan Pink’s Drive. When leading project teams, Jeff strives for empirical based planning and forecasting, continuous learning, and delivering high quality software products that exceed expectations. Jeff believes in leading by actions and focusing on building relationships with others.
Total time execution for this format: 60-90 minutes
The purpose of this dynamic is for everybody to participate and share their feelings, perceptions and opinions without even talking (at first).
For the team: They can see themselves and understand their colleagues from a different perspective, they can really feel others because they are not talking or trying to gain their position within the room. They just observe, feel and act their feelings.
For the facilitator: There is something so powerful about standing in a circle. You know it if you do your daily meeting. We can immediately see the whole picture, the real feedback from the team without mixed perceptions or words, which generally cover the real significance. We can say: “bodies don’t lie”.
Address and specify the situation the coach is sensing and the team doesn’t feel like talking about this for of any reason (e. it’s too painful, they feel uncomfortable, and some team members are unaware).
What you need – Preparation
Find out the number of participants first: The room where the retrospective will be run must have enough space for everybody in the team to be able to stand up in a circle (and move from a tight to a larger circle).
Adhesive tape: to post the cards on the wall or board before the discussion.
An element or object: big enough to serve as a reference for the responses, noticeable and “good looking” (I wouldn’t recommend a trash bin), and not so distracting or not so high that participants can’t look at each other’s faces. (e., it could be a mini statue, an umbrella stand, or a little circle drawn in the middle of the room).
Write down statements or questions: to read out loud on cards so the team can express their response about these topics.
I feel free to express in this retrospective.
I am satisfied with the results of this sprint.
I am happy with the quality of our code.
I consider our releases are easy and smoothly delivered.
I think my daily work is recognised.
Do you feel safe enough to be able to express in this retro?
Are you satisfied with the team collaboration?
Do you consider the technical debt has been reduced in this sprint?
Do you feel motivated in your daily work?
Do you think you are making an impact on people’s lives with our product?
How to run the retrospective
A. Introduction (1-5 minutes)
Brief check in: Make sure the team is relaxed and ready to start. A brief check in exercise can help to set the environment.
Explain the rules: Position the element in the centre of the room to act as a reference for the team members. No one is allowed to talk during this exercise. Only explain that standing closer to the object will mean “YES”, “I TOTALLY AGREE”, while being farther will represent of “I DON’T AGREE”, “NO”.
B. Running the exercise (10-15 minutes)
Read the cards out loud one by one and leave time for the participants to respond with action.
Observe the situation: They will individually respond by getting closer or farther from the object. You will notice people in between: “I AM NOT SURE” or “MAYBE”, just watch. Take mental notes, or have someone external to the team help you with the notes.
Ask the participants about their feelings: Listen closely to what they went through during the exercise. You will notice the different reactions and realisations. That input is invaluable for you as a facilitator to go on with the discussion. Sometimes the participants are so amazed they need time to stay calm and reflect about what had just happened, especially when one of the topics was revealing for the team. Maybe a relaxation exercise is handy here, if necessary.
C. Sharing thoughts (10-15 minutes per topic)
Post the cards on the wall and vote: Tell them to vote prioritising the situations according to what they consider critical to address now for the team.
Select the topics: The most 2 or 3 voted topics will be discussed in pairs or mini teams of 3 or 4 people, according to the time left for the retrospective.
Discuss: Start by the most voted one first. Set the time for discussion. Let the conversation begin!
D. Taking action: (15-20 minutes)
Share results: After each topic discussion, share their opinions, proposals, options and work to find the next steps to follow.
Make a commitment: The result may be an experiment to try: set the hypothesis, metrics, who will be accountable, and time to check again.
How does this topic make you feel?
Do the other team members feel the same? Why?
How can you contribute a solution to the situation you have just found?
What could we do to improve this particular subject?
Is there anything else creating this perception?
Where can we start? Who else can we involve in the solution?
Why is this important for the team?
Additional tips, comments and alternatives:
It is very important to find the right questions/statements for the team to elicit reflection, especially when you already know the situation, and they can’t see it yet.
Questions and statements are good for The participants tend to repeat them in their heads, so they get to their feelings and act accordingly.
Follow a defined format, questions or statements. Following all at the same time might be confusing.
Choose a maximum of 10 topics to avoid losing focus.
The topics can be technical, human, process or product related; there are no limits here. You could even use this dynamic for an agility assessment, where the statements or questions are related to the agile principles.
It has been very useful to me during facilitation in almost any case, with people; talkative or shy, who were new or had been working together for several years, who weren’t participating too much lately in the retros, and so on.
Carolina is a natural connector and team enabler, great at finding people’s strengths and helping them combine their skills to become high performers in the organisations and obtain better results every day. She currently works as an Agile Coach and is a dedicated Creative Change Agent, specialised in problem solving and communication.
One of the Agile principles states that “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” These “meetings” are more likely called Retrospectives and can be held in many different formats (here are some examples https://trello.com/b/40BwQg57/retrospective-techniques-for-coaches-scrum-masters-and-oth er-facilitatorsand http://retrospectivewiki.org/index.php?title=Retrospective_Plans). The most famous is the “Mad, Sad, Glad” format, and many others are just variations of this very basic format.
Read on for the “positive retrospective” format and exercises.
These formats are based on the aim to analyze the previous team’s activities in order to achieve better results. Sometimes, it may also help to analyze the successes of the team in order to understand what helped in achieving them and how to replicate such successes: that’s what I call a “Positive Retrospective”.
The period we may wish to analyze may vary; last iteration, last month, last year and so on. What do we need to organize this retrospective? The usual materials such as some stickers, pens and a whiteboard or a flipchart.
The first action to take is to create a collaborative and positive atmosphere, so ask the attendees to write down some few words of appreciation for a colleague (or more), thanking him/her for something he/she did during the given period, for the person or for the team. Give the team 5 minutes to write.
Then ask each attendee to read aloud what they wrote, speaking to the colleague they want to thank. This phase shouldn’t take more than 5-10 minutes.
The next phase is to list all the positive results achieved in the period.
Ask the attendees to write down on the stickers all the positive results achieved, using a short statement (one per sticker) – they will be given the opportunity to explain in the next phase. Give them 5 minutes to write.
Now ask the attendees to explain the individual positive issues, one by one. They should be concise in their description but still be able to let the other attendees understand the issue. Then the sticker is pinned to the whiteboard. If any other attendee has a similar issue, he/she has to discard it. Please be careful to avoid starting any discussion. This is the time to list the results and not to discuss them (moreover, the discussion will be shaped in a particular way, as we will see in the following stage).
Once everybody has explained their issues (this stage should last no more than 10 minutes), you’ll have all the stickers on the whiteboard. It’s time to vote.
Each attendee will have six votes to give to the issues stuck on the whiteboard: three votes to vote the issues by its intrinsic or technical value (for example, the team reduced the technical debts by 50%, or has stabilized the daily standup) and three votes to vote the issues by the positive impact it had on the product (for example, thanks to this new feature, the customer increased his sales by 20%). You can use any means to vote: in my example, we used little red self-adhesive dots for one and green for the other, but you can use different signs, different colored pens, and so on.
Why differentiate this way? The answer is easy: teams tend to identify their success with the product’s success; we delivered this feature, the customer were happy, we eliminate that bug and so on, forgetting that with success stories, many other aspects must be considered. For example, adopt a more effective framework for the chosen programming language, start unit testing, practice a scrum ceremony in a more efficient way and so on. The team must learn these positive issues as well, as they allow the team to be more effective (as per the above mentioned Agile principle).
Once the voting is finished, just rank the issues by the numbers of votes (any kind).Voting and ranking shouldn’t take more than 5 minutes.
Once the stickers are rearranged on the whiteboard (the most voted ones are on top) you can start to discuss. The format may be free (you can discuss any issue as long as you want), or fixed (an issue can be discussed for a maximum amount of time of 5 or 8 minutes, for example). Choose the format you like, what counts is the discussion itself.
Ok, let’s discuss, but about what? We usually discuss what’s going wrong, and how to fix it. Now, here instead, we’re discussing what went right! Well, we can first identify what made that positive issue possible. Usually, we can identify two main paths: one internal to the team, and one external. The internal one refers to all the actions the team takes to achieve a result, which may impact the team, the process or the product. For example, by autonomously adopting a new programming framework the team was able to deliver those given features and the customer was very happy. Note the word “autonomously”: the team was not forced by any external entity to take that decision, but reached a result that had an external impact anyway.
The external path refers to all those actions taken or conditions set up by the system (your department, your local agency, your company, and so on) that made it possible to achieve that given result. For example, the team was able to learn how to deal with noSQL databases thanks to a dedicated budget for training on new and emerging
technologies/methodologies. In this case, an external reason made it possible to achieve an internal positive result. Nevertheless, we mean to say that an internal result will sooner or later reflect itself into an external positive result (or at least, this is what the system hopes…).
The discussion stage may last up to 50 minutes, to keep the whole retrospective no longer than 2 hours.
And now, just like any Retrospective worthy its name, let’s write down some action points.
Like any positive issue in any field, we aim to replicate it and also do something to improve that experience to feel even better. So we can define the underlying actions that will lead us to even better results. Some questions easily come to mind: can we replicate the positives we had during the period, applying them to current or new issues? For example, we may ask for a new course to learn a new language to create a new software asked by our customers. Or, can we improve the path that led us to have positive results to have better results or even the same results but in different areas? For example, improve the continuous integration process to have a faster/safer deployment of our deliverables.
Or just have more frequent retrospectives to improve our work!
Discussing and writing the Action Points may take up to 20 minutes.
Now the meeting may be closed. See you next Retrospective!
About Enrico Di Cesare
Always interested in improving the quality of the software produced for himself or for his customers, Enrico became an Agile enthusiast as soon as he discovered it. With extensive previous experience as a Project Manager and Coordinator, Enrico works as an Agile Coach, Scrum Master and Product Owner, introducing, mastering, facilitating and refining the adoption of Agile with new collaborative tools.
Retrospectives are a key part of any Scrum team’s process. However, they are also key for Scrum Masters to evaluate their performance. Sven shares with us a process he uses to help him detect possible problems, and invest in solving the right problems to help the team, and himself succeed. We discuss plenty of practical advice regarding the structure and the content of Retrospectives.
About Sven Schnee
Sven started his journey as a developer around the year 2000. He experienced many projects and felt the pain of how traditional approaches to software development failed.
A few years ago he discovered Agile and Lean, and he is not going back.
He is an Agile Coach and Founder of Oikosofy. He wants to bring agile ways of working to a variety of customers from small companies to big enterprises. One of his key strengths is helping teams evolve on their path to self-organization.
You can connect with Sven Schnee on twitter, and link with Sven Schnee on LinkedIn.
You can read Sven Schnee’s blog The Product Owner Toolbox.