Quiz 20 - Agile Performance

Your team's velocity has been 25 story points per iteration. There are 175 story points left. Each iteration is two weeks. How many weeks are left on the project? 7 14 20 21

14

Your agile team is working on a project and they have just completed the fourth sprint. In the first sprint they complete 24 story points. In the second sprint the team completed 32 story points. In the third sprint they completed only 16 story points. And in this last sprint the team complete 38 story points. What is the velocity for this agile team? 28 34 42 25

28 To find the velocity of the team you'll find the average story points completed for the four iterations. This would be 24+32+16+38 for a total number of 110 story points. Then you'll divide 110 by four, for an average of 27.5. The value is rounded up to 28 story points for their velocity. This means the team is expected to completed 28 story points per sprint on average.

Your team's velocity has been 30 story points per iteration. There are 700 story points left. Each iteration is three weeks. Approximately how many weeks are left on the project? 70 35 52 27

70

You're creating the charts for the latest software development project. Which of the following is true regarding burndown and burnup charts? Burnup charts highlight the work you've completed against the features A burnup chart shows the work remaining on a product A burndown chart shows the work remaining on a project A burnup chart contains a completed work line

A burndown chart shows the work remaining on a project

Your team is reaching the halfway mark on their latest project. A team can show its completed value with what tool? A project charter A product backlog burnup chart A sprint burndown chart Kanban Board

A product backlog burnup chart

You've been transitioning from traditional PM to agile methodology. Which of the following is not true regarding how agile teams measure results? Agile measures what the team delivers Agile measures what the team predicts it will deliver Agile teams limit their estimation to the next few weeks at the most There is evidence that the smaller the chunk of work, the more likely people are to deliver.

Agile measures what the team predicts it will deliver

You've been transitioning from traditional PM to agile methodology. Which of the following is not true regarding measurements in agile projects? Transitioning to agile means using different measurements Agile projects deliver finished work on a regular basis Agile projects deliver finished work when the project is done Project teams can use such data for improved forecasts and decision making

Agile projects deliver finished work when the project is done

Lisa is a project manager who needs to put together the burndown chart for a new project that is going to produce a new line of toys for Mr. Duncan's Toy Chest. Which of the following is not a benefit of a burndown chart? Plans for future events Communicates progress Reach work completion on time All of these are benefits of a burndown chart

All of these are benefits of a burndown chart A burndown chart communicates progress, tracks remaining work, takes corrective measures, plans for future events, and helps the team reach work completion on time.

Jean is a product owner responsible for the company's line of smart digital music devices. During an afternoon working session, she works with the team to review user stories in preparation for the next sprint. Her intention is to ensure the team knows enough about the stories and how large they are in relation to each other. What activity is Jean performing? Sprint planning Backlog refinement Sprint retrospective Daily stand-up

Backlog refinement Jean is in the process of refining the backlog in order to prepare for the next iteration. Engaging the team allows everyone to be aligned on the stories, relative to one another.

You're starting a new project management role with a well-known corporation. A few weeks into the project, you need to check on the project's scope. Which tool should you use? Kanban board Fulfilment chart Burndown chart Burnup chart

Burnup chart Burnup charts are a good way to track how much you've already accomplished and check on the project's scope.

A new project begins tomorrow and is planned to be several months long. When is the Sprint progress monitored? At the end of the sprint Once per week Daily Scrum At the end of each iteration

Daily Scrum

David is a Scrum master working closely with Rita, the product owner, to release the latest version of a digital music device. The team is currently in their fourth sprint. David joins the team near the coffee machine, where their Kanban board was placed, to meet for 15 minutes and talk through what each team member completed since yesterday, what they will complete, and any obstacles that may get in the way of their commitment. What activity is David and the team engaged in? Sprint planning Daily Scrum Sprint retrospective Backlog refinement

Daily Scrum

A project has already gone through several iterations, but there's work to be done. What is the purpose of monitoring the project's progress? To check-in with stakeholders To confirm work completed To provide a status report It forecasts the completion date of the project

It forecasts the completion date of the project

A project has already gone through several iterations, but there's work to be done. How often should the project progress be monitored? Once each month Once per Sprint Review Every two weeks During the Daily Scrum

Once per Sprint Review

A project has already gone through several iterations, but there's work to be done. When monitoring Sprint progress, which of the following is not a tool that you should use? Sprint burndown chart Progressive elaboration chart Sprint goal Kanban of user stories

Progressive elaboration chart When monitoring sprint progress, utilize a sprint board for transparency. This might be a sprint burndown chart, a sprint goal, or a Kanban of user stories.

You're putting together a chart for your team's next project. What is the feature burnup/burndown charts may show? Revised project goals The project plan That requirements grew during the project The project or phase end

That requirements grew during the project

You're putting together the burndown chart for your team's next project. What is on the X-axis? The number of sprints The ideal timeline The work to be completed The start and endpoints

The number of sprints

A project has already gone through several iterations, but there's work to be done. Who determines the progress of the project? The product owner Development team members The stakeholders Scrum Master

The product owner The Product Owner is responsible for monitoring the progress of the project. He or she determines the amount of work remaining.

You're putting together the burnup chart for your team's next project. What is on the Y-axis? The number of sprints The ideal timeline The work to be completed The start and endpoints

The work to be completed

You're about to begin calculating your team's velocity. Which of the following is not true regarding team velocity? Velocity is the measure of a team's capacity for work per iteration Velocity continues to rise over time Velocity tends to plateau Velocity is measured in the same unit that the team estimates the work

Velocity continues to rise over time