PMP Practice Question: People — Predictive, Hard
You are leading a government IT system integration project using a predictive lifecycle with a dedicated team of 25 members. Six months into the 24-month project, organizational metrics show your team's velocity is 15% below the planned baseline, though quality metrics remain acceptable. During a retrospective session, team members confidentially share that the project's strict command-and-control governance structure, mandatory daily status emails, and your directive leadership style are demotivating them. Several high performers hint they are exploring other opportunities. However, the government client has explicitly required this governance approach due to previous project failures, and your sponsor strongly supports maintaining tight controls. What is the BEST course of action?
Study this topic
- 📖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.
- 📖Stakeholder Engagement Strategies for Project Success
Master proven stakeholder engagement techniques for the PMP exam and real-world projects. Learn assessment frameworks, communication tactics, and conflict resolution strategies aligned with PMBOK 8.
- 🗂️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?