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. Productivity, in terms of lines of code or story points, will probably suffer during the transition, although even then delivery of business value is still likely to Increase.
C. Feature teams will require time to become productive as people from the different layers and components become accustomed to working and delivering unified functionality together, as one Scrum Team.

Answer Description


Explanation:

B: Productivity, in terms of lines of code or story points, will probably suffer during the transition, although even then delivery of business value is still likely to increase. This is a realistic expectation, as the teams will need to learn new skills, collaborate more effectively, and adapt to changing requirements. However, the benefit of feature teams is that they can deliver working software that provides value to the customers and stakeholders every Sprint, rather than waiting for the integration of different components.

C: Feature teams will require time to become productive as people from the different layers and components become accustomed to working and delivering unified functionality together, as one Scrum Team. This is a natural consequence of changing the team structure and culture, as the teams will need to overcome some challenges and conflicts, build trust and rapport, and establish a shared vision and goal. The Scrum Master can help the teams with this transition by facilitating communication, coaching, and mentoring.

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. 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?”

D. All 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 DescriptionExplanation: The Scrum Value of openness can easily impact all of the aspects listed in the question. Openness means that the Scrum Team and the stakeholders agree to be transparent about their work, their challenges, their learnings, and their progress. This fosters a culture of collaboration, trust, feedback, and continuous improvement. Openness also helps to ensure that the product quality meets the expectations of the customers and the stakeholders, and that the product is delivered in a timely manner. Openness also contributes to employee satisfaction, as it allows the Scrum Team members to express their opinions, share their ideas, and learn from each other.

B. Developers can artificially increase velocity by incurring technical debt.
D. Velocity may unexpectedly drop when the Developers run into technical debt while attempting to complete new Product Backlog items.

Answer DescriptionExplanation:
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.

A. Continue sprinting but shorten the Sprint length to allow for shorter feedback loops.
C. Continue sprinting and include the customer feedback in the Product Backlog.

Answer Description


Explanation:

The Sprint Review is an event that inspects the outcome of the Sprint and determines future adaptations. The Product Owner has the authority to release the Increment to production at any time, but this does not mean that the Sprint has to be stopped or changed. The stakeholders can provide feedback and suggestions for the product, but they cannot interfere with the Sprint Goal or the Sprint Backlog within the Sprint.

The Scrum Team can decide to:

Continue sprinting but shorten the Sprint length to allow for shorter feedback loops (A), which is a valid option if the Scrum Team agrees that this will improve their agility and value delivery. However, this should not be done frequently or arbitrarily, as it may disrupt the rhythm and focus of the team.

Continue sprinting and include the customer feedback in the Product Backlog©, which is the most appropriate option as it respects the empirical nature of Scrum and allows the Product Owner to prioritize and order the Product Backlog based on new insights and stakeholder needs.