Skip to main content

What belongs solely to the Development Team?

Last post 07:20 am June 30, 2016 by Pankaj Ahuja
10 replies
12:43 pm June 29, 2016

While going through mock tests - encountered the following question

What belongs solely to the Development Team?

Among the options -
1) The Sprint Backlog
2) DoD

And the correct answer was 1) The Sprint Backlog

The scrum guide also suggests that it is Development team who creates the DoD and refines the same as part of retrospective inspections as well.

Shouldn't DOD be solely belonging to Development Team?


01:06 pm June 29, 2016

Hi,

The DoD bring transparency and another benefits of course, thinking more in deep on transparency I think that the DoD should be developed and accepted by all scrum team, all stakeholders involved in the company as well.

Best
Gabriel


01:31 pm June 29, 2016

Pankaj,

This specific forum is targeted for certification questions only. Please keep that in mind in the future.

That said, why do you think the Development Team should solely determine when an item is "done"?


01:44 pm June 29, 2016


Timothy - My question is related to PSM-1 exam only.

I understand and agree that determination of DoD is done by Sprint Team rather than just by Development team.

My question is about "Belonging".

Can Product Owner or Scrum Master make changes to DoD during the sprint?





02:13 pm June 29, 2016

The DoD could be changed at retrospective meeting.

The best
Gabriel


02:30 pm June 29, 2016


Posted By Pankaj Ahuja on 29 Jun 2016 01:44 PM

I understand and agree that determination of DoD is done by Sprint Team rather than just by Development team.

My question is about "Belonging".

Can Product Owner or Scrum Master make changes to DoD during the sprint?



The DoD may change during a sprint based on increased ability, understanding, etc. However, any changes made to a Scrum Team's DoD must be both transparent and agreed to by the Scrum Team.

Your question about "unilateral" changes to the DoD (by role) would therefore violate that practice.


02:43 pm June 29, 2016

I'm agree with you Timotly, a especific discussion, to no violate the practice DoD should the updated at retrospective meeting correct? in order to keep the transparency of DoD that evolve.

And I think that DoD need to be agreed by the Scrum Team as you said, in additional by another stakeholders as well, what do you think?


03:44 pm June 29, 2016

Gabriel, while the Retrospective is a convenient point to make improvement experiments visible, it is not a requirement. The Scrum Team should be able to make changes to their DoD at any time - why should the Scrum Team delay any potential improvements until the end of the sprint?

Regarding your second point, the PO must be the voice of the stakeholder(s) within the Scrum Team. The DoD is agreed to between the SM, the PO and the Development Team. Stakeholder involvement in the crafting or modification of the Scrum Team's DoD is not needed.


04:17 pm June 29, 2016

> Shouldn't DOD be solely belonging to Development Team?

If it did, what would the implications be for the wider organization? Since the DoD asserts product quality, what should the organization do regarding the DoD to ensure risks to branding, reputation etc. are managed?


07:54 pm June 29, 2016

Thanks you Timothy, I'm agree with your the continued improvement should happens ASAP., I think that at retrospective is a good instance to update DoD officially for the team and maybe another stakeholders.

Good perspective from view the discussion Ian.

Thanks you guys.
Gabriel


07:20 am June 30, 2016

Thanks every one for your insights.

They way I see key reason for Sole belonging of Sprint back log to Development team is

- Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.
- The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team.
- Only the Development Team can assess what it can accomplish over the upcoming Sprint.
- DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning.

Also notice the use of language in Sprint Guide - for Sprint Backlog - it mentions "development team" and for DoD it uses the term "Scrum Team".

Thanks everyone!


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.