Skip to end of metadata
Go to start of metadata

A Spike is an investigative piece of work.

Where do they come from?

They come from the PO and Dev Team discussions during the backlog refinement.

What is their purpose?

Increase the understanding of a User Story, feed into design and approaches, open the door to creativity and innovation. In general Spikes help the team create a smoother and healthier backlog where there are "unknowns".

For how long do they run?

Spikes are time-boxed to a standard of 2 dev days. If more time is required in order to acquire more knowledge either the time is extended or a follow-up spike is created.

Template

<Spike Title>

<Description (Objective)>

<Outcome>

Example

Investigate different ways of migrating the RCS to secrets

Description

The objective of this spike is to provide an analysis of different options in order to migrate the Remote Content Service to secrets.

Outcome

The outcome of the spike should be:

1) recorded on Confluence

2) discussed with the team

3) POC-ed

4) fed into the follow-up User Story

  • No labels