PMP Practice Question: People — Hybrid, Medium
Your hybrid project team consists of five co-located members following agile practices and three remote members managing waterfall-based procurement and vendor contracts. The remote members rarely participate in daily standups, citing time zone differences and claiming the meetings aren't relevant to their work. Co-located team members complain they're unaware of vendor delays until major issues arise. The remote members feel excluded from project celebrations and recognition. What strategy would best build cohesion across this distributed hybrid team?
Study this topic
- 📖Managing Virtual and Remote Project Teams: A PMP Perspective
Learn proven strategies for leading distributed teams effectively, from communication protocols to trust-building, aligned with PMBOK 8th Edition principles.
- 📖Emotional Intelligence for the PMP Exam 2026: Master the People Domain
Emotional intelligence accounts for crucial skills tested across the People domain (33%) in the 2026 PMP exam. Learn how EI appears in scenarios, key competencies, and proven study strategies.
- 🗂️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?