Sample Exam answer (wrong imo)

Yeah I also found a few of those ... the plus side is you've studied enough to be able to spot wrong answers.

I think that they're right. First of all Scrum Guide also mentions that Scrum Team must have their DoD defined. Now, think of two teams working on the same project and having big difference of Scrum expirience between (or working on completely different areas). The team with more experience will have quite a demanding DoD that would completely paralise work of the other team that needs some time to grow into a Scrum Development Team. On the other hand, both increments produced must be potentially releasable, so common DoD (that will change as the less experienced team grows) is needed. In other words: DoD may be completely common for all teams but it doesn't have to.

The Scrum Master training manual is a poor source of preparation for PSM 1, due to the numerous errors and misunderstandings about Scrum.

Their use of the term "project" here is also erroneous.

Do they mean project or product? If they mean multiple teams working on the same *product* - then all teams must have the same understanding of DoD.

I definitely agree with mattdaniels, because in my opinion the key is that a project and a product are two different things. The Scrum Guide says the paragraph:

"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.”

Wich is in terms of a product. But in the question:

"What happens to the definition of “Done” when multiple Development Teams are working on a single project?"

They are talking about a project, and a project contains the development of a product increment and other activities beyond development, then maybe the answer B) fits better:

"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"

I also would like a more in-depth discussion with some expert in Scrum.org , because that is a tricky question in some way.

In Scrum the focus is on delivering a product rather than a project. That's one of the reasons why the framework has a Product Owner role and not a Project Manager.

Sometimes we may talk loosely about a project, but it is not strictly correct to do so. Note that in Scrum the delivery of a product can actually refer to the delivery of a service as well.

To all who said the question is poorly worded or the stated answer is wrong: I had almost the same question in the Open Assessment: "When many Teams are working on a single product, what best describes the definition of "done"?"

And there they said, too: Correct answer is C) All Development Teams must have a definition of "done" that makes their combined work potentially releasable.

I think, with multiple Development Teams, one should have the Scrum of Scrums in mind. In a large product it is not reasonable to assume that all Sub-Teams have the similar Sprint Goals justifying a shared Definition of Done - like Pawel has already said before.

Addendum:

of course you all are right, in saying a project is different from a product - so the question IS poorly worded.

I just wanted to emphasize the emergence of this very similar question in the Open Assessment.

Very well placed Anke Maerz.

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.

It is also worth remembering that the NEXUS Guide (page 10) does the following regarding about the Definition of "Done":

======================================================

Definition of “Done”

The Nexus Integration Team is responsible for a definition of “Done” that can be applied to the

Integrated Increment developed each Sprint. All Scrum Teams of a Nexus adhere to this definition of “Done”. The Increment is “Done” only when integrated, usable and potentially releasable by the Product Owner.



Individual Scrum Teams may choose to apply a more stringent definition of “Done” within their own teams, but cannot apply less rigorous criteria than agreed for the Increment.

======================================================

does each team have its own Sprint Backlog ?

does each team have its own Sprint Backlog ?

Yes, every development team has it own sprint backlog. That doesn't change with more than one team for a single product. But the product only has one product backlog.

I guess we can answer this question based on practical considerations. There must be a mutually defined DoD that guarantees the integrity of the increment, and each team can decorate it with their own rules fitting their own stack, environment and conventions. I do not see meaningful alternatives.