A team's velocity for the last four sprints was 18, 22, 20, and 24 story points. The team will have two members on training for two days during the next sprint. What is the best estimate for the team's capacity?

21 points, the average of the last four sprints

19 points, slightly below the average to account for the training

24 points, the maximum of the last four sprints

18 points, the minimum of the last four sprints

A team's velocity over the last five sprints was 24, 28, 26, 25, and 27 story points. The product owner wants to know how many story points the team can likely commit to in the next sprint. What should the team use as the basis for this forecast?

The velocity from the most recent sprint of 27 points

The minimum velocity of 24 points

The average velocity of 26 points

The maximum velocity of 28 points

A team's velocity chart shows values of 30, 32, 31, 33, and 32 over five sprints. In the next sprint, the team will have a new junior developer joining. What is the best way to use the velocity chart for planning?

Commit to 32 points, the average, because the chart shows stability.

Commit to 35 points, assuming the new developer will increase capacity.

Ignore the velocity chart and commit based on the product owner's priorities.

Commit to 28 points, slightly below the average, to account for onboarding and mentoring.

A team has been tracking velocity for six sprints. The values are 20, 22, 21, 23, 22, and 24. The team is planning the next sprint and wants to use the velocity chart to forecast. What is the most reliable forecast?

22 points, the average of the last six sprints

24 points, the highest velocity

What is the primary purpose of maintaining a velocity chart that spans several sprints?

To provide a historical record of the team's completed work for planning purposes

To track the amount of time each team member spends on tasks

To show the number of defects found in each sprint

To display the team's sprint goal achievement percentage

GitLabCertified Agile Portfolio Management Associate

Domain 5Objective 1

Track Team Velocity GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE Practice Questions (Page 4)

Part of the Team Velocity and Tracking domain, which makes up ~26% of our current practice bank.

27questions here

6free pages

7concepts

Questions 16–20

16application · medium
A team's velocity for the last four sprints was 18, 22, 20, and 24 story points. The team will have two members on training for two days during the next sprint. What is the best estimate for the team's capacity?
Select an answer first
17application · easy
A team's velocity over the last five sprints was 24, 28, 26, 25, and 27 story points. The product owner wants to know how many story points the team can likely commit to in the next sprint. What should the team use as the basis for this forecast?
Select an answer first
18application · medium
A team's velocity chart shows values of 30, 32, 31, 33, and 32 over five sprints. In the next sprint, the team will have a new junior developer joining. What is the best way to use the velocity chart for planning?
Select an answer first
19application · easy
A team has been tracking velocity for six sprints. The values are 20, 22, 21, 23, 22, and 24. The team is planning the next sprint and wants to use the velocity chart to forecast. What is the most reliable forecast?
Select an answer first
20foundation · easy
What is the primary purpose of maintaining a velocity chart that spans several sprints?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE” is a trademark of its owner, used for identification only.