How Can We Help?
Categories

# PMP Q #34- Burndown Chart-2

Q34. The release was planned in 4 iterations. What can be inferred from the Burndown chart below after the 3rd iteration? (select Two)

A. Work was added in the 3rd iteration.
B. The release is ahead of schedule.
C. The team has a consistent velocity.
D. The team was ahead of schedule in the second iteration.

The Burndown chart shows how much work remains to complete at a particular point. An axis shows the iteration number, and a Y-axis represents the work remaining. The blue line represents expected or planned work, whereas the orange colours primarily focusing on the actual work burned.

Here, options seem tricky and require more interpretation of these particular burn-down charts. So let’s go one by one.

The team added work in the 3rd iteration. So how would you see it? You see that in the second iteration,, you had less than 100 points of work left. And at the end of a 3rd iteration, you have more work left because the line went up.

So how is it possible that after finishing 2 iterations, when you finish the 3rd iteration, you have more work left than where you started? So it can only happen when your work gets expanded during the iteration. Work could get expanded based on various possibilities – One possibility is that new scope got added. Another case is that you end up resizing your remaining work. The 3rd possibility could be that more defects got recognised. So, something has happened which has expanded the work. More work was added, or a re-evaluation of work was done.

Here definitely, you are behind schedule. The team was ahead of schedule in the second iteration because, at the end of the second iteration, the remaining work was less than the anticipated work. You can see the actual line was below the expected line in the second iteration.

So if you have to choose with this particular graph for this specific question, options A (Work was added in the 3rd iteration)  and D (The team was ahead of schedule in the second iteration) are correct.

You can’t say that release is ahead of schedule and the team has a consistent velocity.