Burndown Chart Template
Help your Agile team make their productivity and progress visible
About the Burndown Chart Template
Burndown charts are visual graphs that show teams how much work is left to complete and how much time is available to finish the job.
A typical layout will have two lines representing the volume of work and the number of workdays. Team members leading and executing the day-to-day workload can use a burndown chart to make realistic project estimates.
The visual format helps project managers figure out the difference between the “ideal” progress of work and how the “actual” work is tracking. Teams can use a burndown chart to work toward specific goals and finish a project on time and within budget.
When to use a burndown chart
A burndown chart is a useful project management tool and can be a quicker alternative to a Kanban board or a Gantt Chart. With a burndown, the team can focus on the time left to finish tasks instead of each task’s specific breakdowns.
As a visual reference, burndown charts encourage team transparency and awareness of how much work is getting done on a day-to-day basis.
Burndown charts can also help individual team members realize their pace of work. By checking on it at least once a day, everyone can figure out how to adjust or maintain their output level according to project needs.
How to use the burndown chart template
Making your own burndown chart is easy with Miro's template. Simply follow these steps to get started:
1. Set a target
Set a target for the ideal number of story points you need to finish. Once “total story points” is set, that number should stay untouched for the duration of your team’s sprint.
By default, this template assumes your sprint will last 2.5 weeks. You can edit the X-axis to accommodate week-long, fortnightly, or month-long sprints as well. Your team should keep an eye on the “completed” and “remaining” numbers as these will be updated daily.
2. Set the completion rate
Edit the “ideal” completion rate line to set your target. The grey dotted line represents what the best-case productivity rate would look like. Consider this your visual baseline for whether or not your project is on track.
3. Add to the "completed" storyline
As your team completes story points on a daily basis, update the relevant sticky notes. Grow the solid line that represents your team’s actual completion rate by adding daily extensions. Keep in mind non-working days like weekends or public holidays where progress slows down or isn't expected.
4. Check-in regularly
Keep an open line of communication with your team to set expectations, predict risks, and keep your project on track. Priorities will evolve, and stakeholders may come back to your team with new requests. If your team keeps a record of their progress, they can push back on unreasonable requests together.
A burndown chart tracks your team’s daily progress honestly. Burndowns should also account for when new items are added after the sprint kicks off.
5. Plan future sprints based on previous ones
Use the chart as a reference to plan for future sprints. The chart can help you visualize the impact of new stakeholder requests over time and how much your team can do in an allocated sprint period. Notice a large productivity spurt at the end of your sprint? Break tasks into smaller, manageable tasks for your next sprint.
Get started with this template right now.
Sailboat Template
Works best for:
Agile Methodology, Meetings, Retrospectives
The Sailboat Retrospective is a low-pressure way for teams to reflect on how they handled a project. By defining your risks (the rocks), delaying issues (anchors), helping teams (wind), and the goal (land), you’ll be able to work out what you’re doing well and what you need to improve on for the next sprint. Approaching team dynamics with a sailboat metaphor helps everyone describe where they want to go together by figuring out what slows them down and what helps them reach their future goals.
Iceberg Reflection
Works best for:
Agile
The Iceberg Reflection template is a visual tool for facilitating reflective exercises within Agile teams. It prompts participants to explore both visible and underlying aspects of challenges or successes, akin to an iceberg where only a portion is visible above the waterline. This template encourages deeper reflection and insights, fostering a culture of continuous improvement and learning. By addressing root causes and hidden factors, teams can better understand and overcome obstacles, driving growth and resilience.
Customer Journey Mapping Template Pack
Works best for:
Mapping, User Experience, Workshops
A customer journey map (CJM) is a visual representation of your customer’s experience. It allows you to capture the path that a customer follows when they buy a product, sign up for a service, or otherwise interact with your site. Most maps include a specific persona, outlines their customer experience from beginning to end, and captures the potential emotional highs and lows of interacting with the product or service. Use this template to easily create customer journey maps for projects of all kinds.
The 4-Step Retrospective
Works best for:
Retrospectives, Agile Methodology, Meetings
The 4-Step Retrospective template offers a simple yet effective framework for conducting retrospectives. It provides steps for reflecting on what went well, what didn't go well, what could be improved, and action planning. This template enables teams to systematically review past iterations, identify areas for growth, and implement actionable improvements. By promoting a structured approach to reflection and improvement, the 4-Step Retrospective empowers teams to drive continuous learning and enhancement effectively.
Design Research Template
Works best for:
UX Design, Design Thinking, Desk Research
A design research map is a grid framework showing the relationship between two key intersections in research methodologies: mindset and approach. Design research maps encourage your team or clients to develop new business strategies using generative design thinking. Originally designed by academic Liz Sanders, the framework is meant to resolve confusion or overlap between research and design methods. Whether your team is in problem-solving or problem space definition mode, using a research design template can help you consider the collective value of many unrelated practices.
User Flow Template
Works best for:
Desk Research, Flowcharts, Mapping
User flows are diagrams that help UX and product teams map out the logical path a user should take when interacting with a system. As a visual tool, the user flow shows the relationship between a website or app’s functionality, potential actions a user could take, and the outcome of what the user decides to do. User flows help you understand what a user does to finish a task or complete a goal through your product or experience.