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:

Practice More Questions From: Module 3: Assessment (Graded)

Q:

The daily meeting meant to synchronize the development team and discover any impediments to work is known as the ________.

Q:

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?

Q:

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)?

Q:

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?

Q:

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 _____.

Q:

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?

Q:

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:

Q:

Clara and her development team are using a whiteboard task board to help them with their iteration burndown. On day twelve, three tasks were moved on the task board to the done column. These tasks were 9 hours, 2 hours, and 12 hours. Another task that took 5 hours was moved into the verify column. How can this information help Clara update the iteration burndown?

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments