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
Servant Leadership PMP Exam Scenarios ExplainedMaster servant leadership concepts for the PMP exam with practical scenarios, real-world examples, and detailed explanat…
More People Questions
View all →You are leading an agile project with a newly formed team. During the first two sprints, you notice that one team member, Sarah, consistently remains quiet during daily stand-ups and retrospectives. When she does speak, her contributions are valuable, but she appears uncomfortable in group settings. Other team members have started making decisions without her input. The team's velocity is acceptable, but you sense Sarah's potential is not being fully utilized. What should you do first to address this situation?
During sprint planning, two developers on your agile team disagree strongly about the technical approach for implementing a user story. The discussion is becoming heated and the team is running out of time to complete the planning session. Both approaches appear technically viable. What should you do as the servant leader?
You are facilitating a sprint planning meeting for your agile team. One team member consistently volunteers to take on all the high-priority user stories, while other team members are hesitant to commit to work. This pattern has continued for several sprints, and you are concerned about team balance and knowledge sharing. What is the best approach to address this?
