Burnup Charts

Correct Answer: The team is completing new work at the same rate as the scope is increasing.

In the context of Scrum, if the burnup (which shows the amount of work that has been completed) and scope lines (which represents the total amount of work) on a graph are parallel and rising, it implies that the team is adding and finishing new work at a consistent rate. What this means is, as new work is being added (increasing the scope), the team is also completing work at the same rate (increasing the burnup). The other options are incorrect because: 'The team is not completing any work' is not accurate as the burnup line is rising, which shows work is being completed. 'There are errors in the graph's plotting.' is incorrect, as there's no evidence presented suggesting errors in the graph. Lastly, 'The scope is decreasing alongside the progress.' is also wrong as the scope line is rising, not decreasing.

Correct Answer: Scope change or requirement addition likely happened during the sprint.

The burnup chart is a visual representation of the work done versus time. Frequent spikes above the trend line in the burnup chart indicate that the amount of work is increasing more than planned. From a ScrumMaster's perspective, this scenario suggests that there has likely been a scope change or requirement addition during the sprint, resulting in the team taking on more work. The other potential answers are not quite accurate. 'Over-performing and finishing more work than planned' would show as a steeper line but not necessarily spikes, 'incorrect data input' would affect the entire chart not just cause spikes, and 'team slacking during early part of sprints' would cause a flat line or decrease, not spikes.

Correct Answer: Work addition has ceased

A burnup chart is a graphical representation of work done versus time in Agile projects, often used in Scrum. A flattening of the 'total work' curve on a burnup chart typically signifies that no new work is being added to the Sprint backlog, hence indicating that work addition has ceased. This cessation could be due to reaching a point in the Sprint where the team decides not to add more work to focus on completing what is already committed. The other options are incorrect for the following reasons: 'Increased velocity by the team' is represented by a faster upward slope in the 'work completed' section, not a flattening of the 'total work' curve. 'Constant work completion rate' would affect the 'work completed' curve rather than the 'total work' curve. 'Scope reduction by the Product Owner' would actually cause the 'total work' curve to decrease, not just flatten, as tasks are removed from the Sprint backlog.