r/scrum • u/penfoc007 • 7h ago
r/scrum • u/takethecann0lis • 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
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 • u/jiralearner • 20h ago
Looking for Part-Time Jira Administration / Atlassian Freelancing Opportunities
reddit.comIs Scrum dead in the era of AI?
Should we inspect and change the way software delivery is managed?
The following article provides a balanced view.
https://medium.com/agileinsider/in-an-ai-era-is-scrum-dead-or-was-it-already-8b8f9cf5dde4
#ai #agile #scrum
Discussion Is Scrum dead in the era of AI?
This post provides a balanced view.
#ai #scrum #agile
r/scrum • u/TheCentenian • 3d ago
PSM I and PSM II
Hey all, I passed both PSM I and PSM II exams. Both over 90%.
I did lots of reading and mock tests. This sub was very helpful. Thank you all for the insights you have posted. One thing I found helpful to understand, was using AI to build scenarios where I could apply the learnings. This went beyond just reading and retaining and help me internalize the concepts better.
Now on to look for a Scrum Master role.
Scrum Master role in the current IT landscape?
Hi everyone,
I'm wondering - how are your feelings about a role of the Scrum Master in the modern days.
It feels like the "good days" are over and now things are at least... more complicated.
Companies save money - and usually the role of a Scrum Master is the first role to cut.
I'm watching the market and truth be told there is nothing really... interesting, to say at least.
Maybe I should consider a different path? Get some additional skills?
r/scrum • u/KookyOky • 3d ago
Anyone else feel like classic Agile delivery metrics are becoming redundant?
reddit.comAnyone redefined their delivery metrics for an AI-native SDLC?
We’re shifting toward a more AI-native SDLC (agents/AI involved across the full lifecycle, not just coding assistance).
I’ve been thinking about the usual suite of metrics we track DORA metrics, cycle time, lead time, sprint burndowns / burnups, velocity, etc.
A lot of them are starting to feel a bit hollow. What’s the actual value in proudly showing that we burned down 200 story points in a a day ?
Curious if anyone has actually redefined or replaced their delivery metrics with something more meaningful. What are you measuring now instead (or in addition)? What still feels useful and what have you quietly dropped?
Would love to hear real experiences rather than the usual “just use outcome metrics” advice.
r/scrum • u/annafromsoldevelo • 5d ago
Yes, we built another retrospective tool. But first, we built it for ourselves. 🦈
Hey r/scrum!
I know, I know. Another retrospective tool. Just what the world needed, right? 😅
But we didn't build RetroShark because we thought the world needed another Scrum tool. We built it because we needed it ourselves. We were tired of discussing the same problems every two weeks, losing track of action items, and starting each retro as if the previous one never happened. So we built something that remembers past discussions, helps teams follow through on action items, and uses AI to spot recurring problems.
Now we're looking for 15-20 teams willing to try our MVP for free and tell us what works, what doesn't, and whether we've just spent months solving a problem only we have. 😄
Does this sound painfully familiar? If you'd like to give RetroShark a try with your team, drop a comment or DM me. We'd love to have you on board!
And if you're not interested in testing, I'd still love to hear how your team handles recurring issues and unfinished action items.
Just please be gentle with the shark. 🦈
r/scrum • u/[deleted] • 6d ago
PSM I test suggestions please
Hi,
I've been a Scrum master for 4 yrs. I'd like at least one cert for scrum. However, I'm a horrible test taker.
Non timed tests, I usually finish well, no issue.
This 80 question test is giving me fits. I failed completing only 47 questions, 45 I got right. But, I pretty much failed before I started after I saw the question to time ratio.
Any suggestions, please thanks
r/scrum • u/mclac127 • 7d ago
Exam Tips I passed PSM II with 96.5%
Hi I am a software project manager and I just passed PSM II with score 96.5% (32.8 points scored out of 34 maximum points). Here are my learning materials aside from the Scrum Guide and Scrum Master Learning Path:
Skillsoft live classes for PSM I and II (company provided access)
This youtube video of David McLachlan helped in understanding the Scrum guide with better visualizations
Also this youtube video explained some concepts not in the guide but still valuable
Answering lots of practice questions aids in learning, but these are the 4 that I used:
thescrummaster.co.uk free PSM II
thescrummaster.co.uk ultimate PSM II practice (bought for £25) - this one I highly recommend
Scrum open just to get familiar with the exam UI
I was thinking of doing PSM I first but glad I jumped straight to PSM II.
r/scrum • u/coursor-org • 8d ago
We just launched 1SCRUM: planning poker, retros, Daily Scrum and health checks for Scrum teams
We just launched a new version of 1SCRUM, a tool that covers the whole Sprint: estimating, planning, the Daily Scrum and the retro.
Planning poker
Votes stay hidden until everyone reveals together.
Fibonacci, T-shirt sizes, time-based decks or your own.
After the reveal, an agreement meter shows the spread, and a re-vote is one click away.
Shared timer, auto-reveal, spectators, emoji reactions and comments next to votes.
Backlog and async estimation
Paste stories or import a CSV from Jira or Linear, then export results as CSV or Markdown.
Everyone votes before a deadline, so the meeting only covers the stories where votes differ.
Team Space
Plan Sprints with a goal and items. Velocity builds up from closed Sprints.
Estimation rooms send final estimates back to the Sprint's items.
A calendar file with your Sprint Planning, Daily Scrums, Reviews and Retros.
Retrospectives
Six templates or your own columns.
Cards are written privately and revealed together, without names. Dot voting decides what to discuss first.
Action items have an owner and keep coming back at the next retro and planning until they're done.
Daily Scrum
One speaker order and timer, shared on every device.
The Sprint Goal and days left on screen, plus a parking lot for topics to pick up afterwards.
Health checks
Anonymous green, yellow or red ratings for areas like pace, quality and fun.
Results show once at least 3 people have answered, with trends over time.
Scrum Academy
Twelve practice quizzes, with a streak for each day you practise.
Printable estimation and glossary cards.
Try it in your next refinement or retro: https://1scrum.com
If something gets in your way, or you're missing a feature, tell us in the comments. We read everything.
r/scrum • u/AgileSeekersOfficial • 8d ago
Your team's velocity dropped for three consecutive Sprints. What would you investigate first?
Your team's velocity was 50 in the first Sprint, dropped to 35 in the second, and reached 25 in the third.
As a Scrum Master, what would you investigate first?
A. Changes in team capacity
B. Differences in estimation
C. External dependencies
D. Technical challenges
Here's an interesting point: a drop in velocity doesn't automatically mean the team is underperforming.
Before taking corrective action, we need to understand what's actually happening.
Would you investigate the team's delivery pattern, speak with the developers, or look at the Sprint Retrospective findings first?
I'd like to hear how experienced Scrum Masters approach this situation. What's worked in your experience?
r/scrum • u/priyanka_1717 • 11d ago
Need Suggestion
Hi Folks, Just seeking suggestion or idea for retro call.
r/scrum • u/Otherwise_Rule_2492 • 11d ago
Studying for PMP - Pivoting from Architecture to Software/Tech - What other courses/certs do I need?
reddit.comr/scrum • u/Puzzleheaded-Elk5443 • 11d ago
Software Project Management Survey (please fill its urgent)
r/scrum • u/nutmegpudding • 13d ago
How I prepared for PSM I in 4.5 days
I recently passed the Professional Scrum Master I (PSM I) from Scrum.org. Quick facts if you’re considering it: it costs USD 200 per attempt, and you need 85% to pass, with 80 questions in 60 minutes.
I studied for 4.5 days, about 4 to 6 hours a day. Here’s what worked for me:
1. Read the 2020 Scrum Guide once, carefully.
Highlight key points as you go, then move on. You’ll come back to it later.
2. Work through the learning modules on Scrum.org.
You can find them on the PSM I certification page under the three Focus Areas. I mainly focused on “Understanding and Applying the Scrum Framework” and “Managing Products with Agility.”
3. Start the free Scrum Open assessment on day 2.
Alternate between the modules and the Open assessment until you’re consistently scoring 100%. The questions repeat, so this builds your confidence quickly.
4. Move on to harder practice quizzes.
I used Mikhail Lapshin’s Scrum quizzes (real mode), which are tougher than the Open assessment. While doing them, reread the modules and the Scrum Guide, and write down any concepts or questions that tripped you up. I ended up with about 2 to 3 pages of my own notes.
5. Repeat the quizzes and review every wrong answer.
Don’t just memorise answers. Make sure you understand why each one is right according to the Scrum Guide.
6. On exam day, manage your time.
If you’re unsure about a question, answer with your best guess, bookmark it and move on. Once you’ve reached the end, go back to your bookmarked questions and give them a second look. That should leave you enough time to check everything once.
Good luck, and make that USD 200 count!
r/scrum • u/Turkishblokeinstraya • 15d ago
Slicing big upfront plans into sprints and calling it Agile?
reddit.comr/scrum • u/Hopeful-Fly-5292 • 15d ago
Discussion Scrum for AI: Insights from Scrum co-creator Dr. Jeff Sutherland
I had a very insightful conversation with Jeff about Scrum in the age of AI.
What's your take on his thoughts?