![]() ![]() “Spike” is an Extreme Programming term meaning “experiment”. Photo of a hammer, some nails and a board 640×790 57.4 KBīut Ron Jeffries also describes it in another book, “Extreme Programming Adventures in C#”: According to a well-documented comment in The Agile Dictionary, a spike, like rock climbing, involves driving a spike (a piton) into the rock face.Īlthough it doesn’t directly lead to reaching the top, it facilitates future progress. I guess that the first time I read about spikes was in the book “Extreme Programming Installed” by Ron Jeffries (one of the authors of the Agile Manifesto), but unfortunately there are some discrepancies about the original meaning of the metaphor. a workable framework, before committing to a particular solution. ![]() Spikes are meant to provide answers or insights into areas of uncertainty, i.e. it is a short-term and focused effort undertaken by the development team or an individual developer to gain knowledge and inform decision-making at a specific technical or design problem. Definition of spikeĪs stated by Ward Cunningham: a spike answers the question «What is the simplest thing we can program that will convince us we are on the right track?», i.e. And finally, I’ll suggest how to add spikes to your project using Taiga. In this article I’ll also cover the origin of this metaphor (including the answer directly from one of its authors), and its pros and cons. In a previous article on how to manage uncertainty, I already mentioned this and other techniques that are often used interchangeably, so I believe it’s worth knowing more about spikes. A spike in Agile is a focused effort to address uncertainties and gather insights before committing to a full implementation. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |