You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the frontend, one for the middle tier, one for the back-end, and one for the interfaces and services. This resembles what is known as component teams. But you have read that it's a good idea to have teams organized by feature.
What are the advantages of keeping component teams while starting Scrum?

Question

You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the frontend, one for the middle tier, one for the back-end, and one for the interfaces and services. This resembles what is known as component teams. But you have read that it's a good idea to have teams organized by feature.

What are the advantages of keeping component teams while starting Scrum?

Siraj Moosa · Accepted Answer

There's less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this.

Siraj Moosa · Answer

Component teams generally have the skills needed to create a working Increment of software that provides business value.

Siraj Moosa · Answer

Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would.

Siraj Moosa · Answer

There are fewer cross-team dependencies than working in feature teams.

Question list

List of questions

Question 1

(0)

Question 2

(0)

Question 3

(0)

Question 4

(0)

Question 5

(0)

Question 6

(0)

Question 7

(0)

Question 8

(0)

Question 9

(0)

Question 10

(0)

Related questions

Question 33 - PSM I discussion

Suggested answer: A

0 comments