![]() ![]() Although there are different types of spikes, the ultimate goal will be to gain knowledge we didn’t previously possess. When it comes down to it, all jelly beans are sugary snacks, and all spikes are research tasks. Most of us aren’t jelly bean connoisseurs, though, and the best part of the experience is the surprise. Knowing that the jelly bean you hold in your hand is of the Superfruit Flavors versus the Harry Potter™ Bertie Bott’s Every Flavor Beans™ variety might give you some idea of what flavor to expect. Still, there is little value in categorizing them as they flow through your process.Īs it turns out, jelly beans also have categories. Understanding the different categories may help you appreciate all the situations where spikes may be helpful. ![]() Finding a different color of post-it to use for a risk spike versus an architectural spike isn’t necessary. Agile teams don’t need a different Jira issue type to organize them. Any descriptive word we put in front of ‘spike’ is mainly a way to categorize the effort and add some context to the work.Īlthough being familiar with the types of spikes can elevate your understanding of their usefulness, the act of categorizing them provides little value. Kent Beck initially coined the term ‘spike,’ which Extreme Programming subsequently popularized. Is this necessary? The same question applies to typing spikes. ![]() There are so many flavors of jelly beans now that we categorize them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |