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

Re: Open ended iterations/releases

Expand Messages
  • jhrothjr <yahoogroups@jhrothjr.com>
    ... That s exactly correct. The release is what the customer wants. Iterations are to keep project management under control, and not let the infamous 90%
    Message 1 of 11 , Jan 3, 2003
    • 0 Attachment
      --- In extremeprogramming@yahoogroups.com, "banshee858 <cnett858@s...>" <cnett858@s...> wrote:
      > > > >
      > > > > 1. What your customer is getting from variable-length
      > iterations
      > > > that s/he
      > > > > values. What s/he feels is lost from fixed-length.
      > > > >
      > > > I think the customer does not feel the fixed length iterations
      > match
      > > > up with their business priorities/deadlines. By alternately
      > > > expanding and contracting the release, they can add/remove
      > features
      > > > for the release that fit what they want to give to their
      > customers.
      > >
      > > Aha! Are you shipping at the end of every iteration now? If you
      > are, I can see the confusion between iterations and releases really
      > impacting things.
      > >
      > That is not the case. We ship on a specific date. I think I am just
      > uncomfortable with the idea of changing the size of the release since
      > I know how much I can create/test/release in an 8 weeks.
      >
      > I guess what I am asking is it better to fix the release size or let
      > it expand and contract to fit what the customer wants? I am thinking
      > since the customer drives, the size of the release is up to them.

      That's exactly correct. The release is what the customer wants. Iterations are to keep project management under control, and not let the infamous "90% complete for 90% of the time" syndrome happen.

      John Roth
    Your message has been successfully submitted and would be delivered to recipients shortly.