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

Ownership in Scrum

Expand Messages
  • David Vydra
    Jeff, Do you mean a single developer should own a system component or a should it be a small team, so at least there is some extra coverage and perhaps some
    Message 1 of 1 , Sep 25, 2003
      Jeff,
      Do you mean a single developer should own a system component or a should it
      be a small team, so at least there is some extra coverage and perhaps some
      pair programming?

      David Vydra

      ----- Original Message -----
      From: Jeff Sutherland
      To: scrumdevelopment@yahoogroups.com
      Sent: Thursday, September 25, 2003 6:45 AM
      Subject: Re: [scrumdevelopment] Digest Number 405


      We don't use a sustaining team. Development must eat their own dog food. If
      there are bugs, they go on the backlog list with everything else.

      In general it is better to get developers to own system components. Anything
      breaks, they fix it. This allows experience eyes on fixes which may cause
      refactoring into a better component and provides motivation to developers to
      deliver clean code.

      Jeff Sutherland
    Your message has been successfully submitted and would be delivered to recipients shortly.