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.
Jobs to be Done template
Works best for:
Ideation, Design Thinking, Brainstorming
It’s all about a job done right — customers “hire” a product or service to do a “job,” and if it's not done right, the customer will find someone to do it better. Built on that simple premise, the Jobs To Be Done (JTBD) framework helps entrepreneurs, start-ups, and business managers define who their customer is and see unmet needs in the market. A standard job story lets you see things from your customers’ perspective by telling their story with a “When I…I Want To…So That I …” story structure.
App Wireframe Template
Works best for:
UX Design, Wireframes
Ready to start building an app? Don’t just imagine how it will function and how users will interact with it—let a wireframe show you. Wireframing is a technique for creating a basic layout of each screen. When you wireframe, ideally early in the process, you’ll gain an understanding of what each screen will accomplish and get buy-in from important stakeholders—all before adding the design and content, which will save you time and money. And by thinking of things in terms of a user’s journey, you’ll deliver a more compelling, successful experience.
Kubernetes Architecture Diagram Template
Works best for:
Software Development, Diagrams
Use the Kubernetes Architecture Diagram template to manage your containerized applications better and bring your apps’ deployment, management, and scalability to the next level. This template helps you lower the downtime in production and allows you to have a more agile app production. Improve the deployment of your apps by visualizing every step of the process with the Kubernetes Architecture template. Try it out, and see if it works for you and your team.
Cost-Benefit Analysis Template
Works best for:
Leadership, Decision Making, Strategic Planning
With so many day-to-day decisions to make—and each one feeling high-stakes—it’s easy for all the choices to weigh a business or organization down. You need a systematic way to analyze the risks and rewards. A cost benefit analysis gives you the clarity you need to make smart decisions. This template will let you conduct a CBA to help your team assess the pros and cons of new projects or business proposals—and ultimately help your company preserve your precious time, money, and social capital.
Kanban Framework Template
Works best for:
Kanban Boards, Agile Methodology, Agile Workflows
Optimized processes, improved flow, and increased value for your customers — that’s what the Kanban method can help you achieve. Based on a set of lean principles and practices (and created in the 1950s by a Toyota Automotive employee), Kanban helps your team reduce waste, address numerous other issues, and collaborate on fixing them together. You can use our simple Kanban template to both closely monitor the progress of all work and to display work to yourself and cross-functional partners, so that the behind-the-scenes nature of software is revealed.
Idea Funnel Backlog
Works best for:
Design, Brainstorming, Agile Workflows
An Idea Funnel Backlog enables you to visualize your backlog and restrict the number of backlogged items at the top. In doing sos, you can prioritize items on your list without having to engage in unnecessary meetings or create too much operational overhead. To use the Idea Funnel Backlog, break up the funnel into different phases or treat it like a roadmap. Use the Idea Funnel Backlog as a hybrid model that combines your roadmap and backlog into one easily digestible format.