Exam PMP topic 1 question 188 discussion

A. Backlog is priorized considering VALUE and RISK, nothing related to velocity is considered for that. so A is FULLY WRONG. B. Adjust the Scope will reduce the Work In Progress, as KANBAN, it will ensure the team keep focused correctly and keep velocity and timeline. HAVE BIG SENSE C. New Velocity will be checked by experience and testing, how many story points will be the new team able to accomplish per iteration? let´s check how it´s going on the following iterations. so no sense reevaluate as first option, the most importance is keep the team focus on work. D. Less sense than B for me.for sure Projec Schedule will suffer modifications but before change it PM will need to check for solutions like hire another team member, reduce the project scope, etc.

if lost resource can not keep the same velocity, and check pb priority cos new requirements

A doesn't make sense, we don't reevaluate priority just because someone has left!

The answer makes no sense, without backlog priority, how can the scope be defined or even adjust??

One resource left, and topic backlog (requirement is uncovered), then time to finetune the backlog by having prioritization with product owner, which impact to velocity (how many backlogs can be finished in 1 iteration)

The project manager should **reevaluate the backlog priority with the product owner** since the velocity has been impacted (Option A). The loss of resources and the addition of new requirements will likely affect the team's velocity, or the amount of work the team can handle in a given iteration. By reevaluating the backlog priority with the product owner, the project manager can ensure that the most important tasks are still being addressed first, despite the changes. This approach maintains the focus on delivering value and meeting the project goals.

Debe ser A, en agil más que cronograma se maneja backlog, eso descarta la opción B y las otras opciones no tienen sentido.

A. Reevaluate the backlog priority with the product owner since the velocity has been impacted: This approach makes sense because with reduced capacity (due to the loss of a resource) and additional requirements, it's important to prioritize which items in the backlog should be tackled next. The product owner is responsible for this prioritization.

There is a loss of resource so the velocity of team will be impacted then the schedule.

I don't like A since the backlog priority will not change because someone leaves the company/ team. It's like "Oh, Fredy, the developer, was fired... now this feature is less relevant to the product/company" c'mon... The only thing I is that the ITEMS inserted from the backlog into the sprint will be evaluated according to the new team's expertise and velocity...

A. Reevaluate the backlog priority with the product owner since the velocity has been impacted - in agile projects, time and budget are fixed while the scope is flexible. Given the reduced number of resources, the project owner might want to reconsider which features he would like to have built.

A. Reevaluate the backlog priority with the product owner since the velocity has been impacted

A, As there are new requirements, a project backlog reevaluation is needed

D should be correct. 1. new requirements, it is required to re-priority based on business value not team's velocity so A is out 2 once the sprint is started, scope cannot be changed, it is committed by product owner and team. but the team velocity is not dropped because of reduced resource. Agile is time boxing and based on team velocity, the incompleted user stories should put back to product backlog and re-prioritized for subsequent sprint, so B is out 3 Agile length of iteration is fixed and should not be changed due to change in velocity unless it is float based but this point is not mentioned in the question so C is out 4. In Agile, scope is the user stories, now more requirements so user stories are increased but resource is reduced , we can only adjust / increase the no. of iterations so I selected D

B is maybe the worst answer not sure why it shows as correct. I like A the most but also think D is good. I think you would want to do A before updating the schedule as the velocity has changed and the new requirements may have a higher priority so the backlog should be reviewed. D takes into account the velocity reduction but not the new requirements.

In reality, I will choose D.

Going for option C, as the velocity should be the first metric to define before reviewing or making changes to scope or schedule.