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

2126RE: [scrumdevelopment] Bombastic

Expand Messages
  • Ken Schwaber
    Nov 2, 2003
    • 0 Attachment
      A six week sprint is long enough that the team starts to require
      documentation, additional models, additional communication vehicles to
      remind them of their prior work and decisions. Sprints can be longer or
      shorter than thirty calendar days, but each direction has its downside and
      loss of productivity and collaboration. However, the world isn't optimal
      either.
      Ken

      -----Original Message-----
      From: Ron Jeffries [mailto:ronjeffries@...]
      Sent: Friday, October 31, 2003 7:56 AM
      To: scrumdevelopment@yahoogroups.com
      Subject: Re: [scrumdevelopment] Bombastic


      On Thursday, October 30, 2003, at 12:36:51 PM, Jim McCusker wrote:

      > I was actually wondering what the community's view was if someone were
      > to add 2 weeks to a sprint - mostly because the time given from start to
      > code freeze was 6 weeks instead of 30 days.

      Two shorter sprints would provide better feedback and more flexibility on
      the part of the PM.

      Ron Jeffries
      www.XProgramming.com
      Do, or do not. There is no try. --Yoda



      To Post a message, send it to: scrumdevelopment@...
      To Unsubscribe, send a blank message to:
      scrumdevelopment-unsubscribe@...

      Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
    • Show all 5 messages in this topic