Spike in Agile

 

In Agile , a "spike" refers to a time-limited research or exploratory activity undertaken by a development team to address specific technical uncertainties or gather essential information crucial for project planning and decision-making. It could be investigating the feasibility of a new feature, learning a new framework, experimenting with an architecture, or researching a specific technology. Spike should:

1. Typically lasting no longer than a single sprint, spikes aim to investigate potential solutions, evaluate new technologies, or assess the feasibility of proposed features.

2. Teams allocate resources, such as skilled personnel and time, to delve into the problem, often producing prototypes, conducting experiments, or researching alternative approaches. 

3. Documentation of findings is vital, enabling the team to share insights, inform stakeholders, and guide subsequent development efforts.

4. By embracing spikes, Agile teams effectively manage risks, enhance project understanding, and foster informed decision-making throughout the development lifecycle.

5. Working on a spike in Agile involves several steps to effectively gather information, explore possibilities, and make informed decisions which involves:
a. Identifying the problem or task
b. Set objectives, allocate resources & time box the activities
c. Conduct research and exploration & documents the findings
d. Review and share results, make informed decisions & iterate if necessary