Spikes are a really good way for teams to figure out stuff that they don't know and need to know in order to understand the complexity so that it can be properly estimated, or quoted on or simply to find out if something is technically possible or not. [agilebuddy]. The work is not focused on the finished product. It may even be designed to be thrown away at the end. When do you need a spike? When no shippable product is the goal, What god comes out of it after all?
No comments:
Post a Comment