Fibonacci Scale Template
Estimate how much effort it takes to perform tasks and assign teams during a work sprint efficiently with the Fibonacci Scale Template.
Trusted by 65M+ users and leading companies
About the Fibonacci Scale Template
The Fibonacci scale is a series of numbers based on the Fibonacci sequence (0, 1, 2, 3, 5, 8, 13, 21, etc.). In the context of Agile, these numbers are used to estimate and agree upon the amount of effort required to complete a specific task. At the beginning of an Agile sprint, a team will discuss the various tasks that need to be completed and assign points to each task based on the Fibonacci scale.
What is the Fibonacci scale?
The Fibonacci sequence contains numbers that exhibit exponential growth, where each number is the sum of the two previous ones. That’s why Agile teams have come to use the Fibonacci scale for business because it’s easier to evaluate task efforts when you don’t have many numbers close to each other to choose from, as opposed to an even scoring scale. When managing a team, it’s often important to estimate how long it might take to complete a given task. More complex tasks are assigned more points, and smaller tasks are assigned fewer points. Managers can then review and prioritize tasks depending on their points. The Fibonacci scale is used to assign those point values.
How does the Fibonacci scale work?
The numbers in the Fibonacci scale are based on the Fibonacci sequence. In this sequence of numbers, each number is the summation of the two previous numbers. In the context of Scrum, the numbers represent the level of complexity and degree of difficulty involved in completing a task. For example, a task assigned “0” points would be very simple and quick to complete, a task assigned “1” point would be slightly more complex or time-consuming, and so on and so forth. Since the Scrum approach generally works in one-week sprints, it’s unlikely that many tasks will be assigned “21.”
Why use the Fibonacci scale?
The Fibonacci scale is a useful tool for a variety of reasons. For one, its growth is exponential. When estimating how long it might take to complete a task, estimating time for shorter tasks is much easier than estimating time for longer tasks. An exponential scale reflects that growing uncertainty. As you move up the scale, the numbers quickly become much larger.
Relatedly, the Fibonacci scale forces your team to make a choice. For example, when estimating time for a complex task, you ask, “is it an 8, 13, or 21?” and there is no in-between. This intuitive anchoring mechanism cuts down on debate and helps you make clear judgment calls.
Overall, the Fibonacci scale is a powerful method to ensure that work is distributed evenly and can help ensure that everyone is accurate when estimating the work and time involved in a project. If your team uses this approach on an ongoing basis, you will likely become more accurate and avoid overcommitting during each sprint.
How to use the Fibonacci Scale Template in Miro
Start selecting our ready-made Fibonacci Scale Template. It will help you visualize your team’s tasks, evaluate efforts and prioritize them.
The Fibonacci Scale Template is divided into three sections:
User stories
Here is where you list tasks or user stories you want to estimate. If you use Jira, import stories as cards directly with the Jira app. Afterward, discuss with your team the risk and effort for each story.
Fibonacci Scale
Place the stories previously added to the sprint onto the Fibonacci scale matrix. Following your discussion, add them to the appropriate region according to their effort and risk levels.
To get perspectives and assess correctly how much effort and risk a task might take, allow each member to vote on the tasks with a unique emoji or sticker.
Priorities
Based on the Fibonacci scores and the team's prioritization, copy or drag stories onto the priorities frame. Be mindful of your team's capacity, and prioritize taking everyone’s opinions and schedules into consideration.
If you’re finding it hard to estimate task points, Artem Shein, Agile coordinator, created an interesting and fun template to help you and your team give points to tasks. Try it out!
Example of the Fibonacci Scale Template in action
Let’s say you are launching different product functionalities. You have user stories that look like this:
Service catalog
Calendar integration
Video integrations
Live cursors
After everyone has added their tasks to the Fibonacci scale, these are the points each task has:
Calendar integration: 8
Live cursors: 5
Video integration: 3
Service catalog: 2
To prioritize this list, start with the tasks with the least effort and lower risk. Those are the ones that your team will be able to deliver quicker. Afterward, list the ones that range from medium to high effort.
If you think a task that is higher up on the scale might not require so much effort, discuss it with your team to see what you can do to make its completion easier.
Create your priority list according to your team’s feedback and assign each task to its owner via Jira cards or tagging the stickies on your Fibonacci Scale Template.
Get started with this template right now.
Kaizen Report Template
Works best for:
Agile Methodology, Operations, Documentation
What makes a great company great? They know that greatness needs to be fostered and maintained — meaning they never stop working to improve. If you’re one of those companies (or aspire to be), a kaizen report is an ideal tool. It creates a simple visual guide to continuous improvement activities on a team, departmental, and organizational level. Using a kaizen report approach, every employee in an organization audits their own processes and understands what they might have overlooked, making this a powerful tool for increasing accountability at all levels.
User Story Map Template
Works best for:
Marketing, Desk Research, Mapping
Popularized by Jeff Patton in 2005, the user story mapping technique is an agile way to manage product backlogs. Whether you’re working alone or with a product team, you can leverage user story mapping to plan product releases. User story maps help teams stay focused on the business value and release features that customers care about. The framework helps to get a shared understanding for the cross-functional team of what needs to be done to satisfy customers' needs.
Technology Product Canvas Template
Works best for:
Product Management, Roadmaps, Meetings
Originally created by Prem Sundaram, the Technology Product Canvas allows product and engineering teams to achieve alignment about their shared roadmap. The canvas combines agile methodologies with UX principles to help validate product solutions. Each team states and visualizes both product and technology goals, then discusses each stage of the roadmap explicitly. This exercise ensures the teams are in sync and everyone leaves with clear expectations and direction. By going through the process of creating a Technology Product Canvas, you can start managing alignment between the teams -- in under an hour.
Design Sprint Kit Template
Works best for:
Agile Methodology, UX Design, Sprint Planning
With the right focused and strategic approach, five days is all it takes to address your biggest product challenges. That’s the thinking behind Design Sprint methodology. Created by Tanya Junell of Blue Label Labs, this Design Sprint Kit provides a set of lightweight templates that support the Design Sprint’s collaborative activities and voting—and maintains the energy, team spirit, and momentum that was sparked in the session. Virtual sprint supplies and prepared whiteboards make this kit especially useful for remote Design Sprint Facilitators.
Opportunity Solution Tree Template
Works best for:
Flowcharts, Product Management, Diagrams
Solving problems — successful companies and productive teams just know how to do it. They’re able to identify many possible solutions, then settle on the one that leads to the desired outcome. That’s the power an Opportunity Solution Tree gives you. Designed by Teresa Torres, a product discovery coach, this mind map breaks down your desired outcome into opportunities for the product to meet user needs, then gives your team an effective way to brainstorm potential solutions.
Start, Stop, Continue Template
Works best for:
Retrospectives, Meetings, Workshops
Giving and receiving feedback can be challenging and intimidating. It’s hard to look back over a quarter or even a week and parse a set of decisions into “positive” and “negative.” The Start Stop Continue framework was created to make it easier to reflect on your team’s recent experiences. The Start Stop Continue template encourages teams to look at specific actions they should start doing, stop doing, and continue doing. Together, collaborators agree on the most important steps to be more productive and successful.