Exam PMI-ACP topic 1 question 98 discussion

D is the right answer. According Mike Griffiths , PMI-ACP Exam Prep, 1st Ed, Velocity is defined as the “measure of a team’s capacity for work per iteration.” This powerful metric allows the team to gauge how much work they will be able to do in future iterations, based on the amount of work they completed in past iterations. This provides a way to track and communicate what they have accomplished, anticipate what they will be able to accomplish in the future, and forecast when the project (or release) is likely to be done.

Historical Velocity: Utilizing the team's historical velocity allows for a data-driven approach to estimating future work. Velocity is the amount of work a team can complete in a given iteration, measured in story points or other units. By analyzing past performance, the scrum master can make more accurate predictions. Range of Features: Instead of committing to a specific set of features, providing a range offers flexibility and accounts for uncertainties. This approach acknowledges that exact predictions are challenging in agile projects and helps manage stakeholder expectations. Realistic Planning: Using historical data helps in setting realistic goals and avoids overcommitting. It ensures that the team can maintain a sustainable pace without compromising quality. Transparency: This method promotes transparency with stakeholders by showing how estimates are derived and the factors considered, fostering trust and understanding.

I would go with D. The questions says „provide an estimate“. A. „commit to..“ - nobody asks for a commitment B. „commitment will be provided“ - same as above C. „commit to“ - same as above D. „.. to calculate a range of features that CAN be delivered“ - this looks like an answer that will provide an ESTIMATE, not commitment

C IS RELATIVE D THERE IS NO PROOF THAT THERE ARE PAST SPRINTS

I think of 'D'. All options demands to commit except for 'D'. but the question doesn't ask for commitment but for estimate(relative).

A = wrong B = seems to be correct. Planning is ongoing, but C & D are about estimation, which can be conducted in the planning session. C = wrong, story points is a relative metric, so cannot provide an estimate of what can be delivered in a certain period. D = wrong. Cannot calculate a range of features for Project A based on a historical velocity of Project B. Can do that in the frame of the same project. What if the projects are completely different in technology, architecture, nature...

Vote D

Option D. In the Agile framework, the scrum master should use empirical data to make estimates rather than committing to specific features. The team's historical velocity is a useful metric to estimate what can be delivered in a given time frame. Based on the team's past performance, the scrum master can calculate a range of features that can be delivered in six months. This approach allows for flexibility and adaptability, which are important principles of Agile.

D is correct. Look at "Admirable" response to understand.

C and D make sense. But I'd go for D

D sure

D is correct

A is wrong. The scrum master cannot commit on behalf o the team B is wrong. Planning is ongoing - rolling wave. C is wrong. The team is busy doing the work. The Scrum Master should not interrupt the team to estimate. Also the team can't commit to a specific set of features. The PO must first prioritize. D is the best response. Use the historical info to come up with a range of what can be delivered within 6 months. Note, this is not a commitment but a forecast.

B - Correct - The development team needs to perform both C & D during Sprint Planning to provide an estimate. From The Scrum Guide: “Sprint Planning Topic Two: What can be Done this Sprint? Selecting how much can be completed within a Sprint may be challenging. However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts.”

I would go for C.

Ref : https://www.lucidchart.com/blog/how-to-estimate-sprint-velocity In order to estimate what work can be completed in the future, you need to measure the work that has previously been done. To get a good average measurement of work that has been done, plan to review the previous three sprints.