As more and more companies adopt OKR (Objectives – Key Results) as a management practice, it is critical that Scrum Masters understand how that tool is used in their organization. In this episode, we discuss how OKR’s can totally derail a company, and how Scrum Masters can join the process and help it improve. This is especially important because OKR’s – when effectively used – will have a large influence on the teams we work with.
About Ines Stuppacher
Ines Stuppacher is a passionate team coach and Scrum Master. Working with people challenges and inspires her every day. Her coaching mentality is an important pillar of her life and work. Ines does not impose things on people but rather sees herself as a waiter of options. She strives to show up as her full human self in all kinds of situations and with that fosters real connections with other people.
When an organization starts adopting Agile, the temptation is to organize a “transformation” and to focus on the change process. In this episode, we explore what happens when we focus on small changes, grass-roots change.
How we can slowly get more and more teams on-board, and ultimately avoid a large and difficult transformation.
About Ben Clark
Ben’s career has spanned from working assembly at Ford Motor Co, IT consulting, DSL Internet provider using wireless building-to-building antennas, systems administration and engineering, data center floor work, DevOps, cloud engineering, cloud architecture, scrum master, people-leader, and agile coach.
Of the many types of changes we need to go through, scaling up the use of Scrum may be one of the most common at the moment. When we go from one team using Scrum, to many teams collaborating and using Scrum together many things change.
In this episode, we talk about some of the challenges that scaling up Scrum brings, and how we – Scrum Masters – can prepare for those, so that we can help both the teams and the organization benefit from Scrum in larger projects.
About Dragana Hadzic
Dragana is an agile enthusiast who believes communication is critical for success in everything, including software projects. A Scrum Master and an Agile Coach with broad experience in IT industry and different leadership roles. Passionate about everything that brings positive energy and enables people to achieve great results.
It is a scary change, when Scrum Masters must go from focusing on the team to focusing on the organization. However, this is something that most Scrum Masters will have to face in their career.
In this episode with Isaac Garcia, we learn about the circles of influence that help us understand what we can influence (and what we can’t); we discuss Causal Loop Diagram, a tool to understand organizational dynamics that affect our teams; and the ideas behind “flow”, a way to view organizations that focuses on allowing the teams to find their performance levels.
For more on Causal Loop Diagrams and their use for Scrum Masters, check this episode with Antti Tevanlina where we explore how you can use CLD’s to understand the causes of the problems affecting the team.
About Isaac Garcia
Isaac is a passionate Agilist who builds teams with heart and walks their journey together. His driving goal in life is to invest in and impact world changers. He has a lot to learn but is enjoying the discovery in the journey.
It’s common to hear the “build a guiding coalition for change” mantra. It is part of a famous change management model (The Kotter 8-step change model), and a practical tip that we all can benefit from. However, how is that done in practice? In this episode, we talk about an Agile transformation at a large, distributed organization and how Gilson and others were able to build that guiding coalition for change.
Gilson has worked with Scrum for over ten years, first as a software engineer, then taking in both roles of Scrum Master and Developer and currently 100% dedicated as Scrum Master. As a Scrum Master, he truly believes in empowered and self-organizing teams and works inside and outside of the team to achieve it.
There’s often a misconception in certain organizations that Agile is just shorter waterfall projects. That’s very far from reality. In this episode, we talk about how David’s team showed – by example – the power of an agile way of working, and how that inspired other teams to change.
About David Gentry
David Gentry is an Agile Coach and Scrum Master. He has served in a variety of other roles in his career including developer, data analyst, business analyst, quality analyst, and project manager. In his free time, he can be found playing bass guitar and interpreting how groove applies to life and agility.
Change can happen at any time, it does not need to be large or involve many teams. As Scrum Masters, we help the teams change continuously. In this episode, we talk about a change of perspective in a Product Owner team that led to positive changes and create a collaborative environment. We also talk about what was the role of the Scrum Master when it comes to helping change happen in that team.
Are you having trouble helping the team working 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 Long Suciu
Long is driven by a passion to help people unlock their potential and discover their own capacities. He has spent the past 20 years helping teams and organizations find and put in place better ways of working.
Sometimes, new teams are formed where some team members still have “legacy” tasks in their to-do lists. When that happens, it is the responsibility of the team (with the help of the Scrum Master) to figure out how to handle that work. There are many options to handle that situation. What is not ok is to let it grow, and spiral out of control. Teams own tasks, not individuals, therefore the Scrum Masters should help the team understand that legacy tasks are a team issue, not a personal issue.
Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.
Scrum Masters that move onto organizations that are just in the start of Scrum adoption may find that it is not an easy process, even when you have top-management support.
In this episode, we talk about what goes wrong when we focus on change from the top, and forget that the teams (whom we work with), might be against the change. Top management support is not enough for Scrum adoption!
About Nick Vitsinsky
Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.
Planning for a Sprint is not an easy task. There are many unknowns, even at the Sprint level, and team members justifiably feel uncomfortable discussing commitments, when they know there will be unexpected events during the Sprint.
How can Scrum Masters help teams learn the value, and the mechanics of planning? That’s what we discuss in this episode.
About Mili Shrivastava
Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.