Scrum PSM-II Test Dumps

C.   You suggest working with the program manager and the project managers of the other components on the ordering and the value of your open Product Backlog items to redefine the possible delivery date.

Answer DescriptionExplanation:

As a Scrum Master, you could help the Product Owner by suggesting working with the program manager and the project managers of the other components on the ordering and the value of your open Product Backlog items to redefine the possible delivery date. This would allow you to collaborate with the stakeholders and align on the expectations and priorities of the product. You could also inspect and adapt your integration process and communication channels with the other teams to minimize the impact of changes and dependencies.

References:

The Scrum Guide 2020, section “The Scrum Master”
The Scrum Master Learning Path, module “The Scrum Master as a Coach”
The Professional Scrum Master II Course, topic “Stakeholder Management”

A.   Having one Product Owner will improve the clarity of accountability to the teams and to the product management department.


D.   A single Product Backlog should be maintained holding all requirements for the new product.

Answer DescriptionExplanation:

A. Having one Product Owner will improve the clarity of accountability to the teams and to the product management department. This is a good suggestion, as it ensures that there is a single person who is responsible for maximizing the value of the product and managing the Product Backlog. Having one Product Owner also avoids confusion, duplication, or conflict among multiple Product Owners who may have different visions, priorities, or expectations for the product.

D. A single Product Backlog should be maintained holding all requirements for the new product. This is also a good suggestion, as it ensures that there is a single source of truth for the product requirements and that they are transparent and visible to all stakeholders. Having a single Product Backlog also enables the Product Owner to order the items based on their value, risk, dependency, and urgency, and to collaborate with the Scrum Teams to select and refine the items for each Sprint.

References:

The Scrum Guide, section 2.3 (The Scrum Team), page 7
The Scrum Guide, section 4.1 (The Product Backlog), page 11
The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 4 (Sprint Planning)
and lesson 5 (The Sprint Review)

A.   Having an Increment that could be released to end users.


C.   All work performed meets the Definition of Done.

Answer DescriptionExplanation:

Done means that the Increment is in a usable condition and meets the Scrum Team’s 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. The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. Having an Increment that could be released to end users means that it is potentially releasable, which is one of the goals of Scrum. All work performed meets the Definition of Done means that the Developers have ensured that every Product Backlog item selected for the Sprint conforms to the agreed quality standards.

References:

• The Scrum Guide, November 2020, p. 10-11
• What is a Definition of Done?, Scrum.org, accessed on September 30, 2023
• DONE Understanding Of The Definition Of "Done”, Scrum.org, December 16, 2019

A.   The Scrum Master coaches the Scrum Team and the organization how to work empirically.


D.   The Scrum Master facilitates Scrum events as requested or needed

Answer DescriptionExplanation:

The Scrum Master serves the Scrum Team by coaching them and the organization how to work empirically, which means using an evidence-based approach to inspect and adapt the product and the process1. The Scrum Master also facilitates Scrum events as requested or needed, such as the Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective2. The Scrum Master ensures that these events are positive, productive, and kept within the timebox2.

The Scrum Master does not resolve every impediment that the Developers run into, but rather helps them to remove or overcome those impediments themselves3. The Scrum Master also does not never intervene in matters of the Scrum Team, but rather balances between providing guidance and allowing autonomy. The Scrum Master is not a passive observer, but an active servant leader who supports the team in achieving their goals.

References:

• What is a Scrum Master? | Scrum.org, section “The Accountabilities of the Scrum Master”
• The Scrum Guide 2020, section “The Scrum Master”
• What is a scrum master? [+ Responsibilities] | Atlassian, section “Scrum master responsibilities”
• [The 8 Stances of a Scrum Master by Barry Overeem], section “The Servant Leader”
• [What Is a Scrum Master (and How Do I Become One)? - Coursera], section “What is a scrum master?”

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.