Prototypes, Proof of Concepts (PoC), and Wireframes all fall into the classification of Spikes. If the team estimated that a Spike takes four hours, then ONLY four hours should be spent researching or developing. Ultimately the value from the spike is a direction or re-direction in the course of the feature. That thing can be a working piece of software, workflow, documentation, etc. The task’s duration should be spent researching and developing some ‘thing’ that can be delivered. Spikes should be estimated as in-Sprint tasks during Sprint Planning. “Prototype a histogram in the web portal and get some user feedback on presentation size, style, and charting” Functional spikes are often best evaluated through some level of prototyping, whether it be user interface mockups, wireframes, page flows, or whatever techniques is best suited to get feedback from the customer or stakeholders., “how long it takes to update a customer display to current usage, determining communication requirements, bandwidth, and whether to push or pull the data” Functional SpikeĪ functional spike are used whenever there is significant uncertainty as to how a user might interact with the system. The technical spike is used more often for evaluating the impact new technology has on the current implementation that the team needs experiment a new technology to gain more confident for a desired approach before committing new functionality to a timebox. A distinction can be made between technical spikes and functional spikes: Technical Spike Spikes primarily come in two forms: technical and functional.
0 Comments
Leave a Reply. |