PMP Exam Questions

Total 377 Questions

Last Updated Exam : 16-Dec-2024

Topic 1: Exam Pool A

An agile project manager would like to convert the requirements document into epics, capabilities, features and stories In how many iterations should the project manager estimate the story duration?


A.

Four iterations


B.

One iteration


C.

Two iterations


D.

Three iterations





B.
  

One iteration



Explanation:

An agile project manager would like to convert the requirements document into epics, capabilities, features and stories in order to create a product backlog that can be prioritized and refined by the agile team and the product owner. The product backlog is a dynamic and evolving artifact that represents the customer’s needs and expectations for the product. To estimate the story duration, the agile project manager should use the team’s historical data and empirical evidence from previous iterations. The agile project manager should also involve the team members who will perform the work in the estimation process, as they have the best knowledge and expertise about the tasks and the complexity involved. The agile project manager should estimate the story duration in one iteration, as this is the timebox for delivering a potentially releasable product increment. Estimating the story duration in one iteration allows the agile project manager to plan and monitor the iteration progress, adjust the scope and priorities based on feedback and changes, and ensure that the team delivers value to the customer in a timely manner. Estimating the story duration in more than one iteration would introduce uncertainty and risk, as the team’s velocity, the customer’s requirements, and the product’s quality might change over time. Estimating the story duration in less than one iteration would not be feasible, as the team would not have enough time to complete the work and validate the results.

References:
PMBOK Guide, 6th edition, Section 6.2, 6.3, 6.4, 6.5, Agile Practice Guide, Section 3.2, 3.3, 4.2, 4.3

A company is changing their current business model The change requires implementing a complex project using multiple agile teams.

What three options should the project manager have the testing team adopt as testing mechanisms? (Choose three)


A.

Independent personal testing


B.

Security and performance testing


C.

An experimental approach to cover all possible choices


D.

Story testing


E.

Tests based on behavior and test-driven development





B.
  

Security and performance testing



D.
  

Story testing



E.
  

Tests based on behavior and test-driven development



Explanation:

According to the Agile Testing: A Practical Guide For Testers And Agile Teams1, security and performance testing are two types of nonfunctional testing that are important for agile teams. Security testing ensures that the system is protected from unauthorized access, data loss, or corruption. Performance testing measures how the system responds to different levels of load, stress, and concurrency. These types of testing can be done at different levels of granularity, from unit testing to system testing, and can use tools such as JMeter, LoadRunner, or Selenium.

Story testing is a type of functional testing that verifies that the system meets the acceptance criteria of each user story. User stories are short descriptions of the features or functionalities that the customer wants from the system. Story testing can be done by the developers, testers, or customers, and can use tools such as FitNesse, Cucumber, or SpecFlow.

Tests based on behavior and test-driven development are two approaches that support agile testing practices. Behavior-driven development (BDD) is a technique that uses natural language to describe the expected behavior of the system in different scenarios. Test-driven development (TDD) is a technique that involves writing the tests before the code, and then refactoring the code to make the tests pass. Both BDD and TDD help to clarify the requirements, design the system, and ensure the quality of the code. They can use tools such as JUnit, NUnit, or RSpec.

References: (Professional in Business Analysis Reference Materials source and documents)

  • Agile Testing: A Practical Guide For Testers And Agile Teams, Lisa Crispin and Janet Gregory, Addison-Wesley Professional, 2009
  • Scrum Testing: A Detailed Guide to Testing on an Agile Team, Testim, Accessed on January 29, 2024
  • Agile Testing Best Practices & Why They Matter, Atlassian, Accessed on January 29, 2024

During project execution, the project manager discovered that a key deliverable was missing from the scope of work After investigation, the project manager and the team discovered that the missing deliverable will impact the critical path

What should the project manager do to avoid future delays?


A.

Submit a change request.


B.

Add additional resources to the project.


C.

Update the scope of work.


D.

Review the risk management plan.





A.
  

Submit a change request.



Explanation:

The project manager should submit a change request to update the scope of work, the schedule, and the budget to accommodate the missing deliverable. A change request is a formal proposal to modify any aspect of the project, such as the scope, schedule, cost, quality, resources, or risks. A change request must be documented, reviewed, approved, and communicated by following the change control process. The change control process is part of the perform integrated change control process, which is one of the processes in the project integration management knowledge area. By submitting a change request, the project manager can ensure that the missing deliverable is properly identified, analyzed, and integrated into the project plan, and that the impact on the project objectives and constraints is minimized. The other options are not correct. Adding additional resources to the project may not solve the problem of the missing deliverable, and it may also introduce new risks, costs, and communication issues. Updating the scope of work without submitting a change request may lead to scope creep, which is the uncontrolled expansion of the project scope without proper authorization and approval.

Reviewing the risk management plan may help to identify and mitigate any potential risks related to the missing deliverable, but it does not address the root cause of the problem or the impact on the project plan.

References: PMBOK Guide, 6th edition, Chapter 4.6, 5.6, How to Manage Change Requests on a Project- PMI

The project team follows a hybrid framework for its delivery. During the execution of a project, the team learns of a new compliance requirement that has to be delivered before any other requirements

How should the project manager address this situation?


A.

Ask the team to include the compliance requirement in the current sprint and deliver it.


B.

Add the new compliance requirement to the backlog as the technical team does not have any capacity.


C.

Include the compliance lead in the stakeholders list and wait for the next status meeting


D.

Collaborate with the compliance team member to review and prioritize the requirement’s delivery





D.
  

Collaborate with the compliance team member to review and prioritize the requirement’s delivery



Explanation:

The project manager should collaborate with the compliance team member to review and prioritize the requirement’s delivery, as this is a way to manage the change request and ensure that the project meets the compliance standards and expectations. The project manager should also communicate the impact of the change on the project scope, schedule, cost, and quality to the project sponsor and other stakeholders, and obtain their approval and support. The project manager should not ask the team to include the compliance requirement in the current sprint and deliver it (choice A), as this would disrupt the sprint planning and execution, and create scope creep and quality issues. The project manager should not add the new compliance requirement to the backlog as the technical team does not have any capacity (choice B), as this would delay the delivery of the compliance requirement and expose the project to legal and regulatory risks. The project manager should not include the compliance lead in the stakeholders list and wait for the next status meeting (choice C), as this would not address the urgency and importance of the compliance requirement, and it would not involve the compliance lead in the decision-making and problem-solving process. 

References:

  • PMBOK Guide, 6th edition, page 115: “A change request is a formal proposal to modify any document, deliverable, or baseline.”
  • PMBOK Guide, 6th edition, page 119: “The project manager should review all change requests, assess their impact on the project, and either approve them or submit them to the change control board (CCB) or other decision-making authority for approval or rejection.”
  • PMBOK Guide, 6th edition, page 120: “The project manager should communicate the approved change requests to the project team and other stakeholders, and update the project management plan and other project documents accordingly.”
  • PMBOK Guide, 6th edition, page 39: “Compliance requirements are the set of standards or regulations that the project must adhere to, such as health, safety, security, performance, environmental, or quality standards.”

A company that is heavily focused on delivering projects using predictive approaches on-boards a new project manager who uses hybrid approaches The scope of the project contains a number of unclear requirements.

How should the project manager plan the delivery of the project?


A.

Wait for the requirements to be more clear before any further action is taken on the project


B.

Ignore the unclear requirements and focus on the delivery plan of the project


C.

Escalate the issue of unclear requirements to the management team and wait for final authorization


D.

Break down the requirements and prioritize the requirements into iterative work packages





D.
  

Break down the requirements and prioritize the requirements into iterative work packages



Explanation:

A hybrid approach combines predictive and adaptive elements to deliver projects. In a hybrid approach, the project manager can break down the requirements into smaller and manageable chunks, and prioritize them based on their value and risk. This way, the project manager can deliver the most important and uncertain requirements first, and get feedback from the stakeholders and customers. This feedback can help clarify the unclear requirements and improve the quality of the project deliverables. The project manager can also adjust the delivery plan based on the changing requirements and environment. A hybrid approach is suitable for projects that have some degree of uncertainty and complexity, and that need to respond to changing customer needs and expectations. 

References:

  • A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Seventh Edition, Chapter 2: Value Delivery System, Section 2.3: Delivery Approaches, pp. 31-35
  • Project Management Professional (PMP) Handbook, Section 2.2: PMP Exam Content Outline, Domain II: Process, Task 1: Plan and manage project scope, pp. 14-15
  • Hybrid Project Management: What It Is & How to Implement It, by Simplilearn, published on February 10, 2020

A project manager invites the company CEO, sponsor, team members, and an external client representative to a meeting to review the project management plan. The project manager starts to present the budget but the CEO suddenly asks to end the meeting

What should the project manager have done to avoid this situation?


A.

Reviewed the communications management plan before inviting an external client representative to the meeting


B.

Reviewed the cost management plan with internal participants and CEO prior to inviting an external client representative to the meeting


C.

Performed a root cause analysis with the external client representative and documented the findings in the lessons learned register


D.

Sent the presentation slides to internal participants first and then to the external client representative prior to the meeting





A.
  

Reviewed the communications management plan before inviting an external client representative to the meeting



Explanation

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 requirements, methods, and channels for different stakeholders, as well as the confidentiality and security levels of the information to be shared. The project manager should have reviewed the communications management plan before inviting an external client representative to the meeting, to ensure that the information presented was appropriate and authorized for external disclosure. The project manager should also have obtained the approval of the project sponsor and the CEO before sharing any sensitive or confidential information with the external client representative. By not reviewing the communications management plan, the project manager may have violated the communication policies and protocols of the organization, and potentially compromised the project’s budget, scope, quality, or schedule. This could have caused the CEO to end the meeting abruptly, to avoid further disclosure of information that could harm the project or the organization. The other options are not the best choices because they do not address the root cause of the situation, which is the lack of review of the communications management plan. Reviewing the cost management plan with internal participants and CEO prior to inviting an external client representative to the meeting (option B) may be a good practice, but it does not ensure that the information shared with the external client representative is appropriate and authorized. Performing a root cause analysis with the external client representative and documenting the findings in the lessons learned register (option C) may be useful after the situation has occurred, but it does not prevent the situation from happening in the first place. Sending the presentation slides to internal participants first and then to the external client representative prior to the meeting (option D) may also be a good practice, but it does not guarantee that the information in the slides is suitable and approved for external communication.

References:

Project Management Professional (PMP) Reference Materials:
A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 10: Project Communications Management, pp. 361-411
Project Communication Management According to the PMBOK

Professional in Business Analysis (PBA) Reference Materials:
Business Analysis for Practitioners: A Practice Guide, Chapter 4: Planning Business Analysis Work, pp. 59-60
Effective Project Communication Plan Template: TeamGantt

After the second iteration of a component development project, the project team conducts a retrospective It shows that in the initial phase the project has failed to comply with a product functionality. The planning for this product has a predominantly predictive approach.

Which technique will help the project manager to accelerate the deliverable?


A.

Impact mapping


B.

Rolling wave planning


C.

Collective code ownership


D.

Scrum of Scrums





B.
  

Rolling wave planning



Explanation:

Rolling wave planning is a project planning technique that allows the project manager to plan and execute the project in short iterations, based on the available information and the level of detail required12. Rolling wave planning is suitable for projects that have a high degree of uncertainty, complexity, or change, such as a component development project13. Rolling wave planning can help the project manager to accelerate the deliverable by enabling the following benefits123:

  • It reduces the risk of rework and waste by allowing the project manager to adjust the plan as more information becomes available or as the requirements change.
  • It increases the flexibility and responsiveness of the project team by allowing them to focus on the most important and urgent tasks in each iteration, rather than following a rigid and detailed plan.
  • It improves the quality and customer satisfaction of the deliverable by allowing the project manager to incorporate feedback and lessons learned from each iteration into the next one, and by delivering incremental value to the customer.
  • It enhances the collaboration and communication among the project team and stakeholders by involving them in the planning and execution of each iteration, and by providing frequent and transparent updates on the project progress and status.

The other options are not the best techniques to accelerate the deliverable in this scenario. Impact mapping (A) is a strategic planning technique that helps the project manager to align the project deliverables with the organizational goals and the customer needs, by identifying the actors, impacts, and deliverables involved45. However, impact mapping does not address the issue of how to plan and execute the project in a fast and adaptive way, especially when the project has failed to comply with a product functionality. Collective code ownership © is a software development practice that encourages the entire team to share the responsibility and the authority to modify any code file as necessary, to improve the quality, the performance, and the functionality of the software product67. However, collective code ownership does not address the issue of how to plan and execute the project in a fast and adaptive way, especially when the project has a predominantly predictive approach. Scrum of Scrums (D) is a scaling technique that helps multiple Scrum teams to coordinate and collaborate on complex and interdependent projects, by having representatives from each team meet regularly to report on their progress, their impediments, and their dependencies89. However, Scrum of Scrums does not address the issue of how to plan and execute the project in a fast and adaptive way, especially when the project has a predominantly predictive approach.

References:
https://www.teamgantt.com/waterfall-agile-guide/hybrid-approach https://www.float.com/resources/hybrid-project-management/ https://en.wikipedia.org/wiki/Rolling-wave_planning

A project manager led the implementation of an electronic invoicing project that has just been completed. The financial manager communicated that the team discovered three invoices with errors.

Which two documents should the project manager update as soon as possible? (Choose two)


A.

Issue log


B.

Risk register


C.

Stakeholder register


D.

Change log


E.

Backlog register





A.
  

Issue log



D.
  

Change log



Explanation:
According to the PMBOK® Guide, the issue log is a project document that records and tracks the issues that arise during a project and how they are resolved1. The change log is a project document that records all the changes that occur during a project, including their status, description, and impact2. The project manager should update these two documents as soon as possible to reflect the invoices with errors and the actions taken to correct them. The risk register is a project document that identifies and analyzes the project risks and their responses3, but it does not record the issues that have already occurred. The stakeholder register is a project document that identifies and classifies the project stakeholders and their requirements4, but it does not record the issues or changes that affect them. The backlog register is not a standard project document, but it may be used in agile projects to list the product features or user stories that need to be delivered, but it does not record the issues or changes that affect the product quality. 

References:

  1. PMBOK® Guide, page 123;
  2. PMBOK® Guide, page 122;
  3. PMBOK® Guide, page 436;
  4. PMBOK® Guide, page 513; : Agile Practice Guide, page 77

Team members are having a discussion with the project manager In the last retrospective meeting, the team realized that the obsolete equipment could affect the next iteration of the project The team recommends buying new equipment because it is critical to the success of the final deliverable

What should the project manager do next?


A.

Check the project budget to verify if there is enough contingency reserve


B.

Review the cost management plan to determine how to address this issue


C.

Tell the team members that more equipment is not part of the project's scope.


D.

Submit a change request to increase the budget and buy new equipment





D.
  

Submit a change request to increase the budget and buy new equipment



Explanation:

  • According to the PMBOK Guide, a change request is a formal proposal to modify any document, deliverable, or baseline of a project. Change requests can be initiated by any stakeholder, including the project team, and should be processed through the perform integrated change control process.
  • In this scenario, the project team has identified a potential risk that could affect the quality and schedule of the next iteration of the project. The team has also proposed a solution to mitigate the risk by buying new equipment. This solution would require an increase in the project budget, which is a baseline that needs to be approved by the project sponsor or customer.
  • Therefore, the project manager should submit a change request to increase the budget and buy new equipment, and follow the change control procedures to obtain the necessary approval and authorization. This would ensure that the project scope, schedule, and quality are not compromised, and that the project stakeholders are aware of and agree with the proposed change.

The other options are not appropriate because:

  • Checking the project budget to verify if there is enough contingency reserve (option A) is not sufficient to address the issue. Contingency reserves are funds set aside to cover known risks that may or may not occur during the project. Even if there is enough contingency reserve, the project manager still needs to submit a change request to use it and update the project baseline.
  • Reviewing the cost management plan to determine how to address this issue (option B) is also not sufficient to address the issue. The cost management plan is a component of the project management plan that describes how the project costs will be planned, estimated, budgeted, managed, and controlled. It does not provide specific guidance on how to deal with changes that affect the project budget. The project manager still needs to follow the change control procedures and submit a change request.
  • Telling the team members that more equipment is not part of the project’s scope (option C) is not a constructive or collaborative way to deal with the issue. The project manager should not ignore or dismiss the team’s input and recommendations, especially if they are based on valid and relevant information. The project manager should respect the team’s expertise and experience, and work with them to find the best solution for the project.

References:
[PMBOK Guide] - A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Project Management Institute, Inc., 2021.

A project to develop a large hydropower plant is in the implementation phase and is managed using a hybrid approach. What should the project manager do to ensure full compliance of quality requirements during the execution phase?


A.

Analyze the quality requirements.


B.

Plan quality management


C.

Continually survey the quality of the deliverable


D.

Set up quality policies and procedures





C.
  

Continually survey the quality of the deliverable



Explanation:
This answer is based on the PMI Guide to Business Analysis, which is one of the reference materials for the PMI-PBA exam1. According to the guide, quality is the degree to which a set of inherent characteristics fulfill requirements2. Quality requirements are the criteria that define the acceptable level of performance, reliability, usability, and other attributes of the project deliverables2. In a hybrid approach, which combines predictive and adaptive methods, the project manager should continually survey the quality of the deliverable to ensure that it meets the quality requirements and the stakeholder expectations2. This can be done by using various quality management tools and techniques, such as inspections, audits, reviews, testing, feedback, and metrics2. Continual quality surveillance helps the project manager to identify and correct any defects, errors, or deviations from the quality standards, and to prevent or mitigate any risks related to quality2. The other options are not correct because they are either part of the planning phase or not sufficient to ensure full compliance of quality requirements during the execution phase.

References:
PMI Guide to Business Analysis
Professional in Business Analysis Reference Materials


Page 2 out of 38 Pages
Previous