Week 16 - 17 Burndown Charts

A burndown chart which marks the days worked on the x-axis, and the total effort on the y-axis and represent a single sprint is known as

• burndown chart

• an iteration burndown chart

• chart burndown iteration

• an chart burndown iteration

Sam and her development team are working on a project. They estimate all the user stories of the project add up to 100 story points. In their first sprint, they finish 15 story points, and they mark this change on their release burndown chart. However, the team removed a feature at the beginning of Sprint 2 from the project, resulting in the removal of 5 story points. How could this be represented in an adjustable floor?

• Five story points would be removed from the bottom of the bar representing Sprint 2, so the bar seems to start above the x-axis.

• Five story points would be added to the bottom of the bar representing Sprint 2, so the bar starts below the x-axis.

• Five story points would be added to the top of the bar representing Sprint 2.

• Five story points would be removed from the top of the bar representing Sprint 2.

Thomas and his development team finished enough user stories in his last sprint to add up to 12 story points. The sprint before that, Thomas and his team finished 15 story points, which they had expected to finish again. What was the actual velocity of their most recent sprint?

• 15 story points / sprint

• 12 story points / sprint

• 13 story points / sprint

• 14.5 story points / sprint

Lola takes a look at the release burndown chart her team has created for their project. She knows for a fact that her team has been working hard on a number of tasks. However, she sees that for the past four sprints, the bars on the release burndown chart have stayed the same – no story points have been finished. What is likely happening?

• No one has updated the release burndown chart.

• The team is not working.

• The team should count hours instead of story points.

• Too many new user stories are being started before old ones are completed.

When more tasks are added to a sprint than are completed or removed, this can increase in work hours or story points increasing over time instead of decreasing. This is an example of

• burning up

• burning down

• burning change

• burning across

Previous velocities can be used as an estimate for how much work will be done in the next sprint. What potential factors may influence the outcome of the actual velocity of the sprint (select two that apply)?

• Bugs may occur which affect how long it takes to finish tasks.

• A previous velocity may affect this velocity.

• Actual velocities should always be stable.

• The team may experience a learning curve and accomplish this sprint much more quickly.

The name for two processes that occur when burndowns do not stay on target are _____ and ______.

• burning across / burning off.

• burning up / burning across.

• burning up / burning down.

• burning across / burning down.

Release burndown charts can help a development team visualize (Choose two that apply)

• defects in a product

• how many sprints it will take to finish a project

• what metrics to use in a project to monitor progress

• the work completed and left to finish