Generate and Analyze Project Burndown Charts

Burndown Chart Generator helps teams visualize remaining work over time and discuss sprint or release progress. Guidance covers sprint, release, epic, and team burndown charts. A chart typically plots time periods on the horizontal axis and remaining work, such as story points, hours, or tasks, on the vertical axis. It can compare an ideal line with actual progress and mark scope changes.

The guidance covers collecting daily progress and scope-change data, checking estimation consistency and missing updates, and accounting for weekends or holidays. Example analysis calculates daily points burned, average daily velocity, projected completion, and a simple increasing or decreasing trend. It also describes trend indicators for acceleration, weekends, scope changes, confidence intervals, and forecast outcomes.

Use this skill to create a visual summary of sprint progress, compare actual work against an ideal burndown, or support a conversation about scope and delivery trends. It can help project managers and Scrum teams review patterns and prepare retrospective discussion.

Do not treat chart movement as a complete measure of team performance. Flat lines may reflect weekends or blocked work; upward movement may reflect added scope or estimation changes. Forecasts depend on data quality and assumptions about recent velocity, so do not present an estimated completion date or confidence value as certain. Sample dates, sprint number, point totals, lookback window, and formulas are examples, not default project settings.

Inputs include sprint dates, total estimated work, working days, daily remaining and completed points, and recorded scope additions or removals. Use consistent estimates and regular updates; document scope changes and account for non-working days.

The output can be a chart with ideal and actual lines, axis labels, legend, grid, and annotations for scope changes. Analysis may summarize average daily velocity, a projected completion estimate, or a trend label. Recommendations can compare slopes, identify velocity variation, correlate external factors, and inform retrospective discussion. Predictions should expose their assumptions and be checked against the underlying progress data.

The source demonstrates Python chart generation with Matplotlib, NumPy, and datetime utilities, and gives spreadsheet formula examples for Excel or Google Sheets. It names Jira and Azure DevOps as possible project data sources. Suggested exports include PNG, PDF, and SVG, and it mentions dashboards, daily collection, real-time updates, and notifications as integration considerations. No particular connector is specified.

This skill is for project managers, Scrum practitioners, and teams tracking sprint or release work. It is most useful when teams want to discuss progress and scope using a shared visual. Keep charts transparent about estimates, non-working days, scope adjustments, and forecast uncertainty so they support communication rather than stand in for it.

import matplotlib.pyplot as plt
import numpy as np
from datetime import datetime, timedelta

def generate_burndown_chart(sprint_data):
    days = [d['day'] for d in sprint_data['daily_progress']]
    remaining = [d['remaining_points'] for d in sprint_data['daily_progress']]