Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Rohit discusses his experience as a Scrum Master working with a back-end team suffering from high attrition rates. He realizes that the team members feel undervalued and that the monotonous work is affecting their motivation. To address this, he arranged a workshop with the team and leaders, where the team gained new insights into their importance to the organization. The workshop helped the team see the bigger picture and meaning behind their work, revitalizing their motivation. The key takeaway is the significance of creating opportunities for teams to understand their value and fostering open communication to prevent attrition.
Rohit discusses "The Five Dysfunctions of a Team" by Lencioni, which provides valuable insights into team dynamics. The book helped him understand the hidden dynamics within teams and enabled him to observe and analyze their functioning. It particularly highlighted the significance of trust and conflict in team success. Rohit emphasizes the need for adaptability when working with different teams, as each team is unique and requires a tailored approach. Overall, the book enhanced his understanding of how teams work together and his role within them, emphasizing the importance of trust and conflict resolution.
[IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!
About Rohit Ratan Mani
Rohit is an Enterprise Agile Coach, helping Leaders, individuals and teams to develop a growth mindset to be top achievers in their respective work area and in personal life.
You can link with Rohit Ratan Mani on LinkedIn and connect with Rohit Ratan Mani on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Rohit shares his journey from a project management mindset and a need for control to a Scrum Master mindset. As he learned more about being a Scrum Master, he realized he was a bottleneck for the team's progress. Going on leave highlighted the team's dependence on him, and he felt frustrated. This experience led him to embrace the art of letting go and find new ways for the team to work independently. He emphasizes the importance of doing things differently to foster a mindset change. We discuss the conflict between control and empowerment, with the key takeaway being the significance of awareness and a willingness to change.
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Rohit Ratan Mani
Rohit is an Enterprise Agile Coach, helping Leaders, individuals and teams to develop a growth mindset to be top achievers in their respective work area and in personal life.
You can link with Rohit Ratan Mani on LinkedIn and connect with Rohit Ratan Mani on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, Andrew emphasizes the importance of moving POs out of engineering and into the business to better understand business needs. Inspired by Marty Cagan's book “Inspired”, this great PO excelled in writing effective stories and facilitated closer collaboration between developers and customers. They viewed the engineers' involvement with customers as a helpful aid rather than a threat. This shift toward self-management empowered the team and enabled faster delivery of products. A great PO plays a crucial role in fostering collaboration, understanding business requirements, and driving successful outcomes.
In this segment, Andrew discusses the challenges that arise from having a bad Product Owner (PO). These POs excel in discovery but struggle to communicate effectively with the team, leading to frustration and a lack of trust. Andrew suggests coaching the POs in writing clear stories and focusing on value and prioritization. Interrupting the team's work is another issue to avoid. He emphasizes the importance of well-defined acceptance criteria in stories. Andrew also notes that problems with bad POs often stem from organizational issues rather than individual skills. Bringing the team closer to the discovery work can help address these challenges effectively.
[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Andrew Mitchell
Andrew prioritizes people when building products, aiming for happy and engaged employees who create great products and serve customers well. He emphasizes trust, psychological safety, servant leadership, and believes Scrum is the best framework to achieve these goals.
He was also a host of the Product Owner Summit 2023, where we collaborated.
You can link with Andrew Mitchell on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Andrew shares that success is achieved when the Scrum Master can gradually step back and allow the team to navigate Agile events independently. This includes team members reminding each other of Agile values, active participation without the Scrum Master's constant input, and the ability to carry out refinement meetings and handle customer interactions without heavy reliance on the Scrum Master. Avoiding unhealthy conflicts and not making decisions on behalf of the team are key aspects. Conducting team happiness surveys is recommended to gauge team dynamics. Overall, a successful Scrum Master empowers the team and fosters autonomous decision-making.
In this segment, Andrew discusses his favorite retrospective format, which is always “the one that works best for the team” at that time. He shares that a colleague started surveying the team by asking a few questions. The survey is conducted two days before the end of the sprint, allowing team members to think about their answers in advance. This approach generates great conversations during the retrospective and helps facilitate meaningful discussions. Andrew emphasizes that this format leads to valuable exchanges and contributes to the overall effectiveness of the retrospective.
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Andrew Mitchell
Andrew prioritizes people when building products, aiming for happy and engaged employees who create great products and serve customers well. He emphasizes trust, psychological safety, servant leadership, and believes Scrum is the best framework to achieve these goals.
He was also a host of the Product Owner Summit 2023, where we collaborated.
You can link with Andrew Mitchell on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Andrew discusses his change process of transitioning from traditional story point refinement to flow-based metrics and #NoEstimates. He faced resistance at the team and organizational levels. Andrew conducted an experiment using two years' worth of data, showing that story points were not superior to throughput. He presented the results to leadership and the teams, emphasizing the importance of holistic metrics and their impact on predictability and team dynamics. Andrew introduced t-shirt sizing for simpler estimation conversations and highlighted that counting stories was more predictive than relying solely on story points. The episode emphasizes lessons in change management, including metric selection and fostering collaboration and predictability.
[IMAGE HERE] As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.
About Andrew Mitchell
Andrew prioritizes people when building products, aiming for happy and engaged employees who create great products and serve customers well. He emphasizes trust, psychological safety, servant leadership, and believes Scrum is the best framework to achieve these goals.
He was also a host of the Product Owner Summit 2023, where we collaborated.
You can link with Andrew Mitchell on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Andrew discusses a team that struggled with excessive time spent on refining stories and engaging in arguments during daily scrums. The organization was in the early stages of its agile transformation, and the team had difficulty transitioning from detailed requirements. Engineers felt judged by bugs, leading to a fear of making mistakes. To address these issues, Andrew introduced the concept of shared accountability, shifted the team's focus to problem-solving, and encouraged smaller work slices. He also emphasized the importance of prioritizing helping people over solely delivering software. These changes aimed to foster collaboration and a supportive team environment.
In this episode, we refer to the book NoEstimates, and the method it describes that served as inspiration for Andrew’s work.
In this segment, Andrew recommends the book "Leaders Eat Last" by Simon Sinek as required reading for Scrum Masters. The principle of the book originates from the US Marines, where leaders eat their meals after the soldiers. Andrew highlights the key tip of "They would do it for me," emphasizing the importance of leaders who prioritize the well-being and needs of their team members. He describes the book as wonderful, implying that it offers valuable insights and lessons for Scrum Masters.
[IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!
About Andrew Mitchell
Andrew prioritizes people when building products, aiming for happy and engaged employees who create great products and serve customers well. He emphasizes trust, psychological safety, servant leadership, and believes Scrum is the best framework to achieve these goals.
He was also a host of the Product Owner Summit 2023, where we collaborated.
You can link with Andrew Mitchell on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Andrew shares his experience as a new Scrum Master and the mistake he made by trying to replicate a command and control leadership style. The team was demotivated and lacked trust, and Andrew initially felt the need to have all the answers despite his limited experience. However, he learned the importance of admitting mistakes and building trust with the team. He also discusses the transition from project manager to Scrum Master, emphasizing the need to let go of control and embrace shared leadership. Lastly, he advises embracing silence to foster deeper thinking and collaboration.
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Andrew Mitchell
Andrew prioritizes people when building products, aiming for happy and engaged employees who create great products and serve customers well. He emphasizes trust, psychological safety, servant leadership, and believes Scrum is the best framework to achieve these goals.
He was also a host of the Product Owner Summit 2023, where we collaborated.
You can link with Andrew Mitchell on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, Chuck discusses the qualities of a great scrum master who maximizes time and talent within the team. He shares an example of a scrum master who displayed exceptional empathy and understanding of team dynamics, even in remote meetings. This scrum master skillfully selected retrospective formats that facilitated discussions on crucial topics. Additionally, the scrum master played a valuable role in helping Chuck understand his own responsibilities as a development manager. Chuck provides tips on the importance of addressing resistance to change and the scrum master's responsibility in communicating with stakeholders. Overall, a great scrum master possesses empathy, effective communication skills, and the ability to facilitate meaningful discussions within the team.
In this segment, Chuck addresses the issue of scrum masters becoming overly rigid in their adherence to the process, which can lead to conflict within the team. He highlights that successful agile practitioners understand the need to adapt Scrum to fit their specific context. Chuck shares an example of a novice scrum master who insisted on a particular story pointing process, causing frustration among senior developers. He advises providing feedback to the scrum master and encourages self-reflection on whether one is imposing processes on the team. In this segment, we mention the book "NoEstimates" as a resource for further exploration of this topic. The segment emphasizes the importance of flexibility and considering individual team dynamics in Scrum implementation.
[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Charles “Chuck” Durfee
Chuck Durfee is an Engineering Manager in the Denver area. He leads teams to deliver quality software on-time and within budget. With expertise as a Scrum Master and Agile Coach, he uses relationships, teamwork, and a pragmatic approach to solve complex business problems. In this episode, we explore his perspective as an engineering leader, and learn what makes a great Scrum Master from the perspective of the leaders they work with.
You can link with Charles “Chuck” Durfee on LinkedIn and connect with Charles “Chuck” Durfee on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Chuck discusses the qualities that make a successful development manager. While scrum masters are measured on different metrics, dev managers are primarily evaluated based on results and retention. They are responsible for delivering projects on time and within budget, and it is their role to establish effective mechanisms and processes. They also need to consider the people aspect, striking a balance between team demands and the challenges of finding and retaining talented individuals. Chuck advises scrum masters to understand the factors of time and talent and find the right timing to discuss matters with dev managers. The episode highlights the importance of achieving results while managing people effectively in the role of a dev manager.
In this episode, Chuck shares his favorite Agile retrospective format that he used with a team after completing a project using Kanban. He introduced the activity of designing a movie poster (explained here) that would encapsulate the story of bringing the feature to life. The team had a lot of fun with this exercise, and it fostered creativity and honesty.
Chuck explains that the activity of storytelling enabled the team to express themselves in a more imaginative and authentic way. The ultimate goal of this retrospective format was to encourage creativity and facilitate open and honest discussions within the team.
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Charles “Chuck” Durfee
Chuck Durfee is an Engineering Manager in the Denver area. He leads teams to deliver quality software on-time and within budget. With expertise as a Scrum Master and Agile Coach, he uses relationships, teamwork, and a pragmatic approach to solve complex business problems. In this episode, we explore his perspective as an engineering leader, and learn what makes a great Scrum Master from the perspective of the leaders they work with.
You can link with Charles “Chuck” Durfee on LinkedIn and connect with Charles “Chuck” Durfee on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Chuck discusses his experience as a Dev Manager implementing a change process to help a team adapt to a new organizational structure. He started by asking developers to volunteer and assist in refactoring a subsystem using the "strangler pattern." The subsystem was divided into smaller slices and distributed among team members. Chuck introduced the practice of running single test cases before release, allowing others to witness the practical application of Scrum. He emphasized the importance of experiential learning and leveraging previous successful examples to motivate the team. Their efforts resulted in delivering ahead of schedule. Chuck recommends explaining the holistic process and choosing demo-able increments to showcase the benefits of incremental development.
[IMAGE HERE] As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.
About Charles “Chuck” Durfee
Chuck Durfee is an Engineering Manager in the Denver area. He leads teams to deliver quality software on-time and within budget. With expertise as a Scrum Master and Agile Coach, he uses relationships, teamwork, and a pragmatic approach to solve complex business problems. In this episode, we explore his perspective as an engineering leader, and learn what makes a great Scrum Master from the perspective of the leaders they work with.
You can link with Charles “Chuck” Durfee on LinkedIn and connect with Charles “Chuck” Durfee on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Chuck discusses a team he led for a mission-critical software project with structural challenges. The arrival of a new developer from a startup background, while the rest of the team had experience in larger companies, created friction. Misunderstandings arose when the new developer pushed the message "move fast, break things," leading to frustration as the team, and the company were not ready to hear and act on that message. Chuck sought help from his manager, who asked questions to understand the situation. Lessons learned included the importance of setting clear expectations, focusing on people problems, fostering relationships with product managers, and ensuring regulatory clarity. Effective communication and problem-solving within the team were highlighted as crucial elements for success.
In this segment, Chuck recommends the book "The Coaching Habit" by Bungay Stanier, which focuses on the power of asking questions. Chuck highlights that he found seven specific questions from the book to be highly effective in his role. One of these questions is the strategy question: "If I say YES to this, what do I need to say NO to?" This question helps in making thoughtful decisions by considering trade-offs. Chuck also advises staying curious a little bit longer, emphasizing the value of maintaining a curious mindset during coaching conversations.
[IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!
About Charles “Chuck” Durfee
Chuck Durfee is an Engineering Manager in the Denver area. He leads teams to deliver quality software on-time and within budget. With expertise as a Scrum Master and Agile Coach, he uses relationships, teamwork, and a pragmatic approach to solve complex business problems. In this episode, we explore his perspective as an engineering leader, and learn what makes a great Scrum Master from the perspective of the leaders they work with.
You can link with Charles “Chuck” Durfee on LinkedIn and connect with Charles “Chuck” Durfee on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Chuck, a development manager, shares his experience as a team lead and scrum master for a non-software company. He discusses the mistake he made in assuming others had knowledge of agile practices. Through conversations with skeptical stakeholders, Chuck realized the need to ask questions and challenge assumptions. He emphasizes the importance of remaining curious, leveraging proven training materials, and using experiential learning tools like the GetKanban game, Pizza Kanban game, and Scrum Lego City game. The episode highlights the significance of effective communication, managing expectations, and avoiding assumptions when introducing agile methodologies to non-software teams.
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Charles “Chuck” Durfee
Chuck Durfee is an Engineering Manager in the Denver area. He leads teams to deliver quality software on-time and within budget. With expertise as a Scrum Master and Agile Coach, he uses relationships, teamwork, and a pragmatic approach to solve complex business problems. In this episode, we explore his perspective as an engineering leader, and learn what makes a great Scrum Master from the perspective of the leaders they work with.
You can link with Charles “Chuck” Durfee on LinkedIn and connect with Charles “Chuck” Durfee on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Eliza emphasizes that a great PO genuinely cares about the team, the product, and the project. They have a strong desire to perform well and ensure the success of the team. Eliza mentions the importance of reminding the PO to take breaks and rest, if they may have a tendency to shoulder too much responsibility. A great PO should be able to say "no" when necessary, demonstrating their care for the team's workload and effectively prioritizing tasks to align with the product's goals. Overall, a great PO is someone who combines a genuine concern for the team, a passion for the product, and the ability to make informed decisions for the project's success.
In this episode, Eliza discusses the challenges of working with a bad Product Owner (PO) who was new to the company, and exhibited behaviors that were not in the team's best interest, despite claiming to support change and act as a catalyst for it. In meetings, the PO constantly fought against change and advocated for the status quo. Additionally, they frequently interrupted and spoke over the team, and even asked the Scrum Master for more command and control.
Eliza found it confusing that the PO seemed to be fighting against Agile principles and stepping on the team's autonomy. Eventually, Eliza left the company, but learned that the PO had conflicts with other Agile coaches and managers as well.
She provides tips for dealing with such situations, including having one-on-one conversations with the PO and coaching them as part of the Scrum Master's role. Creating a safe space for the team to express themselves without interruptions is crucial, and understanding the perspective and background of the PO is also important. Eliza suggests getting training to better understand the PO's job. Overall, the episode highlights the challenges posed by a bad Product Owner and offers strategies for managing and coaching them effectively.
[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Eliza Gregory
Eliza Gregory has worked as a Project Manager, Scrum Master, and Agile Coach for U.S. Defense and the German automotive industry. She uses teachings from Agile to hone her writing process, and has a new novel out this May about an IT Project Manager coping with burnout and work stress. Originally from Virginia, she now resides in Bavaria, Germany.
You can link with Eliza Gregory on LinkedIn and connect with Eliza Gregory on Twitter, and you can read about her novel Painting the Whiskey Blue.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Eliza explores success for Scrum Masters and discusses a situation where success was achieved when her team no longer relied on her. She describes an anti-pattern where teams still ask for permission as if she were their boss, indicating a lack of autonomy. Eliza shares an experience with a team that was initially closed off to change. A manager's demoralizing comment caused the entire team to shut down. However, during a retrospective, Eliza was able to facilitate a discussion by getting one team member to open up, leading to the team collectively sharing their feelings about the manager's comment. This retrospective proved to be a success as it allowed for an open conversation about a difficult topic with a little prompting from Eliza. The team then took the initiative to address the issue themselves. Eliza provides tips, noting that when the entire team realizes they are on the same page, they gain the courage to bring up important topics. She also highlights the significance of shared experiences within the team, as it contributes to their overall growth and effectiveness.
In this segment, Eliza introduces the concept of the "Letter From the Future" and shares her experience of implementing it for the first time. She advises that it may require explaining the concept multiple times before being able to successfully conduct it. The retrospective follows a specific format, beginning with setting up a digital whiteboard. Eliza then assigns a postcard to each developer. To engage the team, she appeals to their culture. The main activity involves writing a letter to oneself from the future. Eliza highlights that the different format of this retrospective helps the team think differently and encourages fresh perspectives.
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Eliza Gregory
Eliza Gregory has worked as a Project Manager, Scrum Master, and Agile Coach for U.S. Defense and the German automotive industry. She uses teachings from Agile to hone her writing process, and has a new novel out this May about an IT Project Manager coping with burnout and work stress. Originally from Virginia, she now resides in Bavaria, Germany.
You can link with Eliza Gregory on LinkedIn and connect with Eliza Gregory on Twitter, and you can read about her novel Painting the Whiskey Blue.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Eliza discusses a specific experience in a new company where processes were not yet solidified. She describes a situation where an external person, known as the "JIRA god," had access to her team's backlog and re-opened an item without consulting the team. This led to an argument and conflict, prompting Eliza to apply the Crucial Conversations techniques to resolve the issue. She emphasizes the importance of understanding different expectations and avoiding judgment during such conversations. Eliza shares tips, including clarifying the desired outcome and the benefits of the proposed change, as most people are unlikely to change unless they see the benefits. She also suggests taking a break from the computer, seeking feedback and support from other scrum masters, and giving the situation time to evolve. Ultimately, she highlights the significance of effective communication and patience in navigating conflicts.
[IMAGE HERE] As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.
About Eliza Gregory
Eliza Gregory has worked as a Project Manager, Scrum Master, and Agile Coach for U.S. Defense and the German automotive industry. She uses teachings from Agile to hone her writing process, and has a new novel out this May about an IT Project Manager coping with burnout and work stress. Originally from Virginia, she now resides in Bavaria, Germany.
You can link with Eliza Gregory on LinkedIn and connect with Eliza Gregory on Twitter, and you can read about her novel Painting the Whiskey Blue.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Eliza shares a story about an international team that faced trouble with communication and escalation issues. The team initially attempted to create team agreements using a shared whiteboard. However, Eliza later discovered that team members were escalating concerns directly to management without involving her. This raised concerns about whether the team felt safe communicating with her. Eliza offers the tip of addressing this issue through one-on-one conversations, emphasizing the importance of creating a safe space for team members to express themselves. She found that these coaching conversations had the most significant impact. Eliza advises making it clear to team members that you are there to listen and understand their concerns. Additionally, she recommends setting up one-on-one meetings and allowing individuals to define the cadence that suits them best. Eliza also suggests conducting more workshops, especially for teams that are not yet mature, to facilitate better communication and collaboration.
In this segment, Eliza describes the book "Crucial Conversations." She highlights that the book is dense and cannot be read in one sitting. Although it is not specifically focused on Agile or Scrum, it delves into conversations that occur when emotions are high and people feel unsafe or threatened. The book emphasizes the importance of creating a safe space and presents essential skills for effective communication with one's team and others. Eliza emphasizes the significance of recognizing within oneself when entering a crucial conversation.
[IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!
About Eliza Gregory
Eliza Gregory has worked as a Project Manager, Scrum Master, and Agile Coach for U.S. Defense and the German automotive industry. She uses teachings from Agile to hone her writing process, and has a new novel out this May about an IT Project Manager coping with burnout and work stress. Originally from Virginia, she now resides in Bavaria, Germany.
You can link with Eliza Gregory on LinkedIn and connect with Eliza Gregory on Twitter, and you can read about her novel Painting the Whiskey Blue.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Eliza discusses an anti-pattern when her project management background interferes with her scrum master role, causing her to insert her opinion instead of allowing the team to fix the problem. She emphasizes the importance of acknowledging mistakes publicly and showing vulnerability. Eliza also talks about the challenge she faced when transitioning to a new company and culture without enough time to adjust. She advises being prepared for changes in terminology when moving industries. Feeling the need to improve her skills, Eliza went back to the basics by reading more books and seeking opportunities to gain knowledge. Additionally, she shares the challenges of working with teams that don't speak English as their native language and suggests learning the working styles of the team. Eliza emphasizes the significance of asking for feedback from the teams and highlights that adapting to new teams is a personal journey.
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Eliza Gregory
Eliza Gregory has worked as a Project Manager, Scrum Master, and Agile Coach for U.S. Defense and the German automotive industry. She uses teachings from Agile to hone her writing process, and has a new novel out this May about an IT Project Manager coping with burnout and work stress. Originally from Virginia, she now resides in Bavaria, Germany.
You can link with Eliza Gregory on LinkedIn and connect with Eliza Gregory on Twitter, and you can read about her novel Painting the Whiskey Blue.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this segment, Greg highlights a specific example of a remarkable Product Owner who would physically visit the team's building two days a week and sit closely with them, establishing accessibility and close collaboration. What made her stand out was her deep knowledge of the product, as she had been a previous customer and actively used the product being developed.
Furthermore, the great product owner was unafraid to provide valuable insights and articulate why users needed certain features, even if they hadn't explicitly requested them. She actively participated in every sprint review, where the team would allow her to test the product live and provide immediate feedback. Greg recalls this Product Owner as an integral part of the team, both professionally and personally, emphasizing her pleasant demeanor and strong team integration.
Overall, this segment showcases the qualities of a great product owner: accessibility, deep product knowledge, proactive involvement in sprint reviews, and a strong sense of collaboration and team integration. Such attributes contribute to effective communication, understanding user needs, and ultimately delivering a successful product.
In this segment, Greg highlights an example of a Product Owner anti-pattern, where a project manager with limited training and a negative attitude was assigned as the Product Owner for the Scrum team. This led to issues such as micromanagement and team dissatisfaction. Greg emphasizes the importance of building a personal relationship with the product owner and understanding their underlying fears and motivations. He also recommends the book "How to Win Friends and Influence People" by Dale Carnegie as a resource for effective communication and relationship-building. This episode sheds light on the challenges of product ownership and provides valuable tips for fostering a positive and collaborative environment.
[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Gregory (Greg) Miller
Greg is an Agilist and Coach who has been working in Agile software development for more than 10 years. He hosts The Agile Within podcast with Mark Metze (a previous guest), which promotes agile behaviors and mindset. He lives in Ohio with his wife and four children, two of which are twins.
You can link with Gregory (Greg) Miller on LinkedIn and connect with Gregory (Greg) Miller on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Greg dives into the key elements that contribute to the success of a Scrum Master. Drawing from his experience, he highlights: Firstly, building strong relationships and establishing trust with team members is paramount. A successful Scrum Master actively listens, empathizes, and makes themselves available to support the team. They prioritize collaboration and create an environment where team members feel safe and supported.
Secondly, a successful Scrum Master demonstrates a deep understanding of the Scrum framework and ensures its effective implementation. They facilitate Scrum events, encourage adherence to Agile principles, and address any impediments that hinder the team's progress. They act as servant leaders, advocating for the team's needs and fostering a culture of continuous learning and improvement. Moreover, they invest in their own growth by seeking opportunities for personal development and staying connected with the Agile community.
Overall, a successful Scrum Master excels in building relationships, guiding the team through the Scrum process, and serving as a catalyst for growth and improvement. Their ability to foster collaboration, trust, and continuous learning sets the stage for a successful Agile software development journey.
In this segment, Greg shares his favorite retrospective format and highlights the importance of generating actionable outcomes. He begins by evaluating the team's readiness and chooses the appropriate retrospective format accordingly. When working with a new team, he utilizes a shared whiteboard and follows the Kudos/Start/Stop/Continue framework. However, he discovered that some teams expressed dissatisfaction with retrospectives because they lacked actionable items despite having productive conversations. Greg emphasizes the significance of combining meaningful discussions with concrete action items. He suggests voting on at least one item to prioritize for action and maintaining an action item list backlog to ensure follow-through. By incorporating these practices, teams can have engaging retrospectives that lead to tangible improvements.
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Gregory (Greg) Miller
Greg is an Agilist and Coach who has been working in Agile software development for more than 10 years. He hosts The Agile Within podcast with Mark Metze (a previous guest), which promotes agile behaviors and mindset. He lives in Ohio with his wife and four children, two of which are twins.
You can link with Gregory (Greg) Miller on LinkedIn and connect with Gregory (Greg) Miller on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Greg recounts his involvement in a change process as a Business Analyst (BA). Hired for his Agile expertise, he was assigned to the manufacturing engineering section of the company, which already embraced Lean and Kaizen principles. However, in the software side, there was a lack of backlog and prioritization. Greg took initiative by introducing a clear prioritization method, emphasizing the need for a dedicated Product Owner (PO), and establishing regular meetings with managers to prioritize their work. Through his efforts, a force-ranked list of stories was created, allowing for efficient and streamlined prioritization.
Greg shares valuable tips based on his experience, including the importance of defining a simple prioritization method, fostering a collaborative mindset among managers, and ensuring stakeholder buy-in. He also highlights the significance of checking one's ego at the door and focusing on what is best for the company's success. Overall, this episode demonstrates the transformative impact of implementing prioritization and backlog management in an organization, even when Agile principles are already embraced in certain areas. Greg's proactive approach and insights provide valuable guidance for achieving efficient and effective change processes.
[IMAGE HERE] As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.
About Gregory (Greg) Miller
Greg is an Agilist and Coach who has been working in Agile software development for more than 10 years. He hosts The Agile Within podcast with Mark Metze (a previous guest), which promotes agile behaviors and mindset. He lives in Ohio with his wife and four children, two of which are twins.
You can link with Gregory (Greg) Miller on LinkedIn and connect with Gregory (Greg) Miller on Twitter
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Greg reflects on a team that self-destructed, causing him significant pain. The team, previously considered an exemplary high-performing unit, faced external factors and decisions that disrupted their dynamics. Leadership discussions about replacing their product, the removal of their Product Owner (PO), and a lack of support left the team directionless and demoralized. Greg recognizes the detrimental impact of removing the PO, highlighting it as an anti-pattern that ultimately led to the team's disbandment. This episode serves as a powerful reminder of the importance of providing support, direction, and maintaining team cohesion to foster a thriving and motivated workforce.
In this segment, Greg talks about his most influential book for Scrum Masters, which is "The Scrum Pocket Guide" by Gunther Verheyen, a previous guest on the podcast. He highly recommends this book, as it has been invaluable to him in his role. Greg frequently refers to it and even keeps it on his nightstand for easy access.
One aspect that stands out to Greg is Gunther's emphasis on the values side of Agile. The book delves into why the Scrum values are significant and explores their importance in the context of Scrum. Greg appreciates this focus on values as a fundamental aspect of Agile practices.
For further exploration of the Scrum values, Greg suggests referring to the values section in the Scrum Guide. Overall, "The Scrum Pocket Guide" has had a profound impact on Greg's understanding of Scrum and serves as a go-to resource for him as a Scrum Master.
[IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!
About Gregory (Greg) Miller
Greg is an Agilist and Coach who has been working in Agile software development for more than 10 years. He hosts The Agile Within podcast with Mark Metze (a previous guest), which promotes agile behaviors and mindset. He lives in Ohio with his wife and four children, two of which are twins.
You can link with Gregory (Greg) Miller on LinkedIn and connect with Gregory (Greg) Miller on Twitter.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Greg shares a story during a time of large company changes. He was assigned to a team that had previously struggled with a problematic Scrum Master. Greg had a conversation with the team's manager to understand their expectations. However, he failed to address the manager's assumption that the Scrum Master should perform the team's work.
As a result, the team remained confused about the role of the Scrum Master, and they constantly questioned Greg's activities. The failure, in Greg's perspective, was his inability to establish a stronger relationship with the manager and gain a deeper understanding of their expectations. Greg emphasizes the importance of building relationships with the teams one works with, even if it means setting aside the framework of Scrum temporarily.
In this episode, we recommend the book "How to Win Friends and Influence People" by Dale Carnegie as a valuable resource for improving interpersonal skills. Greg also shares a couple of tips based on his experience. Firstly, he suggests sitting next to the team from day one to foster a sense of belonging. Additionally, spending quality time with the team can help in developing a better understanding of their dynamics and needs. Greg emphasizes that effective work happens through people and building relationships is crucial for success.
Greg's failure to build a better relationship with the manager resulted in confusion within the team and a lack of clarity about the Scrum Master's responsibilities.
[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.
About Gregory (Greg) Miller
Greg is an Agilist and Coach who has been working in Agile software development for more than 10 years. He hosts The Agile Within podcast with Mark Metze (a previous guest), which promotes agile behaviors and mindset. He lives in Ohio with his wife and four children, two of which are twins.
You can link with Gregory (Greg) Miller on LinkedIn and connect with Gregory (Greg) Miller on Twitter.
BONUS: Achieving Agility and Exploring the Product Owner's Impact in DevOps with Zhenya Balyasin
We start this episode by highlighting the challenges that Product Owners (POs) face when working with DevOps teams. Zhenya explains that DevOps work is unique and comes with a variety of incoming tasks and requests on a daily basis. Additionally, DevOps teams also require time to invest in improving their operations, which adds to the workload. The constant interruptions and chaotic nature of the work make it challenging for the PO to manage effectively. Unlike traditional backlogs where POs are used to prioritize tasks, in DevOps teams, the backlog may not always be the main focus. Zhenya identifies a common anti-pattern where DevOps teams have a strong willingness to help others, which can further complicate the role of the PO.
Zhenya identifies several common anti-patterns that she has observed in DevOps teams. One anti-pattern is the resistance from the team to have their work organized by the Product Owner (PO) when they were already functioning without that role. Another anti-pattern is the team's excessive focus on maintenance tasks rather than prioritizing the development of the product itself. The lack of clarity in identifying the products among the various types of work received is also a common anti-pattern.
Zhenya emphasizes the importance of defining the product or service for the teams and establishing a clear roadmap. She suggests discussing the product development process and the role it plays within the team. It is crucial to involve the team in these discussions rather than imposing processes on them without consultation.
Zhenya also highlights the need for effective communication and collaboration with the team. Merely presenting a process without prior discussion and understanding of the team's dynamics and self-identity can lead to resistance. Instead, she recommends discussing process-related matters with the team beforehand.
In this segment, Zhenya discusses how she changed her own work and the dynamics of the team after the Product Owner (PO) role was introduced to the DevOps team. She initially encountered an anti-pattern where the team seemed resistant to accepting the perspective and needs of the customers.
To address this challenge, Zhenya offers a couple of tips. First, she suggests initiating a discussion within the team to clarify who the customer is and how they are being served. This helps align the team's understanding and focus on meeting customer needs.
Additionally, Zhenya recommends conducting interviews with customer teams or the company itself. These interviews provide valuable insights and highlight the differences in expectations between the DevOps team and the customer's requirements. By understanding these differences, the team can adjust their approach and ensure their work aligns with the customer's needs.
By implementing these tips, Zhenya was able to foster a better understanding of the customer's viewpoint within the team, leading to improved collaboration and a more customer-centric approach to their work.
Zhenya shares her approach to facilitating change within the team. She emphasizes the importance of change management and highlights the Unfreeze-Change-Refreeze model. Zhenya advises breaking down the steps of change into smaller, manageable tasks while consistently communicating the value behind each step. She encourages the use of data to measure progress and guide decision-making.
Additionally, Zhenya underscores the significance of focusing on the people involved in the change process. She suggests investing time in conversations to understand individual perspectives and values. Zhenya also recommends introducing the Product Owner (PO) role gradually, addressing questions and concerns, and being mindful of the potential impact of introducing multiple changes simultaneously. Building strong relationships with the team is seen as essential in driving successful change.
In this segment, Zhenya discusses the support she expects from Scrum Masters in helping Product Owners in similar situations. She advises Scrum Masters to proactively prepare the team for the upcoming changes even before the PO joins the team. Zhenya suggests working collaboratively with the PO, Scrum Master / Agile Coach, and team lead to define a clear strategy for the team. She highlights that the PO can also assist the Scrum Master/Agile Coach in this process by providing inputs such as the roadmap, OKRs (Objectives and Key Results), and defining the team's mission. Zhenya emphasizes the importance of redefining the team's identity to facilitate and embrace the desired change. She encourages close collaboration between the Scrum Master/Agile coach, PO, and team lead to drive successful transformation.
Zhenya recommends further reading and resources related to the topic of change management. She mentions the Lewin Change Management model as a valuable resource to explore. Additionally, Zhenya suggests subscribing to the newsletter of Rob Lambert from Cultivated Management, who provides insightful content and potentially offers workshops on the subject. Another newsletter recommendation is Patrick Kua's level up newsletter.
About Zhenya (Evgeniia) Balyasin
Evgeniia, commonly known as Zhenya, is an experienced professional who collaborates closely with DevOps Engineers, assuming the crucial roles of Product Owner and Product Manager. With a strong background in agile software development, Zhenya brings her expertise to drive product strategies, prioritize backlog items, and ensure seamless coordination between development and operations teams. Her insightful approach and deep understanding of the DevOps landscape contribute to successful product delivery and continuous improvement.
You can link with Zhenya (Evgeniia) Balyasin on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
Bojan highlights the importance of coaching the Product Owner (PO) as a Scrum Master. He emphasizes that scrum masters should be prepared to provide coaching to the PO, focusing on their development rather than becoming product coaches themselves. Bojan notes that great POs possess the ability to multitask and actively participate in meetings. They act as focused salespeople, selling product ideas and visions to stakeholders and the team. Simply mastering tools like JIRA and stakeholder communication is not enough; the PO must also sell their ideas to the team and scrum master. By coaching the PO and helping them refine their skills, Scrum Masters contribute to the overall success of the product development process.
If you want to know more about what topics, and how you can coach your Product Owner, check out our e-course on How to Coach Your PO.
In this segment, Bojan discusses a team composed of newcomers, including a newbie Product Owner (PO), working on an existing product. Bojan noticed that here was a disconnection between the work on the team’s Scrum board and the actual product. The PO struggled to bridge the gap between the technical tasks and the features used by customers. Consequently, the team lost sight of the purpose behind their work and the reasons for building the product. One prominent anti-pattern was the lack of a customer feedback loop, resulting in a missed opportunity to gather valuable insights. Bojan advises the implementation of appropriate feedback loops tailored to the specific product being developed. Additionally, he references the concept of "Genchi Genbutsu," which encourages going and seeing the product in action with customers to gain a deeper understanding.
[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.
About Bojan Smudja
Bojan is an Agile coach dedicated to assisting individuals, teams, and organizations in reaching their objectives. With his expertise and guidance, he empowers others to embrace Agile methodologies and maximize their potential for success.
You can link with Bojan Smudja on LinkedIn.
Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.
In this episode, Bojan discusses the factors that contribute to the success of a scrum master. He emphasizes the importance of being recognized as a valuable part of the team and providing genuine assistance to team members. Bojan also mentions the transformative aspect of Scrum in changing the way work is approached. As an example, he shares a conversation with a product owner (PO) where he asked how the PO determines if the work being done is good. The PO responded by looking at the faces of team members and using their smiles as an indicator of success. This highlights the significance of fostering a positive and collaborative environment within the team, and measuring “smiles” as a way to evaluate our own success as Scrum Masters.
In this segment, Bojan shares his experience as a new Scrum Master for a highly technical team working with cryptocurrency. Initially, the team was hesitant to engage in open discussions during retrospectives and preferred writing post-it notes. To address this, Bojan introduces a powerful technique called the Team Mirror Retrospective. The process involves conducting individual interviews, anonymizing the responses, and then sharing them with the team as grouped reflections. This method is employed selectively for significant and sensitive topics that team members are reluctant to openly discuss. Bojan emphasizes that this retrospective format can also enhance interviewing skills when engaging with team members. He recommends this approach for remote teams and highlights its effectiveness in boosting morale and incorporating feel-good metrics.
[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox!
About Bojan Smudja
Bojan is an Agile coach dedicated to assisting individuals, teams, and organizations in reaching their objectives. With his expertise and guidance, he empowers others to embrace Agile methodologies and maximize their potential for success.
You can link with Bojan Smudja on LinkedIn.