×
Back to book

Tech Spike

The tech spike allowance creates a bank of time which can be drawn upon when the development team needs it. The tech spike allocation is used as a chance for the team to take time to research or test concepts before they estimate properly on something.

Similar to the trim the tail allowance, the tech spike allowance creates a bank of time which can be drawn upon when the development team needs it. The tech spike allocation is used as a chance for the team to take time to research or test concepts before they estimate properly on something. Typically, it is a developer who indicates the need for it, though all tasks with a risk rating higher than eight must be de-risked before estimating, which is almost always reduced through the completion of a tech spike.

A tech spike can be included in the development process in two ways: If the issue being estimated has a high priority and cannot be moved into another iteration, then the tech spike can slot in before the next iteration as a chance to research before estimating. The other option is that the issue can be moved into a later iteration, and a tech spike can be put into the next iteration in its place (This option doesn't interrupt the development flow).

Currently, the tech spike allocation is calculated using a 10%^ modifier on an estimation including risk, allocation and trim the tail factors.

^These modifier amounts are a recommendation based on our experience.

tech spike.png