Skip to main content

Scrum confusion

Last post 04:49 pm September 18, 2016 by Ian Mitchell
4 replies
06:33 pm August 29, 2016

Hi,

I need to better understand "DoD". Precisely, I wonder when is it most appropriate for a Dev Team to change the definition of "DoD"?

I think that good moment for change it is prior to starting a new Sprint, but I am not sure. Maybe is better for Dev Team to do it during Sprint Planning meeting?

I hope someone will be able to help me with this.

Br.


07:13 pm August 29, 2016

A team's Definition of Done can really be modified at any time, especially if changing it improves their process or their ability to deliver. A mid-sprint DoD change would therefore make sense.

I do agree with you that a great opportunity to change the DoD is prior to a new sprint starting, perhaps as a result of Sprint Retrospective discussions. However, that doesn't have to be the only opportunity available to change it.


08:42 pm August 29, 2016

There is no specific rule when DoD can be changed.

1. It is also a good practice to check any possibility of improvement or change required in DoD at the end of sprint Planning meeting due to newly selected SBI.
2. I found it more suitable to change DoD at the end of Retrospective meeting as product and process feedback is with the team.
3. I tried to avoid any change to DoD during the sprint as it could affect all completed items.


12:01 pm August 30, 2016

During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of “Done” as appropriate.

http://scrumguides.org/scrum-guide.html#events-retro


04:49 pm September 18, 2016

> I think that good moment for change it is prior to starting a new Sprint

It isn't a bad one, which is why the Retrospective is commonly used for this purpose. However, the general principle to be teased out is that inspection and adaptation should occur as close as is *reasonably* possible to the time and place of work being performed.

In the case of the DoD, if it is suspected at any point during a Sprint that quality can be improved, then the DoD may be enhanced accordingly. This helps to avoid technical debt, rework, and other waste. A well-executed Retrospective should limit any such waste to the current increment and the Sprint boundary.


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.