How should a Development Team deal with non-functional requirements?

1. A. Ensure every Increment meets them.
2. B. Make sure the release department understands these requirements, but it is not the Development Team’s responsibility.
3. C. Handle them during the Integration Sprint preceding the Release Sprint.
4. D. Assign them to the lead developers on the team.

Correct Answer: A
The correct answer is A, because the Scrum Guide states that “the definition of ‘Done’ is a formal description of the state of the Increment when it meets the quality measures required for the product.” Therefore, non-functional requirements should be part of the definition of ‘Done’ and ensure every Increment meets them.

Select two ways in which technical debt impacts transparency. (Choose two.)

1. A. When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
2. B. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.
3. C. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.
4. D. It enhances transparency for the Product Owner as a Development Team is not allowed to do additional feature development in a Sprint as long as there is technical debt.

Correct Answer: BC
The correct answers are B and C, because technical debt impacts transparency in these ways. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint, as it may contain hidden defects or incomplete functionality. It also results in future work being slowed down in unpredictable ways, as development progresses and code is added, the system becomes more difficult to stabilize and maintain.

What is the timebox for a Sprint Planning event? (choose the best answer)

1. A. Monthly.
2. B. 8 hours for a one-month Sprint
3. C. Whenever ills done
4. D. 4 hours for a one-month Sprint

Correct Answer: B
According to the Scrum Guide, the timebox for a Sprint Planning event is 8 hours for a one-month Sprint, proportionally shorter for shorter Sprints. The other options are not valid, as they are either too long (such as monthly), too vague (such as whenever it’s done), or too short (such as 4 hours for a one-month Sprint).

A Scrum Master is introducing Scrum to a new Team. The Team has decided that a Sprint Retrospective is unnecessary. What action should the Scrum Master take?
(choose the best answer)

1. A. Comply with the decision of the self-managing team.
2. B. Begin facilitating productive and useful Sprint Retrospectives.
3. C. Call a meeting between the ScrumTeam and senior management
4. D. Consult with the Product Owner to see how they feel about the situation.

Correct Answer: B
According to the Scrum Guide, the action that the Scrum Master should take when the Team decides that a Sprint Retrospective is unnecessary is to begin facilitating productive and useful Sprint Retrospectives. The Sprint Retrospective is an essential event for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Scrum Master is responsible for ensuring that this event takes place and that positive outcomes are achieved. The other options are not valid actions, as they either imply that the Scrum Master complies with or ignores the decision of the Team (such as complying with it, calling a meeting with senior management, or consulting with the Product Owner), which is not consistent with Scrum values and principles.

Who must attend the Daily Scrum?

1. A. The Scrum Master and Product Owner.
2. B. The Development Team.
3. C. The Development Team and Product Owner.
4. D. The Scrum Team.
5. E. The Development Team and Scrum Master.

Correct Answer: D
According to the Scrum Guide1, the Daily Scrum is an event for the Developers of the Scrum Team. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The Scrum Master and Product Owner may attend as observers, but only if it is useful for the Developers.
References: Scrum Guide