Mastering Waterfall Cards: Step-by-Step Guide

Waterfall cards, also known as planning poker cards, are a powerful tool used in Agile methodologies to estimate effort required to complete a task. They help teams make informed decisions and plan their work more effectively. If you're new to waterfall cards or want to improve your understanding of how to use them, this step-by-step guide will walk you through the process.

Before we dive into the steps, let's briefly understand the concept. Waterfall cards are a set of cards with numbers written on them, typically ranging from 1 to 20. These numbers represent the effort required to complete a task, with 1 being the smallest and 20 being the largest. The most common scale used is the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21, etc.), which helps to avoid arbitrary estimates.

Preparing for Waterfall Card Estimation

Before you start the estimation process, there are a few things you need to prepare.

First, ensure all team members are present and have a clear understanding of the task at hand. It's crucial that everyone is on the same page to make accurate estimates.

Gather Information

Before you start estimating, you need to gather as much information about the task as possible. This includes understanding the task's requirements, dependencies, and any potential risks.

Break down the task into smaller, more manageable pieces if necessary. This will make it easier to estimate and understand the effort required for each part.

Set Up the Cards

Prepare your waterfall cards. You can use physical cards or digital tools that simulate the cards. Ensure each card has a unique number representing the effort required.

If you're using the Fibonacci sequence, remember that each number represents a magnitude of effort, not an exact amount of time. For example, an estimate of 8 is roughly five times more effort than an estimate of 2.

Conducting the Waterfall Card Estimation

Now that you're prepared, it's time to conduct the estimation.

Follow these steps to ensure a smooth and productive estimation session:

Present the Task

The product owner or the person presenting the task should clearly explain what needs to be done, including any dependencies and assumptions.

Encourage questions and clarifications to ensure everyone understands the task before estimating.

Estimate Individually

Each team member should estimate the task independently. This helps to avoid groupthink and ensures a diverse range of opinions.

Team members should select the card that best represents the effort they believe is required to complete the task. They should consider the task's complexity, size, and any risks involved.

Reveal Estimates

Once everyone has made their estimate, they should reveal their card simultaneously. This helps to avoid influencing each other's estimates.

If there's a significant difference in estimates, it's a good opportunity to discuss why. This can help the team understand different perspectives and refine their estimation skills.

Discuss and Adjust

After revealing the estimates, discuss the differences. The goal is not to reach a consensus but to understand the reasons behind each estimate.

If necessary, adjust the estimate based on the discussion. It's common for the final estimate to be the average of the individual estimates.

Record the Estimate

Record the final estimate for future reference. This can help track progress and improve estimation accuracy over time.

Also, record any assumptions, dependencies, or risks discussed during the estimation. This can help the team plan their work more effectively.

Using Waterfall Card Estimates

Once you have your estimates, it's time to use them to plan your work.

Waterfall card estimates help you prioritize tasks, allocate resources, and set realistic deadlines. They also help you identify tasks that may be too large or complex and need to be broken down further.

Relative Sizing

Waterfall card estimates are relative, not absolute. This means they help you compare the size of tasks, not predict the exact time it will take to complete them.

For example, if task A is estimated at 5 and task B is estimated at 8, you know that task B is roughly 1.6 times larger than task A. But you don't know exactly how long it will take to complete either task.

Velocity and Capacity Planning

Waterfall card estimates help you determine your team's velocity, which is the average number of story points (the unit of measure for waterfall card estimates) completed per sprint.

Once you know your velocity, you can use it to plan your capacity and set realistic goals for your sprints.

Remember, waterfall card estimation is an iterative process. The more you use it, the better you and your team will become at estimating effort. Regularly review and refine your estimation process to ensure it continues to serve your team's needs.

Embrace the uncertainty that comes with estimating complex work. Waterfall cards help you make informed decisions, but they're not a crystal ball. Stay flexible and adapt your plans as new information comes to light.

Now that you know how to make waterfall cards and use them to estimate effort, it's time to put your new skills into practice. Start with the next task on your team's backlog and see the power of waterfall cards for yourself.