Skip to main content

DoD by user story or by sprint result?

Last post 07:13 pm October 19, 2017 by koti Reddy Bhavanam
5 replies
06:56 am October 12, 2017

Dear community, 

a client of mine asked a question, which I am not sure how to answer:

Scenario:

A DevTeam works on a few User-Stories in a sprint. For Example one User-Story would be to create a Startpage of a website. At the end of the sprint, everything works, except one button is not working. According to DoD, the result of the sprint would not meet the goal of being "potentially releasable. The boss of my client would not be happy, if the whole sprint would be considered not to have achieved the goal, because of the one button. Now:

Should the whole sprint be considered as not having met its goal, or can we just take the parts, which work, and put the button back to the backlog?

Or in other words: Does DoD apply to the whole result, or can it also apply to single User-Stories within a sprint?

 

Falk


08:06 am October 12, 2017

To meet the Sprint Goal and to respect the DOD is absolutely not the same.

If the forecast of the Dev Team is too optimistic, the Dev Team will probably not meet the Sprint Goal, for instance, the last item is not coded.

But still, at the end of the Sprint, the increment must be potentially shippable. That means what is declared as "done" is terminated.


08:34 am October 12, 2017

Should the whole sprint be considered as not having met its goal, or can we just take the parts, which work, and put the button back to the backlog?

Do you think these are mutually exclusive? Isn’t it true that while the Sprint Goal was not met, some work was nevertheless performed during the Sprint? Shouldn’t the work remaining on the Product Backlog now be revised and re-estimated accordingly?

Or in other words: Does DoD apply to the whole result, or can it also apply to single User-Stories within a sprint?

The Definition of Done applies to the Increment, since that is the artifact which is potentially subject to release. There can however be multiple levels of Done which contribute to the DoD. In the case of individual User Stories this very often takes the form of acceptance criteria.


01:21 pm October 12, 2017

one User-Story would be to create a Startpage of a website. At the end of the sprint, everything works, except one button is not working. 

Just an observation, but perhaps your 1 user story was too ambitious?   Certainly a good subject for a retrospective discussion, but maybe there is benefit in splitting such large user stories into smaller items that are much more focused (i.e. - UX of web page, "button" stories, "link" stories, stories for other page content, etc.)?

 


02:20 am October 16, 2017

DoD is applied to all user stories. For example, unit tested code as one of the item of DoD. Well, you could not have some user stories do not have unit test, isn't it?

Sprint Goal is applied to Sprint Result. Sprint Goal is more of validating the overview of success of the sprint (even if some of the user stories are not completed).


06:13 am October 19, 2017

Does DoD apply to the whole result, or can it also apply to single User-Stories within a sprint?

Ideally DoD applies to the increment to make it potentially releasable to the customer.

From my experience what have seen is the development team defines a DONE at PBI level, which has to be adhered by all the PBIs and also another definition for increment level which is applies to the integrated components of all PBIs.

Hope it helps.


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.