team independence Archives - Scrum Master Toolbox Podcast

Iryna Stelmakh: The Almost Invisible Scrum Master, Why Team Independence Is the Ultimate Success Metric

“A successful Scrum Master is almost invisible — not because they don’t contribute, but because the team is no longer dependent on them for every decision.” — Iryna Stelmakh

Iryna offers a powerful definition of success for Scrum Masters: becoming almost invisible. Not because the Scrum Master isn’t contributing, but because the system works — with or without them. The team takes ownership of delivery, solves problems collaboratively, and continuously improves its own process. Each team member can propose, vote, and suggest changes because the environment has a high level of trust.

When that happens, Iryna explains, the Scrum Master becomes more of a system observer and catalyst rather than a daily driver. As Vasco adds, this perspective is valuable because it looks beyond personal metrics — it examines behaviors across all the interactions the Scrum Master facilitates: between the team and the product owner, between the team and stakeholders during reviews, and within the team itself. The Scrum Master role sits at the nexus of many interactions, and success means those interactions work well even when you step back.

Self-reflection Question: If you were absent for a full sprint, would your team maintain the same quality of collaboration, decision-making, and delivery — or would things fall apart without you?

Featured Retrospective Format for the Week: The Energy Retrospective

Iryna shares her favorite retrospective format — one she calls the Energy Retrospective. Instead of the standard “what went well / what didn’t” framing, it asks three questions: What gave us energy this sprint? What drained our energy? And what should we start, stop, or continue doing to keep our energy at the right level?

This approach shifts the conversation from purely technical task problems to real human dynamics. As Iryna explains, closing technical tasks and resolving issues is important, but so is the wellness of the team. The Energy Retrospective creates space for both. She also notes that retrospective format should match the team: for open, trusting teams, a straightforward format works fine. But for new teams or teams with high resistance — those still in the forming stage where the Scrum Master isn’t yet a trusted figure — she uses metaphorical approaches, like asking team members to pick pictures that represent their feelings about the sprint. Even a happy, sad, or frustrated monkey picture can surface insights that direct questions might not.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

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 Iryna Stelmakh

IRYNA Stelmakh is a Project & Delivery Leader and Agile Coach who helps leaders turn complexity into clarity. With 10+ years across US, Nordic, and Eastern European environments, she works at the intersection of business transformation and human systems, building resilient organizations and high-performing teams in complex contexts.

You can link with Iryna Stelmakh on LinkedIn.

Natalia Curusi: Measuring What Matters Beyond Velocity and Story Points

“We as Scrum Masters need to put a scope for ourselves—we need to aim to leave the place where we work a little bit better than it was, and to make sure that this place could improve itself without us.” – Natalia Curusi

Natalia defines success for Scrum Masters with crystal clarity: leave the organization better than you found it, and ensure it can continue improving when you’re gone. This means fostering independence and ownership in teams so they can perform whether you’re on vacation, in another meeting, or have moved to coaching other teams.

The opposite pattern—where everything falls apart when the Scrum Master isn’t present—reveals someone who hasn’t truly succeeded in the role. Natalia also emphasizes the importance of establishing metrics early, but not the traditional ones.

Using velocity as a metric is an anti-pattern that focuses teams on the wrong outcomes. Instead, she recommends metrics like predictability, team morale, psychological safety measured through 360 feedback, and the quality of conversations both within teams and with stakeholders. But metrics alone don’t tell the story.

Natalia champions the concept of Gemba walks—going to see what’s actually happening, talking to people, observing the reality rather than just reviewing dashboard numbers. Some metrics are easily gamed, others provide only narrow perspectives on reality. The most important practice is using metrics to trigger reflection and adaptation, not as fixed targets. Natalia believes strongly that the quality of conversations—how teams discuss options, make decisions together, and adapt when facing pressure—reveals more about a Scrum Master’s success than any velocity chart ever could. The ultimate question: can your team succeed without you?

Self-reflection Question: If you disappeared from your team tomorrow, would they continue improving, or would progress stop until someone replaced you?

Featured Retrospective Format for the Week: Spotify Squad Health Check

“This is a multidimensional retro that I run with teams every 2 to 3 months—you need around 30 minutes for it, and I often get insights and new ideas from this retrospective that help me as a Scrum Master.” – Natalia Curusi

The Spotify Squad Health Check is Natalia’s favorite retrospective format because it provides a comprehensive view of team health across multiple dimensions. Unlike traditional retrospectives that might focus on a single sprint or specific issue, this format examines the team’s overall state across areas like teamwork, support, mission clarity, and technical quality. Teams rate themselves on various health indicators, creating a visual representation that reveals patterns over time.

What makes this particularly valuable is that it works whether you know the team well or are just starting with them—either way, you gain insights and “aha moments” about where the team truly stands. The multidimensional nature prevents teams from optimizing just one aspect while neglecting others, and the regular cadence (every 2-3 months) allows you to track trends and celebrate improvements.

For Natalia, this format consistently surfaces the hidden challenges that teams might not raise in regular retrospectives, making it an essential tool in her Scrum Master toolkit.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Natalia Curusi

With over 20 years in software delivery, Natalia Curusi is an expert in Agile Transformations, Delivery Optimisation, and Systems Thinking. As an Agile Coach at Endava, she leads Asia Pacific initiatives, driving business agility and continuous improvement while mentoring teams to build customer-centric, high-performing, and collaborative cultures.

You can link with Natalia Curusi on LinkedIn.

Bernie Maloney: From Permission-Seeking to Forgiveness-Begging—Agile Team Evolution in Self-Management

Bernie defines success for Scrum Masters as creating teams that can thrive and do their best work independently. His ultimate goal is to make himself unnecessary – developing self-directing teams that step out of waiting for direction and instead seek permission or even beg forgiveness when needed. Using the “Circles and Soup” framework, Bernie helps teams stretch their circles of influence and control. He recognizes that every manager wants teams to succeed but may lack the necessary tools, making it crucial for Scrum Masters to coach managers as well. Bernie recommends building a backlog of organizational impediments and focusing on the top priority that will move the ball forward most effectively.

Featured Retrospective Format for the Week: Sailboat

Bernie champions the Sailboat retrospective format for its simplicity and adaptability. While the basic format is straightforward, he appreciates that you can add layers of complexity as needed. Bernie tends to keep retrospectives simple and also mentions the “What the Duck?” technique as another valuable retrospective tool. He suggests incorporating creative elements like having people build LEGO representations of what they’re discussing, which helps teams visualize and engage with concepts more effectively.

To know more about LEGO Serious Play, check out the Serious Play book.

In this segment, we also refer to Dissociation in Psychology, which helps with “third position” coaching/thinking, and Bernie’s video on creative retrospective formats.

Self-reflection Question: How are you measuring whether your teams are becoming more self-directing, and what specific behaviors indicate they’re ready to operate with less guidance?

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Bernie Maloney

Bernie Maloney has helped teams grow businesses to beyond $4B / year, delivering products from consumer electronics to network infrastructure to services & payments. He helps clients achieve performance breakthroughs with their teams, organizations and themselves, and believes that leads both to outrageous effectiveness, and a whole lot more fun.

You can link with Bernie Maloney on LinkedIn, and visit Bernie’s website and YouTube Channel.

Mariano Gontchar: Fear-Free Teams—Creating Psychological Safety for High Performance

Mariano’s definition of Scrum Master success has evolved dramatically from his early days of focusing on “deliver on time and budget” to a more sophisticated understanding centered on team independence and psychological safety. Today, he measures success by whether teams can self-manage, communicate effectively with stakeholders, and operate without fear of criticism. This shift represents a fundamental change from output-focused metrics to outcome-focused team health indicators that create sustainable high performance.

Self-reflection Question: How has your definition of success evolved in your current role, and what would change if you focused on team independence rather than traditional delivery metrics?

Featured Retrospective Format for the Week: Frustration-Based Retrospective

Mariano’s retrospective approach focuses on asking team members about their biggest frustrations from the last sprint. This format helps team members realize their frustrations aren’t unique and creates psychological safety for sharing challenges. The key is always asking the team to propose solutions themselves rather than imposing fixes, making retrospectives about genuine continuous improvement rather than just complaining sessions.

Transform Your Agile Teams with Hard-Earned Lessons from Super-Experienced Scrum Masters

About Mariano Gontchar

Mariano is a Madrid-based Scrum Master with a unique multi-perspective journey through Agile roles. Having evolved from developer to Product Owner, Project Manager, and now Scrum Master, he brings comprehensive insights to team facilitation and backlog management. Mariano specializes in practical Agile adoption strategies that work in real-world environments.

You can link with Mariano Gontchar on LinkedIn.

Lilia Pulova: Building Self-Sufficient Teams Through Emotional Intelligence

Lilia defines success for Scrum Masters by asking a simple but powerful question: “Do people feel supported?” Her approach focuses on training teams to take on her responsibilities and make their own decisions. Rather than dictating solutions, she presents options and allows teams to choose their path. Over time, teams learn these options and develop independence in decision-making.

She maintains awareness by monitoring delivery metrics, watching for tickets that take too long, and staying attentive during daily stand-ups. With her primarily remote team keeping cameras open, Lilia reads emotions and body language to identify potential issues early, preventing small conflicts from escalating into major problems.

Self-reflection Question: How well do you read the emotional state of your team members, and what early warning signs might you be overlooking?

Featured Retrospective Format for the Week: 1-on-1 Retrospective

Lilia advocates for the 1-on-1 retrospective as her most effective format, explaining that people open up more in private conversations than in group settings. While group retrospectives can work well with smooth conversation flow, she finds that structured formats don’t always suit every team – sometimes the “lack of format” creates better outcomes. The key to successful 1-on-1 retrospectives is building strong relationships and establishing trust, which she considers the most important foundation for effective retrospectives.

The Scrum Master Toolbox Podcast Recommends…

🔥 In the ruthless world of fintech, success isn’t just about innovation—it’s about coaching! 🔥

Angela thought she was just there to coach a team. But now, she’s caught in the middle of a corporate espionage drama that could make or break the future of digital banking. Can she help the team regain their mojo and outwit their rivals, or will the competition crush their ambitions? As alliances shift and the pressure builds, one thing becomes clear: this isn’t just about the product—it’s about the people.

🚨 Will Angela’s coaching be enough? Find out in Shift: From Product to People—the gripping story of high-stakes innovation and corporate intrigue.

Buy Now on Amazon

The Scrum Master Toolbox Podcast Recommends…

About Lilia Pulova

Lilia Pulova, a former Business Intelligence Analyst, discovered her passion as a Scrum Master by chance. A natural communicator with a love for languages, she now bridges the gap between business and tech, translating complex needs into streamlined processes that boost productivity and keep teams aligned and focused.

You can link with Lilia Pulova on LinkedIn.