Rahul Bhattacharya: the dangers of specialized Scrum teams

When Rahul started to work with a team that was new to Scrum and Agile, he noticed that the team members were very focused on their individual part of the product. Front-end developers only worked and worried about the front-end, and back-end developers focused on the back-end functionality. In the Sprint reviews, team members focused on their individual contribution, and the inevitable synchronization and coordination problems followed.

In this episode, we talk about the risks of highly specialized teams and how to tackle those in your role as a Scrum Master.

Featured Book for the Week: The 4-hour workweek by Tim Ferriss

In The 4-hour workweek by Tim Ferriss, Rahul found an inspiring story about the choices we make in our daily lives. He learned about “time” as a spendable resource, and how to create more options for yourself as you seek a better life situation. In this segment, we also refer to the Tim Ferriss podcast.

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