Over the years, research spikes have proven to be valuable tools for Agile project management teams because they enable them to make informed decisions and deliver a better product. So what exactly is a research spike? And when, why and how should teams use them?
A research spike is a brief period of investigation, with a predetermined timeframe, when the team digs into a specific problem or question that has come up during software development. During times of uncertainty, research spikes play a crucial role in the development process because they empower teams to make the best possible decisions about technology, architecture, or solutions, while boosting efficiency and improving problem-solving.
When Would a Team Use Research Spikes?
Research spikes are particularly useful when the team faces a challenge involving an unclear approach, technology stack, or implementation. Research spikes also help when dealing with complex problems or unfamiliar domains that require exploration. They assist with external dependencies, such as integrating with third-party systems or APIs. Additionally, they are valuable for prototyping when testing the feasibility or performance of a new concept or approach.
Characteristics of a Research Spike
A research spike typically has four defining characteristics. First, it is time-boxed, meaning that it lasts for a short, defined period — usually one to two days or up to one sprint. Second, it is focused, targeting a specific area of uncertainty or exploration. Third, it is non-deliverable, meaning that it produces knowledge rather than a working feature or code. Lastly, a spike is collaborative because team members share knowledge and insights with each other.
Steps for Conducting a Research Spike
- Identify the Problem: Clearly define the uncertainty or question that needs investigation.
- Set a Goal: What do you aim to discover or solve during the spike?
- Timebox the Spike: Establish a predetermined duration to ensure efficiency and prevent delays.
- Gather Information: Research relevant resources such as documentation, libraries, or prototypes.
- Collaborate: Involve the right team members to maximize knowledge-sharing.
- Summarize Findings: At the end of the spike, share findings and recommend the next steps.
Best Practices for Research Spikes
To maximize effectiveness, teams need to set clear objectives to ensure they are tackling a well-defined question or problem. Also, it is essential to involve the right people, including technical experts or stakeholders, in the research process. Limiting the scope helps prevent scope creep and keeps the spike focused. Finally, documenting and sharing findings ensures transparency and accessibility of knowledge.
Example Scenarios for Research Spikes
At Tria Federal, research spikes are particularly valuable to our Human Experience team, which uses them during sprints to break down tasks and develop designs that can support later product development. Other scenarios where research spikes prove beneficial include:
- Evaluating frameworks for a new project.
- Investigating new machine learning tools for integration.
- Optimizing database indexing strategies for improved query performance.
- Diagnosing complex bugs or defects.
Benefits of a Research Spike
Research spikes offer several advantages. They reduce technical debt by addressing uncertainty early, preventing future complications. They generate insights that lead to better design, resulting in well-thought-out architecture and solutions. They save time and facilitate faster decision-making. Finally, research spikes foster collaboration, engaging team members and encouraging cross-functional teamwork.
Challenges and Considerations
Despite their benefits, research spikes present some challenges. Managing time effectively is crucial because it is easy to overextend research spikes beyond their intended scope. Without well-defined goals, spikes can become unfocused or unproductive. Moreover, unclear next steps after a research spike can hinder progress, which reinforces the need to document findings and establish actionable steps.
Research spikes are essential practices for teams looking to reduce uncertainty, make informed decisions, and improve collaboration. By following best practices, teams can confidently navigate technical challenges and deliver better results efficiently.
Marcele Viana is the Agile Practice Lead at Tria Federal. She is a Certified Scrum Master, SAFe Advanced Scrum Master, SAFe Product Owner Product Manager, SAFe DevOps, SAFe Agilist, and SAFe Practice Consultant (SPC) and Trainer.
Read about how the Agile process equips teams to succeed in uncertain environments.
Learn why the future of design is not CX or UX, but HX.