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

Re: [scrumdevelopment] Re: Prioritizing work during a 30 day sprint

Expand Messages
  • Ilja Preuss
    ... If priorities change so often, and you are able to release once a week, why would you *not* do one-week sprints? Curious, Ilja
    Message 1 of 11 , Mar 23, 2008
      Brian Bailey wrote:

      > 1. This is a web project and many of the stories can be completed without core changes
      > to the environment. In these cases, I still have trouble understanding why a completed
      > feature should be held until the end of the sprint. Obviously reducing the sprint to 2-
      > weeks makes this less of an issue, but so I understand, is the assumption that if you want
      > to release new features (even small changes) once a week, that you should be doing 1-
      > week sprints?

      If priorities change so often, and you are able to release once a week,
      why would you *not* do one-week sprints?

      Curious, Ilja
    Your message has been successfully submitted and would be delivered to recipients shortly.