Hi all,
I'm preparing for the PSM1, so I also took a look on the The Scrum Master Training Manual from mgmtplaza.com. At the end of the "manual" they have 2 sample exams, with 20 questions each. Besides the visible errors (the question is about the Sprint Review and the answer is about the Sprint Retrospective) I found this controversial question / answer:
"What happens to the definition of “Done” when multiple Development Teams are working on a single project?
A. Each team defines its own “Done”, and communicates it with others so that everyone knows what it means when a team claims that they are Done with something
B. Each team defines its own “Done”, in a way that the integration of their work results in a definition of “Done” that is potentially releasable
C. They all use the same definition of “Done”
D. Any of the above answers, based on the nature of the project and the environment of the organization"
The correct answer in their opinion is B, while I marked C. Their explanation is:
"We should always have Increments of potentially shippable product, even when multiple teams are working on a single project. In this case, a single definition of “Done” might not be suitable for all teams, but the integration of their definitions should result in an overall definition of “Done” that is potentially shippable."
I’m curious about an expert opinion on this, since the Scrum Guide mentions:
"If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of “Done.”
I'm preparing for the PSM1, so I also took a look on the The Scrum Master Training Manual from mgmtplaza.com. At the end of the "manual" they have 2 sample exams, with 20 questions each. Besides the visible errors (the question is about the Sprint Review and the answer is about the Sprint Retrospective) I found this controversial question / answer:
"What happens to the definition of “Done” when multiple Development Teams are working on a single project?
A. Each team defines its own “Done”, and communicates it with others so that everyone knows what it means when a team claims that they are Done with something
B. Each team defines its own “Done”, in a way that the integration of their work results in a definition of “Done” that is potentially releasable
C. They all use the same definition of “Done”
D. Any of the above answers, based on the nature of the project and the environment of the organization"
The correct answer in their opinion is B, while I marked C. Their explanation is:
"We should always have Increments of potentially shippable product, even when multiple teams are working on a single project. In this case, a single definition of “Done” might not be suitable for all teams, but the integration of their definitions should result in an overall definition of “Done” that is potentially shippable."
I’m curious about an expert opinion on this, since the Scrum Guide mentions:
"If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of “Done.”