Professional Scrum Master II PSM-II Exam Questions with Experts Answers Updated Recently

A.  

Each Scrum Team provides a separate Increment with the functionality added by the individual team. The Sprint Review is used to identify the work needed to integrate with the other Scrum Teams. This work is then added to the Product Backlog.

B.  

Each Scrum Team delivers done Increments in its own area of responsibility. Upon functional acceptance at the Sprint Review, the code is isolated for future stabilization. The release date is adjusted according to the expected work and time of such integration phase.

C.  

In the first Sprint, integration is less important. The goal is to deliver business value. Functionality that is not integrated with the work of other Scrum Teams by the end of a Sprint is still reviewed to assess its potential business value. It can still be released at the Product Owner's discretion, and silent consent of the stakeholders.

D.  

All Scrum Teams agree on a shared Definition of Done that describes all work needed to deliver an Increment that is the integrated sum of the work from all Scrum Teams.

A.  

Collaboration.

B.  

Product quality.

C.  

Employee satisfaction.

D.  

Time to market.

E.  

Stakeholder trust.

F.  

All of the above.

A.  

Having an Increment that could be released to end users.

B.  

All work for which enough expertise and skills are present in the Scrum Team.

C.  

All work performed meets the Definition of Done.

D.  

All work to create an Increment that is ready for testing.

E.  

All work to create an Increment that is ready for acceptance testing by the

Product Owner.

A.  

Feature development of a next release is not allowed to start as long as there is technical debt from the current release. The Product Owner should first accept this impact before the Definition of Done can be reduced.

B.  

A generic Product Backlog item is not good enough. The amount of technical

debt will have to be calculated and estimated much more precisely, so the total

amount of extra work that needs to be budgeted is well known.

C.  

Releasing the version creates false assumptions about the actual state of the

system. This is likely to result in interruptions during future Sprints in order to react to unforeseen problems arising from not having met the Definition of Done.

D.  

As development progresses and functionality is added upon the reduced

Definition of Done, unknown errors will creep in. The system becomes more

difficult to stabilize. Work for the actual release as well as future releases Will be slowed down in unpredictable ways.