We start this episode by talking about why it is important to have a specific focus on your first 90 days when working with a new team. The first 90 days are all about setting yourself up for success, and that requires that you take certain actions.
Start preparing before you start helping
Rahul suggests that we start preparing for our new role as a Scrum Master by asking specific questions (even in the job interview if that’s the case). Rahul suggests that to understand the expectations placed on you, you must understand what others have done before, what the team might be struggling with, but also how the context around the team works. What are the hierarchies, what do the team expect the Scrum Master to do, and more!
Do the Gemba: a critical step for your success as a Scrum Master
The gemba (a term from Lean that means “the place where the work happens”) walk is all about seeing with your own eyes, and talking directly to the people that you will be working with, or that your work will depend on. It’s important for Scrum Masters that are getting started that they not only talk to the team, but also to the stakeholders of the team, and possibly other teams that represent dependencies for the team you are trying to help.
See the system: looking beyond software development
Finally, the third step in this structured approach to the first 90 days with a new team, is all about what’s around the team that you need to deal with, even if it is not at the core of what the team does. This is “the systemic view” or context for the team. Rahul shares some critical questions we should ask ourselves (and those around the team), so that you can understand what kind of pressure and expectations are placed on the team.
Mega tips to close off this episode (make sure you listen all the way to the end)
Once we review the 3 main activities to prepare your Scrum Master assignment successfully, we dive into some of the tips that Rahul has collected over the years as an Agile Coach and Scrum Master. Rahul shares some critical insights that will help you overcome the most common challenges Scrum Masters face when taking on a new team.
To know more about Rahul’s approach, check out this article for Agile Coaches and Scrum masters called “Needs-oriented model of Agile Coaching”.
And check out Rahul Bhattacharya’s podcast, The Agile Atelier!
About Rahul Bhattacharya
Rahul Bhattacharya is currently working as an Agile Coach at Delivery Hero. He is responsible for optimizing the ways of working within the organization, coaching others on best practices while simultaneously guiding teams working on different products. Rahul is passionate about constant learning through experimentation and feedback
You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter.
And check out Rahul Bhattacharya’s podcast, The Agile Atelier!
Yves Hanoulle
Mike Leber
Nagesh Sharma
Vasco Duarte is a managing partner at Oikosofy where he wants to change the world, one company at a time. He’s also the regular 
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:
Rahul and Markus, another Scrum Master were helping the QA team move from QA at the end to a more involved QA approach, where QA engineers were to be involved earlier in the process. As you’d expect, this was not an easy change. How did they pull it off? They started by thinking that change happens as a result of new actions as described by 