Agile Agile Metrics and Reporting Questions and Answers — Questions and Answers
Question 1: An Agile Coach is reviewing a team's Cumulative Flow Diagram (CFD). They notice that over the last several weeks, the band representing the 'Testing' phase is progressively widening, while the 'Done' band's slope is much flatter by comparison. What is the most likely conclusion?
- The team's overall velocity is increasing steadily.
- Work is entering the testing phase faster than it is being completed, indicating a bottleneck. (Correct answer)
- The Product Owner is adding new work to the sprint at an unsustainable rate.
- The development team is completing their work ahead of schedule.
Correct answer: Work is entering the testing phase faster than it is being completed, indicating a bottleneck.
A widening band on a Cumulative Flow Diagram (CFD) for a specific stage, like 'Testing', signifies that the number of work items in that stage is increasing over time. This happens when the entry rate into the stage exceeds the exit rate. This pattern is a classic indicator of a bottleneck in the workflow. [7, 12, 17]
Question 2: A Product Owner wants a chart that not only tracks the team's progress towards a release goal but also clearly visualizes the impact of scope changes over time. Which reporting tool is most effective for this purpose?
- Sprint Burndown Chart
- Velocity Trend Chart
- Release Burnup Chart (Correct answer)
- Cycle Time Scatterplot
Correct answer: Release Burnup Chart
A Release Burnup Chart is ideal for visualizing scope changes. It has two primary lines: one showing the cumulative work completed and another showing the total scope of the release. When scope is added, the total scope line moves up, making the impact on the release plan immediately apparent in relation to the completed work. [20, 24, 29]
Question 3: A customer submits a feature request on May 1st. The product team prioritizes it and adds it to the product backlog on May 5th. The development team starts working on it on May 15th and completes the work on May 25th. What is the Lead Time for this feature?
- 10 days
- 20 days
- 25 days (Correct answer)
- 14 days
Correct answer: 25 days
Lead Time measures the total time from the initial customer request to the final delivery of the completed work. In this scenario, the clock starts when the request was made on May 1st and ends when the work was completed on May 25th, resulting in a total Lead Time of 25 days. Cycle Time, in contrast, would be 10 days (from May 15th to May 25th). [2, 4, 5]
Question 4: Which of the following is an anti-pattern, or misuse, of the team velocity metric?
- Using the average velocity over the last three sprints to help forecast the next sprint's capacity.
- Comparing the velocity of Team A (30 points/sprint) to Team B (50 points/sprint) to determine which team is more productive. (Correct answer)
- Observing a downward trend in velocity as an indicator to investigate potential impediments.
- Using historical velocity to create a rough forecast for a multi-sprint release plan.
Correct answer: Comparing the velocity of Team A (30 points/sprint) to Team B (50 points/sprint) to determine which team is more productive.
Velocity is a team-specific metric based on its unique estimation scale and context. Because story points are relative and not standardized across teams, comparing the velocity of different teams is a meaningless and harmful practice that can lead to unhealthy competition and inaccurate conclusions. [14, 15]
Question 5: An engineering manager asks a team to start tracking 'lines of code written per developer per week' to measure productivity. Why is this considered a 'vanity metric' in an Agile context?
- It provides a direct measure of the value delivered to the customer.
- It does not necessarily correlate with positive outcomes and can encourage poor behavior, like writing inefficient code. (Correct answer)
- It is the most accurate way to compare the performance of senior and junior developers.
- It is difficult to track automatically and requires too much manual effort.
Correct answer: It does not necessarily correlate with positive outcomes and can encourage poor behavior, like writing inefficient code.
A vanity metric is one that can look good on the surface but doesn't provide actionable insight or correlate with value. [28, 31] Tracking lines of code encourages quantity over quality and has no direct link to customer value. An elegant, 50-line solution is far more valuable than a complex, 500-line one that achieves the same outcome. Focusing on this metric can lead to bloated codebases and discourage refactoring. [21, 25]
Question 6: A Scrum Master needs to communicate the team's progress to stakeholders who are primarily concerned with forecasting a release date. Which combination of information would be most valuable for this conversation?
- The team's task board and daily stand-up notes.
- A Release Burnup Chart and the team's average velocity. (Correct answer)
- Individual developer capacity and the number of tasks completed.
- The Sprint Burndown Chart and a list of all story points completed.
Correct answer: A Release Burnup Chart and the team's average velocity.
For long-term forecasting and stakeholder communication about releases, a Release Burnup Chart provides a high-level view of progress against the total scope. [26, 27] The team's average velocity provides the historical data on their rate of completion. Combining these two allows for a data-driven forecast of when the remaining work in the release backlog might be completed. [6, 10]
Agile Agile Metrics and Reporting Questions and Answers
An Agile Coach is reviewing a team's Cumulative Flow Diagram (CFD).
They notice that over the last several weeks, the band representing the 'Testing' phase is progressively widening, while the 'Done' band's slope is much flatter by comparison.
What is the most likely conclusion?
What Practice Test Geeks adds beyond an AI chat for Agile
An AI chatbot can quiz you, but it can't reproduce the exam conditions or keep your record. Here you get:
- A timed, full-length Agile mock exam — 120 questions in 180 minutes with a 70% pass mark, modeled on the official exam's question count and time limit, followed by a score report broken down by exam domain.
- A fixed Agile question bank: the same test every attempt, so your score is comparable from one try to the next instead of changing with every regenerated quiz.
- Progress saved on your device: completed tests, scores and missed questions stay in My Progress, so you can retake only what you got wrong.
- A printable Agile cheat sheet you can print or save as a PDF.
- Agile flashcards built from the same question bank.