1/16/2024 0 Comments Spike meaning agile development![]() Spikes should be assigned a short timebox limit.Completing a Spike does not directly deliver value to the customer.They are accepted by the product owner and are put in the backlog and sized to fit into an iteration just like any other story. Spikes have acceptance criteria, whether it be documentation or a demonstration of what was learned via the Spike therefore, a Spike creates value for the project.Team velocity can be negatively skewed if an abundant amount of Spikes are in your current iteration and have not been assigned points.Also, anytime effort is put forth on a task, it should be made visible to the project. A Spike should be assigned points because it requires a team’s resources to complete.Naturally, we started questioning whether or not we should even be pointing Spikes? Here are some of the pros and cons of assigning points to a Spike that our team discussed. The philosophy when I joined the team was that a Spike always got assigned 3 points since there was too much uncertainty in a Spike to estimate the work correctly. ![]() Like any other story or task, the spike is then given an estimate and included in the sprint backlog. ![]() The solution is to create a “spike,” which is a story whose purpose is to provide the answer or solution. Sometimes a user story is generated that cannot be estimated until the development team does some actual work to resolve a technical question or a design problem. In case you are unfamiliar with the term Spike (in regards to agile development), the definition, according to, is:Ī story or task aimed at answering a question or gathering information, rather than at producing shippable product. Our team has been discussing the pros and cons of assigning points to a Spike and determining our approach. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |