Exam PSM I All QuestionsBrowse all questions from this exam
Question 33

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?

    Correct Answer: A

    Transitioning to Scrum with existing component teams offers the advantage of less initial disruption. Teams are already familiar with each other and their workflows, which allows them to begin implementing Scrum practices without the additional complexity of re-organizing into feature teams. This smoother transition enables them to adapt and evolve their processes incrementally, discovering what works best over time and assessing the need for future re-organization if necessary.

Discussion
julioglez88Option: A

Option A: While it is generally recommended to organize teams by feature in Scrum, in this specific scenario where there are already established component teams, there may be advantages to keeping them initially. Option A is the correct answer because maintaining the existing component teams allows for a smoother transition to Scrum with less initial disruption. The teams can start implementing Scrum and adapt their processes incrementally, discovering what works best for them. Over time, they can assess the need for re-organization and potentially transition to feature teams if it aligns with the project's goals and requirements.

amogOption: A

Answer is A

DjedjigOption: A

A is correct

kunlemaxwellOption: A

A because it speaks to self-management

Jyoti1010Option: A

Option A is correct.

PinhaOption: A

NOT B: in feature teams, Focus is on delivering value to the customer through features NOT D: in feature teams, Less likely to have dependencies on other teams for delivering features Option C may also be true but option A is the most relevant.