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

Re: [scrumdevelopment] On spikes

Expand Messages
  • Nicholas Cancelliere
    You want to treat a SPIKE as time-boxed story, not as a task. The outcome of this story is special though - as it doesn t produce end-user value, but instead
    Message 1 of 4 , May 8, 2007
    • 0 Attachment
       
      You want to treat a SPIKE as time-boxed story, not as a task.  The outcome of this story is special though - as it doesn't produce end-user value, but instead knowledge.  You then apply this knowledge to the story you were having trouble estimating.
       
      Some general rules about spikes:
       
      a) try to defer their coutnerpart story into the next sprint (so that you reduce risk)
       
      b) time-box them so you don't end up in analysis paralysis
       
      c) only use them if the decision to go one way or another will wildy vary the estimate so that you cannot make a good estimate;  if either outcome is likely to be the same then just use that as the estimate no reason to spike


       
      On 5/7/07, Alan Cyment <acyment@...> wrote:

      Hi everyone out there,

      How do you consider spikes? As user stories or as tasks corresponding to a committed user story?

      Cheers,
      Alan




      --
      Nicholas Cancelliere, Austin TX
      "The wide world is all about you: you can fence yourselves in, but you cannot for ever fence it out." -Gildor, Fellowship of the Ring (Lord of the Rings)
    Your message has been successfully submitted and would be delivered to recipients shortly.