Scrum Professional Scrum Master II Exam Questions

The Scrum values of courage, openness, and respect are touched in this situation. Courage means that the Scrum Team members have the courage to do the right thing and work on tough problems, and also to speak up when they have concerns or disagreements. Openness means that the Scrum Team members and stakeholders agree to be open about all the work and the challenges with performing the work. Respect means that the Scrum Team members respect each other to be capable, independent people, and also respect the opinions and ideas of others.

In this case, the newest developer showed courage by expressing his feelings during the Sprint Retrospective, which is an opportunity for the Scrum Team to inspect itself and create a plan for improvements. The rest of the Developers should have been more open to listening to his perspective and ideas throughout the Sprint, as they might have valuable insights or suggestions for improving the product or the process. The Developers should also have respected the newest developer as a member of the team, and given him a fair chance to contribute and collaborate with them.

The Scrum Guide, November 2020, p. 13-14

What are the 5 Scrum Values?, Visual Paradigm, accessed on September 30, 2023

Scrum Values Poster, Scrum.org, accessed on September 30, 2023

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.

What is Technical Debt in Scrum? | StarAgile, section ''The technical debt is created when''.

Technical Debt & Scrum: Who Is Responsible? | Scrum.org, section ''What Is Technical Debt?''.

Managing Technical Debt in a Scrum Project | SCRUMstudy Blog, section ''Technical debt accrues''.

The Scrum values of courage, openness, and respect are touched in this situation. Courage means that the Scrum Team members have the courage to do the right thing and work on tough problems, and also to speak up when they have concerns or disagreements. Openness means that the Scrum Team members and stakeholders agree to be open about all the work and the challenges with performing the work. Respect means that the Scrum Team members respect each other to be capable, independent people, and also respect the opinions and ideas of others.

In this case, the newest developer showed courage by expressing his feelings during the Sprint Retrospective, which is an opportunity for the Scrum Team to inspect itself and create a plan for improvements. The rest of the Developers should have been more open to listening to his perspective and ideas throughout the Sprint, as they might have valuable insights or suggestions for improving the product or the process. The Developers should also have respected the newest developer as a member of the team, and given him a fair chance to contribute and collaborate with them.

The Scrum Guide, November 2020, p. 13-14

What are the 5 Scrum Values?, Visual Paradigm, accessed on September 30, 2023

Scrum Values Poster, Scrum.org, accessed on September 30, 2023

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.

What is Technical Debt in Scrum? | StarAgile, section ''The technical debt is created when''.

Technical Debt & Scrum: Who Is Responsible? | Scrum.org, section ''What Is Technical Debt?''.

Managing Technical Debt in a Scrum Project | SCRUMstudy Blog, section ''Technical debt accrues''.

When multiple Scrum Teams work from the same Product Backlog, they need to collaborate and coordinate their work to deliver a potentially releasable Increment that meets the Definition of Done. This requires minimizing dependencies between Scrum Teams, such as technical, functional, or organizational dependencies. Dependencies can cause delays, rework, waste, and lower quality.Scrum Teams should strive to be cross-functional and autonomous, and use techniques such as feature slicing, dependency mapping, and integration testing to reduce dependencies123.Reference:1: https://www.scrum.org/resources/blog/dependencies-between-scrum-teams2: https://www.scrum.org/resources/blog/feature-slicing-how-make-it-work3: https://www.scrum.org/resources/blog/integration-testing-scrum-projects