The second is the use of retrospectives as a coaching opportunity for Scrum Masters. In this episode Andrew describes his approach and experience with the coaching retrospectives.
About Andrew Hudson
Andy is a Scrum Master within the Media industry. He’s passionate about making work a motivating, enjoyable and empowering place to be. He wants to help teams and individuals reach their full potential and believes developing the right vision and mindset is more valuable to effective teams than any process or framework.
Scrum Master success is the visible outcome when team members are performing. The role of the Scrum Master is therefore, at least in part, to help team members grow and improve their approach to work, and collaboration. In this episode we discuss the signs that team members may be ready for a jump in performance, and how to support their growth.
Featured Retrospective Format of the Week: #NoFormat
Scrum Masters that have tried many formats in their Retrospectives may grow tired of the structure that the default Agile Retrospectives book recommended back when Retrospectives were “new”. Gilberto eventually got tired of that approach and created a new approach to retrospectives. Listen in to learn about how an experienced Scrum Master now oragnizes his Retrospectives alone or with the help of team members.
About Gilberto Urueta
Gilberto is a Berlin-based Scrum Master. He is passionate about Agile, Lean, Scrum and most of all complexity. He is currently working at Takeaway, a leading online food delivery marketplace in Continental Europe.
Retrospectives are a critical tool for the Scrum Master. How we use them, how we treat the information from them is critical for our success. In this episode we explore how we can approach retrospectives from our Scrum Master’s role point of view.
Featured Retrospective Format of the Week: Hot Air Balloon
The Hot Air Balloon is one of the many metaphor-focused retrospective formats. These formats help the teams talk about the real problems without the pressure of being exact or literal in their descriptions. “It felt as if we had too much ballast”, can be the conversation starter that leads to finding previously undiscussed (and undiscussable?) blockers for the team.
About Zeshan Ilyas
With a firm focus on Agile and Scrum methodologies, Zeshan has worked within high profile organisations, including the HSBC, Capgemini Financial Services, Talk, Talk, and many more.
Having worked with Agile companies for many years, Zeshan identified a need for a community of Agilists in Pakistan, which would bring together professionals adopting an Agile or Scrum approach, help increase awareness of Agile.
As Scrum Masters it is easy to get focused on the team or the organization. However, the customer is the reason for the work we do. In this episode we discuss some of the metrics or questions we can use to assess our success as Scrum Masters. A special focus on the customer is part of the mix!
Featured Retrospective Format of the Week: Constellation exercise
The Constellation Retrospective starts with the team standing in a circle, then the facilitator asks a question with a yes/no or agree/disagree answer, and the team moves away from the center of the circle if they say “no” or disagree, and move towards the center if they say “yes” or agree. This exercise allows the teams to see where each team member stands, and helps recognize possible differences that need to be addressed. David also shares a tip on how to make these retrospectives deliver anonymous information that is useful for the Scrum Master but can avoid unnecessary conflict.
About David Spinks
David has over 15 years experience in the IT industry. He began his career as a software developer before becoming a Scrum Master in 2012. He calls himself an ‘agile adventurer’ and believes in continuous learning in himself and others. His passion is getting the best out of teams and seeing people reach their full potential. He has worked in a variety of industries, including eCommerce, social housing and education.
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.
When we start our roles, we often (and rightly so) focused on the process. How to get people to understand and benefit from the power of Scrum. This focus on process may seem counterproductive because, after all, our success depends on the success of the people around us. But is it? Listen in to learn how Ryan uses his process experience to build trust with the team, which he later on turns into a critical ingredient for his own success as a Scrum Master
Featured Retrospective format for the week: “Proud, thankful, learned”
Ryan breaks the rules once more by introducing, not one, but 2 retrospective formats that empower the team to find, and focus on the most important improvements for them.
The first format is “Proud, thankful, learned”. Three simple headings that help the team focus on, and amplify the positive things that happened during a Sprint. Consider also using this (in a shorter version) as a check-in exercise.
The second format is “Lean Coffee”. A simple way to generate and prioritize possible improvement items.
About Ryan McCann
Ryan is a former waiter, car detailer, line worker, cemetery worker, intern, financial analyst, tech support rep, team lead, QA manager, Scrum Master and Product Owner. Current husband, father, school board member, community volunteer and agile coach. He believes in building trust and social capital, which is not easy for any of us (himself included)…Ryan does his best everyday to help teams make this happen.