Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
All Vendors
  2. Home
  3. Exams
  4. Scrum
  5. PSM I

Free Scrum PSM I Exam Braindumps (page: 23)

Page 10 of 68
PDF with 268 Questions

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?

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

Answer(s): A

Explanation:

The correct answer is A, because keeping component teams while starting Scrum may cause less initial disruption than organizing into new teams. As they start using Scrum, they will discover what works best for them and how to potentially re-organize towards feature teams. However, component teams may face some challenges in delivering a working Increment of software that provides business value every Sprint, as they may depend on other teams or layers.



How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?

  1. The Scrum Team with the highest velocity pulls Product Backlog items first.
  2. The Development Teams pull in work in agreement with the Product Owner.
  3. The Product Owner should provide each team with its own Product Backlog.
  4. Each Scrum Team takes an equal numbers of items.
  5. The Product Owner decides.

Answer(s): B

Explanation:

The correct answer is B, because when multiple Scrum Teams work from the same Product Backlog, they should pull in work in agreement with the Product Owner. The Scrum Guide states that "multiple Scrum Teams often work together on the same product. One product goal unites them. Therefore, they must mutually define and comply with a definition of `Done' that applies to their combined work product." Therefore, they should collaborate and coordinate with each other and with the Product Owner to select Product Backlog items that align with their shared product goal.



How often should Scrum Team membership change?

  1. As needed, while taking into account a short term reduction in productivity.
  2. Never, because it reduces productivity.
  3. As needed, with no special allowance for changes in productivity.
  4. Every Sprint to promote shared learning.

Answer(s): A

Explanation:

The correct answer is A, because Development Team membership should change as needed, while taking into account a short term reduction in productivity. The Scrum Guide states that "development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality." Therefore, changing Development Team membership may affect their cross- functionality and self-organization in the short term.



Who should make sure everyone on the Development Team does their tasks for the Sprint?

  1. The Project Manager.
  2. The Product Owner.
  3. The Scrum Master.
  4. The Development Team.
  5. All of the above.

Answer(s): D

Explanation:

According to the Scrum Guide1, the Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. No one tells them how to do their work. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The other roles are not responsible for making sure everyone on the Development Team does their tasks for the Sprint.


Reference:

Scrum Guide






Post your Comments and Discuss Scrum PSM I exam prep with other Community members:

PSM I Exam Discussions & Posts