Forums

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. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

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.

Definition of Done (DoD)
Last Post 28 Dec 2013 05:14 AM by Bassem Hamdi. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Mehdi Hafezi
New Member
New Member
Posts:46
Mehdi Hafezi

--
26 Dec 2013 01:28 AM
    How in Scrum projects normally the agreed definition “Done” is distributed? Is it a separate document (artefact) that everybody can access it or is it just an entry in a project specific glossary?

    Thanks
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1607
    Ian Mitchell

    --
    26 Dec 2013 04:14 AM
    The Scrum framework does not prescribe the format a Definition of Done must take.

    One common approach is to write out a DoD and place it on (or close to) a task board, so it is clear to observers what "Done" on that board means.
    Mehdi Hafezi
    New Member
    New Member
    Posts:46
    Mehdi Hafezi

    --
    26 Dec 2013 06:00 AM
    @Ian Mitchell: Thanks (Mehdi)
    Bassem Hamdi
    New Member
    New Member
    Posts:3
    Bassem Hamdi

    --
    28 Dec 2013 05:14 AM
    Either you print it on a large paper and you place close to scoreboards so that everybody can see it, to radiate information and to be more transparent.
    Or If team don't have visual workplace around and it's more technology oriented ( think JIRA, TFS etc.), part of it can be automated and integrated to your build system ( i.e code metrics analysis run before each check-ins ) and the other part can be agreed on or within the team during pair programming it could be a check list to go through among other things.
    You are not authorized to post a reply.


    Feedback