QUESTION: 73

Steven is a Scrum Master for three Scrum Teams building the same product and working from the same Product Backlog. Management wants to standardize how velocity is calculated across all three teams in order to identify which teams are high performing and which teams need more support.
What would be the best two responses Steven could provide to management? (Choose two.)

There is no direct relationship between velocity and value.
Standardizing velocity across teams is a good way to understand which teams are producing the most value.
Providing incentives based on velocity can increase the Scrum Team’s motivation to produce more value.
Velocity is the amount of business functionality that a Scrum Team creates in a Sprint. It is unique to that team and used as an input to Sprint Planning.

Answer(s): A,D

Explanation:

Working software is the primary measure of progress. Scrum is based on empirical process control theory where delivering working software frequently and measuring the impact helps the Product Owner maximize opportunity for the business to deliver value.

Reveal Solution Next Question

QUESTION: 74

Which approach would you recommend to ensure that the Product Backlog items discussed at Sprint Planning are well understood, actionable, and easier to forecast?

Having a separate group of business analysts and functional testers analyzing high-ordered Product Backlog items before Sprint Planning.
Having the Product Owner work with stakeholders between the end of the last Sprint and before beginning the next to prepare the Product Backlog items so not to interrupt the Development Team.
Having the business analysts in the Development Team create the upcoming Product Backlog items during a Sprint and adding them to the next Sprint’s forecast.
Having the Development Team use some time during each Sprint to help the Product Owner analyze, estimate, and design items at the top of the Product Backlog that is projected to be worked on in the upcoming Sprint.

Answer(s): D

Explanation:

Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.

Reveal Solution Next Question

QUESTION: 75

During the Sprint Review of a scaled development effort, each Scrum Team should demonstrate its individual Increment in a separate branch of the code.

True
False

Answer(s): B

Explanation:

If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of “Done”. Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together.

Reveal Solution Next Question

QUESTION: 76

What would be the best two ways to identify that a Development Team is self-organizing? (Choose two.)

Management is able to know which members are working on which items.
Creativity thrives and new possibilities are explored.
The Development Team members are cross-functional and knows what it needs to do to deliver the all tasks committed to the Sprint Planning.
The Development Team is able to resolve internal conflicts between members in order to continue working.

Answer(s): B,D

Explanation:

In self-organized teams creativity thrives, conflicts can be resolved, and new possibilities are explored.

Reveal Solution Next Question

Free PSM II Exam Braindumps (page: 20)

QUESTION: 73

Explanation:

QUESTION: 74

Explanation:

QUESTION: 75

Explanation:

QUESTION: 76

Explanation:

PSM II Exam Discussions & Posts