Whether to timebox or estimate Spikes is one of the controversial topics. Some scrum teams believe spikes should be treated the same way as user stories. As a result, they estimate Spikes.
On the other hand, you have another group that believes one should timebox spikes. And that begs the question; who is right?
In my experience as a scrum master, no one is wrong or right on this matter. I had worked with teams from both parties.
But which is better; timebox or estimate spikes?
Well, let’s see which is better and why you may want to choose one over the other.
What are Spikes in scrum?
Spike(s) was originally invented from Extreme Programming (XP). It is a type of user story to capture tasks like researching and exploring in a sprint.
The purpose of Spike is to help the team gather knowledge. This knowledge helps them understand the requirements or functionality of a product or feature.
Developers can also create a spike to collect information needed to reduce technical risks. Prototyping a solution is another task a spike can be used for.
While spikes don’t deliver value to customers or add to product increment, they’re as important as user stories.
Should you timebox or estimate spikes in scrum?
For a scrum team that is new to the scrum framework, time-boxing spikes may be the best practice.
However, if such a team deals with spikes a lot, time-boxing might affect determining the team’s capacity.
Scrum teams avoid estimating spikes because no one wants to spend all day on a spike. You cannot say when a spike is completed. Especially if it has to do with understanding requirements or exploring new technologies.
As a result, many scrum teams prefer to timebox spikes rather than estimate them. That way, they know when to stop and focus on delivering value to their customers.
But for a mature scrum team, estimating spikes should work perfectly well. They understand the purpose of Spikes.
In addition, they have an idea of the average time a story point would take them to complete. With that, the team knows exactly when it’s time to close a spike.
In my experience, the choice between timeboxing and estimating spikes depends largely on your team’s specific needs. It also depends on the maturity and the nature of the tasks.
Who is responsible for spikes in scrum?
In scrum, the development team is primarily responsible for handling spikes. They take on spikes to have a clear understanding of the problem and can come up with the best solutions.
The development team is well-equipped to tackle spikes because they possess the technical expertise required for detailed exploration.
They conduct research, experiments, and other investigative work to gather information.
This process helps them to identify potential risks and devise strategies to mitigate them effectively.
Having the development team handle spikes ensures that the insights gained are directly from those who will implement the solutions.
This hands-on approach ensures that any technical challenges are understood thoroughly.
For effective spike management, the development team collaborate closely with the scrum master and product owner.
In addition, documentation of findings is their responsibility. They do this so the entire team can benefit from the insights gained, leading to improved decision-making and project outcomes.
How do spikes benefit the scrum process?
Spikes are crucial for the scrum process as they help refine the product backlog and address uncertainties early.
By investigating uncertainties and gathering detailed information, scrum team can better understand complex or unfamiliar aspects of their project.
This knowledge allows them to refine user stories. It ensures that each task in the product backlog is well-defined. Each task is achievable within a sprint.
As a result, the product backlog becomes a more accurate representation of the tasks ready to go into sprint. And this facilitates smoother progress throughout the project.
The development team, through spikes, can also provide accurate estimates for future tasks.
When they work on a spike, they delve into specific technical challenges or unknowns. They conduct research and experiments to gain clarity.
This process helps them break down large or vague tasks into manageable components.
With a detailed understanding, the team can create more precise estimates for the effort and resources required.
Moreover, each spike equips the development team with valuable knowledge and experience. This helps the team build a repository of insights that can be applied to future challenges.
Timebox or estimate spikes: Which should you choose?
Timeboxing spikes and estimating them are valuable practices in the Scrum toolkit, each with its strengths. In practice, a combination of both techniques offers the best results.
Integrate timeboxing for regular tasks and utilize estimating spikes to handle uncertainties. This way, you can create a balanced approach that maximizes productivity and minimizes risks.
The key point?
By understanding when and how to use these techniques, you can optimize your team’s workflow. This will enhance productivity. It ensures you deliver high-quality results consistently.
Have you tried both methods in your team? Share your experiences and insights below.
Here’s my post on documentation in scrum. I recommend that you read it.
I hope you found this post helpful.
