Steven is a Scrum Master asked to assist in creating five new Scrum Teams that will be working to build a highly anticipated product. He talks with them about the importance of being able to integrate their Increments by the end of their Sprints. This includes the first Sprints. The product is very important to both the end users and the organization.
Of the choices raised by future team members, what would Steven encourage?
A . Each Scrum Team delivers Increments in its own code branch. After UAT is performed at the Sprint Review, the code branch is isolated until enough Increments are considered acceptable. All code branches will then be merged during the release phase.
B . Each Scrum Team delivers functionality at the end of each Sprint. New Product Backlog items will then be added to the next Sprint Backlog to integrate their functionality with the other teams to create a unified Increment.
C . All Scrum Teams agree on a mutual understanding of ‘done’ that defines all work necessary to deliver a potentially shippable Increment that includes all previous Increments delivered for the product.
D . Wait until enough of the infrastructure and architecture is in place before starting the first Sprints. This will increase the success of delivering integrated Increments in Sprint 1.
Answer: C
Explanation:
When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of “Done” to have a shared understanding of what it means for work to be complete, to ensure transparency. Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together.