PMP Exam Questions

Total 377 Questions

Last Updated Exam : 16-Dec-2024

Topic 1: Exam Pool A

An agile project is running activities to define the minimum viable product (MVP) During the session, the project manager identifies some mandatory regulations but there is no consensus to include these regulations in the MVP because it may extend the duration of the project.

What should the project manager do?


A.

Train the team on the new regulations as requested by management


B.

Get commitment from the team to include all of the required regulations


C.

Ask the project sponsor to add more time to the project


D.

Share with participants the need to focus only on product functionality





B.
  

Get commitment from the team to include all of the required regulations



Explanation

According to the Project Management Professional (PMP) Reference Materials, the project manager should get commitment from the team to include all of the required regulations in the MVP when there is no consensus to do so. This is because the MVP is the version of the product that delivers the most value to the customer while meeting the minimum requirements and constraints1. If the project manager identifies some mandatory regulations that are essential for the product to be viable, compliant, and safe, then they should be included in the MVP, regardless of the impact on the project duration2. The project manager should explain the importance and rationale of the regulations to the team and stakeholders, and seek their agreement and support to incorporate them in the MVP3. The other options, A, C, and D, are not appropriate actions for the project manager to take. Training the team on the new regulations as requested by management may not resolve the lack of consensus or commitment from the team and stakeholders, and may delay the MVP definition process. Asking the project sponsor to add more time to the project may not be feasible or necessary, and may not address the root cause of the disagreement. Sharing with participants the need to focus only on product functionality may ignore the regulatory requirements and risks, and may compromise the quality and value of the product.

References:

  1. Agile Practice Guide, Chapter 4.1.2, "Minimum Viable Product".
  2. How to Define a Minimum Viable Product (MVP) - ProjectManager.com, Section "What Is a Minimum Viable Product?".
  3. How to use Consensus Decision-Making for Project Management, Section "The 6 Stages of Consensus Decision-Making".

A vendor informed the project manager that a critical resource will be on a long leave of absence The project team reviewed the pending vendor deliverables and identified an alternative solution, but the solution will incur an additional cost The project is currently on schedule and slightly under budget

What should the project manager do next?


A.

Request a replacement resource


B.

Perform a cost-benefit analysis


C.

Implement risk responses


D.

Perform Integrated Change Control





D.
  

Perform Integrated Change Control



Explanation:
Perform Integrated Change Control is the process of reviewing all change requests, approving changes and managing changes to deliverables, organizational process assets, project documents, and the Project Management Plan, and communicating the decisions1. This process is important to ensure that only approved changes are implemented and that the project remains aligned with the project objectives and stakeholder expectations. In this scenario, the project manager should perform Integrated Change Control to evaluate the impact of the proposed alternative solution on the project scope, schedule, cost, quality, risk, and other aspects. The project manager should also consult with the project sponsor, customer, and other key stakeholders to obtain their approval or rejection of the change request. The project manager should document the change request and its status in the change log and update the project management plan and other relevant documents accordingly. The project manager should also communicate the change and its implications to the project team and other affected parties. By performing Integrated Change Control, the project manager can ensure that the project is managed in a controlled and consistent manner, and that the project deliverables meet the agreed requirements and expectations.

References:

  • How To Successfully Perform Integrated Change Control?
  • 6 Steps for an Integrated Change Control Project Management Strategy
  • Performing Integrated Change Control: PMP Tips

During the planning stage of a project the project manager realizes that a standard stakeholder engagement approach will not suffice One of the client representatives, who is not a key decision maker, is extremely opinionated This client representative could become a roadblock to progress due to their perceived level of authority during meetings

How should the project manager handle this moving forward?


A.

Ask that only key decision makers attend the project meetings.


B.

Update the project schedule to cater to this particular stakeholder.


C.

Allocate time to gain buy-in from the stakeholder prior to key decision meetings.


D.

Update the risk register to consider the possible project impacts.





C.
  

Allocate time to gain buy-in from the stakeholder prior to key decision meetings.



Explanation:

Stakeholder engagement is the process of identifying, analyzing, planning, and implementing actions to communicate with, influence, and involve stakeholders throughout the project lifecycle. Stakeholder engagement aims to ensure that stakeholders are satisfied with the project outcomes, and that their expectations and needs are met. According to the Professional in Business Analysis Reference Materials1, stakeholder engagement involves the following steps:

  • Identify stakeholders: Determine who are the individuals or groups that have an interest or influence in the project, and what are their roles, responsibilities, expectations, and power.
  • Analyze stakeholders: Assess the level of interest and influence of each stakeholder, and their potential impact on the project objectives, scope, schedule, cost, quality, and risks. Use tools such as stakeholder analysis matrix, power/interest grid, or salience model to categorize stakeholders based on their attributes.
  • Plan stakeholder engagement: Develop strategies and actions to effectively communicate with, involve, and manage stakeholders throughout the project. Use tools such as stakeholder engagement plan, communication plan, or RACI matrix to define the frequency, mode, content, and responsibility of stakeholder interactions.
  • Implement stakeholder engagement: Execute the planned activities to engage stakeholders, and monitor and measure their feedback, satisfaction, and performance. Use tools such as stakeholder register, issue log, change log, or performance reports to track and document stakeholder engagement.
  • Evaluate stakeholder engagement: Review and analyze the effectiveness and outcomes of stakeholder engagement, and identify areas for improvement or adjustment. Use tools such as lessons learned, surveys, or interviews to collect and analyze stakeholder feedback and recommendations.

In this scenario, the project manager realizes that a standard stakeholder engagement approach will not suffice, because one of the client representatives, who is not a key decision maker, is extremely opinionated and could become a roadblock to progress due to their perceived level of authority during meetings. This stakeholder could be classified as a high-interest, low-influence stakeholder, who needs to be kept informed and consulted, but not allowed to dominate or derail the project decisions. Therefore, the best option for the project manager is to allocate time to gain buy-in from the stakeholder prior to key decision meetings. This way, the project manager can:

  • Understand the stakeholder’s perspective, concerns, and expectations, and address them proactively and respectfully.
  • Build trust and rapport with the stakeholder, and demonstrate the value and benefits of the project for them and their organization.
  • Involve the stakeholder in the project planning and design process, and solicit their input and feedback on the project scope, objectives, deliverables, and requirements.
  • Negotiate and compromise with the stakeholder on any conflicting or unrealistic demands, and seek their support and agreement on the project decisions.
  • Acknowledge and appreciate the stakeholder’s contribution and participation, and recognize their role and authority within their organization.

By allocating time to gain buy-in from the stakeholder prior to key decision meetings, the project manager can enhance the stakeholder engagement, satisfaction, and collaboration, and reduce the risk of resistance, conflict, or delay in the project.

The other options are not the best choices, because:

  • Asking that only key decision makers attend the project meetings could alienate and offend the stakeholder, and damage the relationship and trust with them and their organization. It could also create a communication gap and a lack of transparency and accountability in the project.
  • Updating the project schedule to cater to this particular stakeholder could disrupt the project workflow and priorities, and create inefficiencies and delays in the project. It could also cause resentment and frustration among other stakeholders, who may feel that their needs and expectations are not being met or respected.
  • Updating the risk register to consider the possible project impacts could be a useful step, but it is not sufficient to address the root cause of the problem, which is the stakeholder’s opinionated and authoritative behavior. It could also imply that the project manager is avoiding or ignoring the stakeholder, rather than engaging and influencing them.

References:
Stakeholder Engagement.

A key stakeholder for a construction project has been spending a lot of time at the site and interrupting the team's efforts What should the project manager do in this situation?


A.

Work to understand the key stakeholder's concerns and provide feedback in regular project status reports


B.

Arrange an ad hoc meeting to address the key stakeholder's concerns with team members


C.

Reinforce with the key stakeholder that the project is performing on schedule


D.

Escalate the situation to the project sponsor because the key stakeholder's behavior is impacting progress





A.
  

Work to understand the key stakeholder's concerns and provide feedback in regular project status reports



Explanation:
According to the PMBOK Guide, the project manager should manage stakeholder expectations by communicating and working with stakeholders to meet their needs and address issues as they occur. This includes understanding the stakeholder’s concerns, interests, and expectations, and providing timely and accurate information to keep them informed and satisfied. By working to understand the key stakeholder’s concerns and providing feedback in regular project status reports, the project manager can maintain a positive relationship with the stakeholder and avoid unnecessary interruptions and conflicts.

References: 
PMBOK Guide, 6th edition, page 540-541, section 13.3.2.4 Manage Stakeholder Engagement: Data Analysis.

A project manager is leading a project which shows a trend to exceed the cost baseline What should the project manager do first to manage the budget?


A.

Ask the project sponsor for assistance in getting the budget back on track


B.

Meet with the project team to analyze the actual cost to determine deviations


C.

Inform the stakeholders that the project will be finished over budget


D.

Issue a change request including the analysis to increase the budget





B.
  

Meet with the project team to analyze the actual cost to determine deviations



Explanation:
The project manager should do first to manage the budget is to meet with the project team to analyze the actual cost to determine deviations. This is the first step in the control cost process, which involves monitoring the status of the project to update the project costs and manage changes to the cost baseline2. By analyzing the actual cost, the project manager can identify the causes and sources of the cost variance, and evaluate the impact and implications on the project performance and objectives. The project manager can also use various tools and techniques, such as earned value analysis, forecasting, and variance analysis, to measure and report the cost performance and status2. Based on the analysis, the project manager can then decide on the appropriate actions and responses to bring the project back on track, such as requesting additional funds, reducing scope, adjusting resources, or implementing corrective or preventive actions2.

Option A is not a good choice, because it is premature and passive. The project manager should not ask the project sponsor for assistance in getting the budget back on track before analyzing the actual cost and determining the deviations. The project manager should first understand the nature and extent of the cost variance, and then present the facts and data to the project sponsor, along with possible solutions and recommendations. The project manager should also demonstrate their own initiative and responsibility in managing the budget, rather than relying on the project sponsor to solve the problem.

Option C is not a good choice, because it is pessimistic and irresponsible. The project manager should not inform the stakeholders that the project will be finished over budget before analyzing the actual cost and determining the deviations. The project manager should first assess the situation and explore the options to improve the cost performance and meet the budget expectations. The project manager should also communicate the cost status and issues to the stakeholders in a timely and transparent manner, and seek their feedback and support, rather than delivering bad news without any justification or action plan.

Option D is not a good choice, because it is hasty and presumptuous. The project manager should not issue a change request including the analysis to increase the budget before analyzing the actual cost and determining the deviations. The project manager should first verify the accuracy and validity of the cost data, and evaluate the feasibility and necessity of increasing the budget. The project manager should also consider the impact of the change request on the project scope, schedule, quality, and stakeholder satisfaction, and obtain the approval of the change control board before implementing the change2.

References:
1: Project Management Professional (PMP)® Certification
2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition

During a retrospective meeting a project manager hears that stakeholders have been constantly complaining at iteration demos about product features not being delivered as requested. What advice should the project manager give to the Product owner to ensure that product features are always delivered as requested?


A.

Include stakeholders during daily standup meetings to monitor progress.


B.

Validate acceptance criteria with stakeholders prior to backlog refinement


C.

Avoid including stakeholders in iteration reviews.


D.

Create a requirements traceability matrix and distribute it accordingly





B.
  

Validate acceptance criteria with stakeholders prior to backlog refinement



Explanation

The product owner is responsible for defining and prioritizing the product backlog, which contains the features and requirements that the project team will deliver in each iteration. To ensure that the product backlog reflects the needs and expectations of the stakeholders, the product owner should validate the acceptance criteria with them before refining the backlog. Acceptance criteria are the conditions that a product feature or requirement must meet to be accepted by the stakeholders. By validating the acceptance criteria with the stakeholders, the product owner can ensure that they are clear, measurable, testable, and aligned with the project vision and goals. This will also help to avoid misunderstandings, conflicts, and rework during the iteration demos, as the stakeholders will have agreed on what constitutes a satisfactory product feature or requirement.

References: PMBOK Guide, 6th edition, section 5.1.3.2; Agile Practice Guide, section 4.2.1

Two functional managers disagree on key features of one deliverable during the planning of a project The project manager discovers that each manager included requirements that contradict each other The functional managers do not want to meet with each other to find a solution This situation has been escalated to the sponsor who requests a meeting with them

What strategy should the project manager use to resolve this conflict in the meeting?


A.

Explain to the managers that the contradicting requirements are being considered for implementation in the project


B.

Explain to the managers that only one of the two requirements can be implemented, and submit a change request,


C.

Ensure that both managers understand the requirements and search for a solution that best satisfies this deliverable


D.

Request that the managers explain why each requirement must be implemented and decide by considering the cost and benefits





C.
  

Ensure that both managers understand the requirements and search for a solution that best satisfies this deliverable



Explanation

The project manager should use a collaborative or problem-solving strategy to resolve this conflict in the meeting. This strategy involves finding a solution that fully satisfies the concerns of both parties and results in a win-win outcome. The project manager should ensure that both managers understand the requirements and the impact of their contradiction on the project scope, quality, and schedule. The project manager should also facilitate a constructive dialogue between the managers and help them identify and evaluate alternative solutions that can meet the project objectives and satisfy the stakeholders. The project manager should avoid imposing a decision or favoring one side over the other, as this may lead to resentment, resistance, or further conflict.

Option A is not a good choice, because it does not address the root cause of the conflict or seek a resolution. It may also create confusion, ambiguity, or inconsistency in the project deliverable, as well as increase the project risk and complexity.

Option B is not a good choice, because it does not involve the managers in finding a solution or consider their interests and needs. It may also create dissatisfaction, frustration, or hostility among the managers, as well as affect the project quality and stakeholder satisfaction.

Option D is not a good choice, because it does not foster a cooperative or integrative approach to resolving the conflict. It may also create a competitive or adversarial atmosphere in the meeting, as well as ignore the

non-monetary or intangible factors that may influence the managers’ preferences and expectations.

References: 1: Project Management Professional (PMP)® Certification 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition

A company starts implementing Scrum About halfway through the first sprint, communication issues develop Some project team members are not in sync with other team members

What is the cause for this communication gap?


A.

The project sprint board has not been updated


B.

Daily standup meetings were not held or enforced


C.

The project status dashboard has not been updated


D.

The communications management plan has not been developed





B.
  

Daily standup meetings were not held or enforced



Explanation:
Daily standup meetings are an essential practice of Scrum, which aim to facilitate communication, collaboration, and coordination among the project team members1. Daily standup meetings are short, time-boxed, and focused sessions where each team member answers three questions: what they did yesterday, what they will do today, and what impediments they face2. Daily standup meetings help the team to:

  • Align their work with the sprint goal and the definition of done.
  • Identify and resolve any issues or dependencies that may affect the sprint progress.
  • Share information, feedback, and ideas with each other.
  • Foster a sense of accountability, transparency, and trust If daily standup meetings are not held or enforced, the team may experience communication gaps, which can lead to misunderstandings, conflicts, delays, or poor quality of work3. Therefore, the project manager or the Scrum master should ensure that daily standup meetings are conducted regularly, effectively, and efficiently, and that all team members participate actively and respectfully4. 

References:

  • Daily Stand-up Meeting - Scrum Inc Daily Scrum - Scrum Guide
  • Scrum & the challenge of effective communication - Medium
  • 7 ways the Scrum Master can improve Scrum Team Communication

A team has been struggling with various issues during the course of an iteration. The project lead facilitates a discussion of the issues and the team forms new team agreements. During the next iteration, some of the same issues appear again.

What should the project lead do next?


A.

Notify senior management of the issues and have them review the importance of agreements with the team


B.

Challenge the team to determine if the issues surfaced again because agreements were not followed


C.

Post the agreements in a conspicuous place where all of the team members can see them.


D.

Let the team self-organize and determine the best means to prevent the issues from occurring again.





D.
  

Let the team self-organize and determine the best means to prevent the issues from occurring again.



According to the PMBOK guide, one of the principles of agile project management is to empower the team to self-organize and make decisions about how to best accomplish their work. Self-organizing teams are more likely to be motivated, creative, and productive, as they have a sense of ownership and autonomy over their work. Self-organizing teams also have the ability to inspect and adapt their processes and practices based on feedback and learning. Therefore, when a team faces recurring issues, the project lead should not intervene or impose solutions, but rather facilitate the team’s reflection and improvement. The project lead can use techniques such as retrospectives, which are meetings where the team reviews their performance and identifies what went well, what did not go well, and what actions they can take to improve. The project lead can also help the team to update their team working agreement, which is a document that defines the team’s norms, values, and expectations. A team working agreement can help the team to align on their goals, roles, responsibilities, and communication methods, as well as to resolve conflicts and issues. The project lead should not notify senior management, challenge the team, or post the agreements, as these actions may undermine the team’s trust, autonomy, and accountability.

References:

  • PMBOK guide, page 18, section 1.2.3, Agile Considerations in Project Management
  • PMBOK guide, page 437, section 11.2.2.3, Meetings
  • Creating a Team Working Agreement

A new project has been kicked off following a planning session. The project is under direct oversight of an executive in the organization After a review meeting, the project manager overhears an executive request a dashboard from one of the team members to show the overall project status. What should the project manager do?


A.

Update the stakeholder engagement assessment matrix


B.

Update the communications management plan to include informal requests


C.

Ask the team member to develop a dashboard to fulfill the request.


D.

Tell the team member to route the request through the project manager





B.
  

Update the communications management plan to include informal requests



Explanation:

According to the PMBOK Guide, the communications management plan is a component of the project management plan that describes how project communications will be planned, structured, implemented, and monitored for effectiveness. It also defines the communication methods, formats, frequency, and escalation process for different types of communication. In this scenario, the project manager should update the communications management plan to include informal requests from the executive, such as the dashboard, and specify how they will be handled by the project team. This way, the project manager can ensure that the communication expectations of the executive are met, and the project team is aware of their roles and responsibilities in providing the requested information. Updating the stakeholder engagement assessment matrix, asking the team member to develop a dashboard, or telling the team member to route the request through the project manager are not effective options, as they do not address the root cause of the communication issue, which is the lack of a clear and comprehensive communications management plan.

References: PMBOK Guide, 7th edition, pages 123-124, 127-128.


Page 4 out of 38 Pages
Previous