The definition of done is a fairly popular (and sometimes emotional) topic in the Agileverse. It seems everyone has an opinion on the matter ranging from “It depends,” to “Let the teams decide,” to a meticulously designed set of business rules and criteria that account for every possible scenario. However, as organizations adopt Agile practices (and specifically, Scrum), they seek to leverage guidance from those of us who have already blazed the trail. Why then is this such a complex topic? This session will discuss what the "Definition of Done" means to different stakeholders across the organization at the User Story, Sprint, Release, Product, and Program Level. The session is based on a series of articles that I have published on this topic. Also, I have presented various versions of this session for my clients and will be doing a dry-run of the actual Agile 2012 format for one of our Wilmington ALN meetings this Spring.
http://submit2012.agilealliance.org/files/session_pdfs/What's Done is Done - 081412 0800.pptx.pdf
