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

4677Abnormal Termination by another name...

Expand Messages
  • Deb
    Sep 30, 2004
    • 0 Attachment
      > If the customer changes what they want they will be
      > given a new estimate.

      This is a great way to talk about what we usually call Abnormal
      Termination of a Sprint. I'm going to remember that. It's so
      customer-centric.

      --- In scrumdevelopment@yahoogroups.com, "Mike Dwyer"
      <mike.dwyer1@c...> wrote:
      > Let's ask some questions.
      >
      >
      >
      > Within a Sprint, what value does measurement add to the functionality
      > committed to at the end of the sprint?
      >
      > If a customer is willing to reduce the functional output
      of a
      > sprint in order to measure the effectiveness of the sprint then let
      it be a
      > task in the backlog and assigned a priority and commitment.
      >
      >
      >
      > Second what value does measurement of sprints add to the
      functionality of
      > the product being delivered.
      >
      > If a customer is willing to pay for nonfunctional tasks
      to be
      > conducted while moving a product through a series of sprints then
      track the
      > resources being consumed by allowing the providers of the non functional
      > tasks to provide and track their own resources to conduct the
      measurements
      > as chickens.
      >
      >
      >
      > Finally what value is there in evaluating a product developed through
      > measurements if there is no means to verify and measure points of
      > improvement between products that use the same methodology?
      >
      >
      >
      > Some thoughts
      >
      > If we are going to apply Scrum and Agile principles to measurements
      we need
      > to begin with the customer
      >
      > What have they assigned us at any given time?
      >
      > The delivery of a specific set of functions using the available
      resources
      >
      > Measurement equals delivery. Period.
      >
      > If the customer changes what they want they will be given a new
      estimate.
      >
      > Measurement equals old commitment minus new commitment giving
      >
      > A negative value indicating the resources are saturated and cannot
      absorb
      > the change
      >
      > A positive value indicating the resources are either not saturated
      (bad) or
      > have increased their productivity (good)
      >
      >
      >
      > .
      >
      >
      >
      >
      >
      > Michael F. Dwyer
      >
      >
      >
      > -----Original Message-----
      > From: Steven Gordon [mailto:sagordon@a...]
      > Sent: Monday, September 27, 2004 12:05 AM
      > To: scrumdevelopment@yahoogroups.com
      > Subject: RE: [scrumdevelopment] SCRUM performance measurements
      >
      >
      >
      > Jim,
      >
      >
      >
      > How can you make the claim clipped below from the middle of your
      > posting unless this metric was being tracked before starting to do
      >
      > Scrum?
      >
      >
      >
      > What does this metric (actual developer time spent on sprint tasks)
      >
      > even mean outside of the context of Scrum anyway?
      >
      >
      >
      > Steven Gordon
      >
      > -----Original Message-----
      > From: Schiel James - SHS Malvern [mailto:james.schiel@s...]
      > Sent: Sun 9/26/2004 7:52 PM
      > To: 'scrumdevelopment@yahoogroups.com'
      > Cc:
      > Subject: RE: [scrumdevelopment] SCRUM performance measurements
      >
      >
      >
      > <clip>
      >
      > My experience so far shows a measurable increase in
      > actual developer time when compared to non-Scrum iterations.
      >
      > <clip>
      >
      > Jim Schiel
      > Siemens Medical Solutions, Malvern, PA
    • Show all 19 messages in this topic