A common question in transformations to Agile is: do Scrum teams have to be dedicated to a single product?

Unfortunately, there isn’t a single right answer for that one. However, there are situations when you want your team to be dedicated and there are situations when you don’t. Here’s a little bit about both:

My team should be dedicated to one or a couple products when…

  1. I don’t have enough people to create multiple teams,
  2. The products themselves don’t require a lot of work,
  3. ???

Keep in mind, even if a team is dedicated to multiple products, you can always reduce the context-switching costs by dedicating a Sprint to a specific, single product. The next Sprint works with a different product, and so on.

My team should be dedicated to a single product when…

  1. I need the team focused on the single product and can’t afford the context switching at all,
  2. There’s a lot of work to do and deadlines are very important,
  3. The learning curve to work on the product is excessive,
  4. ???



Product Ownership Overview

Download Now!

Swipe this FREE DOWNLOAD and maximize your product’s value.

Normally available ONLY to Artisan students, we’re offering this handy guide to you for a limited time!

More About #TransitioningToScrum

What Causes Conflict on a Team?

Change usually creates conflict, but a good ScrumMaster knows what types of conflict to expect and is prepared to handle it with correct conflict responses.

It’s All About Value

One small change can make a BIG difference to your Product Owner success. Before worrying about putting value on backlog items, here's some simple tips.

What Does it Mean to BE Agile?

With the Agility mindset, it's critical to understand the concept of "being" Agile. Some people want "to do Agile", but you don't DO Agile, you must BE Agile.