What are two ways that regulatory compliance issues are dealt with in Scrum? (choose the best two answers)
Correct Answer:
BD
The best two answers are B and D. These two ways of dealing with regulatory compliance issues are consistent with Scrum’s values and principles, as they allow the Scrum Team to deliver valuable and potentially releasable increments of the product while meeting the necessary standards and regulations. They also enable the Scrum Team to inspect and adapt their compliance strategy based on feedback and changing requirements.
A is not a good answer because it creates a separate silo of responsibility for compliance issues, which can lead to delays, conflicts, and inefficiencies. It also violates the Scrum value of transparency, as the compliance team may not have full visibility into the product development process.
C is not a good answer because it implies a waterfall approach that assumes all the compliance requirements are known and fixed upfront, which is rarely the case. It also reduces the flexibility and responsiveness of the Scrum Team, as they may have to follow a rigid plan that does not reflect the current reality of the product or the market.
Which are appropriate topics for discussion in a Sprint Retrospective? (Choose the best three answers.)
Correct Answer:
CDE
According to the Scrum Guide, the Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The topics that are appropriate for discussion are those that relate to how the team does its work, such as team relations, Definition of Done, and processes, tools, communication, collaboration, quality, etc. The other options are not appropriate topics for discussion in a Sprint Retrospective, as they belong to other Scrum events (such as arranging the Sprint Backlog for the next Sprint in the Sprint Planning or evaluating the value of work in the Product Backlog in the Sprint Review).
What is the tactic a Scrum Master should use to divide a group of 100 people into multiple Development Teams?
Correct Answer:
C
According to the Nexus Guide2, which is a framework for scaling Scrum, one way to form multiple Development Teams from a large group of people is to ask them to self-organize into teams based on dependencies, skills, domain knowledge, and personal preferences. This approach respects the autonomy and empowerment of the Developers and allows them to choose how they want to work together.
References: Nexus Guide
Which phrase best describes a Product Owner?
Correct Answer:
B
The correct answer is B, because a Product Owner is best described as a value optimizer. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Therefore, a Product Owner should focus on delivering value to the customers and stakeholders through the product.
If burndown charts are used to visualize progress, what does a trend line through a release burndown chart indicate?
Correct Answer:
C
a burndown chart is a graphical representation of work left to do versus time. It is very useful for predicting
when all of the work will be completed. It is often used in agile software development methodologies such as Scrum. However, burndown charts can be applied to any project containing measurable progress over time. A release burndown chart tracks progress across multiple Sprints towards a product release. It shows how much work remains in the Product Backlog at any given time during the release cycle. A trend line through a release burndown chart indicates when the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.
