PMP practice question 26 of 35

Solution Development Case Study A project manager was assigned to a project to deliver a corporate IT security solution within a 12-month timeline…

Full set: 230 questions

Domain People

Solution Development Case Study A project manager was assigned to a project to deliver a corporate IT security solution within a 12-month timeline and a budget of $2.5 million USD. To help ensure project success, the project manager established a governance framework featuring a steering committee of senior executives from relevant functional areas. The project manager conducted a detailed stakeholder analysis using a power/interest grid to prioritize engagement strategies and developed a quality management plan incorporating quality metrics, control charts, and acceptance criteria for each deliverable. Project work required specialized security testing tools, so the project manager collaborated with the procurement team to develop vendor selection criteria and contract terms. The team used an agile approach to develop software coupled with a predictive approach to manage other aspects of the project. The project manager implemented a configuration management system to track changes and maintain version control of project information. During execution, the project manager coordinated between various teams, including software development, cybersecurity, quality assurance, compliance, and customer experience, each with its own methodologies and tools. To address integration challenges, the project manager developed a comprehensive project management plan, with a detailed work breakdown structure (WBS), a master schedule using the critical path method, and earned value management (EVM). The team helped the project manager create and tailor a risk management plan focusing on integration points between teams, along with a communications matrix to ensure consistent cross-functional meetings with stakeholders. During the project, challenges such as resource conflicts, scope creep, and technical integration issues arose. The project manager addressed these challenges using a resource optimization plan, a formal change control process, and technical working groups. The project was delivered within budget and was concluded 2 months later than the original baseline due to an approved change. Stakeholders accepted the delay due to additional security features added during execution. The final product met all quality metrics and received positive feedback from beta customers. The project provided valuable lessons on early stakeholder alignment, integrated change control, cross-functional communication, and regular risk reassessment, which informed good practices for future projects within the organization. What should the project manager do to facilitate and improve communications between the multiple teams within this project? (Refer to the Solution Development Case Study exhibit.)
Answer options
A: Begin weekly cross-functional meetings. Correct answer
B: Distribute bi-weekly status reports.
C: Start daily coordination meetings.
D: Conduct monthly stakeholder reviews.
Correct Answer:
A. Begin weekly cross-functional meetings.
Explanation

In a hybrid project involving multiple diverse teams (software development, cybersecurity, QA, compliance, and customer experience), interactive communication is essential to address integration challenges. The case study explicitly highlights the creation of a communications matrix to ensure "consistent cross-functional meetings." Weekly cross-functional meetings provide a regular, interactive forum for representatives from each team to align on integration points, resolve dependencies, and share updates. This frequency strikes the right balance, fostering collaboration and shared understanding across multi-disciplinary teams without imposing the excessive administrative burden that daily cross-departmental meetings would create. This aligns with PMI's emphasis on tailoring interactive communication methods to project complexity.

Why Incorrect

B. Distribute bi-weekly status reports. Status reports are push communication and lack the interactive, two-way dialogue necessary to actively resolve complex integration dependencies between diverse teams.
C. Start daily coordination meetings. While daily standups suit individual agile teams, mandating daily cross-functional meetings across all distinct departments (compliance, QA, CX) is generally inefficient and overly burdensome.
D. Conduct monthly stakeholder reviews. Monthly reviews are too infrequent to effectively manage, coordinate, and resolve the dynamic, ongoing integration challenges occurring between active project teams.

References

1. Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 10.1.2.5 (Communication Methods), p. 374. (Highlights interactive communication as the most efficient way to ensure common understanding).

2. Project Management Institute (PMI). PMBOK® Guide – Seventh Edition. Section 2.1 (Stakeholder Performance Domain), pp. 11-14. (Discusses tailoring communication and engagement strategies to foster cross-functional alignment).

3. Project Management Institute (PMI). Agile Practice Guide. Section 5.2.2 (Cross-Functional Teams), p. 40. (Emphasizes the need for regular, sustainable coordination mechanisms between diverse functional groups in hybrid/agile environments).

Scroll to Top