AGILE IN ACTION

Wednesday, January 11, 2006

Spike

Posted by Simon Baker

Read our latest thinking on spikes.

A spike is an experiment that allows developers to learn just enough about something unknown in a user story, e.g. a new technology, to be able to estimate that user story. A spike must be time-boxed. This defines the maximum time that will be spent learning and fixes the estimate for the spike. William McKnight of 3M once said “Give it a try - and quick”.

Creative Commons Licence

Recent Posts

  1. Spark The Change - Innovation Governance
  2. Lean Day London 2014
  3. The Mechanics Of Meaning
  4. Engineering Design
  5. Debugging Grails Database Performance
  6. Grails for Hipsters
  7. Governance - Friend or Foe?
  8. The Energized Work lab is moving aboard ship
  9. Gus Power on the future of software development at The CW500 Club
  10. Agile On The Beach: Session: How Are We Doing?

Archives

  1. 2014 (4)
  2. 2013 (2)
  3. 2012 (27)
  4. 2011 (24)
  5. 2010 (31)
  6. 2009 (41)
  7. 2008 (69)
  8. 2007 (152)
  9. 2006 (128)
    1. December (16)
    2. November (26)
    3. October (7)
    4. September (11)
    5. August (7)
    6. July (7)
    7. June (4)
    8. May (4)
    9. April (4)
    10. March (4)
    11. February (14)
    12. January (24)
      1. Look after your product backlog
      2. 1-week iterations
      3. Root cause analysis using 5 Whys
      4. Agile In Action is now available at Artima
      5. Planning with the Horizon of Predictability
      6. The knowledge worker and the new organisation
      7. Setting Norms to help internalise Agile values
      8. Agile is ... Agile isn't ...
      9. It doesn't have to be about business value
      10. Task-switching is waste
      11. Flow, ideal time and the E-factor
      12. A Scrum Master is like a music conductor
      13. Slack != Waste
      14. Go on. You know you want to. Say 'Hello'
      15. Spike
      16. Why agile principles are important
      17. Pareto Principle
      18. My interaction style
      19. An 'aeroplane in flight' metaphor for agile tracking
      20. A Scrum Master is like a skilled helmsman
      21. Fun and games
      22. Innovation games from enthiosys
      23. Thomas Edison on 'Lean'
      24. The speed of thinking
  10. 2005 (63)
  11. 2004 (2)

Tags

agile (43) big visible chart (15) conference (43) culture (18) extreme programming (22) leadership (18) lean (47) people (27) planning (17) retrospective (18) scrum (41) story (19) team (30) testing (19) xpday (19)