3 Roles but 1 Team

How common misunderstandings about the Scrum Roles prevent Scrum Teams to become effective

I am sure you have heard the saying “There is no ‘i’ in Team” before. For an effective Scrum team that statement makes perfect sense. On the flip-side, Scrum defines 3 distinct roles with very specific responsibilities and accountabilities. When roles are defined this way, there is a risk that gaps and gray areas emerge. We will take a closer look at the roles of Product Owner, Scrum Master and Development Team and most importantly the areas where they intersect. 


In this upcoming free webinar, we will explore common misunderstandings that often prevents Scrum Teams work effectively together towards a common goal. Let’s explore what common misunderstandings about these role exist and give you some fresh new ideas and how to tackle those. We will take this idea even further during our Agile Power Week in Munich Germany when we not only teach the individual roles but unite the roles in an Open Space.

Presenter: Jochen (Joe) Krebs pioneered Agile Portfolio Management in 2008 and has been active in the agile community for almost two decades. He is the founder and organizer of the local agile user group in New York City since 2008, the host of the Agile FM podcast, a Professional Scrum Trainer and founder of Incrementor. Joe held director-level leadership positions prior to Incrementor and connects the dots in his courses how agility impacts modern management. He offers a series of Agile Leadership Certification courses in the upcoming months in the United States and Europe you might be interested in as well.

This article originally appeared on the Scrum.org blog