You are managing a multinational IT implementation project with team members across five countries spanning four time zones. The project follows a traditional waterfall approach with phase gates. Your project management office (PMO) requires weekly status meetings with all core team members present. After three months, you notice declining participation, with team members frequently joining late, multitasking during meetings, or sending delegates. Survey feedback reveals that team members find the meetings unproductive and poorly timed for their time zones. However, the PMO director insists the meeting format is a governance requirement and cannot be changed. Your sponsor is concerned about team engagement scores dropping from 85% to 62%. What is the BEST way to address this situation?
Study this topic
PMP Certification Salary Increase: How Much More Will You Earn?Discover the real financial impact of PMP certification with current salary data, industry breakdowns, and career advanc…
More People Questions
View all →During sprint planning, your development team commits to 45 story points based on historical velocity. However, your product owner insists they must complete 60 story points this sprint because of a commitment made to a key stakeholder. The product owner argues that the team 'just needs to work harder' and threatens to escalate to senior management if the team doesn't comply. The team looks to you, the Scrum Master, for guidance. How should you respond?
Your agile team has a new member, Sarah, who joined two weeks ago. Sarah has strong technical skills but comes from a traditional waterfall background. During the current sprint, you notice Sarah working in isolation, not updating the task board, and not asking for help despite her story being blocked. In the standup, she reports 'everything is fine' even though you can see she's struggling. Other team members have offered help, but she politely declines. What is the most effective way to help Sarah adapt to the agile team environment?
During sprint planning, your cross-functional agile team is struggling with significant disagreement about story point estimates. Your senior architect insists a complex integration story is 5 points based on his experience, while two developers argue it's at least 13 points because they'll be doing the actual implementation and foresee multiple technical challenges. The product owner is pressuring for the lower estimate to fit more stories in the sprint. The tension is escalating, with team members becoming defensive and the meeting has already run 30 minutes over. How should you handle this situation?
