![]() ![]() So if you start doing more spikes than story points, the customer could become confused. Over time the customer may be able to learn what is expected out of an iteration. Story points are a way of estimating complexity and size to the customer.If the spike drags on, it can actually slow down the iteration. 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |