PMP Practice Question: People — Predictive, Hard
You are managing a large infrastructure project with a 24-month timeline using a predictive approach. During the execution phase, your technical lead, who has been with the project since initiation and possesses critical knowledge about legacy system integrations, submits their resignation with a two-week notice. The project is currently 40% complete, and the integration work is scheduled to begin in six weeks. Your sponsor is concerned about the impact on the project schedule and is pressuring you to immediately hire a replacement at a higher salary to retain institutional knowledge. What should be your FIRST action as the project manager?
Study this topic
- 📖Risk Management PMP Exam: Complete Strategic Guide
Master risk management for the PMP exam with strategic insights on identification, assessment, and response planning aligned with PMBOK 8 principles.
- 📖Navigating Regulatory Compliance in Project Management
Master regulatory compliance strategies for the PMP exam. Learn how to navigate legal requirements, industry standards, and governance frameworks across project lifecycles.
- 🗂️Flashcards: Leadership, Team & Stakeholder Models
15 cards · quick recall practice
More People Questions
View all →You are leading a manufacturing facility construction project following a predictive lifecycle. The project team consists of 15 members, including contractors and internal staff. After three months of work, you receive feedback from several team members that the weekly status meetings are too long and not productive. Team members feel they spend too much time listening to updates irrelevant to their work. The meetings currently last 90 minutes and cover all work packages. What is the best approach to address this concern?
A cross-functional agile team is preparing for their next sprint. During sprint planning, the QA specialist expresses concern that the team has been committing to user stories without adequately considering testing effort. She feels that her input is often sought too late in the process, after developers have already estimated and committed to stories. This has resulted in quality issues and testing becoming a bottleneck in the last two sprints. The team wants to improve but is unsure how to better integrate QA perspective earlier. What should the team do?
Your organization is piloting agile practices within traditionally predictive portfolios. You're leading a hybrid project with a co-located agile team and distributed predictive workstreams across three continents. After four months, you notice the agile team has strong cohesion and high performance, but the distributed predictive teams report feeling disconnected and undervalued. Several key resources from the predictive workstreams have requested transfers, citing lack of engagement. Executive stakeholders are questioning whether the hybrid approach is sustainable. What is the MOST effective way to address this disparity?