Latest PSM-I Pass Guaranteed Exam Dumps Certification Sample Questions [Q42-Q60] : Top Exam Collection : http://blog.topexamcollection.com

NO.42 What is included in the Sprint Backlog?

User Stories.

Tasks.

Use Cases.

Tests.

Any of the above (or others) which are a decomposition of the selected Product Backlog items.

NO.43 Who is accountable for clearly expressing Product Backlog items? (Choose the best answer.)

The business analyst who represents the Product Owner.

The Product Owner.

The Scrum Master, or the Scrum Master may have the Developers do it.

The Scrum Master.

NO.44 Sprint burndown charts are an efficient tracking tool, because they show:

An estimate of the total work remaining for the Sprint.

How much effort has gone into a Sprint.

How many hours have been worked by each Development Team member.

How many Product Backlog items remain.

NO.45 When do Development Team members take ownership of a Sprint Backlog item? (Choose the best answer.)

At the Sprint planning meeting.

During the Daily Scrum.

Never. All Sprint Backlog Items are “owned” by the entire Scrum Team.

Whenever a team member can accommodate more work.

NO.46 When many Scrum Teams are working on a single product, what best describes the Definition of Done?
(Choose the best answer.)

Each Scrum Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.

The Scrum Masters from each Scrum Team define a common Definition of Done.

Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known.

All Scrum Teams must have a Definition of Done that makes their combined work potentially releasable.

NO.47 During a Sprint Retrospective, the Development Team proposes moving the Daily Scrum to only occur on Tuesdays and Thursdays. Which two are the most appropriate responses for the Scrum Master? (Choose the best two answers.)

Consider the request and decide on which days the Daily Scrum should occur.

Coach the team on why the Daily Scrum is important as an opportunity to update the plan.

Have the developers vote.

Learn why the Development Team wants this and work with them to improve the outcome of the Daily Scrum.

Acknowledge and support the self-organizing team’s decision.

NO.48 Which are NOT appropriate topics for discussion in a Sprint Retrospective? (Choose all that apply.)

Definition of “Done”.

How the team does its work.

Team relations.

The value of work currently represented in the Product Backlog.

Arranging the Sprint Backlog for the next Sprint.

NO.49 Who is accountable for tracking the remaining work toward the Sprint Goal? (Choose the best answer.)

The Developers.

The Scrum Master.

The Product Owner.

The Project Manager.

NO.50 What are three benefits of self-organization? (Choose the best three answers.)

Increased creativity.

Increased rule compliance.

Increased accuracy of estimates.

Increased self-accountability

Increased commitment.

NO.51 Which three of the following are time-boxed events in Scrum? (Choose three.)

Release Testing.

Release Retrospective.

Sprint Retrospective.

Sprint Planning.

Sprint Testing.

Sprint 0.

Daily Scrum.

NO.52 When is the Sprint Backlog created?

At the beginning of the project.

During the Sprint Planning meeting.

Prior to the Sprint Planning meeting.

During the Sprint.

NO.53 How much of the Sprint Backlog must be defined during the Sprint Planning event?

Just enough tasks for the Scrum Master to be confident in the Development Team’s understanding of
the Sprint.

The entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting.

Enough so the Development Team can create its best forecast of what is can do, and to start the first
several days of the Sprint.

Just enough to understand design and architectural implications.

NO.54 In accordance with Scrum theory, how should a group of 100 people be divided into multiple Development Teams?

Understanding the product, the product vision and the rules of the Scrum framework, the group divides itself into teams.

It doesn’t really matter because you can rotate the teams every Sprint to spread knowledge.

Check with the allocation department to see who has worked together before and make these the first teams.

Create a matrix of skills, seniority, and level of experience to assign people to teams.

NO.55 What is the role of management in Scrum? (Choose the best answer.)

To present the Scrum Teams with insights and resources that help them improve.

To monitor the Development Team’s productivity.

To identify and remove people that aren’t working hard enough.

To continually monitor staffing levels of the Scrum Team.

NO.56 Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces).

True

False

NO.57 A Sprint Retrospective should be held:

At the end of each Sprint.

At the beginning of each Sprint.

Only when the Scrum Team determines it needs one.

At the end of the last Sprint in a project or a release.

NO.58 What is the best suited structure for Development Teams in order to produce integrated Increments? (Choose the best answer.)

Each Development Team works only one technical layer of the system (e.g. GUI, database, middle tier, interfaces).

Each Development Team develops functionality from beginning to end throughout all technical layers.

NO.59 Every Scrum Team must have a Product Owner and Scrum Master. (Choose the best answer.)

True. Outcomes affected by their participation and availability.

False. A Product Owner can be replaced by a subject matter expert in the Scrum Team.

False. A Scrum Master is only required when asked for by the Scrum Team.

True. Each must be 100% dedicated to the Scrum Team.

NO.60 The Development Team should have all the skills needed to:

Turn Product Backlog items into an Increment of potentially releasable product functionality.

Do all of the development work, except for specialized testing that requires additional tools and environments.

Complete the project within the date and cost as calculated by the Product Owner.