What are a Burndown Chart, a Burnup Chart, and Velocity?

The video tutorial explains burn down and burn up charts as tools for measuring progress in agile projects. Burn down charts show remaining work over time, while burn up charts display completed work. The video also covers how to compare actual progress with planned progress using these charts. Additionally, it introduces the concept of velocity, which measures the rate of work completion, and discusses its role in planning future work. The tutorial emphasizes that velocity should not be used as a performance measure.

What does a burn down chart typically show?

• Completed work over time

• Remaining work over time

• Team efficiency

• Project budget

In agile projects, burn up charts are often used to:

• Estimate project costs

• Measure progress in a single sprint

• Summarize progress over the entire project

• Track team performance

How is velocity calculated in agile projects?

• Time elapsed divided by work completed

• Efficiency divided by time

• Work completed divided by time elapsed

• Number of sprints divided by story points

What is the primary purpose of measuring velocity?

• To measure team efficiency

• To assess team performance

• To estimate future work

• To calculate project costs

Why should velocity not be used as a performance measure?

• It does not account for team efficiency

• It is too complex to calculate

• It varies too much between projects

• It is not a reliable metric

What is a common mistake when using velocity in agile projects?

• Calculating it over multiple sprints

• Using it to estimate story points

• Using it as a KPI for team performance

• Using it to plan future work

What should be considered when averaging velocity over time?

• Focus on the most recent sprint

• Remove the earliest cycles

• Include all cycles equally

• Include only the latest sprints