Question 1
Who starts the Daily Scrum?
- The person coming in last. This encourages people to be on time and helps to stay within the time-box.
- Whoever the Development Team decides should start.
- The person who has the token.
- The Scrum Master. This ensures that the Development Team has the meeting and stays within the time-box.
- The person who last broke the build.
Question 2
When can a Development Team cancel a Sprint?
- When a technical dependency cannot be resolved.
- When the selected Product Backlog items for the Sprint become unachievable.
- When the Product Owner is absent too often.
- It cannot. Only Product Owners can cancel Sprints.
- When functional expectations are not well understood.
Question 3
How should a Development Team deal with non-functional requirements?
- Make sure the release department understands these requirements, but it is not the Development Team's responsibility.
- Assign them to the lead developers on the team.
- Handle them during the Integration Sprint preceding the Release Sprint.
- Ensure every Increment meets them.
Question 4
When many Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint?
- No, each Scrum Team stands alone.
- Yes, but only for Scrum Teams whose work has dependencies.
- Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.
- No, that is far too hard and must be done in a hardening Sprint.
Question 5
The Development Team should have all the skills needed to: (Choose the best answer.)
- Turn Product Backlog items into an Increment of potentially releasable product functionality.
- Do all of the development work, except for specialized testing that requires additional tools and environments?
- Complete the project within the date and cost as calculated by the Product Owner.