Skip to main content

PO role clarification in definition of 'Done'

Last post 04:42 pm May 20, 2018 by Karen Grigoryan
2 replies
11:38 pm May 16, 2018

Dear All,

 

In definition of "Done" we have this sentence : "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.”"

 

As we know there is only one product owner, even more than 1 Scrum team is working on the same product.

Does it mean that this single PO is included in more than 1 Scrum teams, and the PO considers all the definitions of 'Done' defined by all the groups?


05:43 pm May 17, 2018

It means that Scrum Teams working on the same product must consider each other’s work, if a product is to be integrated and of release quality. Therefore they must reach a common undersranding of what “Done” means for that product.

The Product Owner should expect the teams to observe this standard when developing each Sprint increment.


03:58 am May 19, 2018

thank you Ian Mitchel


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.