r/scrum • • Jan 02 '25

Junior dev saved our sprint by being a bit paranoid

676 Upvotes

Quick background: New junior dev joins our team, super enthusiastic about security stuff. During Sprint Planning, she's really adamant about adding extra story points to account for potential payment processor issues due to "crypto market volatility." Most of the senior devs were like "that's not even in our scope" but she wouldn't let it go.

I was about to move things along, but something made me pause and really listen. We ended up adding it to our risk assessment and slightly modifying our acceptance criteria to include a backup payment flow.

Thank. Freaking. God.

Mid-sprint, the crypto market does its thing, our payment processor has a meltdown, and starts rejecting valid transactions left and right. But because we'd actually planned for this "impossible" scenario, our sprint wasn't totally derailed. We flipped to the backup system and kept rolling.

The retrospective was pretty interesting - lots of "how did she know?" and "what other risks are we dismissing?" It's completely changed how we approach risk assessment in Planning.

Anyone else have stories about junior team members spotting risks that the seniors missed? How do you make sure everyone's voice gets heard during Planning, especially when their concerns seem far-fetched?


r/scrum • • 6d ago

Story My (former) employer this week, unfortunately

Post image
350 Upvotes

r/scrum • • Aug 12 '22

Advice To Give Mike Ehrmantraut - Agile Coach

Post image
259 Upvotes

r/scrum • • Nov 17 '22

Seen on Twitter.

Post image
230 Upvotes

r/scrum • • Jan 23 '26

We've all been there! What are your best strategies for keeping standups focused?

Post image
223 Upvotes

r/scrum • • Mar 28 '23

Advice To Give Starting out as a Scrum Master? - Here's the r/Scrum guide to your first month on the job

194 Upvotes

The purpose of this post

The purpose of this post is to compile a set of recommended practices, approaches and mental model for new scrum masters who are looking for answers on r/scrum. While we are an open community, we find that this question get's asked almost daily and we felt it would be good to create a resource for new scrum masters to find answers. The source of this post is from an article that I wrote in 2022. I have had it vetted by numerous Agile Coaches and seasoned Scrum Masters to improve its value. If you have additional insights please let us know so that we can add them to this article.

Overview

So you’re a day one scrum master and you’ve landed your first job! Congratulations, that’s really exciting! Being a scrum master is super fun and very rewarding, but now that you’ve got the job, where do you start with your new team?

Scrum masters have a lot to learn when they start at a new company. Early on, your job is to establish yourself as a trusted member of the team. Remember, now is definitely not a good time for you to start make changes. Use your first sprint to learn how the team works, get to know what makes each team member tick and what drives them, ask questions about how they work together as a group – then find out where things are working well and where there are problems.

It’s ok to be a “noob”, in fact the act of discovering your team’s strengths and weaknesses can be used to your advantage.

The question "I'm starting my first day as a new scrum master, what should I do?" gets asked time and time again on r/scrum. While there's no one-size-fits-all solution to this problem there are a few core tenants of agile and scrum that offer a good solution. Being an agilist means respecting that each individual’s agile journey is going to be unique. No two teams, or organizations take the same path to agile mastery.

Being a new scrum master means you don’t yet know how things work, but you will get there soon if you trust your agile and scrum mastery. So when starting out as a scrum master and you’re not yet sure for how your team practices scrum and values agile, here are some ways you can begin getting acquainted:

Early on, your job is to establish yourself as a trusted member of the team now is not the time for you to make changes

When you first start with a new team, your number one rule should be to get to know them in their environment. Focus on the team of people’s behavior, not on the process. Don’t change anything right away. Be very cautious and respectful of what you learn as it will help you establish trust with your team when they realize that you care about them as individuals and not just their work product.

For some bonus reading, you may also want to check out this blog post by our head moderator u/damonpoole on why it’s important for scrum masters to develop “Multispectrum Awareness” when observing your team’s behaviors:

https://facilitivity.com/multispectrum-awareness/

Use your first sprint to learn how the team works

As a Scrum Master, it is your job to learn as much about the team as you can. Your goal for your first sprint should be to get a sense for how the team works together, what their strengths are, and a sense as to what improvements they might be open to exploring. This will help you effectively support them in future iterations.

The best way to do this is through frequent conversations with individual team members (ideally all of them) about their tasks and responsibilities. Use these conversations as an opportunity to ask questions about how the person feels about his/her contribution on the project so far: What are they happy with? What would they like to improve? How does this compare with their experiences working on other projects? You’ll probably see some patterns emerge: some people may be happy with their work while others are frustrated or bored by it — this can be helpful information when planning future sprints!

Get to know what makes each team member tick and what drives them

  • You need to get to know each person as individuals, not just as members of the team. Learn their strengths, opportunities and weaknesses. Find out what their chief concerns are and learn how you can help them grow.

  • Get an understanding of their ideas for helping the team grow (even if it’s something that you would never consider).

  • Learn what interests they have outside of work so that you can engage them in conversations about those topics (for example: sports or music). You’ll be surprised at how much more interesting a conversation can become when it includes something that is important to another person than if it remains focused on your own interests only!

  • Ask yourself “What needs does this person have of me as a scrum master?”

Learn your teams existing process for working together

When you’re first getting started with a new team, it’s important to be respectful of their existing processes. It’s a good idea to find out what processes they have in place, and where they keep the backlog for things that need to get done. If the team uses agile tools like JIRA or Pivotal Tracker or Trello (or something else), learn how they use them.

This process is especially important if there are any current projects that need to be completed—so ask your manager or mentor if there are any pressing deadlines or milestones coming up. Remember the team is already in progress on their sprint. The last thing you need to do is to distract them by critiquing their agility.

Ask your team lots of questions and find out what’s working well for them

When you first start with a new team, it’s important that you take the time to ask them questions instead of just telling them what to do. The best way to learn about your team is by asking them what they like about the current process, where it could be improved and how they feel about how you work as a Scrum Master.

Ask specific questions such as:

  • What do you like about the way we do things now?

  • What do you think could be improved?

  • What are some of your biggest challenges?

  • How would you describe the way I should work as a scrum master?

Asking these questions will help get insight into what’s working well for them now, which can then inform future improvements in process or tooling choices made by both parties going forward!

Find out what the last scrum master did well, and not so well

If you’re backfilling for a previous scrum master, it’s important to know what they did so that you can best support your team. It’s also helpful even if you aren’t backfilling because it gives you insight into the job and allows you to best determine how to change things up if necessary.

Ask them what they liked about working with a previous scrum master and any suggestions they may have had on how they could have done better. This way, when someone comes to your asking for help or advice, you will be able to advise them on their specific situation from experience rather than speculation or gut feeling.

Examine how the team is working in comparison to the scrum guide

As a scrum master, you should always be looking for ways to improve the team and its performance. However, when you first start working with a team, it can be all too easy to fall into the trap of telling them what they’re doing wrong. This can lead to people feeling attacked or discouraged and cause them to become defensive. Instead of focusing on what’s wrong with your new team, try focusing on identifying everything they’re doing right while gradually helping them identify their weaknesses over time.

While it may be tempting to jump right in with suggestions and mentoring sessions on how to fix these weaknesses (and yes, this is absolutely appropriate in the future), there are some important factors that will help set up success for everyone involved in this process:

  • Try not to convey any sense of judgement when answering questions about how the team functions at present or what their current issues might be; try not judging yourself either! The goal here is simply gaining clarity so that we can all move forward together toward making our scrum practices better.

  • Don’t make changes without first getting consent from everyone involved; if there are things that seem like an obvious improvement but which haven’t been discussed beforehand then these should probably wait until after our next retrospective meeting before being implemented

  • Better yet, don’t change a thing… just listen and observe!

Get to know the people outside of your scrum team

One of your major responsibilities as a scrum master is to help your team be effective and successful. One way you can do this is by learning about the people and the external forces that affect your team’s ability to succeed. You may already know who works on your team, but it’s important to learn who they interact with other teams on a regular basis, who their leaders are, which stakeholders they support, who often causes them distraction or loss of focus when getting work done, etc..

To get started learning about these things:

  • Gather intelligence: Talk with each person on the team individually (one-on-one) after standups or whenever an opportunity presents itself outside of agile events.

  • Ask them questions like “Who helps you guys out? Who do you need help from? Who do we rely upon for support? Who causes problems for us? How would our customers describe us? What makes our work difficult here at [company name]?

Find out where the landmines are hidden

While it is important to figure out who your allies, it is also important to find out where the landmines are that are hidden below the surface within EVERY organization.

  • Who are the people who will be difficult to work with and may have some bias towards Agile and scrum?

  • What are the areas of sensitivity to be aware of?

  • What things should you not even touch with a ten foot pole?

  • What are the hills that others have died valiantly upon and failed at scaling?

Gaining insight to these areas will help you to better navigate the landscape, and know where you’ll need to tread lightly.

If you just can’t resist any longer and have to do something agile..

If you just can’t resist any longer and have to do something agile, then limit yourself to establishing a team working agreement. This document is a living document that details the baseline rules of collaboration, styles of communication, and needs of each individual on your team. If you don’t have one already established in your organization, it’s time to create one! The most effective way I’ve found to create this document is by having everyone participate in small group brainstorming sessions where they write down their thoughts on sticky notes (or index cards). Then we put all of those ideas into one room and talk through them together as a larger group until every idea has been addressed or rejected. This process might be too much work for some teams but if you’re able to make it happen then it will help establish trust between yourself and the team because they’ll feel heard by you and see how much effort goes into making sure everyone gets what they need at work!

Conclusion

Being a scrum master is a lot of fun and can be very rewarding. You don’t need to prove that you’re a superstar though on day one. Don’t be a bull in a china shop, making a mess of the scrum. Don’t be an agile “pointdexter” waving around the scrum guide and telling your team they’re doing it all wrong. Be patient, go slow, and facilitate introspection. In the end, your role is to support the team and help them succeed. You don’t need to be an expert on anything, just a good listener and someone who cares about what they do.


r/scrum • • Mar 06 '21

Success Story How it works

Post image
190 Upvotes

r/scrum • • Jul 25 '21

Discussion New teams adopting scrum...why they fail

Post image
163 Upvotes

r/scrum • • Jan 15 '25

Built a meeting cost calculator

Post image
159 Upvotes

A fun little tool that visualizes your meeting costs in real-time https://meeting-cost-ten.vercel.app/


r/scrum • • Mar 28 '25

Discussion 5 Hard-Earned Lessons from an experienced Scrum Master – the Guide Won’t Tell You

142 Upvotes

I’ve been a Scrum Master for years now across startups, mid-tier firms. Certifications and the Scrum Guide got me started, but the real learning came from the trenches. Here’s 

what I wish I’d known earlier—hope it helps some of you decide if Scrum is for you or not.

  1. You’re Not a Meeting Scheduler, You’re a Barrier-Buster: Early on, I got stuck facilitating every standup and retro like a glorified secretary. Big mistake. Your job isn’t to run the show—it’s to clear the path. When my team hit a dependency wall with another group, I stopped “noting it” and started chasing down their lead, unblocking it myself. Teams notice when you fight for them, not just log their complaints.

  2. Self-Organization Doesn’t Mean Hands-Off: The Guide says teams self-organize, but don’t kid yourself—most need a nudge. I had a dev team spinning on backlog priorities until I coached them to own it with a simple “What’s the one thing we can finish this sprint?” question. Guide them to independence, don’t just wait for it.

  3. Tech Chops Matter (Even If They Say They Don’t): Non-technical SMs can survive, but you’ll thrive if you speak the language. I learned basic Git commands and SQL queries—not to code, but to grok what devs were griping about. When a pipeline broke, I could ask smart questions instead of nodding blankly. Respect skyrocketed.

  4. Burnout’s Real—Pick Your Battles: This role’s a marathon. I nearly quit after a year of fighting every anti-Agile exec. Now, I focus on one big win per quarter—like getting a team to ditch pointless status reports—over death-by-a-thousand-cuts fixes. Protect your energy; you can’t fix everything.

Bonus tip: If your team’s humming and you’re twiddling your thumbs, you’re doing it right. Success is them not needing you 24/7.

What’s your take? Any lessons you’d add from your own SM grind?


r/scrum • • Jun 18 '21

Our Sprint Goal... ...is to finish the backlog items

Post image
134 Upvotes

r/scrum • • Jun 13 '23

Exam Tips Cleared PSM-1 with 97.5% in first attempt. Two tips for anyone that might be thinking of attempting this exam

130 Upvotes

I only followed the following two things while preparing and this helped:

  1. Read and understand the scrum guide really well, read it for atleast 3-4 times and since it's an open book exam, open the guide on another tab while you give the exam, and have a quick look when you feel stuck in exam.

  2. Give multiple mock tests here (https://www.scrum.org/open-assessments/scrum-open) and here (http://scrumquiz.org/#/scrum-master-practice-test) till you consistently score more than 95% in these tests with a lot of time left. Some questions from these are repeated in the exam, and these questions broaden your understanding.

Also, no matter what you do, please DON'T refer to mlapshin mock tests which everyone swears by. These tests follow 2017 scrum guide, and hence, some answers are incorrect.


r/scrum • • Aug 31 '22

I almost fell off my chair laughing. Please don't be offended!

Thumbnail
reddit.com
115 Upvotes

r/scrum • • Dec 27 '20

The Scrum Master We Need

Post image
111 Upvotes

r/scrum • • Oct 12 '21

Advice To Give So you want to be a Scrum Master? (or you are looking to improve)

110 Upvotes

This is just my opinion based on my experience as a Scrum Master. None of it is a factual.

This is going to be terribly written and probably won’t make sense. I am having to rush this. I will come back and edit it so it reads better in the future.

Who this is for: People looking to become Scrum Masters. People who are new in the role of Scrum Master. Anyone with an interest in leadership.

Some hard truths:

If you do not have experience working in a range of teams then being a Scrum Master is off the cards until you have that under your belt. It does not have to be experience with Agile Teams, just working closely with people.

If you are not a people person you will struggle.

No one cares about certs. The benefit of getting a cert is the training. Certs do not prove you have what it takes to be a good Scrum Master.

This is not an entry-level job and will require demonstrable experience. I have seen people from HR, Project Management, QA, Software Engineering become good Scrum Masters. You do not necessarily require lots of experience in an Agile environment if you can prove your other important skills.

Some good news:

I have seen people from HR, Project Management, QA, Software Engineering become good Scrum Masters. You do not require lots of experience in an Agile environment if you can prove your other important skills.

Regardless of your current job role or experience, there are things you can do to build your skills and gain useful experience for getting that Scrum Master job. This applies even in non Agile environments.

The stuff I want to chat about will help your career even if you do not become a Scrum Master or work in Agile.

Becoming a good Scrum Master:

Very little about being a Scrum Master is chatting about the framework or reciting the Scrum Guide. This role is so much more. Check out these areas below, treat it like a research list and always assume you are only scratching the surface of a topic. I will not provide resources for these but there is plenty out there.

A Scrum Master is a facilitator. This is key, learn how to lead productive meetings/workshops/retros from the background or if required drive, them hard to reach the desired outcomes. Ensure that everyone has a voice and everyone is heard. Make sessions fun and valuable, people should be happy when they find out you are hosting.

A Scrum Master is a coach. Learn the difference between mentoring and coaching and get good at both. Learn how to ask powerful questions. Get comfortable with people coming up with ideas and solutions you do not agree with.

A Scrum Master builds Psychological Safety everywhere This is fundamental to healthy and high performing teams. Look into project Aristotle. Read up on techniques and approaches, advocate for them across your company, be a bastion of safety.

A Scrum Master is a conflict Resolver Learn techniques to deal with conflict. Embrace bold and difficult conversations, do not shy away from conflict. However, build a safe and constructive environment.

A Scrum Master is a great team builder Learn techniques for team building that create deep and lasting bonds. See opportunities for team building everywhere.

A Scrum Master can do root cause analysis. Everyone can come up with a solution, but are they addressing the cause? Learn how to delve into issues and understand the symptoms and the causes. Learn how to guide a team to do this.

A Scrum Master is not a Sith and does not deal in absolutes. Preach that everything is an experiment. Things can be both good and bad and you need to expose both sides, or better yet enable the team to do this. Any solution or idea should be treated as an experiment that must be measured.

A Scrum Master understands Output vs Outcomes Jeff Patton is your friend, read and watch his stuff.

A Scrum Master knows how to give and take feedback Believe it or not, this is a really hard skill to master but it will serve you well.

A Scrum Master holds people/teams accountable or better yet, makes them accountable for themselves. This is not telling people off, it is much deeper. A Scrum Master encourages a team to experiment whilst ensuring they understand the cost of such an experiment. The SM coaches the team to badly face their problems and when they are off track. A well-coached team will be self-correcting and will be happy to chat about delivery.

A Scrum Master challenges assumptions Everyone has ideas and opinions. Most will be wrong and that is ok. What is important is that we test them and back up the follow up with data. For example, A PO thinks a feature will solve a Users Problems, cool let us prove it!

A Scrum Master is hungry for knowledge This is self-explanatory. There are loads of books, videos, podcasts, Meetups, etc, get stuck in and join at least one community.

There are loads more and I may update this from time to time. Hopefully, others will add in the comments too!

So what to do next?

You should survey yourself, there are tests out there but look at the above and figure out where you need to improve. Bring these elements into your working life right now. Very quickly you can build a bank of scenarios that you could discuss in an interview. For example, even in a non Agile company, you should be able to answer “Can you tell me about a time that you successfully facilitated a conflict resolution”.

Some examples:

Offer to hold a retrospective for a recent project, event, session, etc

Offer to hold a team building session, this is a good idea when someone new joins your team

Offer to host your team meeting in a different format

Offer to run a goal/OKR setting session for your team

Whatever you do, get into the mindset of proving the impact of your actions.

The big one:

So you say your company are not Agile, well a Scrum Master is an advocate for Agile and sees opportunities everywhere. Agility is not a framework but a set of principles and I am yet to meet anyone who disagrees with them. Be the change that you want to see in your company. Get stakeholder buy-in and run very small experiments. If you can prove you have made a small but meaningful difference in your non-agile team or company, it will take you much further than a Cert would. If I were interviewing someone who was not currently in an Agile team, I would be probing to find out what they have done in that space to make a difference. Therefore, when I see people mention that their company. Is not Agile and they simply want to move into an already Agile environment I can’t help but think they are missing out on key opportunities to have an impact.


r/scrum • • Sep 27 '23

Advice Wanted I'm really fed up with Scrum please enlighten me

106 Upvotes

Hi,

I'm a developer with 8 years of experience. All my projects were "agile" using Scrum. All projects had the same issues which really start to make me hate Scrum right now.

Please enlighten me what the benefits of scrum are. Right now I only see negatives.

Too many meetings

Yes, it sounds like a cliche but beside the daily standup we had pre-finements, re-finements, task plannings, separate estimation meetings, Sprint plannings, reviews, retros + many irregular meetings to clarify stuff or discuss something that came up in a retro.

No time for unplanned work

Everything needs a story. Want to evaluate a tool that might help your team? Better write a story for next Sprint. Want to get rid of technical debts? Where is the story for that? Oh, the customer need information about this or that? Story please! Most of the time this means I have to do this stuff after work.

Religious Scrum Masters

Scrum is the best thing ever, it has no flaws. If you don't like it, you are the problem or you just don't understand it. :( You are not happy about the third scrum meeting this week which interruptes your coding flow? Can't you see the benefit of all these great meetings? They help you to be more productive.

Commitment

For me commitment is another word for deadline.

The team commits itself to a certain amount of stories they get done this Sprint. It's the teams commitment. It doesn't mean you have to do overtime but the stories need to get done. Whatever it takes. Don't do overtime. But hold the commitment. PLEASE!!! Remember, no overtime, just get it done!!!

Self Organized

The team is self Organized. So please get your shit together. The scrum master doesn't have to do this. The team can do it itself. Isn't that great? The project manager doesn't need to do everything. A self Organized team can handle it much better,... oh you want to code? Please schedule some meetings first. Remember you are self Organized.

Cargo Cult

We need a DoR and a DoD in Confluence that nobody cares about. Please schedule some meetings for that.

I hope you get the idea what I'm talking about. I just want to code 🥹

###############

Thank you for all your comments. Some helped, some created even more negative feelings and brought up some more points 🥹

Story Estimation

Of course we estimate stories using the Fibonacci sequence. They are just a rough estimation and the numbers don't mean days of work needed for a story. But please be as precise as possible. We need the numbers for controlling. The customer pays us by story points.

You want to do estimations in T-Shirt sizes? Nada that's too difficult to calculate with. Let's keep the numbers.

There are no roles except PO, SM, Developers

What about architects? What about DevOps? What about UI/UX? How to handle different experiences (Junior/Senior)? Some people hate Frontend, some people have 0 knowledge and interest in docker, jenkins, databases. Not everyone is a Full Stack Developer with 10 years experience. Who does the controlling? Who attends endless meetings with the customer that focuses on long term goals? Who talks to the other teams that work on other Microservices in our system?

For me it seems like scrum comes from a time where there were monoliths deployed on local servers. But times have changed. Scrum didn't.

Retro

As already written in a comment most of the retros result in absolute bullshit action items. The worst of them all is to schedule another meeting to discuss it even further.


r/scrum • • Jan 12 '25

Story Turned my zombie stand-up into a power session

97 Upvotes

After noticing our stand-ups were turning into 25-minute snoozefests, I flipped the script. Started by banning status updates and instead focused purely on coordination needs and roadblocks. Really glad I did it! The quiet devs suddenly came alive when they realized they didn't need to give boring progress reports. We even ditched the "three questions" format and just let the conversation flow naturally within our 15-minute timebox. Our velocity actually improved since making this change, and the team seems way more pumped.

Has anyone else tried breaking away from traditional stand-up formats?


r/scrum • • Nov 07 '25

Thought on this?

Post image
96 Upvotes

Personal opinion: It isn’t truly a full-time role unless you’re driving change at the organizational level - leading end-to-end transformation and supporting enterprise-wide operational decisions. At that point, the role becomes closely aligned with change management, which every organization genuinely needs.

Unfortunately, most Scrum Masters today are disempowered, confined to the team level rather than influencing systemic change.

I also believe that Agile thought leaders - including Allen, Jeff, and Ken — should take some accountability for not ensuring the framework was properly understood and adopted by business leaders, not just delivery teams.

Like I’ve said before, the first mistake the founders of Scrum made was giving the role a title that made little sense outside the Agile community.

“Scrum Master” is vague, ambiguous, and frankly sounds poor - which is why it’s been left open to so much misinterpretation.


r/scrum • • Jul 16 '23

Advice Wanted What does a Scrum Master actually do all day? [Serious]

96 Upvotes

I've been a BA/PO/ProjM/ProdM for the past 6 or so years and recently got into the contracting game over here which is sweet cash (nearing $1k/day), but I have been looking at what some of the Scrummies are getting paid and it's absolutely bonkers (up to $2k/day, which is the highest paid role in the team).

My question is, what do Scrum Masters actually do all day?

Run Scrum ceremonies, make reports on the team's progress, give advice and make pretty jam/miro/lucid boards for Retro?

What else?

I mean granted my role only takes up maybe 3 - 4 hours a day on any given day but it seems like most days a Scrum Master is doing 15mins - 2 hours Max, for up to $2,000?

What am I missing here? Are there some secret Scrum Master activities that you only discover when you get your $500 CSM certificate after a 2 day course?


r/scrum • • Dec 29 '24

SAFe is just like playing Waterfall with more steps

87 Upvotes

You know how everyone's drinking the SAFe Kool-Aid lately? Well, I'm starting to think we're all just playing pretend here.

Don't get me wrong, I get why big companies love SAFe. It's got all the right buzzwords: team autonomy, incremental delivery, collaboration. But let's be honest - when you peel back all those fancy ceremonies and roles, aren't we just doing waterfall with extra steps?

Those PI planning sessions crack me up. We spend days mapping out the next few months in detail, while the Agile Manifesto is literally telling us to embrace change. The irony is real, folks.

And can we talk about team autonomy? SAFe keeps preaching about empowered teams, but in reality, it feels like we're just following a more complicated command-and-control structure. The decisions still come from up high, just wrapped in fancier packaging.

I will say though, SAFe isn't totally useless. It works pretty well in highly regulated industries where you need that extra layer of control and planning. But maybe we need to stop pretending it's actually agile?

What's your experience been like? Are you also feeling this disconnect, or am I just being too cynical here?


r/scrum • • Jun 26 '24

The majority of Scrum Masters are not fit for their position!

87 Upvotes

According to data from ScrumMatch (which validates Scrum Master capability with in-person reviews), most Scrum Masters lack the necessary knowledge and understanding of Scrum to effectively lead their teams.

The numbers tell a chilling story:

  • 38% are grossly incompetent: These individuals, despite holding Scrum Master roles, have no understanding of Scrum and likely haven't even read the Scrum Guide.

  • 10% are also incompetent: They've read the Scrum Guide but can't apply its principles effectively and yet still apply for Scrum Master roles.

  • 13% can apply Scrum at a basic level: This is not sufficient for a Scrum Master and should be the minimum expected of any Scrum Team member.

Worse many of the low skilled Scrum Masters assessed had been in the role for a decade or more!

And that's 61% of Scrum Masters? Alarmingly, some are even celebrating being part of this group, mistakenly believing it makes them a good hire.

It does not.

This leaves only the top 39% (just over one-third) of Scrum Masters able to fulfil any aspect of the accountability described in the Scrum Guide, with a mere 3% able to fulfil it entirely.

This is why Agile Coaches and Scrum Masters are losing their jobs: In the boom times of the agile economy, these incompetent individuals were overlooked, but now, as times are tougher, the wheat is being separated from the chaff. 🌾

Let's strive for better standards and ensure our Scrum Masters are truly equipped as leaders!

TakeBackScrum


r/scrum • • Aug 11 '26

our standup starts with "let's give it two more minutes" every single day and i think it's making things worse

86 Upvotes

remote team, standup at 9:00. every morning the SM goes "let's give it a couple minutes for the others" and now the real start is like 9:05-ish. the people who show up on time just sit there waiting

i don't want to go async, the live call is the whole point for us. and i don't want to start tracking who's late, that's a great way to make everyone hate standup even more.

so what's left? just starting without them? i wanna know what's worked for y'all because right now it feels like the choices are to nag people or ignore it.


r/scrum • • Feb 14 '26 Bravo

Discussion My devs are on AI steroids and Scrum is officially too slow. Now what?

81 Upvotes

Serious talk. My team has fully embraced AI agents/LLMs and their velocity is absolute madness.

I can’t keep the backlog relevant. Honestly, it just looks like a graveyard of "things that are already done." By the time I refine a ticket or set up a sprint, they’ve usually built it, refactored it, and moved on.

Scrum rituals now feel like massive administrative overhead rather than actual work.

For those managing high-velocity, AI-native teams: Are we ditching Scrum? Switching to pure Kanban? Or just vibing?

How do I actually manage this chaos without slowing them down?


r/scrum • • Feb 15 '25

Most Scrum Masters are babysitters, not leaders

73 Upvotes

Too many SMs are just checking off ceremonies and tracking velocity instead of truly enabling their teams.

Real Scrum leadership isn't about policing standups or updating boards. It's about building self-managing teams that don't need you hovering over them.

I keep asking myself: Have I created a space where my team feels safe to take risks? Am I actively removing organizational BS that slows them down? Does everyone connect their daily work to our product vision?

What do you guys think? Have you caught yourself slipping into babysitting mode? What helped you break out of it?