Willem-Jan has a background in Project Management, and in his company, the leadership asked the teams to move away from Project Management and embrace Agile. That led Willem-Jan on a learning journey, to understand and apply Agile ideas in his work. In the process, as it usually happens, a team got fixated on the “velocity” metric. In this episode, we explore what can happen when teams get fixated on “velocity”, and what Willem-Jan learned to avoid that anti-pattern in the future.
Featured Book for the Week: The Scrum Pocket Guide by Gunther Verheyen
In The Scrum Pocket Guide by Gunther Verheyen, Willem-Jan found an explanation for Scrum that made things click. This led him to explore the ideas behind “complexity” and to start to understand why “the plan” wasn’t always the thing to follow.
As a Scrum Master and writer for Serious Scrum, Willem-Jan is passionate about helping people understand what it means to work in a complex Product Environment. Which is how he likes to talk about Scrum.
Once in a while, we work with a team that is down in the doldrums of morale. That’s never an easy challenge to take on as a Scrum Master because the reasons for the lack of morale can be deep-seated and completely outside the team’s control. On the other hand, as we discuss in this episode, that realization can transform our perspective and help thet eam find ways to jump out of the hole they found themselves in. We talk about morale, and how simple tricks can totally transform the morale of a team, and we do that by realizing and implementing something all Scrum Masters should focus on work on what you can directly affect.
Featured Book of the Week: Agile Retrospectives
In Agile Retrospectives by Diana Larsen and Esther Derby, Justin found great inspiration for how to facilitate retrospectives with the teams he works with and also learned how important it is to prepare and crush the facilitation challenges we face as Scrum Masters.
About Justin Chapman
A Product and Agile Coach with product management experience ranging from payments to enterprise custom build. Justin has hosted a small series on Product Management and another series on Being a Scrum Master.
Justin has also pioneered a new form of Canvas to help bring teams together. All of this information can be found on his blog: http://www.ponolabs.com/labs/
In this team, the developers only wanted to focus on their own tasks and did not care to help the Product Owner. This was, as it turned out, a recipe for disaster. We discuss with Dimitri, what drives teams to be task-focused, instead of impact-focused, and discuss techniques we might be able to use to bring the team’s attention to the overall goals and the collaboration with the Product Owner.
Featured Book for the Week: Creating Great Teams by Mamoli and Mole
Dimitri is a business, transformation, and agile coach and a repented project manager. Dimitri works side by side with executives, managers, and teams to uncover better ways of developing software and delighting customers.
Communication is a common “failure” domain for teams. We often hear that communication wasn’t “good enough”, or that it failed. In this episode, we explore some of the possible reasons for those failures, and Saritha shares her story of improving communication in a scaled Agile environment by using the “Mega Standup” tool, which she defines in this episode.
In Mindset: The New Psychology of Success by Carol Dweck, Saritha found the inspiration for focusing on mindset. The book also helped Saritha with designing her retrospectives to help teams focus on their success. In this segment, Saritha also shares a few tips on how to help your teams change their attitude towards the challenges they face.
About Saritha Rai
Saritha has been working in the IT industry for 13+ years and is an adaptable and constant learner. She has over a decade of experience in software development and is passionate about training, guiding and coaching people to have a good working environment which will result in high-quality deliverables.
Team members in many organizations share their time across multiple projects. That brings a lot of problems that are often ignored because “on paper”, the team members can easily share their time between projects. However, as Scrum Masters, we know the reality is very often much harder for those same team members. For example, team members start missing important ceremonies, like planning meetings or are unable to help each other (because they are working part-time in different projects). The multi-project productivity myth is a serious problem, and in this episode, we talk about the consequences and what we can do as Scrum Masters to help our teams survive those difficult situations.
George Mathews is a Scrum Master at SentryOne for two fully remote teams. Prior to that, he had experience as a Customer Service Representative, Operations Analyst and Finance Technical Analyst allowing him to employ a broad practical point of view as he coaches Agile teams at SentryOne.
When multiple teams work on high-impact or high-visibility programs or projects, it is critical that they align how they work, and that certain processes are in place to support the teams. In this episode, we talk about what problems arise when teams are working separately, not aligned, and the supporting processes are missing. A key realization for Scrum Masters: the supporting processes can have a big impact on the performance of the team
Featured Book for the Week: Thinking Fast, Thinking Slow, Kahneman et. al
These books helped Mandy understand many different aspects of Agile beyond the work with the team.
About Mandy Sunner
Mandy calls herself the Angel of Agile as she guards her team and stakeholders from attacks and compromises which are forthcoming in an era of uncertainty. Her Agile approaches are thought through by virtue of being a systematic thinker and keeping the customers at the forefront of development. A problem solver with many years of practical experience.
Katja is an Agile Coach in an organization that had to organize a distributed/#Remote Big Room Planning session in less than 24 hours! Listen in to learn how they pulled it off.
One of the key learnings from that effort was that a #Remote event will take a longer time (maybe 3-4 days) than a locally organize Big Room planning event. But there are many more insights that Katja shares on this LIVE Q&A
What have been the biggest challenges for you and for the teams that you support?
As we work with organizations in transition, we need to help teams and Product Owners make sense of the new ways of working. In this episode, we discuss how Scrum Masters can help Product Owners and teams find a way to collaborate when changing towards Agile. We share some tools that help large groups come together and learn to focus more on the impact they seek, rather than just the work they need to do.
About Bradley Pohl
Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an “Agile Transformation.” As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.
OKR’s are a management tool that is gaining wide acceptance in the tech industry and other industries. The ideas are simple and should be simple to adopt, except they are not.
In this episode, we talk about what Jeremy learned about the roll-out of OKR’s at his company and how Scrum Masters can help adopt OKR’s the right way! Not a simple process.
About Jeremy Willets
Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!
As Agile and Scrum get adopted in more and more organizations, there’s a need to help organizations replace the old coordination mechanisms, like the Program (several projects coordinated via a centralized organization). In this episode, we talk about coordinating at Portfolio level many Scrum teams. We also share the steps to get that implemented at Elena’s company.
About Elena Popretinskaya
Elena considers herself a lifetime learner (she says, she absolutely loves having “aha!” moments). And she especially enjoys learning together with and from other people: her team and her friends. Elena is curious about everything: people, software craftsmanship and the world around. Elena is also a passionate hiker and a cross-country skier 🙂