Summary5 min read

Podcast Summary:

The Slippery Slope — How Small Compromises Lead Teams to Abandon Scrum Entirely | Juliana Stepanova
Podcast: Scrum Master Toolbox Podcast
Host: Vasco Duarte
Guest: Juliana Stepanova
Air Date: February 3, 2026

Episode Overview

In this “Team Tuesday” episode, Vasco Duarte welcomes back Juliana Stepanova to explore a crucial challenge faced by many agile teams: how seemingly minor shortcuts and compromises can gradually undermine and eventually dismantle the entire Scrum framework within a team. Drawing from a real-life story, Juliana shares how well-intentioned adaptations can snowball into habits that are hard to reverse, and offers insights into recognizing and addressing the slippery slope before it jeopardizes team effectiveness.

Key Discussion Points and Insights

1. Juliana’s Go-To Book for Scrum Masters ([01:23]–[03:24])

Juliana recommends "Startup, Scaleup, Screwup" by Jurgen Appelo as the book that has most inspired her.
- "What is cool there... you have assured chapters for each particular tool which are covering the most essential stuff for the Scrum Master or Agile Coach to know." — Juliana Stepanova [02:15]
She values its practical applicability not just at the team level, but across the whole organization:

"...not only focused on the team level but as well to the company level... in this book you'll find the tools which you can apply all over the company, not only for the team." — Juliana Stepanova [02:45]

2. Story of a Scrum Team’s Downward Spiral ([04:20]–[06:38])

Juliana shares an example of a classical Scrum team:
- Seven developers, experienced in Scrum, working in IT development.
The problem starts with small deviations from Scrum rules, specifically time-boxes:
- For example, extending the Daily Scrum from 15 to 30 minutes to “fit the team’s needs.”
- Initially, such decisions seem harmless—just practical adaptations.
- Over time, they signal that rules and frameworks are negotiable, weakening respect for Scrum structure:
  
  "...it starts to change our mindset in the way that this rules, this frameworks could be changed up to some conditions and... it's not correct." — Juliana Stepanova [04:55]
This mindset shift paves the way for further, bigger deviations:
- Skipping retrospectives due to operational pressures like releases or test phases.
- Gradual erosion of regular Scrum rituals.
The cumulative effect is profound:
- "...in a time frame, I would say half a year, the Scrum will not work at all. And you cannot bring it back in one day because you have already habit to not respect this framework." — Juliana Stepanova [06:15]

3. Causes Behind the Slippery Slope ([06:38]–[09:42])

Host Vasco's Framing:
- "I would call it the slippery slope, right? Like it's one small 'let's skip it here,' it's another small 'let's skip it there,' and soon you're skipping the whole thing." — Vasco Duarte [09:42]
Juliana’s Diagnosis of Causes:
- External Influences:
  - Company-wide meeting schedules clashing with Scrum events.
  - Lack of alignment between multiple development teams’ Scrum rituals.
  - Management pressures leading to skipped or rescheduled events.
- Team Habituation:
  - The team becomes used to bending or breaking rules “for good reasons,” making such behavior acceptable.
- Outside Pressure vs. Internal Discipline:
  
  "...mostly their influence, it's of course outside the team. So itself the team, they would like to have all the scheduled events as it is. But if this flow brokes on some way it could repeat, repeat and happen again. And with the time it's really like damaging behavior." — Juliana Stepanova [09:01]

4. Root Causes: Lack of Buy-In and Excessive Chaos ([09:42]–[11:19])

Host’s Reflection:
- Vasco considers if some teams were never truly invested in Scrum to begin with:
  
  "...the team never really wanted to work with Scrum anyway. Right. Like they were never bought in." — Vasco Duarte [09:56]
- Alternatively, teams may be overwhelmed by constant firefighting and management pressure, making Scrum rituals feel expendable.
Juliana’s Validation:
- Teams who choose Scrum themselves are more likely to stick with it and protect its rituals.
  
  "...it's like 90% of success when the team really would like to do it and see how it works for the best productivity and the best results." — Juliana Stepanova [10:48]
- Imposed frameworks struggle to survive; enthusiastic adoption is key.

5. Solutions: Re-centering on Purpose and Team Autonomy ([11:19]–[11:53])

Scrum as a Means, Not an End:
- "Scrum is a solution. It's not the goal... always be aligned on what the goal is because Scrum might not be the solution." — Vasco Duarte [11:25]
- Sometimes, fixing underlying problems (e.g., high “quality debt”) should take precedence over process adherence.
Takeaway:
- Team alignment and genuine buy-in are critical to sustaining Scrum.
- Scrum Masters must watch for small erosions and address their roots, especially those coming from outside the team.

Notable Quotes & Memorable Moments

On the Dangers of Small Compromises:

"...if you have already the habit to not respect this framework, you can't bring it back in one day." — Juliana Stepanova [06:15]
On Organizational Impact:

"...influence from other departments was not respecting or not taking into account the Scrum rituals... This is the point where the Scrum Master should work more not on the team level, but above it..." — Juliana Stepanova [07:47]
On Team Buy-In:

"When the team really would like to do it and see how it works for the best productivity and the best results, that's 90% of success." — Juliana Stepanova [10:48]
On Solutions and Focus:

"...Scrum is not necessarily a good solution if what you have is internal chaos with constant firefighting and so on. Maybe we should focus on paying the quality debt first." — Vasco Duarte [11:37]

Important Timestamps

01:23 — Juliana introduces her favorite book, “Startup, Scaleup, Screwup.”
04:20 — Juliana begins her story of the “slippery slope” in a Scrum team.
06:38 — Vasco asks about underlying causes for drifting away from Scrum.
07:47 — Juliana explains how external pressures and habit formation lead to decline.
09:42 — Vasco highlights the “slippery slope” and probes root causes.
10:35 — Juliana emphasizes voluntary adoption and ownership of Scrum.
11:19 — Vasco suggests aligning on goals, not just processes.

Key Takeaways

Small deviations from Scrum rules, if left unchecked, rapidly become entrenched bad habits.
External pressures—like organizational misalignment and management priorities—often drive teams to compromise on Scrum.
True commitment and understanding of Scrum by the team are crucial; imposed methods rarely stick.
Scrum Masters must operate beyond the team, influencing wider organizational practices to protect and enable Scrum rituals.
Focus on underlying goals—sometimes, process compliance is less urgent than addressing root causes such as chaos or poor quality.

A candid, practical episode that rings true for any Scrum Master or team struggling with “framework fatigue.” Juliana’s stories and Vasco’s questioning provide tactical and strategic insight into sustaining agility in the real world.

Loading summary

Transcript13 lines

[00:04]
A
Hey there Agile adventurer, just a quick question. What if for the price of a fancy coffee or half a pizza, you could unlock over 700 hours of the best agile content on the planet? That's audio, video, E courses, books, presentations, all that you can think of. But you can also join live calls with world class practitioners and hang out in a flame war free and AI slop clean slack with the sharpest minds in the game. Oh, and yes, you get direct access to me, Vasko, your Scrum Master Toolbox podcast. No, this is not a drill. It's this Scrum Master Toolbox membership and it's your unfair advantage in the agile world. So if you want to know more, go check out scrummastertoolbox.org membership, that's scrummastertoolbox.org Membership. And check out all the goodies we have for you. Do it now. But if you're not doing it now, let's listen to the podcast. Hello everybody. Welcome to our Team Tuesday this week with Juliana Stepanova. Hey Juliana, welcome to the show or welcome back to the show I should say.
[01:22]
B
Hello everybody.
[01:24]
A
So Tuesday is Team Tuesday here on the podcast. But before we dive into that, do share with us what is the book that most inspired you in your career as a Scrum Master?
[01:36]
B
So it's a hard question because we have really great and brilliant books and on my shelf I have I don't know how many of them and like in a ten times more on their like in the email version so an electronic version but one book that I really very like it's startup scale up screw up from Jugen Apello and I use this book for inspiration and actually recommended to read it at least once but I use it constantly. So in this book it's actually it's officially said that 42 tools to accelerate your business growth and what is cool there. So you have like an assured chapters for each particular tool which are covering the most essential stuff for the Scrum Master for Agile coach to know. So if you are looking for what you really need to know before you start working or growing your career as a Scrum Master, please read this book in the very easy way and from other side with another perspective and what is most important for me not only focused on the team level but as well to the company level because sometimes Scrum Master not forget but not paying so many attention on the company level or between departments and actually in this book you will find the tools so normal tools which you can apply all over the company, not only for the team.
[03:24]
A
Very Good. And definitely start up, scale up and Screw up is a great book. So check it out. The link is in the show notes so that people can easily find it and as Juliana said, be inspired perhaps once, maybe more to do things differently in their organizations. All of this, the books, the things we try out, what we try to learn, we apply to help teams. But sometimes even when we try, we can't help teams. And that's the story we would like to explore. Juliana. So share with us the story of a team, tell us a little bit about their context so that we may know what they were working on, how big the team was and so on. And then walk us through those little behaviors, attitudes, patterns that maybe were small at first, but grew and over time became a problem for the team.
[04:21]
B
Okay, so I will take the classical Scrum team example. So it was seven, seven developers as a team, classical IT development and the habit. So and the team has already practiced in Scrum for years. So they have like a lot knowledge what the Scrum is, how it's applied and so on. And the habits was or behavior is like not respecting in the small way some written rules I would say. So if the classical daily should be 15 minutes, they say okay, we are bigger team, we can do it in 30, we need this time. And if you have it like once you see things, it's okay, but it starts to change our mindset in the way that this rules, this frameworks could be changed up to some conditions and with a small stuff that it's not correct. So as a Scrum master here their answer would be or the solution would be to find out what the problem to have this 15 minutes. So if it happens once, okay, could be. But if it's repeatedly coming in the life and appear, the question is how to to put it back on the 15 minute time box. And actually what caused this change. And then it starts, oh, let's keep the retro, we don't have time today we have release or the test phase or we have a lot of other stuff or not respecting the structure in their like continuous time, it bring to the condition that in a time frame, I would say half a year, the Scrum will not work at all. And you cannot bring it back in one day because you have already habit to not respect this framework.
[06:39]
A
So. So I can totally see like this habit of like you know, small changes over time kind of compound and accumulate and eventually destroy the ability to do to execute the repeatable process. And I've seen that in many situations. But I think that an interesting question here is why does it even start happening? So I mean, the daily meeting I can totally see why this would happen, right? Like there's just too much stuff that is going on. Maybe the team is working on four or five different projects and they're inviting all of the stakeholders at the same time to the daily meeting. Like, it's easy to imagine why the daily meeting would get out of control and maybe become one hour. And then people would go like, hey, this is not productive anymore. Let's do this without having the daily meeting, which is of course in itself already a big red flag. But what drives these teams kind of slowly push back and even discard the process that in the end is there to help them succeed.
[07:42]
B
It the course actually the cost could be very different. Started from the influence from other departments was not respecting or not taking into account the Scrum rituals. For example, that time we have more than six or seven development teams with a not aligned Scrum rituals days and if we have some important meeting all over the company. So it's hard to choose date and time to not bother the Scrum events. And this is what's like an exactly this point where the Scrum Master should work more not on the team level, but above it to align and to allow to have some time or some days where the company meetings can can be done. And when it happened once, it's exactly now the question is that our brain is changing that you have in your head. Yes, if we have a good reason, we can skip it or to postpone it, or to reschedule it. And then if you have another reason, critical bug or some very important question from the management and you say probably this is exactly this point where we can exactly the skip. So like in pain, which coming directly on the moment it's taken advantage with comparing to this following the rules, following the schedule and mostly their influence, it's of course outside the team. So itself the team, they would like to have all the scheduled events as it is. But if this flow brokes on some way it could repeat, repeat and happen again. And with the time it's really like damaging behavior.
[09:42]
A
Yeah. So what you're describing sounds familiar. I would call it the slippery slope. Right. Like it's one small let's skip it here. It's another small let's keep it there and soon you're skipping the whole thing. And I get that. I get that that dynamic can emerge. What I'm considering is like from us as Scrum masters is what might be the reasons and the One that comes to mind immediately is that the team never really wanted to work with Scrum anyway. Right. Like they were never bought in. That was not something they wanted. They just were told, you're going to work with Scrum. Now that would be one reason. Another reason would be chaos. Right. Like constant firefighting and lots of pressure from management. That's also a potential reason. What other reasons do you see that may lead teams to get into this slippery slope anti pattern?
[10:36]
B
For sure, for sure. And actually the first reason that you are telling, it's like the team was not chosen by themselves to use the Scrum. So I saw the teams I work with, the teams who really come to the management say, yes, we would like to try. We are really see that it can work for us. And they are like standing behind this framework and they are protecting the framework in the team by themselves, not only with the help of Scrum Master. And then like it's like 90% of success when the team really would like to do it and see how it works for the best productivity and the best results.
[11:20]
A
Yeah, absolutely. And this also highlights how important it is to make sure that we're helping the team doing something they already want to do. Right. Like Scrum is a solution. It's not the goal. Right. And we need to always be aligned on what the goal is because Scrum might not be the solution. Like Scrum is not necessarily a good solution if what you have is internal chaos with constant firefighting and so on. Maybe we should focus on paying the quality debt first. Yeah, but that's a great point. Thank you for sharing that with us, Juliana.
[11:53]
B
Thank you very much.
[11:58]
A
Alright, I hope you liked this episode, but before you hit next episode, here's the deal. This podcast is powered by people like you. The members who wanted more than just inspiration. They wanted real tools and real connection to people who are practicing Agile every day. We're talking access to over 700 hours of agile gold, CTO level strategy talks, summit keynotes, live workshops, E courses, Deep Dive interviews, books. And if you're into no estimates, we got the pioneers of no Estimates in those Deep Dive interviews as well. Agile Business intelligence, creating product visions, coaching your product owner courses, you name it. You'll get invites to monthly live Q&As with agile pioneers and practitioners. Plus a private Slack community which is free of all of that AI slop you see everywhere. And of course, without the flame wars, it's a community of practitioners that want to learn and thrive together. It's the best place to connect with community and learn together. So if this podcast has helped you before, imagine what you will get from this podcast membership. So head on over to scrummastertoolbox.org membership and join the community that's shaping the future of Agile. We have so much for you, so check out all the details@scrummastertoolbox.org membership because listening is great. It's important. But doing it together, that's next level. I'll see you in the community. Slack we really hope you liked our show. And if you did, why not rate this podcast on Stitcher or itunes? Share this podcast and let other Scrum masters know about this valuable resource for their work. Remember that sharing is carrying.