BONUS: Rahul Bhattacharya on what do on your first 90 days of a scrum master for a new team

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

 

BONUS: Developing a Vision for the Scrum Master role in practice, the Scrum Master Summit 2021

In this episode, we have the organizing team for the Scrum Master Summit 2021, and they share their vision of how we can help form and develop the Scrum Master Community. 

As our guests, we have the track curators for the Scrum Master Summit sharing their vision for the Scrum Master role. We explore why the Scrum Master role is so critical for our organizations, and how we – as the Scrum Master community – can come together to develop and progress that role. 

Listen in to learn about the Scrum Master Summit live events, and community get-togethers that can help you become the awesome Scrum Master you want to be!

About Yves Hanoulle, Mike Leber, Rahul Bhattacharya, Nagesh Sharma

Yves Hanoulle is the track curator for the “Scaling Agile Beyond One Team” track in the Scrum Master Summit 2021. He’s also the author and co-host for the Tips from the Trenches – Scrum Master Edition Audiobook. 

You can connect with Yves Hanoulle on Twitter and link with Yves Hanoulle on LinkedIn.

Mike Leber is the track curator for the “Scrum Masters enabling Business Agility” track, and organizer of the Business Agility Conference. Mike is also a Business Agility Coach. 

You can link with Mike Leber on LinkedIn and connect with Mike Leber on Twitter

Rahul Bhattacharya is the host of the Agile Atelier podcast and the curator for the “Common Product Owner blindspots” track. He’s also an Agile Coach. 

You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter

Nagesh Sharma is the curator for the “Remote facilitation for Scrum Masters” track on the Scrum Master Summit 2021 and a certified Remote Facilitator. 

You can link with Nagesh Sharma on LinkedIn and connect with Nagesh Sharma on Twitter

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 host at the Scrum Master Toolbox Podcast.

Product Manager, Scrum Master, Project Manager, Director, Agile Coach are only some of the roles that he’s taken in software development organizations. Having worked in the software industry since 1997, and Agile practitioner since 2004. He as worked in small, medium and large software organizations as an Agile Coach or leader in agile adoption at those organizations.

Vasco was one of the leaders and catalysts of Agile methods and Agile culture adoption at Avira, Nokia and F-Secure.

You can read more from Vasco at his blog: http://SoftwareDevelopmentToday.com

You can link with Vasco Duarte on LinkedIn and connect with Vasco Duarte on Twitter.

Rahul Bhattacharya from Micro-managing to engaging the team, a critical shift for Product Owners

In this episode, we talk about 2 extremes of team engagement by Product Owners: from micro-managing to asking questions and involving the team.

The Great Product Owner: Asking Questions to involve the team

Good Product Owners allow the team to participate and contribute their views when planning the Sprint. In this segment, we talk about Great Product Owners, those that not only allow, but encourage the team to bring their view into planning and defining the product.

We also discuss how asking questions is a critical tool for Product Owners to get teams engaged in the development of the product.

In this segment, we talk about transactional analysis, a tool that can help Scrum Masters recognize when the Product Owner needs help in involving the team.

The Bad Product Owner: The micro-managing Product Owner

When Product Owners “take over” the planning aspects they miss the team’s contribution, and likely motivation. However, there is an even more serious anti-pattern for Product Owners: being a micro-manager. In this segment, we discuss the dangers of over-controlling Product Owners, and how Scrum Masters should react in those cases.

 

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: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Rahul Bhattacharya

Rahul Bhattacharya is currently working as an Agile Coach at trivago. 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.

He is also the host of a podcast about Agile, called the Agile Atelier.

You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter.

Rahul Bhattacharya: Follow Scrum team progress with the Agile Fluency Model

In this episode, we review 5 different aspects that Rahul follows with each team he works with. From how the team delivers each Sprint, to the interaction with the Product Owner, we discuss different aspects that Scrum Masters should pay attention to.

In this episode, we also refer to the Agile Maturity Model. There are several maturity models you can follow, I’d recommend starting with the Agile Fluency Model by Diana Larsen and James Shore, which has been introduced here on the podcast.

Featured Retrospective Format of the Week: Radar chart for team self-evaluation

There are many different exercises for teams to run a self-evaluation exercise. The Radar chart helps the team choose several (typically 5-7) items they want to follow-up on, and evaluate themselves in each topic. If you collect similar charts over time, you will have a graphical representation of how the team has evolved in those core skills or aspect.

About Rahul Bhattacharya

Rahul Bhattacharya is currently working as an Agile Coach at trivago. 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.

He is also the host of a podcast about Agile, called the Agile Atelier.

You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter.

Rahul Bhattacharya: a new change management model by John Shook

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 John Shook and helped the QA’s and the teams experiment with new approaches. In this episode, we also talk about the importance of accepting that not everybody can accept certain changes, and how that affects your change management efforts.

In this episode, we also mention Test-Driven Development and the concept of Pi-Shaped Skills.

About Rahul Bhattacharya

Rahul Bhattacharya is currently working as an Agile Coach at trivago. 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.

He is also the host of a podcast about Agile, called the Agile Atelier.

You can link with Rahul Bhattacharya on LinkedIn and connect with Rahul Bhattacharya on Twitter.

Get The Booklet!
How to deliver on time and eliminate scope creep By scoping projects around outcomes and impacts, not requirements!
Get the Product Owner Booklet!
Avoid scope creep! And learn to scope projects around impacts and outcomes, not requirements!
Get These Valuable Lessons Today!
Down-to-earth, hard-earned Scrum Masters lessons and the Tips from the Trenches e-book table of contents, delivered by email
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works