Comments on: Should Your SCRUM Team Assign Story Points to a Spike? https://intellitect.com/blog/should-your-scrum-team-assign-story-points-to-a-spike/ Complex Software Development - Simplified Tue, 14 Mar 2023 18:47:52 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Erin https://intellitect.com/blog/should-your-scrum-team-assign-story-points-to-a-spike/#comment-390236 Tue, 14 Mar 2023 18:47:52 +0000 http://intellitect.com/?p=19171#comment-390236 In reply to Bryan.

Thanks for your response Bryan! What you say does have merit and it’s great to consider all the options. With agile, however, there are no absolutes. While spike points may not be within the “spirit” of agile, it can be helpful to some teams. Thanks for reading!

]]> By: Bryan https://intellitect.com/blog/should-your-scrum-team-assign-story-points-to-a-spike/#comment-390190 Fri, 10 Mar 2023 19:58:59 +0000 http://intellitect.com/?p=19171#comment-390190 This guidance is fundamentally incorrect. Spikes should NEVER have story points associated with them. Why? Because they do not, in and of themselves, create value. Can the effort required to perform a Spike be tracked if a team choose to do so? Yes, they would track this effort in hours but not in story points, ever.

The intent is to be judicious in the use of Spikes which can only be achieved if they receive zero story points. A Sprint full of Spikes would not create anything that is potentially shippable or of business value. Most of the time you do not need a Spike, simply build something and incrementally adjust it based on what you learn. This is the intent of refactoring. If you are unclear about the purpose of Spikes return back to where it was created and defined: http://wiki.c2.com/?SpikeSolution

]]>