Spike meaning in rasta how to#
Spike meaning in rasta update#

The Exception, Not the RuleĮvery user story has uncertainty and risk. However, if it’s small and straightforward, and a quick solution is likely to be found, doing both in the same iteration can be efficient. Since they represent uncertainty in one or more potential stories, planning for both the spike and the resulting stories in the same iteration is sometimes risky. The Product Owner accepts spikes that have been demoed and meets its acceptance criteria. The output of a spike is demonstrable, both to the team and to any other stakeholders, which brings visibility to the research and architectural efforts and helps build collective ownership and shared responsibility for decision-making. They should develop only the information required to identify and size the stories that drive it confidently or to determine the best technical approach. Spike results may differ from a story because they often produce information rather than working code. Like other stories, spikes are put in the Team Backlog, estimated, and sized to fit in an iteration. Quantifiable, Demonstrable, and Acceptable The following suggested guidelines apply. However, they do create knowledge and learning. Since spikes do not directly deliver user value, use them sparingly. A functional spike – Prototype a histogram in the web portal and get some user feedback on presentation size, style, and charting.

Spike meaning in rasta update#

A technical spike – to research how long it takes to update a customer display to current usage, determining communication requirements, bandwidth, and whether to push or pull the data.In this case, a team might create both types of spikes: “As a consumer, I want to see my daily energy use in a histogram to quickly understand my past, current, and projected energy consumption.” Some features and user stories may require both types of spikes. Develop confidence about the desired solution path.Evaluate specific technical implementation approaches.Evaluate the potential performance or load impact of a new user story.Technical spikes – They are used to research various approaches in the solution domain.

Spike meaning in rasta how to#

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 the following: Spikes may involve creating a small program, research activity, or test demonstrating new functionality.

Gain confidence in a technical or functional approach, reducing risk and uncertainty.

Conduct primary 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 into 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 a mechanism and workflow that Agile Release Trains (ARTs) use to help determine the viability of Epics. Like other stories, spikes are estimated, implemented and demonstrated. 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. Defined initially in Extreme Programming (XP), spikes represent activities such as exploration, architecture, infrastructure, research, design, and prototyping. Note: This article is part of Extended SAFe Guidance and represents official SAFe content that cannot be accessed directly from the Big Picture. If we knew what we were doing, it wouldn’t be called research.