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. The story may contain significant technical risk, and the team may have to do some experiments or prototypes to gain confidence in a technological approach that may allow them to commit the user story to some future timebox.A story requires to be implemented using a 3 rd party library with API that is poorly written and documented.The team may not have knowledge of a new technology, and spikes may be used for basic research to ensure the feasibility of the new technology (domain or new approach).Here are the examples of when Spikes may be used: The Product Owner allocates a little bit of the team’s capacity now, ahead of when the story needs to be delivered, so that when the story comes into the sprint, the team knows what to do. Thus, you may consider a spike as an investment for a Product Owner to figure out what needs to be built and how the team is going to build it. Sometime the team unsure if they can complete the story due to some potential blockers and probably can’t even estimate the story. It features scrum tools like user story map, product backlog management, sprint backlog management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint retrospective tool, burndown, impediment, stakeholder and team management. A powerful scrum software that supports scrum project management.
0 Comments
Leave a Reply. |