試験PK0-005J トピック1 問題291 スレッド

A burndown chart tracks how much work remains over time in an iteration (or release). The most direct inputs are the remaining work and the work completed (often expressed as tasks, story points, or hours). Therefore, to obtain burndown data efficiently, the PM should analyze remaining and completed tasks. This aligns with CompTIA Project+ Agile metrics concepts, where burn charts are used to visualize progress and forecast completion based on work remaining versus time.
The other options are not primary burndown inputs. "Number of people available" affects capacity and can influence how fast work burns down, but it is not what the chart directly measures. "Cost variance" is an earned value / financial control concept (more predictive/traditional) and not what burndown charts are built from. "Number of issues registered" is useful for quality and risk/issue tracking but does not represent the work remaining in the sprint backlog unless issues are explicitly counted as backlog items-and even then, the chart is still fundamentally about remaining work, not raw issue counts.
So, for efficient burndown extraction, the PM should use the team's work tracking (sprint backlog/task board) to calculate remaining vs. completed tasks/work, which is exactly what the burndown visualizes.