One of the critical tasks of a Scrum Master is to help team members contribute to the success of the team. When we look at Anja’s Scrum Master success definition, helping team members directly contribute to the team is very high on the list.
In this episode, we cover how Scrum Masters can help new team members feel like they are part of the team and directly contribute to the team from the start.
Featured Retrospective Format for the Week: What went well/not so well/what can we change?
Anja prefers the classic “What went well/not so well/what can we change?” retrospective format. In her experience, this format gives people the ability to bring up the points that affect them personally. When experimenting with different formats remember that it takes a while for people to get used to new formats.
About Anja Bonatto-Minella
Working with agile and scrum only since for a year Anja still considers herself a scrum-beginner. Before starting at her currrent job which brought her into the world of agile, she studied physics and then worked in research for several years.
Featured Retrospective for the Week: Open Discussion
When the right format is a very simple format, Open Discussion, can be a great start for a team conversation. Jen and Jamie suggest that asking the team members to describe, in their own words, the events of the Sprint, leading to potentially different perspectives. These differences (when facilitated properly) can help the team understand each other better and find insights on how to improve as a team.
About Jennifer Emery and Jamie Cole
Jen and Jamie (sweet and salty as they call themselves) are passionate about people, relationships, leadership, accountability, common sense, and getting sh*t done! Ultimate dream job would be to coach individuals, teams, and organizations in discovering and cultivating potential and doing things better by identifying people’s strengths, passions, and skill sets, along with effective processes and strategy to build a strong, healthy culture.
Featured Retrospective format for the Week: What was good / bad and what actions should we take?
The Good/Bad/Actions format is a simple, yet effective format. Nisha explains how to facilitate this format in a short time frame and how Scrum Masters can prepare to host the retrospective.
About Nisha Balwatkar
Nisha started her career as a programmer for the love of logical reasoning and technology and soon found herself trapped in the mismanagement of software teams affecting the work and efforts put in by the teams. She always had a feeling she could fix it and eventually moved to be a scrum master. She enjoys helping out teams and see the joy of success by identifying and fixing small things.
Tim was faced with a problem. How to be a leader without any formal power. All Scrum Masters and Product Owners who have felt the responsibility, but not any “line authority” have faced the same problem. You need to help move the project along, but you can’t tell people what to do!
In this episode we explore the concept of Lateral Leadership how it can help you as a Scrum Master or Product Owner.
When we can help a team get to a point where they can release software “on demand”, that’s when we’ve had an impact on the team and been successful in our role of Scrum Master. But that’s just the end goal. As Scrum Masters there are a lot more issues to consider, and Eddie explores those in this episode.
Featured Retrospective Format for the Week: What went well / not so well
But beware of the “too many actions” anti-pattern!
About Eddie Kenny
Eddie is an agile coach who has been working with Agile since 2004 using XP, Scrum, Lean, Kanban & Scaled Agile. He coaches teams, scrum masters, product owners, leaders, coaches, organizations and little humans. He likes teaching agile with Lego & games and is also co-founder of the LeanAgileBrighton conference.
Success is an endless journey for Scrum Masters, but there are tools that help us assess where we are, and also what are the areas we are already successful in. We discuss a Scrum Master self-assessment tool developed by Luca Minudel and refer to the Learning Guide for the Certified Team Coach program by Scrum Alliance (not freely available).
Featured Retrospective for the Week: Mad/Sad/Glad
The Mad/Sad/Glad retrospective format, inspired by the Core Protocols is a retrospective format that helps the team discuss the issues that are causing emotional reactions. Emotions are often symptoms of other problems the team needs to process, and this format helps address those problems.
Ivo is an Agile Coach at heart. He tries to live that role every day. His view is that to be somebody like an Agile Coach is a lifestyle, attitude across everything you do. Ivo has been in IT industry about 20 years and has been a Scrum Master and Agile Coach for the last 5 years.
Ben is a project manager with experience in developing digital services and products for worldwide clients. He’s learned some very important lessons and shares some of his key insights with you in this special episode, where we dive deep into the project manager role and the project management world.
When thinking about the role of the Scrum Master, Richard comes up with 4 clear signs that indicate we are on the right path with the teams we work with. In the end, Richard says, we must do ourselves out of a job to be successful Scrum Masters.
Featured Retrospective of the Week: The Amazon Product Review retrospective
Lapsed software developer, agile and scrum learner, tenor, drummer. Richard guides and coaches Scrum Teams and organizations on how to use Agile/Scrum practices and values. Helping to teach, facilitate, collaborate & mentor software development teams, enhancing their agile maturity through coaching technical practices as well as the ceremonies and techniques. Richard likes to help teams and organizations obtain higher levels of maturity, at a pace that is sustainable and comfortable for the team and organization.
When thinking about the aspects that define our success, measuring the critical aspects of our work needs to be part of it. Rade challenges us to try to measure those things that we think we need to improve. We talk about how to measure interactions and the right kind of interactions in the team and between team and stakeholders. Are you measuring the key aspects of your contribution as a Scrum Master?
Featured Retrospective format for the week: Three little piggies