Scrum PSM-I Professional Scrum Master I Exam Practice Test

Answer : A, C, D

The Definition of Done serves the following three purposes:

A . Create a shared understanding of when work is complete.

The Definition of Done is a commitment to the quality of the product increment that is part of Scrum. It is a formal description of the state of the product backlog item or the increment when it meets the quality measures required for the product. The Scrum team must have a shared understanding of what 'done' means and use it to assess when work is complete and transparent1.

C . Increase transparency.

The Definition of Done increases transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the increment. This ensures that the product increment is potentially releasable and that the stakeholders can inspect and provide feedback on it2.

D . Describe the work that must be mostly done before the Sprint is allowed to end.

The Definition of Done describes the work that must be done before the Sprint is allowed to end. Work cannot be considered part of an increment unless it meets the Definition of Done. The Definition of Done is used to guide the Developers in creating a 'Done', usable, and potentially releasable product increment every Sprint3.

B and E are not purposes of the Definition of Done.

B . Guide the Developers on how many Product Backlog items to select for the Sprint.

The Definition of Done does not guide the Developers on how many Product Backlog items to select for the Sprint. The Developers select how many Product Backlog items they can complete within a Sprint based on their capacity, skills, and experience. The Definition of Done helps them ensure that the selected items are completed to a high standard of quality4.

E . Describe the purpose, Objective, and timebox Of each Scrum event.

The Definition of Done does not describe the purpose, objective, and timebox of each Scrum event. The Scrum Guide describes these aspects for each Scrum event, such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective5. The Definition of Done is related to the product increment, not to the Scrum events.

Answer : B

The best answer is B. A valuable, useful Increment that meets the Definition of Done.

According to the Scrum Guide1, ''an Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.'' The Scrum Guide also states that ''work cannot be considered part of an Increment unless it meets the Definition of Done. The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.''

Therefore, a Scrum Team should deliver a valuable, useful Increment that meets the Definition of Done at the end of each Sprint. This ensures that the product is potentially releasable and that the stakeholders can inspect and provide feedback on it.

A, C, and D are not correct answers.

A . A single document, if that is what management asked for.

This answer does not reflect the Scrum values of commitment, focus, and respect1. A Scrum Team should not deliver a single document just because management asked for it, but rather deliver an Increment that provides value to the customers and users. A document may be part of an Increment, but it is not an Increment by itself.

C . Failing unit tests, to identify acceptance tests for the next Sprint.

This answer does not reflect the Scrum principle of empiricism1. A Scrum Team should not deliver failing unit tests, but rather deliver an Increment that is thoroughly verified and meets the quality standards. Failing unit tests indicate that the work is not done and that there are defects or errors in the product. A Scrum Team should use unit tests to ensure that the product works as expected and to identify and fix any issues before delivering the Increment.

D . An Increment of software with minor known bugs in it.

This answer does not reflect the Scrum value of openness1. A Scrum Team should not deliver an Increment of software with minor known bugs in it, but rather deliver an Increment that meets the Definition of Done and is free of any known defects or issues. Delivering an Increment with bugs in it can compromise the trust and satisfaction of the stakeholders and can lead to technical debt or rework in the future. A Scrum Team should strive to deliver high-quality products that meet or exceed the expectations of the customers and users.

Answer : C, D

The two effective ways for the Scrum Team to make non-functional requirements visible are C and D .

C . Add them to the Definition of Done so the work is taken care of every Sprint.

The Definition of Done (DoD) is a shared understanding of what it means for a Product Backlog item to be complete and potentially releasable1. The DoD can include non-functional requirements that apply to the entire product or system, such as performance, security, usability, etc. By adding them to the DoD, the Scrum Team ensures that they are met every Sprint and that the quality of the product is maintained2.

D . Add them to the Product Backlog to ensure transparency.

The Product Backlog is an ordered list of everything that is known to be needed in the product1. The Product Backlog can include non-functional requirements that are specific to certain features or functionalities, such as response time, availability, scalability, etc. By adding them to the Product Backlog, the Scrum Team ensures that they are visible to all stakeholders and that they are prioritized and refined along with the functional requirements3.

A and B are not effective ways for the Scrum Team to make non-functional requirements visible.

A . Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.

This approach does not make non-functional requirements visible, but rather postpones them until the end of the Sprint. This can lead to incomplete or low-quality Increments that do not meet the expectations of the customers or users. Moreover, this approach does not account for any changes or feedback that may occur during the Sprint4.

B . Put them on a separate list on the Scrum board, available for all to see.

This approach does not make non-functional requirements transparent, but rather isolates them from the functional requirements. This can lead to confusion or inconsistency in how they are handled by the Scrum Team. Moreover, this approach does not align with the principle of having a single source of truth for the product requirements, which is the Product Backlog5.

Answer : B

The best answer is B. The Sprint length is unchanged and the Scrum Team continuously learns and adapts.

According to the Scrum Guide1, ''Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.'' Therefore, the Sprint is not extended or shortened based on the completion of the work.

The Scrum Guide also states that ''Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of 'Done' product ensure a potentially useful version of working product is always available.'' Therefore, the Scrum Team should focus on delivering a potentially releasable Increment of value by the end of the Sprint, even if some work items are not completed.

The Scrum Team should also use the Sprint Retrospective to inspect how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The Scrum Team should identify and order the major items that went well and potential improvements, and create a plan for implementing improvements to the way they do their work. This way, the Scrum Team continuously learns and adapts to changing circumstances and challenges.

Answer : B, D

The best two answers are B and D. These two ways of dealing with regulatory compliance issues are consistent with Scrum's values and principles, as they allow the Scrum Team to deliver valuable and potentially releasable increments of the product while meeting the necessary standards and regulations. They also enable the Scrum Team to inspect and adapt their compliance strategy based on feedback and changing requirements.

A is not a good answer because it creates a separate silo of responsibility for compliance issues, which can lead to delays, conflicts, and inefficiencies. It also violates the Scrum value of transparency, as the compliance team may not have full visibility into the product development process.

C is not a good answer because it implies a waterfall approach that assumes all the compliance requirements are known and fixed upfront, which is rarely the case. It also reduces the flexibility and responsiveness of the Scrum Team, as they may have to follow a rigid plan that does not reflect the current reality of the product or the market.

Answer : A, B

According to the Scrum Guide, two characteristics of the Daily Scrum are its location and time remain constant and its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. These characteristics promote consistency, transparency, and adaptation within the Development Team. The other options are not valid characteristics of the Daily Scrum, as they are either irrelevant (such as being held first thing in the morning) or inappropriate (such as being free form, facilitated by the team lead, or consisting of the Scrum Master asking for status).

Answer : B