Free PMI PMP Practice Test & Real Exam Questions

A product owner who possesses a strong technical background has been actively involved with the project team for several years. The product owner has been quite vocal about the expected duration of the work. As a result, the project team has ceased providing development estimates to avoid causing any dissatisfaction with the product owner.
What should the project manager do?

The project manager is leading a project to develop a new product. A representative from the legal team approaches the project team requesting the product go through a legal review before entering the market. This review would lengthen the schedule and would cause the product to miss an important launch window.
What should the project manager do?

During project execution, the development team creates work groups to develop project deliverables. When reporting progress to the project manager, the team struggles to provide a complete picture of overall progress.
What should the project manager do first?

Acustomer has agreed in a contract that interactive displays will be delivered to 14 locations by the end of the year. The contract also states that only software approved by the customer will be installed on these displays. The customer has not approved this new software because they lack the resources to test and approve it.
What should the project manager do?

Health Records Modernization at Hospital Case Study
A project manager led a health records modernization project at a hospital with a project budget of $US5 million and an 18-month timeline. The project involved multiple stakeholder groups including medical, administrative, and IT staff; board members; patients; insurance companies; external vendors; regulatory bodies; and union representatives.
Stakeholder management was complex and a major undertaking for the project manager, but it was critical to achieve a positive project outcome. When the project started, the project manager conducted stakeholder analysis, using the information to create both a power/interest and an influence/impact matrix. The analysis showed that while the hospital board members and regulatory bodies had high power but moderate interest, the medical staff (doctors and nurses) had both high influence and high impact on the project. Administrative staff showed high interest but lower power, while patients and insurance companies had moderate interest and varying levels of influence. Based on the analysis, the project manager created a stakeholder engagement strategy that documented expectations, communication preferences, and influence levels in a stakeholder register. The project manager also made a RACI (responsible, accountable, consulted, informed) chart to show roles and responsibilities; and created communication channels and frequency for each stakeholder group, an issue escalation system, and a feedback system for continuous stakeholder input.
To execute the modernization process of health records, the project manager realized that medical staff members would need to change their daily workflows. To facilitate change management for these stakeholders, the project manager created a clinical advisory committee, appointed department-specific
"champions," created focus groups for requirements gathering, started a training program, and developed key performance indicators (KPIs) to measure satisfaction.
During project execution, several challenges emerged. The doctors expressed concerns about the system's impact on patient care, the nurses' union raised workload concerns, the IT department faced resource constraints, the insurance companies requested additional features, and the administrative staff worried about data security. The project manager responded to these challenges by increasing the frequency of stakeholder meetings, implementing a change management program, creating a beta system for stakeholder testing, developing contingency plans for various stakeholder scenarios, and establishing an issue resolution process.
Despite these mitigation efforts, the medical staff required additional training, leading to a change request for a 2-month extension and a 10% budget increase. The board of directors approved this to help ensure high adoption and satisfaction rates among staff members. The project helped establish new good practices in future programs for stakeholder management in the organization's project management office (PMO). The documented lessons learned became a reference for future projects of similar scope and complexity.
How should the project manager handle the IT department's resource constraints while at the same time maintaining project momentum?
(Refer to the Health Records Modernization at Hospital Case Study exhibit.)

A new, highly innovative project just started and the customer is already complaining that the software company is not delivering as agreed. What should the project manager have done before starting the project?

The client believes that a newly assigned team does not fit well and prefers the previous team, whom the client already knows. What should the project manager do?

A project manager is comparing actual revenue with projected revenue to determine necessary changes for increasing revenue. The revenue is influenced by the volume of transactions and data extractions.

What actions should the project manager take to reduce the gap between projected and actual revenue? (Refer to the Line Chart)

During a review session, the team reports that the daily coordination meetings have been unproductive. The team asks the scrum master to implement a standard format for the daily coordination meetings.
What should the scrum master do?

Health Records Modernization at Hospital Case Study
A project manager led a health records modernization project at a hospital with a project budget of $US5 million and an 18-month timeline. The project involved multiple stakeholder groups including medical, administrative, and IT staff; board members; patients; insurance companies; external vendors; regulatory bodies; and union representatives.
Stakeholder management was complex and a major undertaking for the project manager, but it was critical to achieve a positive project outcome. When the project started, the project manager conducted stakeholder analysis, using the information to create both a power/interest and an influence/impact matrix. The analysis showed that while the hospital board members and regulatory bodies had high power but moderate interest, the medical staff (doctors and nurses) had both high influence and high impact on the project. Administrative staff showed high interest but lower power, while patients and insurance companies had moderate interest and varying levels of influence. Based on the analysis, the project manager created a stakeholder engagement strategy that documented expectations, communication preferences, and influence levels in a stakeholder register. The project manager also made a RACI (responsible, accountable, consulted, informed) chart to show roles and responsibilities; and created communication channels and frequency for each stakeholder group, an issue escalation system, and a feedback system for continuous stakeholder input.
To execute the modernization process of health records, the project manager realized that medical staff members would need to change their daily workflows. To facilitate change management for these stakeholders, the project manager created a clinical advisory committee, appointed department-specific
"champions," created focus groups for requirements gathering, started a training program, and developed key performance indicators (KPIs) to measure satisfaction.
During project execution, several challenges emerged. The doctors expressed concerns about the system's impact on patient care, the nurses' union raised workload concerns, the IT department faced resource constraints, the insurance companies requested additional features, and the administrative staff worried about data security. The project manager responded to these challenges by increasing the frequency of stakeholder meetings, implementing a change management program, creating a beta system for stakeholder testing, developing contingency plans for various stakeholder scenarios, and establishing an issue resolution process.
Despite these mitigation efforts, the medical staff required additional training, leading to a change request for a 2-month extension and a 10% budget increase. The board of directors approved this to help ensure high adoption and satisfaction rates among staff members. The project helped establish new good practices in future programs for stakeholder management in the organization's project management office (PMO). The documented lessons learned became a reference for future projects of similar scope and complexity.
A project to modernize a hospital's records has a large and diverse stakeholder population. As stakeholders request changes, the project manager is aware that some will cause a negative impact to the project timeline and finances.
What should the project manager do?
(Refer to the Health Records Modernization at Hospital Case Study exhibit.)