Mitch Lacey's Estimation Game Template
Estimate and prioritize your tasks using Mitch Lacey’s tried-and-tested Scrum game — to help your teams work more efficiently.
About the Mitch Lacey’s Estimation Game template
Reviewing your backlog doesn’t have to be boring — especially not when you’re playing Mitch Lacey’s Estimation Game, a group activity designed to bring teams together and make priorities clearer.
What is Mitch Lacey’s Estimation Game?
First introduced in his book, The Scrum Field Guide: Practical Advice for your First Year, Mitch Lacey’s Estimation Game is a visual exercise designed to help Agile teams prioritize tasks in their project backlog together — similar to other Agile practices like Scrum Poker. Teams can estimate how high of a priority their tasks are by arranging them along a matrix, which helps measure how important a task is and how much effort it will take.
How do you use the template for Mitch Lacey’s Estimation Game?
We’ve prepared a short step-by-step process to help you make the most of the template for Mitch Lacey’s Estimation Game. Let’s take a look:
1. Understand the matrix
When you first open the template in Miro, you’ll see a matrix, which you’ll use to estimate and assign priorities to your tasks. The x-axis represents how big or small a task is — in other words, how much effort it’ll take to complete it. The y-axis represents how high or low of a priority it is — whether that’s based on ROI, business impact, or any other important metrics. Talk to your team about how you want to measure a task’s priority.
2. Use sticky notes to represent your tasks
When you’re ready, use the sticky notes to represent your tasks on the matrix. Write one task per sticky note, such as “landing page design” or “CMS evaluation”. The template comes with a few sticky notes already, but you can always add more if you need them.
3. Arrange your sticky notes along the matrix
Once you’ve written down all your tasks, arrange the sticky notes along the matrix based on their priority and task size. Tasks in the top-left are small and of higher priority. Tasks in the top-right are also more important but take more effort to complete — consider breaking these tasks into smaller goals. Tasks in the bottom right are less of a priority and take more effort to complete — place them toward the bottom of your backlog. Tasks in the bottom-left are also of low priority but take less effort to complete.
Talk to your team about how to best rearrange your backlog. Want a quicker way to decide on priorities? Start a voting session right on your Miro board using our voting tool.
When should you use the Estimation Game?
Play Mitch Lacey’s Estimation Game whenever your backlog has grown large and you find your team feeling overwhelmed. It can help you review your product backlog and recenter your team’s focus on the tasks that matter most. It’s also a great way for developers and product management teams to collaborate effectively and efficiently. Re-play the game anytime you find your backlog getting unmanageable — or refer to past iterations for guidance.
Get started with this template right now.
Epic & Feature Roadmap Planning
Epic & Feature Roadmap Planning template facilitates the breakdown of large-scale initiatives into manageable features and tasks. It helps teams prioritize development efforts based on business impact and strategic objectives. By visualizing the relationship between epics and features, teams can effectively plan releases and ensure alignment with overall project goals and timelines.
Risk Matrix Template
Works best for:
Leadership, Decision Making, Strategic Planning
A risk matrix--also known as a probability matrix, risk assessment matrix, or impact matrix--is a tool that allows you to evaluate overall risk by visualizing potential risks in a diagram. The tool allows you to weigh the severity of a potential risk against the probability that the risk might occur. Risk matrices are useful for risk management because they visually represent the risks involved in a decision. This empowers you to avoid worst-case scenarios by preparing contingencies or mitigation plans.
User Persona Template
Works best for:
Marketing, Desk Research, User Experience
A user persona is a tool for representing and summarizing a target audience for your product or service that you have researched or observed. Whether you’re in content marketing, product marketing, design, or sales, you operate with a target in mind. Maybe it’s your customer or prospect. Maybe it’s someone who will benefit from your product or service. Usually, it’s a whole collection of personalities and needs that intersect in interesting ways. By distilling your knowledge about a user, you create a model for the person you hope to target: this is a persona.
FMEA Analysis Template
Works best for:
Agile Methodology, Strategic Planning, Software Development
When you’re building a business or running a team, risk comes with the territory. You can’t eliminate it. But you CAN identify it and mitigate it, to up your odds of success. Failure Modes and Effects Analysis (FMEA) is a powerful tool designed to help you manage risk and potential problems by spotting them within a process, product, or system. And you’ll spot them earlier in your process—to let you sidestep costly changes that arise late in the game or, worse, after they’ve impacted your customers and their experience.
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.
SAFe Roam Board
Works best for:
Agile Methodology, Operations, Agile Workflows
A SAFe ROAM Board is a framework for making risks visible. It gives you and your team a shared space to notice and highlight risks, so they don’t get ignored. The ROAM Board helps everyone consider the likelihood and impact of risks, and decide which risks are low priority versus high priority. The underlying principles of SAFe (Scaled Agile Framework) are: drive cost-effective solutions, apply systems thinking, assume that things will change, build incrementally, base milestones on evaluating working systems, and visualize and limit works in progress.