Distributed software development is one of the challenges for Agile organizations. The element of globalization is impossible to avoid because of the nature of the business we work in. However, there are some things we should be aware to ensure that teams are able to deliver. In this episode, we discuss some of the anti-patterns that come when distributed teams fail to account for the different kind of communication that is needed when working with distributed organizations.
In Finding your Element: How to Discover Your Talents and Passions and Transform Your Life by Ken Robinson (book website), Ivo discovered something about himself that helps him be a better Scrum Master. He found and understood the importance of some of the personal strengths he has that help him in the role of Scrum Master.
In this segment, we also discuss Coaching Agile Teams by Lyssa Adkins.
About Ivo Peksens
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.
Full show notes at https://scrum-master-toolbox.org/.
About Ben Aston
Ben has over 15 years of experience in both strategic thinking and tactical implementation from a career at some of the top digital agencies including FCV, Dare, Wunderman, DLKW Lowe and DDB. He's worked across several industries including transit, utilities, consumer electronics, eCommerce, automotive, financial services, public sector, and retail brands.
Ben's a Certified Scrum Master, PRINCE2 Practitioner and founder of the digital project management blog, The Digital Project Manager.
When talking about cultures, we often talk about the contrasts. What makes certain cultures more Scrum-friendly, or the opposite. In this episode, we talk about how certain cultures’ focus on more conversation can help create safe spaces for the team, and help them be more collaborative. But we also talk about the concept of “time”, and how the different perspectives on time (e.g. cyclic vs linear time) can affect the adoption of Scrum.
In this episode, we also refer to the premier Agile conference in Ireland, the Agile-Lean Ireland conference.
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.
Richard suggests the Amazon Product Review retrospective format. And although Retromat suggests this can be used as a “check-in” exercise, we can also use it as the core exercise for the retrospective.
In this episode, we refer to the Agile Retrospectives book and the retrospective outline defined in the book.
Richard shares the story of a change process where an organization decided to standardize on SAFe as the scaling approach. Richard also shares what they learned about adopting SAFe, and the 4-step process they created to help the adoption of SAFe.
In The Scrum Field Guide by Mitch Lacey, Richard found many lessons that helped him in his journey as a Scrum Master. The book shares models and keys to successful scrum mastering, but also many references and other sources to read up on.
Often, as Scrum Masters, we know what needs to change and focus our efforts in “selling” the solution. What it is, why it is a good idea, etc. But, when Richard failed to help an organization change he learned an important lesson. To improve how we help change progress, we should sell the problem, not the solution.
In some countries, we favor order and rules. However, that’s not the case for everybody. How can we adapt to a country that emphasis more rules than what we learned back in our home country?
In this episode, we learn about the German and Serbian cultural traits and how they affect the work of the Scrum Master.
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?
The Three Little Piggies retrospective format focuses on risk management. Asking us to consider what are our Houses of straw, Houses of sticks and the solid House of bricks. And why not ask: who or what is our big bad wolf?
In a business where change and new technology are a day-to-day occurrence, it may seem that teams are constantly ready to adapt to new situations. That’s not the case, however. In this episode, we discuss the story of a team that was uncomfortable with taking on a new technology. This was the perfect environment for Rade to put in practice his approach to helping teams change.
As we work with many different teams, we start to notice some patterns. In this episode, we talk about the pattern where team members take a very critical stance when a mistake happens. As Rade puts it, when this pattern develops, the team creates a culture that does not tolerate failure or allows people to take risks.
How can Scrum Masters tackle this problem? We discuss some concrete approaches to help teams scale back their risk-averse, and mistake-intolerant culture. After all, no mistakes means no learning.
In Don't Shoot the Dog: The New Art of Teaching and Training by Karen Pryor, Rade learned about the techniques we can use to help people change behavior by building new habits and using positive feedback and reinforcement.