Exam PMP topic 1 question 18 discussion

Answer is A. SPI = EV/ PV. EV(US$500,000) / PV(US$550,000) = 0.9 So current SPI is < 1. It means behind schedule.

Project is behind schedule so this question considers techniques to compress project schedule which is either Fast Tracking (increases risks) or Crashing (increases cost). D could be an option, however timeline adjustment must go through Change Control. Another point, the question mentions "critical project", it might (not explicitly though) mean a tight deadline. There is no mentioning or factors not to use Fast Track.

SPI less then 1 so its behind scheduale .

In this scenario SV= EV-PV=(50,000) a negative schedule variance. in this situation speeding up the project to avoid delays will be the best option

500/550 <1 so that is behind the schedule >> fast track to back to schedule

Option A

Voting for Fast Tracking. If the project is almost completed, and there is a schedule variance (earned value is less than planned value) at the end of Sprint 3, fast tracking becomes a suitable option to expedite the remaining tasks and bring the project back on track Option D (Adjust the project timeline) could still be valid in certain situations, especially if the project is not close to completion or if fast tracking is not feasible due to resource constraints or risks associated with overlapping tasks. However, since the project is almost over, adjusting the timeline may not provide sufficient time to recover from the schedule variance.

D. Adjusting the project timeline is the most suitable action. Since the earned value (EV) is less than the planned value (PV), it means that the project is behind schedule at the end of sprint three. In this case, the project manager should consider adjusting the project timeline by extending the remaining sprint(s) or adding additional sprints to account for the work that is behind schedule. This will help ensure that the project can be completed within the adjusted timeline.

A. Fast track the project

Fast tracking

I'm wrong. It's supposed to be fast track. We can fast track projects in software agile. Because the impact of the risk is not that high in software environments. It's easily fixed.

https://www.pmi.org/learning/library/scheduling-resource-leveling-project-progression-8006 D. Level your resources. Fast tracking has a lot of risks. It's a critical software development

A is correct

A is the correct answer, SPI < 1

In this situation, the best option would likely be D. Adjust the project timeline. This could involve re-estimating the remaining tasks, potentially extending the timeline for the final sprint, or adjusting the schedule for specific tasks. Option A, fast-tracking the project, could lead to increased risk and might not be feasible depending on the nature of the work remaining. Option B, adjusting the budget, doesn't directly address the issue, which is a schedule variance, not a cost variance. Option C, introducing a float, refers to schedule flexibility that is typically built in at the planning stage and might not be applicable or sufficient in this situation.

ChatGpt says Option B

Answer A. I don't think it's best practice to keep adjusting the baseline every time there is a delay on a project.