Scrum PSM-II Professional Scrum Master II Exam Practice Test

Page: 1 / 14
Total 75 questions

Want more questions? Get Premium Access.
()

Question 1

You are a Scrum Master and one of the Developers approaches you and says: Every Sprint we are not completing regression testing for all of the selected Product Backlog items in the Sprint, but regression testing is part of the Definition of Done. We have discussed with the Product Owner and during the Sprint we decided to change the Definition of Done to remove regression testing. Which two actions are appropriate in this situation?

(choose the best two answers)

AAgree with altering the Definition of Done, if both the Developers and Product Owner agree.

BAsk the Developers and the Product Owner if removing regression testing from the Definition of Done allows the team to produce useful and valuable Increments at the end of every Sprint?

CAsk the Developers and the Product Owner what problem they are going to solve by altering the Definition of Done during the Sprint to remove regression testing. Will this raise transparency or improve quality?

DDisagree with the decision and tell them that having a stringent Definition of Done is important for the quality of the product, and they need to follow it.

Answer : B, C

B: Ask the Developers and the Product Owner if removing regression testing from the Definition of Done allows the team to produce useful and valuable Increments at the end of every Sprint. This is a good way to challenge the decision and make them think about the consequences of lowering the quality standards. The Scrum Master can help them understand the importance of delivering a potentially releasable product increment that meets the expectations of the stakeholders and customers.

C: Ask the Developers and the Product Owner what problem they are going to solve by altering the Definition of Done during the Sprint to remove regression testing. Will this raise transparency or improve quality? This is a good way to explore the root cause of the issue and find out why they are not able to complete regression testing for all of the selected Product Backlog items in the Sprint. The Scrum Master can help them identify and remove any impediments or inefficiencies that prevent them from achieving their Sprint Goal.

Scrum Guide 2020, page 9: ''The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.''

Scrum Guide 2020, page 13: ''The Scrum Master serves the Scrum Team in several ways, including coaching the team members in self-management and cross-functionality.''

Professional Scrum Master II Course, page 12: ''The Definition of Done is a crucial aspect of transparency. If it is not clear when work is done, then stakeholders may make wrong assumptions about the state of the software.''

Question 2

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?

(choose the best answer)

AEach 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.

BEach 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.

CIn 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.

DAll 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.

Answer : D

The Scrum Guide states that ''the moment a Product Backlog item meets the Definition of Done, an Increment is born'' and that ''the Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints''. Therefore, to deliver a product Increment that is integrated and potentially releasable, all Scrum Teams must have a shared understanding of what ''Done'' means and ensure that their work meets that standard. This also enables transparency, inspection, and adaptation across the Scrum Teams.

The Scrum Guide, section 3.4 (The Increment), page 10

The Scrum Master Learning Path, module 5 (The Increment), lesson 1 (What is an Increment?) and lesson 2 (Definition of Done)

Question 3

After some small experiments with Scrum, your company decides to do a complete project with Scrum. As Scrum Master; you have been invited to the "project kick-off meeting" with IT and product management

The Product Owner asks how many Sprints IT will need to first figure out architecture and infrastructure issues. What are two options to explain how such work is managed using Scrum?

(choose the best two answers)

AYou explain that product management should not worry about such typical IT work. You inform them that you will assure that the team members reach out to the right people within the IT organization when needed During each Sprint Planning event they will keep the Product Owner updated about the additional effort it will take for that Sprint. That effort will come on top of the effort for the forecasted functional development.

BYou explain that technical risks are best controlled when architecture and infrastructure emerge alongside the development of functionality. The additional advantage is that business value is created faster and sooner.

CYou thank product management for understanding that these efforts indeed require effort and budget You confirm that architecture and infrastructure are best addressed before starting Scrum, but that the exact budget is difficult to calculate upfront You say you will organize this work in timeboxed Sprints of no more than 30 days to limit risk and be transparent toward product management on the actual progress.

DYou educate the Product Owner to add this work to the Product Backlog to uphold transparency. Ask the Developers to plan work during the first several Sprints to estimate these items, while also creating some business functionality in these early Sprints

Answer : B, D

B) You explain that technical risks are best controlled when architecture and infrastructure emerge alongside the development of functionality. The additional advantage is that business value is created faster and sooner.

This is a good option because it is consistent with the Scrum principle of empiricism, which means that the Scrum Team learns and adapts based on the actual outcomes and feedback, rather than following a predefined plan12.By allowing the architecture and infrastructure to emerge iteratively and incrementally, the Scrum Team can address the most important and uncertain aspects first, and deliver valuable and functional increments every Sprint34. D. You educate the Product Owner to add this work to the Product Backlog to uphold transparency. Ask the Developers to plan work during the first several Sprints to estimate these items, while also creating some business functionality in these early Sprints

This is another good option because it is consistent with the Scrum value of transparency, which means that the Scrum Team and the stakeholders have a clear and common understanding of the product vision, goals, progress, and risks12. By adding this work to the Product Backlog, the Product Owner can prioritize and refine it according to the value and urgency, and communicate it to the stakeholders.By asking the Developers to plan work during the first several Sprints, they can estimate these items based on their actual experience and capacity, while also delivering some business functionality in these early Sprints34.

Question 4

What are two ways in which technical debt relates to velocity?

(choose the best two answers)

AAdding technical debt items to the Product Backlog to get estimated and added
to your velocity forecasts can guarantee predictability.

BDevelopers can artificially increase velocity by incurring technical debt.

CThey are not related, technical debt should be resolved by the support or
operations department, not by the Developers.

DVelocity may unexpectedly drop when the Developers run into technical debt
while attempting to complete new Product Backlog items.

Answer : B, D

B: Developers can artificially increase velocity by incurring technical debt. This is a true statement, as some Developers may choose to take shortcuts or compromise on quality in order to deliver more work in a Sprint. However, this is not a sustainable or ethical practice, as it will create more problems and costs in the future. The Scrum Master can help the Developers to avoid this temptation and focus on delivering value and quality instead.

D: Velocity may unexpectedly drop when the Developers run into technical debt while attempting to complete new Product Backlog items. This is a true statement, as technical debt can act as a drag on the productivity and progress of the Developers. Technical debt can make the work more difficult, complex, or risky, and may require more time and effort to fix or refactor. The Scrum Master can help the Developers to identify and manage technical debt, and communicate its impact to the Product Owner and the stakeholders.

How Technical Debt Affects Your Velocity1

Understanding the impact of technical debt on the capacity and velocity2

Question 5

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 the best two answers)

ADuring 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.

BThe 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.

CThrough 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.

Answer : A, C

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum is not a status meeting, but a way for the Developers to collaborate and self-organize around the most important work for the next 24 hours. The Daily Scrum also provides an opportunity for the Developers to identify and communicate any impediments that are hindering their progress, and request help from the Scrum Master or other team members to resolve them.

What is a Daily Scrum? | Scrum.org

What Is the Daily Scrum? | A Guide to the Daily Event - Scrum Alliance

Question 6

True or False: Using Scrum ensures that adding more resources to a project proportionally increases the value delivered.

ATrue

BFalse

Answer : B

Using Scrum does not ensure that adding more resources to a project proportionally increases the value delivered.In fact, adding more resources may have the opposite effect, as it can introduce more complexity, communication overhead, coordination challenges, and integration issues12.Scrum values quality over quantity, and focuses on delivering the most valuable and feasible outcomes in a given timebox3.Scrum also encourages teams to be self-organizing and cross-functional, which means that they can work autonomously and collaboratively without relying on external resources or dependencies3.

Question 7

Marian is a product Owner working on a Scrum Team on a new release for her product. Based on the average velocity of the previous release Marian estimated the project to take seven Sprints. Average velocity In the previous release was thirteen completed units of work per Sprint Development is three Sprints underway, with tour more Sprints to go until the release.

Product Backlog has been stable.

Over the first three Sprints, the Developers report their average velocity is nine, while not having fully tested all the delivered functionality. The Developers estimate that the unfinished testing would have required of a Sprints time. The Developers believe that the required

velocity of thirteen is within their reach. What is the most effective way to recover?

(choose the best answer)

A. The Developers set the open work aside to be performed in one or more release Sprints. They remind Marian to find funding for enough Release Sprints in which this remaining work can be done. up to one release Sprint per three development Sprints may be required, It is Marian's responsibility to inform users and stakeholders Of the impact on the release date.

B. Transparency needs to be restored by addng the undone work to the Product Backlog. The Developers must figure out a way to deliver in the upcoming Sprints a velocity of not only 13 units of new work, but also two additional points to catch up undone work. It is the Scrum Master's duty to assess whether such repair is possible. If not, the Scrum Master initiates a restart with a more reliable team Or cancels the project. The Scrum Master will have to inform Product Owner and the stakeholders.

CIn the next Sprints, the Developers keep making sure that all of the selected scope per Sprint is as done as possible, at least at the past level of 90%. In every Sprint the undone work of the previous Sprint is estimated and added to the Sprint Backlog. It comes on top of the expected forecast of 13 units, so it does not mess up progress on the product Backlog.

DThe Developers inform Marian that the progress she has perceived to date is not correct The Increment is not releasable. They give Marian their estimate of the effort it would take to get the past work done, and suggest doing that work first before proceeding with new features. The Developers also re-estimate the effort to complete the remaining backlog, including all testing. In the end, it is Marian's call to continue the project or to cancel.

Answer : D

The most effective way to recover is to restore transparency and trust by informing the Product Owner that the progress she has perceived to date is not correct.The Increment is not releasable because it does not meet the Definition of Done12, which is a shared understanding of what it means for work to be complete12. The Developers should give the Product Owner their estimate of the effort it would take to get the past work done, and suggest doing that work first before proceeding with new features.This way, the Developers can ensure that they deliver a valuable, useful, and potentially releasable Increment every Sprint12. The Developers should also re-estimate the effort to complete the remaining backlog, including all testing, and communicate any changes or risks to the Product Owner.In the end, it is the Product Owner's call to continue the project or to cancel it, based on the value and feasibility of the product12.

Some reasons why the other options are not correct are:

A: The Developers set the open work aside to be performed in one or more release Sprints. They remind Marian to find funding for enough Release Sprints in which this remaining work can be done. This option is not correct because it violates the Scrum framework and the Scrum values.The Scrum framework does not prescribe any release Sprints or separate phases for testing or integration12.The Scrum values include commitment, focus, openness, respect, and courage12. The Developers should commit to delivering a potentially releasable Increment every Sprint, not postpone or hide their undone work. The Developers should focus on creating value for the customers and users, not on meeting artificial deadlines or metrics. The Developers should be open and honest about their progress and challenges, not mislead or deceive the Product Owner.The Developers should respect the Product Owner's authority and accountability for maximizing the value of the product and the work of the Developers12, not shift the responsibility or blame to them. The Developers should have the courage to face their problems and seek help, not avoid or ignore them.

B: Transparency needs to be restored by adding the undone work to the Product Backlog. The Developers must figure out a way to deliver in the upcoming Sprints a velocity of not only 13 units of new work, but also two additional points to catch up undone work. It is the Scrum Master's duty to assess whether such repair is possible. If not, the Scrum Master initiates a restart with a more reliable team or cancels the project. The Scrum Master will have to inform Product Owner and the stakeholders. This option is not correct because it violates the Scrum framework and the Scrum roles.The Scrum framework does not prescribe any velocity or points as measures of progress or success12.The Scrum roles include Product Owner, Scrum Master, and Developers12.The Product Owner is accountable for maximizing the value of the product and the work of the Developers12, not for tracking or controlling their velocity or points.The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide1, causing change that increases the productivity of the Scrum Team1, and working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization1, not for assessing or judging the performance of the Developers or initiating a restart or cancellation of the project.The Developers are accountable for creating a valuable, useful, and potentially releasable Increment every Sprint12, not for meeting a predetermined velocity or points target.

C: In the next Sprints, the Developers keep making sure that all of the selected scope per Sprint is as done as possible, at least at the past level of 90%. In every Sprint the undone work of the previous Sprint is estimated and added to the Sprint Backlog. It comes on top of the expected forecast of 13 units, so it does not mess up progress on the product Backlog. This option is not correct because it violates the Scrum framework and the Scrum values.The Scrum framework requires that each Sprint delivers a potentially releasable Increment that meets the Definition of Done12, not a partially done or incomplete product that accumulates technical debt or quality issues.The Scrum values include commitment, focus, openness, respect, and courage12. The Developers should commit to delivering a potentially releasable Increment every Sprint, not compromise on quality or value. The Developers should focus on creating value for the customers and users, not on meeting artificial deadlines or metrics. The Developers should be open and honest about their progress and challenges, not hide or ignore their undone work.The Developers should respect the Product Owner's authority and accountability for maximizing the value of the product and the work of the Developers12, not burden them with additional work or risk. The Developers should have the courage to face their problems and seek help, not avoid or ignore them.

What is an Increment? | Scrum.org

What is a Product Increment? | Scrum.org