PSM-I · Question #87
When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?
The correct answer is B. Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect. When multiple Scrum Teams work on the same product, all increments must be integrated every Sprint. Without full integration, the Product Owner and stakeholders cannot accurately inspect the true state of the product, making informed decisions about what to do next impossible…
Question
When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?
Options
- AYes, but only for Scrum Teams whose work has dependencies.
- BYes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect
- CNo, each Scrum Team stands alone.
- DNo, that is far too hard and must be done in a hardening Sprint.
How the community answered
(35 responses)- A3% (1)
- B89% (31)
- C3% (1)
- D6% (2)
Explanation
When multiple Scrum Teams work on the same product, all increments must be integrated every Sprint. Without full integration, the Product Owner and stakeholders cannot accurately inspect the true state of the product, making informed decisions about what to do next impossible. Option A is wrong because integration is not limited to teams with direct dependencies - the whole product must be coherent. Option C contradicts the single-product principle in Scrum. Option D violates Scrum's definition of Done - 'hardening Sprints' are an anti-pattern because they defer integration and quality work.
Topics
Community Discussion
No community discussion yet for this question.