Professional Scrum Master I (PSM I) — Question 28

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 front-end, 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?

Answer options

• A. 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.
• B. Component teams generally have the skills needed to create a working Increment of software that provides business value.
• C. Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would.
• D. There are fewer cross-team dependencies than working in feature teams.

Correct answer: A

Explanation

Keeping component teams allows for a smoother transition to Scrum as it minimizes disruption during the initial changes. This approach enables teams to identify effective practices and potential reorganization over time. While the other options highlight benefits of component teams, they do not directly address the primary advantage of reducing initial chaos during the Scrum adoption process.