A Scrum Spike is a time-boxed research and development effort used to answer a specific question or solve a problem. It is an opportunity for a team to explore new technologies or ideas, or to gain a deeper understanding of a particular area. If you wanna know more about Scrum Spikes, feel free to check out this blog post, where we furtherly explain the concept and present best practices.
One huge issue is that it can be challenging to know how much time and effort to invest in a Spike, especially when you are dealing with uncertainty. This is where Colin Powell's 40-70 rule for decision-making can be helpful; and today we will explain how to apply and measure Colin Powell's 40-70 rule when conducting a Scrum Spike.
The first step in conducting a Scrum Spike is to define the problem or question you are trying to answer. Once you have a clear understanding of the problem, you can assess how much knowledge you have about it. Assign a percentage to represent the level of knowledge you have. For example, if you have done some preliminary research and have a general idea of the solution, you might assign a 40% level of knowledge.
Next, you should consider how much time and effort you are willing to invest in the Spike, given the level of knowledge you have. Ideally, you want to balance the amount of effort you put in with the level of knowledge you need to make a decision.
Using the 40-70 rule, you should aim to invest between 30-60% of the effort required to fully solve the problem or answer the question. This means that if you have 40% knowledge, you should aim to invest between 30-60% effort to gather the additional information needed to make an informed decision. Similarly, if you have 70% knowledge, you should aim to invest between 30-60% effort to confirm your understanding of the problem or question.
It's important to remember that this is a guideline, and you should use your judgment to determine how much effort to invest. Factors such as the urgency of the problem, the availability of resources, and the potential impact of the decision should be considered when determining the appropriate level of effort.
To measure the success of your Spike, you should compare the level of knowledge you had before starting the Spike to the level of knowledge you have at the end of the Spike. Ideally, you should have gathered enough information to make an informed decision, without investing too much time and effort.
If you find that you have invested too little effort, you may need to extend the Spike or conduct additional research. Conversely, if you find that you have invested too much effort, you may need to adjust your estimation of the level of knowledge you had before starting the Spike.
In summary, Colin Powell's 40-70 rule can be a useful guideline for conducting a Scrum Spike. By assessing the level of knowledge you have, balancing effort and knowledge, and measuring the success of the Spike, you can make informed decisions and use your time and resources effectively.
Remember that this is a guideline, and you should use your judgment to determine how much effort to invest. The goal is to gather enough information to make an informed decision without investing too much time and effort.
By using the 40-70 rule, you can ensure that you are investing the appropriate level of effort to achieve your goals and make informed decisions.
