tag:blogger.com,1999:blog-1814874240228543789.post6930435554642113619..comments2024-03-28T00:19:17.790-07:00Comments on Agile Adoption Roadmap: Agile Definition of Done Starter KitMario Moreirahttp://www.blogger.com/profile/00969447879025623968noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-1814874240228543789.post-51442744663327720802018-04-24T15:06:10.543-07:002018-04-24T15:06:10.543-07:00Wow - another DoD article from the way-back-machin...Wow - another DoD article from the way-back-machine - this is a grand-daddy of DoD articles... I'm linking to another grand-daddy article. I like the "starter-kit" notion and your list of items.<br /><br />Exercise:: Definition of Ready & Done<br />http://agilecomplexificationinverter.blogspot.com/2011/09/exercise-definition-of-done.html<br /><br />In the winter of 2018 Luke Hohmann & the Scrum Alliance hosted a webinar on Def. of Done and Ready: http://agilecomplexificationinverter.blogspot.com/2018/02/webinar-collaboration-at-scale-defining.html<br />Davidhttps://www.blogger.com/profile/12435527405159930692noreply@blogger.comtag:blogger.com,1999:blog-1814874240228543789.post-57614601166221903252015-05-13T05:30:11.822-07:002015-05-13T05:30:11.822-07:00Each user story is expected to yield, once impleme...Each user story is expected to yield, once implemented, a contribution to the value of the overall product, irrespective of the order of implementation; these and other assumptions as to the nature of user stories are captured by the invest formula..... nice post on <a href="http://www.scrumaxis.com/agile-user-stories.html" rel="nofollow">agile user stories</a> thanks for sharing.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1814874240228543789.post-18248245827452350732013-05-06T09:02:58.789-07:002013-05-06T09:02:58.789-07:00Thanks for your input Mike!Thanks for your input Mike!Mario Moreirahttps://www.blogger.com/profile/00969447879025623968noreply@blogger.comtag:blogger.com,1999:blog-1814874240228543789.post-35412711053909262172013-05-06T03:25:44.724-07:002013-05-06T03:25:44.724-07:00I agree completely and like your starter set. I te...I agree completely and like your starter set. I tend to get the PM & PO to describe what deliverables they need and software is usually just one. There will always be various automated amd scripted tests. Then there will be some sign-offs for example data protection, financial regs, language translations, legal, etc. On largescale projects there will certainly be architectural and deployment models/docs, training, help, security, etc. Kind of done to the power n.<br />Then I get the team to look at each deliverable and say how they will achieve it. Sometimes we have no choice e.g. financial regs must be tested and signed off in a contrrolled way. But sometimes the team can come up with improvements and negotiate new ways of getting to done.<br />It is also worth noting that really there are 3 levels of done. The sprint, the release and the project. So you may for example do performance testing at a release level which is several sprints/teams worth of stories (I try and get as much brought forward into the sprint as possible but there are constraints).Anonymoushttps://www.blogger.com/profile/05256110903237917293noreply@blogger.comtag:blogger.com,1999:blog-1814874240228543789.post-58214368240569109662013-05-05T18:42:31.289-07:002013-05-05T18:42:31.289-07:00Thank you all for sharing your thoughts!Thank you all for sharing your thoughts!Mario Moreirahttps://www.blogger.com/profile/00969447879025623968noreply@blogger.comtag:blogger.com,1999:blog-1814874240228543789.post-76884277928528931572012-03-28T10:30:40.647-07:002012-03-28T10:30:40.647-07:00I agree with Mario. Need to be flexible and opened...I agree with Mario. Need to be flexible and opened as it depends who is your user. <br />Lately i came across an article that summarized the essential points I had been contemplating but did not know how to express. <br />Its main point which i am totally agree with was " Develop a culture of Trust by empowering your teams, let them decide how they will deliver the expected results and how to meet the DOD. Doing so increases productivity and motivation. <br />Nowadays team members are closer to the market place and the customers needs (they know what matter for them and factor this in their DoD). They are also well aware of what processes are not working effectively and efficiently AND most importantly, they know how they can fix them".<br />This tells me that the answers are in your organization, ask your teams to find the solutions (really scrum spirit isnt't it). <br />TRUST, EMPOWER, TRANSPARENCY are the keys to succeedMoniquehttps://www.blogger.com/profile/03701243847978289726noreply@blogger.comtag:blogger.com,1999:blog-1814874240228543789.post-71485966467533047312011-12-02T13:46:07.246-08:002011-12-02T13:46:07.246-08:00Mario - I find it helpful to ask the team what it ...Mario - I find it helpful to ask the team what it will take for the business to make money from their work. That usually gets performance testing, memory leak testing, training created, sales people trained.<br /><br />In addition I stick with "Done Done" as reminder that its more than just my work that has to be done.<br /><br />Cheers<br />Mark Levison<br />Agile Pain Relief ConsultingMark Levisonhttps://www.blogger.com/profile/13339505374559057601noreply@blogger.com