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…
- I don’t have enough people to create multiple teams,
- The products themselves don’t require a lot of work,
- ???
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…
- I need the team focused on the single product and can’t afford the context switching at all,
- There’s a lot of work to do and deadlines are very important,
- The learning curve to work on the product is excessive,
- ???
More About #TransitioningToScrum
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.
Should Scrum Teams be Dedicated to a Single Product?
Should Scrum teams be dedicated to a single product? The truth is, there's times when you want a dedicated team and times when you don't. Let me explain!
Creating the Skills You Need for Agility
When beginning the transformation to Agile Development, it's hard to know exactly what skills the organization needs to adapt to the new way of working.
What is the Role of the ScrumMaster?
Although the Scrum Guide defines the ScrumMaster at length, here we're going to dissect that description and take a much closer look at what a ScrumMaster is.
What Do Testers REALLY Do On a Scrum Team?
Analysis, design, coding, and testing are done constantly rather than in phases, meaning testing ISN'T just a phase but an ongoing part of Agile Development.
Self-Organizing Teams
When I teach or coach people about Scrum, we talk about self-organization, but the importance of self-organizational principles cannot be understated.
Ground Rules for Your Team
Some initial “rules” that everyone agrees to follow will help your team avoid misunderstandings and deliberate misconduct.
DONEness Definitions (DoD)
What's the one thing YOU could do as a Scrum Master to improve your team's reliability, quality, and productivity? Read on and find out!
Leave A Comment