How to use insights to influence implementation decisions.Spikes primarily come in two forms: technical and functional.įunctional spikes – They are used to analyze overall solution behavior and determine: Spikes involve creating a small program, research activity, or test that demonstrates some aspect of new functionality. Gain confidence in a technical or functional approach, reducing risk and uncertainty.Conduct basic research to familiarize them with a new technology or domain.Perform feasibility analysis and other activities that help determine the viability of epics.Estimate new Features and Capabilities to analyze the implied behavior, providing insight about the approach for splitting them into smaller, quantifiable pieces.Teams may use spikes in a variety of situations: When faced with a question, risk, or uncertainty, Agile Teams conduct small experiments before moving to implementation, rather than speculate about the outcome or jump to a Solution. DetailsĪgile and Lean value facts over speculation.
They also provide an agreed upon protocol and workflow that Agile Release Trains (ARTs) use to help determine the viability of Epics. Like other stories, spikes are estimated and then demonstrated at the end of the Iteration. Defined initially in Extreme Programming (XP), they represent activities such as research, design, investigation, exploration, and prototyping. Their purpose is to gain the knowledge necessary to reduce the risk of a technical approach, better understand a requirement, or increase the reliability of a story estimate. Spikes are a type of exploration Enabler Story in SAFe. Note: This article is part of Extended SAFe Guidance, and represents official SAFe content that cannot be accessed directly from the Big Picture.
0 kommentar(er)
