Exam PMP All Questions

View all questions & answers for the PMP exam

Exam PMP topic 1 question 648 discussion

Actual exam question from PMI's PMP

Question #: 648
Topic #: 1

An organization is transitioning to agile delivery, and a new team has been assembled. A project is not going well because the variation of the team velocity is very high and every sprint delivers less than committed. A new project lead with a strong technical background has been assigned to the project.

What should the project lead do?

A. Ask that estimations be provided only by senior developers.
B. Recommend a different estimation method in the retrospective.
C. Allocate more time for estimation in the sprint planning.
D. Review and update the estimations in the daily standup.

Show Suggested Answer

Suggested Answer: B 🗳️

by longge at Nov. 21, 2022, 12:42 p.m.

Comments

Submit Cancel

Abdelmonm

11 months, 3 weeks ago

Selected Answer: B

In the retrospective, the team can discuss and experiment with different estimation methods to identify one that better aligns with their capabilities and improves the accuracy of their predictions. This collaborative approach allows the team to reflect on their performance, identify challenges, and iteratively improve their estimation process.

upvoted 2 times

...

Deeski

1 year, 1 month ago

Selected Answer: B

The retrospective allows issues identified to be discussed in a timely fashion along with ideas for improvement by the agile team.

upvoted 1 times

...

Only12go

1 year, 3 months ago

Selected Answer: B

In a situation where a new team in an organization transitioning to agile delivery is experiencing high variation in team velocity and consistently delivering less than committed in each sprint, the project lead with a strong technical background should take actions to address this issue. The most appropriate action is: B. Recommend a different estimation method in the retrospective.

upvoted 2 times

...

victory108

1 year, 3 months ago

Selected Answer: B

B. Recommend a different estimation method in the retrospective

upvoted 1 times

...

Alizade

1 year, 4 months ago

Selected Answer: B

The correct answer is: B. Recommend a different estimation method in the retrospective.

upvoted 1 times

...

Aish_

1 year, 5 months ago

Selected Answer: C

Voting for C. Instead of recommending a specific solution outright, the project manager should encourage the team to identify and discuss the challenges they are facing with estimations. Together, they can explore different estimation techniques or practices to find the best fit for their team. Allowing more time for estimation might not be the best solution if the issue lies in the accuracy of the estimations themselves. Instead, the project manager should work with the team to analyze the reasons for the high variation in team velocity and identify potential improvement areas.

upvoted 2 times

Aish_

1 year, 5 months ago

I would take back previous comment and rather change my choice to B. As the new lead has a strong technical background, he would be able to give a good recommendation and they could discuss it during retrospective.

upvoted 2 times

...

AbbasTaki

1 year, 7 months ago

Selected Answer: B

The project lead should recommend a different estimation method in the retrospective because the current method is not working. The team is consistently underestimating the complexity of the work, which is leading to a high variation in velocity and less than committed delivery every sprint. In retrospective, the team discusses what went right, wrong and how to improve things.

upvoted 2 times

...

kevzzz

1 year, 7 months ago

Selected Answer: C

A Team’s Velocity improves naturally, based on their understanding of the project, technology and implementation. Take more time estimating the better the understanding will be.

upvoted 2 times

...

Thirukj

1 year, 7 months ago

Selected Answer: C

C is right

upvoted 1 times

...

Yuuns

1 year, 10 months ago

Estimation is not done in retrospective. Only during sprint planning.

upvoted 3 times

cwilson91

1 year, 6 months ago

Sure, but the retrospective is used as self reflection on how to improve. I can see the timeline being the following: 1. Complete the current sprint 2. Hold a sprint review meeting (and probably talk about the goals that weren't accomplished) 3. Hold a retrospective meeting (and suggest a better estimating technique) 4. Perform Sprint Planning (to implement the better estimating technique discussed in the retrospective meeting) We cant just wait around for the teams velocity to improve, we should be estimating our time to account for the velocity variation. Answer is B imo. (In all honestly, since we now have a highly technical project lead, we'd probably need LESS time now to perform our estimates. Making me think even more, that C is the wrong answer.)

upvoted 1 times

...