Loading ...
Sorry, an error occurred while loading the content.

57815Re: [SCRUMDEVELOPMENT] Re: DoD to a Sprint?

Expand Messages
  • Jesse Houwing
    May 21, 2014

      On Wed, May 21, 2014 at 10:12 AM, bhavanamkr@... [SCRUMDEVELOPMENT] <SCRUMDEVELOPMENT@yahoogroups.com> wrote:
      DoD is fixed and same for all the sprints across the release

      Luckily you immediately mention that the retrospective is the place and time to update the DoD, and while I agree that it should normally not be changed to remove quality steps, adding new steps and improving the DoD can happen durign the retrospective and will lead to an updated DoD for the next sprint.

      The DoD will be changed only when it is discussed in retrospective meetings and all the stakeholders are agreed for the same. 

      I don't really agree on this one, the DoD is owned by the development team and is crafted together with the Product Owner. Other stakeholders officially have no say in the definition of done. It's what th eteam needs to do to reach the proper level of quality. The scrum guide says the following about it:

      If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development 
      organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a 
      convention of the development organization, the Development Team of the Scrum Team must 
      define a definition of “done” appropriate for the product. If there are multiple Scrum Teams 
      working on the system or product release, the development teams on all of the Scrum Teams 
      must mutually define the definition of “Done.”

      The stakeholders are usually people from the Business, and they should not influence the work the development team has done, instead they should define their acceptance criteria of the user stories properly. A development team or development department should be able to change it's definition of done....
    • Show all 60 messages in this topic