Spike

A task aimed at answering a question or gathering information, rather than at producing shippable product. Sometimes a user story is generated that cannot be well estimated until the development team does some actual work to resolve a technical question or a design problem. The solution is to create a “spike,” which is some work whose purpose is to provide the answer or solution.

Etymology

The term spike comes from Extreme Programming (XP), where “A spike solution is a very simple program to explore potential solutions.” XP guru Ward Cunningham describes how the term was coined on the C2.com wiki: “I would often ask Kent [Beck], ‘What is the simplest thing we can program that will convince us we are on the right track?’ Such stepping outside the difficulties at hand often led us to simpler and more compelling solutions. Kent dubbed this a Spike. I found the practice particularly useful while maintaining large frameworks.”

This entry was posted in s. Bookmark the permalink.

60 Responses to Spike

  1. Pingback: Retrospiketives | Rob Aston

  2. Pingback: Retrospiketives | SoftDevine

  3. Pingback: Get started write code – Vikram Shetty

  4. Pingback: PEARL V : Scaled Agile Framework® pronounced SAFe™ | Pearls of Wisdom

  5. Pingback: ¿Qué son las historias de usuario y por qué “invertir” en ellas? - Agiland, expertos en Metodologías Ágiles

  6. Pingback: Yikes! Spikes! | My Agile journey

  7. Pingback: Spike Time « Stok Footage

  8. Pingback: Why Software Engineering Isn’t Engineering, and the Implications – Ian Cackett

  9. Pingback: The power of POC in agile projects | Soft Exploration Blog | IT, Software Development, Java, Technology

  10. Pingback: Product Backlog Refinement Explained (2/3) | The Agile People Developer

  11. Pingback: Product Backlog Refinement explained (2/3) - Scrum.org Community Blog

  12. Pingback: Enhanced Scrum Guide | enhancedscrumguidedotcom

  13. Pingback: Exiling a legacy COM component | Schneide Blog

  14. Pingback: The Ultimate Introduction To Agile Project Management | Thoughts on Software design and development

  15. Pingback: Yanado - Task management inside Gmail.

  16. Pingback: Week 1 -Boris bikes and coding spikes – the code bug

  17. Pingback: Spike Abuse | Adept Technologies

  18. Pingback: How We Built Two-Factor Authentication for Betterment Accounts

  19. Pingback: The Ultimate Introduction To Agile Project Management | Repository of Knowledge

  20. Pingback: The Ultimate Introduction To Agile Project Management - Balance SEO

  21. Pingback: The Ultimate Introduction To Agile Project Management – Notes

  22. Pingback: On Building Tools for Developers: Heroku CI | Rake™

  23. Pingback: Vorhersagbarkeit und Agilität - Was wir wissen - Scrum.de

  24. Pingback: Disciplined Learning – Alistair Cockburn

  25. Pingback: Castlebar Solutions | Systemigrams and Complexity

  26. Pingback: The 11 Agile Processes We Use to Run an Efficient Software Team | Process Street

  27. Pingback: To spike or not to spike? – Zen Ex Machina – The blog

  28. Pingback: agiLE#13 – Barcamp warmup – commodus.

  29. Pingback: Bridging Waterfall and Agile teams – Ctrl Alt Dad

  30. Pingback: How to get your backlog ready for PI Planning – Enterprise Agility Blogs…

  31. Pingback: 스파이크 (Spike) • Agile Practices

  32. Pingback: How We Built Two-Factor Authentication for Betterment Accounts | Betterment

  33. Pingback: Moving forward after a Code Spike – ZAFU LABS

  34. Pingback: Two ways for better planning and estimating – Factful Agility

  35. Pingback: Applying product methodologies in data science – Yakanak News

  36. Pingback: Applying product methodologies in data science – Data Science Austria

  37. Pingback: S.P.I.D.R. | Lean QA

  38. Pingback: Is a spike a type of story? –

Leave a Reply to Graham P Cancel reply

Your email address will not be published. Required fields are marked *