";s:4:"text";s:3302:" Sometimes the outcome of a spike is a decision to do another spike.
Just FYI.As I write this, I’m wondering when I turned into the old guy who says “Yeah, we did that all 20 years ago!”, but…Funny, we used to simply call this type of activity “research” or “prototyping” or “risk analysis”. Details. Like other stories, spikes are estimated and then demonstrated at the end of the Iteration. (referring to different types of equipment), but I’ve never heard of spikes. The team determines the right solution through hours spent in discussion, collaboration, experimentation, and negotiation.
You can have spikes on features or user stories.Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Work on it, a better estimate will come later if necessary.Thanks for contributing an answer to Project Management Stack Exchange! So, to me, it would be overkill– and perhaps improper– to point out Spikes. The exception is if the result of the spike is information that will be used by stakeholders outside the team. Sometimes the outcome is a decision not to invest any more time investigating this particular question. Also, if the requirements are not clear, the estimation might also go wrong. A team can always suggest a spike, but they need to convince the Product Owner to actually prioritize it!Normally, when teams don't feel confident to estimate, they are probably pressured. Our goal with this project is to provide broad, authoritative definitions of common Agile terms. I am aware that this answer is many years old.
That is, the team is creating something of value that has been requested by stakeholders.Welcome to iteration zero of The Agile Dictionary! A common analogy used is rock climbing.