PMP Practice Question: People — Agile, Medium
Your agile team has consistently met sprint commitments for the past four iterations, and team morale appears high. However, during a one-on-one conversation, a junior developer confides that they feel overwhelmed and have been working 50-60 hours per week to complete their tasks. They haven't mentioned this in retrospectives because they don't want to let the team down. When you review the sprint metrics, you notice this developer's velocity is significantly higher than other team members. What should you do?
Study this topic
- 📖Coaching and Mentoring in Agile Teams: A PMP Perspective
Learn how servant leadership, coaching, and mentoring drive agile team performance. Essential knowledge for PMP candidates preparing for the 2026 exam's expanded agile focus.
- 📖PMBOK 8 Performance Domains Explained for 2026 PMP Exam
Master the 8 performance domains in PMBOK 7th Edition that form the foundation of your 2026 PMP exam. Learn how the shift from process groups to performance domains changes your study approach.
- 🗂️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?
