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

B. The Scrum Teams pull in work from a shared Product Backlog in agreement with the Product Owner and the other teams.

Answer DescriptionExplanation: When multiple Scrum Teams work on the same product, they share one Product Backlog that contains all the requirements for the product. The Product Owner is responsible for ordering and refining the Product Backlog items, but does not assign them to specific teams. Instead, the Scrum Teams pull in work from the Product Backlog in agreement with the Product Owner and the other teams, based on their capacity, skills, dependencies, and Sprint Goals. This way, the Scrum Teams can self-organize and collaborate to deliver a coherent and valuable product Increment.

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.

D. The Developers inform Marian that the progress she has perceived to date is not correct The Increment is not releasable. They give Marian their estimate of the effort it would take to get the past work done, and suggest doing that work first before proceeding with new features. The Developers also re-estimate the effort to complete the remaining backlog, including all testing. In the end, it is Marian's call to continue the project or to ca

Answer DescriptionExplanation:
The most effective way to recover is to restore transparency and trust by informing the Product Owner that the progress she has perceived to date is not correct. The Increment is not releasable because it does not meet the Definition of Done12, which is a shared understanding of what it means for work to be complete12. The Developers should give the Product Owner their estimate of the effort it would take to get the past work done, and suggest doing that work first before proceeding with new features. This way, the Developers can ensure that they deliver a valuable, useful, and potentially releasable Increment every Sprint12. The Developers should also re-estimate the effort to complete the remaining backlog, including all testing, and communicate any changes or risks to the Product Owner. In the end, it is the Product Owner’s call to continue the project or to cancel it, based on the value and feasibility of the product12.
Some reasons why the other options are not correct are:

A: The Developers set the open work aside to be performed in one or more release Sprints. They remind Marian to find funding for enough Release Sprints in which this remaining work can be done. This option is not correct because it violates the Scrum framework and the Scrum values. The Scrum framework does not prescribe any release Sprints or separate phases for testing or integration12. The Scrum values include commitment, focus, openness, respect, and courage12. The Developers should commit to delivering a potentially releasable Increment every Sprint, not postpone or hide their undone work. The Developers should focus on creating value for the customers and users, not on meeting artificial deadlines or metrics. The Developers should be open and honest about their progress and challenges, not mislead or deceive the Product Owner. The Developers should respect the Product Owner’s authority and accountability for maximizing the value of the product and the work of the Developers12, not shift the responsibility or blame to them. The Developers should have the courage to face their problems and seek help, not avoid or ignore them.

B: Transparency needs to be restored by adding the undone work to the Product Backlog. The Developers must figure out a way to deliver in the upcoming Sprints a velocity of not only 13 units of new work, but also two additional points to catch up undone work. It is the Scrum Master’s duty to assess whether such repair is possible. If not, the Scrum Master initiates a restart with a more reliable team orcancels the project. The Scrum Master will have to inform Product Owner and the stakeholders. This option is not correct because it violates the Scrum framework and the Scrum roles. The Scrum framework does not prescribe any velocity or points as measures of progress or success12. The Scrum roles include Product Owner, Scrum Master, and Developers12. The Product Owner is accountable for maximizing the value of the product and the work of the Developers12, not for tracking or controlling their velocity or points. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide1, causing change that increases the productivity of the Scrum Team1, and working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization1, not for assessing or judging the performance of the Developers or initiating a restart or cancellation of the project. The Developers are accountable for creating a valuable, useful, and potentially releasable Increment every Sprint12, not for meeting a predetermined velocity or points target.

C: In the next Sprints, the Developers keep making sure that all of the selected scope per Sprint is as done as possible, at least at the past level of 90%. In every Sprint the undone work of the previous Sprint is estimated and added to the Sprint Backlog. It comes on top of the expected forecast of 13 units, so it does not mess up progress on the product Backlog. This option is not correct because it violates the Scrum framework and the Scrum values. The Scrum framework requires that each Sprint delivers a potentially releasable Increment that meets the Definition of Done12, not a partially done or incomplete product that accumulates technical debt or quality issues. The Scrum values include commitment, focus, openness, respect, and courage12. The Developers should commit to delivering a potentially releasable Increment every Sprint, not compromise on quality or value. The Developers should focus on creating value for the customers and users, not on meeting artificial deadlines or metrics. The Developers should be open and honest about their progress and challenges, not hide or ignore their undone work. The Developers should respect the Product Owner’s authority and accountability for maximizing the value ofthe product and the work of the Developers12, not burden them with additional work or risk. The Developers should have the courage to face their problems and seek help, not avoid or ignore them.

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.

A. Encourage the Product Owner to bring the performance concerns to the rest of the Scrum Team and work together to improve the Definition of Done

Answer DescriptionExplanation: As a Scrum Master, you are accountable for establishing an environment where the Scrum Team can be effective and deliver valuable products1. One of the ways to do this is by supporting the Product Owner in managing the Product Backlog and engaging with the stakeholders2. In this situation, where there is a performance issue with the product, your best option is:
Encourage the Product Owner to bring the performance concerns to the rest of the Scrum Team and work together to improve the Definition of Done. This option aligns with the principle of empiricism, which is the foundation of Scrum3. Empiricism means that you make decisions based on what is known, rather than what is assumed or predicted3. By encouraging the Product Owner to bring the performance concerns to the rest of the Scrum Team, you are helping them inspect the product Increment and adapt the Product Backlog based on transparent feedback from the stakeholder4. You are also helping them collaborate on improving the Definition of Done, which is a shared understanding of what it means for a product Increment to be complete and potentially releasable. The Definition of Done should reflect the quality standards and expectations of the stakeholders, and should be updated as needed to ensure that the product meets their needs and delivers value.
The other options are not advisable because:
Wait to bring this up in the next Sprint Retrospective as this is the appropriate time for the Developers to re-consider the Definition of Done. This option is incorrect because it contradicts your accountability as a Scrum Master. The Sprint Retrospective is an opportunity for the Scrum Team to reflect on their performance and identify improvements for the next Sprint. However, it is not the only time for them to inspect and adapt their product and process. As a Scrum Master, you should promote continuous improvement and help the Scrum Team address any issues or impediments as soon as they arise1. Waiting to bring this up in the next Sprint Retrospective would mean delaying feedback and action, which can lead to waste or dissatisfaction.

Bring the concern to the quality assurance members of the Scrum Team and ask them to improve how the system is tested. This option is incorrect because it goes against your role as a facilitator, who helps the participants have constructive and respectful conversations. By bringing the concern to only a subset of the Scrum Team, you are creating silos and excluding others from contributing or learning. You are also implying that quality is only their responsibility, rather than a shared accountability of the whole Scrum Team. Moreover, you are not asking them for their input or feedback, but telling them what to do, which can undermine their autonomy and motivation.

Explain to the Product Owner that it is up to the Developers to decide on acceptable performance standards as they own the Definition of Done. This option is incorrect because it contradicts your role as a coach, who helps people grow and improve their skills and behaviors. By explaining to the Product Owner that it is up to the Developers to decide on acceptable performance standards, you are dismissing their concern and creating a gap between them and the Developers. You are also ignoring their valuable perspective and input as a stakeholder representative, who has a clear vision of what value means for the product. Instead of explaining, you should be asking questions and listening actively, and facilitating a dialogue between them and the Developers.

A. During the Daily Scrum the Developers will bring up problems that are hindering their progress, and tor which they nave no means to resolve, this provides an opportunity to resolve those impediments.
C. Through the snort, daily alignment of the Daily Scrum the Developers build and improve a shared understanding of the most important work to be undertaken in the next 24 hours, to achieve the best possible progress toward the Sprint Goal. This daily opportunity to inspect and adapt Will enable the Developers to tackle any unforeseen circumstances that might otherwise disrupt the team's progress.

Answer Description


Explanation:

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Daily Scrum is not a status meeting, but a way for the Developers to collaborate and self-organize around the most important work for the next 24 hours. The Daily Scrum also provides an opportunity for the Developers to identify and communicate any impediments that are hindering their progress, and request help from the Scrum Master or other team members to resolve them.

References:
What is a Daily Scrum?| Scrum.org
What Is the Daily Scrum?| A Guide to the Daily Event - Scrum Alliance

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.