Daniel started his Agile transition a long time ago, when those adopting were mostly early adopter companies, eager to change. Today, in 2018, we are faced with more and more late majority companies. Companies that may not even be ready to start their transition, but they ply on. In this episode we review some of the challenges you can expect when working with late majority company, and help them Cross the Chasm.
Agile coach from Scrum Data since 2010. Daniel comes from a strong Business intelligence background. He is passionate about large scale product development, organisational structure and culture, being idealistic pragmatist, framework agnostic.
When we start in a new organization, it takes a while before we understand all the anti-patterns around us. And something innocent, like a manager asking for a burndown chart, can quickly spiral out of control if we don’t pay attention. In this story, Chad shares with us how sometimes, focusing on metrics and transparency can destroy trust. Listen in to learn about one anti-pattern of the use of the Sprint Burndown, and how that can quickly destroy trust in your organization.
About Chad Beier
Chad’s first experience with Scrum was in 2005 on a global team responsible for consolidating financial software. After some dark days of death march projects, he left his traditional business analyst and project manager roles behind. He is now consulting organizations as an external change agent and organizational agility advisor.
From NASA to Scrum consultant, Heidi has collected a lot of experience of how to apply Agile in diverse environments. From all of those experiences she collected many lessons about working in large organizations, distributed teams and other environments where even finding the root of a problem is difficult at best! In this episode Heidi shares some of the tools that she uses to make those problems visible, and quickly find the causes to tackle.
About Heidi Araya
Heidi is an Agile coach who has been working with remote teams since 1999. She aims to show teams and enterprises the value of a cohesive vision and mission, systems thinking, and self-organizing teams. An active member of the Agile community, she trains and speaks at events and conferences worldwide.
Adopting Agile in a co-located organization is hard enough, but when you need to adopt Agile in distributed team, things get even more complicated. In this episode we discuss how Agile adoption in a distributed / remote team can create problems that are hard to solve, unless you are ready for it. We also discuss many different tips on how to tackle agile adoption in a distributed organization.
About Felix Handler
Felix likes to bring out the best in as many people as possible by providing an environment in which people can sustainably thrive. After his Bachelor in Computer Science he wanted to develop people rather than software. He also is part of 12min.me, a movement for inspiring people.
When we start as Scrum Masters, there’s a lot of things we don’t know yet. Not only are we not able to see the anti-patterns, but we also don’t know how to react to the problems we face. Scrum has in itself a set of patterns that help us when we are starting out, but sometimes we need more than that. In this episode we explore the story of when Leonardo was just starting as a Scrum Master. The anti-patterns he saw, and the steps he took after he learned some hard lessons.
About Leonardo Bittencourt
Currently Leonardo is a Scrum Master at Equifax Ireland. Focused on building high performance teams through Agile and/or Lean adoption, he is an enthusiastic about Lean and Agile mindset in the Software Development industry as the transformation agent to create great working environment as well as products that matters.
Some of us are lucky to have a good experience with our first try at using Scrum. Some, even more lucky, can get great results during the first 2, 3, 5 or more times they help a team adopt Scrum. But, whether we like it or not, eventually we will face a time when Scrum just doesn’t work as we expect. What do do then? Listen in to learn what Ryan went through in just such a situation and what he did to recover from that.
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.
In a high stakes project, like the one Natalie describes, it is tempting to start focusing on the schedule from the start and spend time trying to predict how long things will take. But is that the best us of our time and talents as Scrum Masters? Listen in to learn what Natalie learned about making projects a success that require very little focus on duration or effort estimation.
In this episode we discuss the book NoEstimates, How to measure project progress without estimates.
About Natalie Cervantes
Natalie is a Certified Scrum Master and Agile Coach with over 12 years experience working with both veteran and new agile teams. Her experience spans everything from mobile and embedded systems to enterprise scale website projects with a client base that includes Microsoft, Amazon, Coca-Cola and many others.
Working with a team that is under pressure from someone high-up in the organization is never easy. How about if that person is also changing their mind regularly? And interrupting the team with new ideas all the time? In this episode we explore such a situation. The VP is constantly asking the team for new things, interrupting their work, and requesting everything in very short timeframes. How can we help as Scrum Masters? Ask the right questions. Listen in to learn about how to ask the right questions.
About Tanner Wortham
www.SpikesAndStories.com. He’s helped many organizations in their journey toward agility. He’s been accused that his military training would mold him into a rigid, unmoving Scrum Master, but nothing could be further from the truth. What civilians call agile, the Corps calls leading Marines, and it’s through his experiences as a Marine that he derives most of his insight as a Scrum Master.
There are plenty of available frameworks, processes, models and other “processed” Agile packages. So many that the distracted Scrum Master can be forgiven for thinking that one of those will work for his team. Unfortunately that’s not the case. Listen to this episode, where Miguel explains how he came to the realization that Agile adoption is just the start of the Agile journey, and what you can do about it as a Scrum Master.
About Miguel Santos
Miguel is a Brazilian living in Germany and currently Scrum Master for two teams at NewStore. He believes that there is no single methodology (agile or not) to lead projects and teams to success. Because of that, he would like Scrum Masters to be less biased when working with their teams.
As team members, Scrum Masters, employers, managers we tend to keep a lot of information confidential. But can we really function well as teams when the default behavior is to hide information? In this episode we explore the consequences of hiding information from the team or your colleagues.
Richard is a speaker, trainer, coach, and author focused on high-performance teams. Richard is the author of The Core Protocols: A Guide to Greatness. He leads clients in building great teams that get great results using the Core Protocols, Agile, and Open Space Technology. Richard created and teaches the class Agile Software Development at Harvard University. Learn more and subscribe to Richard’s newsletter at www.kasperowski.com.