PSM-II Practice Test

A. You educate management that it is the Scrum Team's responsibility to improve their velocity. You invite management to the next Sprint Retrospective to brainstorm on how they can improve.

B. You inform management of organizational impediments that prevent the Scrum Team from being more productive. You enlist their help to remove these impediments.

C. You explain how a Scrum Team uses the velocity of a Sprint primarily to forecast work for the next Sprint, not to perfectly predict future productivity. You refer management to the Product Owner for all information concerning the progress of development.

D. You tell management that this is not your accountability in Scrum. You direct them to the Product Owner to determine whether the forecast is accurate.

E. You help management understand that it typically takes a few Sprints for a team to gradually increase the velocity up to the level expected. Meanwhile you present this to the team as a challenge and a company goal, leaving it however up to them to figure out exactly how to achieve this.

You are a Scrum Master helping to establish five Scrum Teams that will be building a product. You discuss with them the high level of integration that the product Increment will require by the end of their first Sprint. It is a highly anticipated product, both by consumers and by the organization. Of the options raised by the future Scrum Team members, which option do you encourage?

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.

During the Sprint Review the Product Owner introduces the functionality that is likely to be done over the next Sprints. The Chief Security Officer reminds everyone that through the envisioned functionality, sensitive personal user data will be stored. This might be the subject of external security audits. He reminds everyone of important non-functional requirements with regards to security. These were not applicable and not considered previously What are two effective ways the Scrum Team can manage these high-security concerns? (choose two answers)

A. They are discussed, determined, and documented in parallel Sprints to not disturb the actual feature development Once analyzed, they should be applied to the work already done before further feature development can continue.

B. The impact of these security concerns on past and future work needs to be determined before new Sprints can start. A list of security-related Product Backlog items needs to be passed on to the Product Owner before starting the next Sprint.

C. They are added to the Product Backlog and addressed throughout the next Sprints, combined with creating the business functionality in those Sprints, no matter how small that business functionality.

D.

E. They should be managed by a separate specialist team in a parallel Sprint, so they can be specifically resolved through an improved application design without hindering functional development.

You are a Scrum Master employed by the IT department. The IT manager considers adopting Scrum tor a new project He wonders however, what the value is in having all team members attend this meeting called "Daily Scrum" every day. The organization already has its employees attending so many mandatory meetings. What are two outcomes of the Daily Scrum you inform him about, to express the importance of the Daily Scrum? (choose two answers)

A. During the Daily Scrum the Developers will bring up problems that are hindering their progress, and tor which they nave no means to resolve, this provides an opportunity to resolve those impediments.

B. The Daily Scrum serves tor the Developers to report to you, as a Scrum Master, all updates on the tasks to the Sprint, as registered in the Sprint Backlog. You can then use the team's updates to plan their work tor the next day, making sure that every team member is assigned the right tasks.

C. Through the snort, daily alignment of the Daily Scrum the Developers build and improve a shared understanding of the most important work to be undertaken in the next 24 hours, to achieve the best possible progress toward the Sprint Goal. This daily opportunity to inspect and adapt Will enable the Developers to tackle any unforeseen circumstances that might otherwise disrupt the team's progress.

D. During the Daily Scrum, the Developers need to update the Scrum board with their current status and progress, at a task level. This is crucial to ensure that the IT manager can go up to the room at any time and view the team's actual progress.

E. The Developers will produce a status report indicating what each individual has done the past working day, and now much time that has taken. The accumulated reports will support discussing how the Sprint went at the Sprint Review meeting. It will provide detailed insights into the accuracy of estimates versus actual time spent, which can be used to create better estimates at the subsequent Sprint Planning meeting.

In an environment where user acceptance testing is required before the Increment can be put into production, a development manager proposes to have user acceptance testing done every third Sprint, because the feedback from the user acceptance tests are disrupting work in Sprints. Is this a good idea?

A. It depends on what is stated in their Definition of Done.

B. No, the Increment will not be transparent and the feedback loop is too long.

C. Yes, the Scrum Team is a self-managing team.

D. Yes, the Scrum Team needs stability in the Sprint.