关于average burnup（平均燃起值）与average burndown（平均燃尽值）的计算方式、实现逻辑及计算公式的技术问询

Hey there! Since you already have standard burnup and burndown charts in your dashboard, let’s break down the average versions of these metrics—their core logic, how to calculate them, and the formulas you can use to derive them.

Average Burnup (平均燃起值) #

Core Logic #

Burnup charts track two key data points: total work to be done, and work completed over time. The average burnup metric measures your team’s average rate of completed work per unit time—think of it as a baseline for how much your team typically delivers in a sprint, day, or other defined time frame. It’s great for forecasting future throughput.

Calculation Methods & Formulas #

There are two common ways to compute this, depending on your team’s tracking cadence:

• Iteration/Sprint-Based Average Burnup
  This is ideal for teams working in sprints. It averages the total work completed across all finished sprints.

  • Logic: Sum up all work completed in each sprint, then divide by the number of sprints you’re analyzing.
  • Formula:

    Average Burnup (Sprint) = Total Completed Work Across All Sprints / Number of Sprints
    

  • Example: If your team completed 10, 12, and 8 story points in 3 sprints, your average burnup is (10+12+8)/3 = 10 story points per sprint.

• Daily-Based Average Burnup
  Use this for day-to-day progress tracking (perfect for short-term projects or continuous delivery workflows).

  • Logic: Calculate total work completed since the project started, then divide by the number of working days elapsed (skip weekends/holidays where no work was completed).
  • Formula:

    Average Burnup (Daily) = Total Completed Work / Number of Working Days Elapsed
    

Average Burndown (平均燃尽值) #

Core Logic #

Burndown charts focus on remaining work over time. Average burndown measures the average rate at which your team reduces remaining work per unit time—it’s a go-to metric for predicting project completion dates and verifying if your team is on track to meet deadlines.

Calculation Methods & Formulas #

Again, two common approaches based on your tracking cadence:

• Iteration/Sprint-Based Average Burndown
  You can calculate this in two equivalent ways, depending on the data you have available:

  1. By Sprint Work Reduction
     • Logic: Sum up how much work your team reduced each sprint (i.e., the work completed that sprint), then divide by the number of sprints.
     • Formula:

       Average Burndown (Sprint) = Sum of Work Reduced Per Sprint / Number of Sprints
       

  2. By Total Work Change
     • Logic: Take the initial total work minus the current remaining work, then divide by the number of completed sprints.
     • Formula:

       Average Burndown (Sprint) = (Initial Total Work - Current Remaining Work) / Number of Sprints Completed
       

  • Example: If your project started with 50 story points, and after 3 sprints you have 20 left, your average burndown is (50-20)/3 = 10 story points per sprint.

• Daily-Based Average Burndown
  For day-to-day tracking, this metric shows how much remaining work your team clears on average each working day.

  • Logic: Subtract current remaining work from the initial total work, then divide by the number of working days elapsed.
  • Formula:

    Average Burndown (Daily) = (Initial Total Work - Current Remaining Work) / Number of Working Days Elapsed
    

Quick Best Practices #

• Stick to a consistent work unit (story points, hours, task count, etc.) across all calculations—mixing units will skew your results.
• If your project scope changes (e.g., new requirements added), adjust your initial total work or calculate a separate average for the post-scope-change period to keep metrics accurate.

内容的提问来源于stack exchange，提问作者PMARCOS