Latest PSM-II Exam Questions

B.   Several Sprints may be funded as a single release, with the result of each Sprint being releasable product


D.   It is ideally revisited as frequently as each Sprint to ensure value is being delivered for the investment spent.

B.   Developers with an interest in Stella's domain could volunteer to take on this work in their respective Scrum Teams.


C.   Ask Stella for a plan to hire and train additional people in her domain, and in the meantime work with the Product Owner and Scrum Teams to re-prioritize the work so that tasks not depending on Stella can be done first.

D.   Product Owners and Developers are satisfied with the increment.

C.   Coach the Scrum Team about the purpose of the Daily Scrum.


D.   Tell the Product Owner your concerns about how his behavior may impact the Developers, and ask him to stop attending the Daily Scrum for some time.

A.   Respect the accountabilities of the Scrum Team members.


C.   Respect people, their experience, diversity, and difference in opinion

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.

Answer Description


Explanation:

Technical debt is the implied cost of rework caused by choosing an easy solution now instead of a better approach that would take longer1. Reducing the Definition of Done for the next three Sprints will create technical debt, which will have negative impacts on the product quality, value, and delivery. Two ways to explain these impacts to the Product Owner are:

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 Done2. This will reduce the transparency, predictability, and adaptability of the Scrum process, and compromise the trust and satisfaction of the customers and stakeholders.

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 ways3. This will increase the complexity, risk, and cost of the product development, and lower the value and quality of the product.

A.   

Timeboxing work to allow for frequent inspection.

C.   Creating a valuable and useful Increment by the end of each Sprint.

Answer Description


Explanation:

The best two answers are A and C.

A. Timeboxing work to allow for frequent inspection. This is a relevant boundary for self-management provided by the Scrum framework, as it helps the Scrum Team to organize their work into fixed-length Sprints and other events, such as the Daily Scrum, the Sprint Planning, the Sprint Review, and the Sprint Retrospective. Timeboxing enables the Scrum Team to inspect their progress, adapt their plan, and deliver value regularly and predictably.

C. Creating a valuable and useful Increment by the end of each Sprint. This is also a relevant boundary for self-management provided by the Scrum framework, as it guides the Scrum Team to focus on delivering a product Increment that meets the Sprint Goal and the Definition of Done. Creating a valuable and useful Increment requires the Scrum Team to collaborate, communicate, and coordinate effectively, and to apply their skills and creativity to solve complex problems.

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?


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

C.   Velocity has no direct relationship with value.


D.   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 Description


Explanation:

C: Velocity has no direct relationship with value. This is a true statement, as velocity is a measure of the amount of work done by a Scrum Team in a Sprint, not the value or quality of that work. Velocity can vary depending on many factors, such as the size, complexity, and priority of the Product Backlog items, the skills and experience of the Developers, the Definition of Done, and the Sprint length. Therefore, velocity is not a reliable indicator of value creation or team performance.

D: 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. This is a true statement, as velocity is a team-specific metric that reflects how much business functionality the Scrum Team can deliver in a Sprint. Velocity can help the Scrum Team to forecast how many Product Backlog items they can select for the next Sprint, based on their past performance and current capacity. However, velocity is not a goal or a target for the Scrum Team, and it should not be compared across teams.

C.   Wherever the Developers think is best.

Answer Description


Explanation:

According to the Scrum Guide 2020, the Developers can choose the location and structure of their Daily Scrum, as long as it is consistent and conducive to inspection and adaptation. The Daily Scrum is an event for the Developers, not for the Scrum Master, the Product Owner, or the management. The Developers are responsible for planning their work for the next 24 hours and synchronizing their progress toward the Sprint Goal.