Question 1
When many Scrum Teams are working on the same product, should all of their Increments be integrated every Sprint?
- 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, each Scrum Team stands alone.
- No, that is far too hard and must be done in a hardening Sprint.
Question 2
When can a Development Team cancel a Sprint?
- It can't. Only Product Owners can cancel Sprints.
- When functional expectations are not well understood.
- When the Product Owner is absent too often.
- When the selected Product Backlog items for the Sprint become unachievable.
- When a technical dependency cannot be resolved.
Question 3
Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?
- The Sprint Backlog.
- The Sprint Goal
- The release plan.
- Sprint Review minutes.
Question 4
How should a Development Team deal with non-functional requirements?
- Ensure every Increment meets them.
- Make sure the release department understands these requirements, but it is not the Development Team's responsibility.
- Handle them during the Integration Sprint preceding the Release Sprint.
- Assign them to the lead developers on the team.
Question 5
When is a Sprint over?
- When the Product Owner says it is done.
- When all Product Backlog items meet their definition of ג€Doneג€.
- When all the tasks are completed.
- When the time-box expires.