PMP PMI Project Management Professional (PMBOK 7th Version) Free Practice Exam Questions (2026 Updated)

In an agile team, autonomy is a key factor for motivation, innovation, and ownership. Autonomy means that the team can decide how to do their work, as long as they are aligned with the project vision and goals. The project manager should support the team’s request for more autonomy, as it will empower them to find creative solutions, overcome challenges, and deliver value to the customer. The project manager should not discourage the team or delegate the decision-making to the team lead, as it will undermine the team’s self-organization and collaboration1. References:

PMP Exam Content Outline

PMI PMP Q&A: What should project manager do if team ask for more autonomy1

Risks and costs are controlled as requirements and constraints emerge.

Requirements are incorporated in real-time during delivery.

Changes are elaborated frequently during delivery.

Key stakeholders are continuously engaged throughout delivery.

 In project management, particularly within the agile framework, it is essential to match the correct practices with the project’s needs. The phrases and statements provided align with the principles of agile project management, where:

Risks and costs must be controlled as they emerge, which is part of the monitoring and controlling process groups.

Requirements should be incorporated in real-time, reflecting the iterative nature of agile projects.

Changes need to be elaborated frequently, allowing for continuous improvement and adaptation during project execution.

Key stakeholders engagement is crucial throughout the project delivery to ensure alignment and satisfaction with the project outcomes.

The PMBOK® Guide1 and the Agile Practice Guide, which are part of the PMI’s foundational standards, provide detailed explanations on these agile practices. Additionally, the PMP Examination Content Outline2 offers insights into the process groups and knowledge areas relevant to these practices. These references emphasize the importance of flexibility, stakeholder engagement, and iterative development in project management.

 According to the PMBOK Guide, a project manager should refer to the communications management plan, when facing issues with both the agile delivery of the product and the predictive development of a marketing strategy, and needing to receive feedback from stakeholders located in different time zones. The communications management plan is a component of the project management plan that describes how the project information will be planned, managed, monitored, and controlled. It also defines the communication requirements, methods, formats, frequency, and channels for each stakeholder group. The communications management plan should address the challenges and opportunities of working in a hybrid project environment, where both agile and predictive approaches are used. The communications management plan should also consider the diversity and distribution of the stakeholders, and ensure that the feedback mechanisms are appropriate, timely, and effective. By referring to the communications management plan, the project manager can ensure that the project communication is aligned with the project objectives, stakeholder expectations, and project methodology. References: PMBOK Guide, 6th edition, pages 89-90, 377-378.

According to the PMBOK Guide 7th edition, a reserve analysis is a technique used to determine the amount of contingency and management reserves needed for a project. Contingency reserves are used to address known risks, while management reserves are used to address unknown risks. The risk management plan is a component of the project management plan that describes how risk management activities will be planned, structured, and performed. The project manager should request a reserve analysis and update the risk management plan to account for the critical element and the reserves needed in the next phase of the project. This will help the project manager to manage the uncertainties and potential impacts of the risks on the project objectives. References: PMBOK Guide 7th edition, pages 215-216, 223-224, 228-229. PMBOK Guide 7th Edition and PMP Exam Prep

An agile approach is suitable for projects with unstable or changing requirements, as it allows for frequent feedback and adaptation. By refining and prioritizing the requirements according to the project objectives, the project manager can ensure that the most valuable features are delivered to the customer in an iterative and incremental manner. This can also increase the stakeholder satisfaction and engagement with the project. References:

PMBOK Guide, 6th edition, section 4.2.2.3, page 141

PMI Agile Practice Guide, section 2.1, page 9

Free PMP Practice Exam Questions - 120 Sample Test Questions, question 18

The project manager should first perform an impact analysis with SMEs to assess the potential effects of the separate project on the network upgrade. This will help the project manager to determine the magnitude and probability of the risks, as well as the possible responses and contingency plans. The impact analysis is part of the Monitor Risks process, which involves tracking the identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness1. Informing the government representative, implementing a change request, and updating the risk register are all possible actions that may follow the impact analysis, but they are not the first thing to do. References: 1 PMBOK® Guide, 6th edition, page 452.

The project manager should clarify expectations by explaining the company culture with the supervisor. The company culture reflects the shared values, beliefs, and norms that influence how people behave and interact in the organization. The project manager should communicate the positive changes that have occurred in the company culture and how they affect the project objectives, scope, quality, and stakeholder satisfaction. The project manager should also seek to understand the supervisor’s leadership style and expectations and try to find a common ground that respects both the company culture and the supervisor’s authority. Asking senior management to move the supervisor, revisiting the company’s organizational culture, or instructing the employees to listen to the supervisor may not resolve the issue and may create more conflict and resentment. References: PMBOK Guide, 6th edition, page 30; PMP Exam Content Outline, 2021, page 8.

 The question is about an agile project, where the team works in iterations or sprints to deliver incremental value to the customer. In such a project, the project manager needs to monitor the team’s performance and knowledge gaps regularly and provide feedback and support. Two project events that can help the project manager to do this are:

Retrospective: This is a meeting held at the end of each sprint, where the team reflects on what went well, what went wrong, and what can be improved in the next sprint. The retrospective allows the team to identify and address any issues or impediments that affect their work, including knowledge gaps. The project manager can facilitate the retrospective and help the team to find solutions or resources to fill the knowledge gaps12

Backlog refinement: This is a process of reviewing and updating the product backlog, which is a prioritized list of features or requirements that the team needs to deliver. The backlog refinement helps the team to clarify and decompose the requirements, estimate the effort and complexity, and plan the upcoming sprints. The project manager can participate in the backlog refinement and help the team to understand the requirements and resolve any ambiguities or uncertainties13

The other options are not as relevant or effective as the retrospective and backlog refinement for the purpose of the question. Requirements analysis is a process of eliciting, analyzing, and validating the requirements, which is usually done before the project starts or during the initiation phase. It is not a specific event that occurs regularly during an agile project4 Sprint planning is a meeting held at the beginning of each sprint, where the team selects the requirements from the product backlog and commits to deliver them within the sprint. It is not a suitable event to assess the team’s knowledge gaps, as it focuses on the scope and schedule of the sprint1 Standup is a daily meeting where the team members share their progress, plans, and problems. It is a useful event to monitor the team’s work and identify any blockers, but it is not enough to address the team’s knowledge gaps, as it is usually brief and focused on the current tasks1

 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 6, Section 6.3.2.2 2: PMI Agile Practice Guide, Chapter 5, Section 5.2.3 3: PMI Agile Practice Guide, Chapter 5, Section 5.2.2 4: Business Analysis for Practitioners: A Practice Guide, Chapter 3, Section 3.1

Organizational process assets (OPAs) are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization1. They can help the junior project manager to follow the best practices and standards of the organization and the industry. Lesson learned registers from past projects are the documented information that captures the knowledge, experience, and lessons learned throughout or at the end of a project2. They can help the junior project manager to avoid repeating the same mistakes and to apply the successful strategies from previous projects. Project management plan is the document that describes how the project will be executed, monitored, and controlled3. It can help the junior project manager to define, coordinate, and integrate all the subsidiary plans and baselines, such as scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement4. References: 1: PMBOK Guide, 7th edition, page 34 2: PMBOK Guide, 7th edition, page 36 3: PMBOK Guide, 7th edition, page 37 4: PMBOK Guide, 7th edition, page 38

The project manager should use the collaborate/problem solve technique to resolve this issue, as it involves finding a mutually beneficial solution that satisfies the interests of both the senior and junior team members. This technique is also known as confronting or integrating, and it is the preferred technique for managing conflicts on a project. The project manager should facilitate a constructive dialogue between the two team members, identify the root cause of the conflict, and help them reach a common understanding and agreement. This way, the project manager can maintain a positive team environment and foster collaboration and trust among the team members. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide 6th Edition, page 368, section 9.5.2.1

PMI Practice Standard for Project Risk Management, page 37, section 3.5.2.1

PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 13, section 3.2.1.1

According to the PMBOK Guide, the project manager is responsible for managing the project work and ensuring that the project objectives are met. One of the processes in the project management process group is Monitor and Control Project Work, which involves tracking, reviewing, and reporting the progress and performance of the project, as well as identifying and resolving issues. The project manager should use the issue log, a project document that records and tracks the issues that arise during the project, to document the issue of the missing notification and assign it to the appropriate project team member(s) for resolution. The project manager should also communicate the issue to the relevant stakeholders and update the project management plan and other project documents as needed. The project manager should not close out the project until the issue is resolved and the system migration is completed for all departments, as this would compromise the quality and scope of the project deliverables. The project manager should also not escalate the issue to the project sponsor and upper management, as this would indicate a lack of control and responsibility for the project. The project manager should also not report the issue during the next status meeting at the end of the week, as this would delay the resolution and potentially cause more problems for the project. The project manager should act promptly and proactively to address the issue and ensure the project is closed successfully. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 4: Project Integration Management, Section 4.6: Monitor and Control Project Work, p. 123-127

PMBOK Guide, 6th edition, Appendix X1: Agile, Iterative, Adaptive, and Hybrid Project Environments, Section X1.5.2: Issue Log, p. 715

Business Analysis for Practitioners: A Practice Guide, Chapter 5: Traceability and Monitoring, Section 5.3: Monitoring the Performance of Business Analysis Work, p. 143-144

The PMI Guide to Business Analysis, Chapter 7: Solution Evaluation, Section 7.3: Assess Solution Limitations, p. 373-374

A minimum viable product (MVP) is the most basic version of a new product with enough functionality and features to appeal to early adopters and validate the concept early in the product development cycle. The concept of an MVP comes from the Lean Startup methodology, which encourages learning and building with scalability in mind. According to its author, Eric Ries, an MVP is the version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least amount of effort. Building an MVP plays a central role in agile product development. It aligns with agile principles of releasing updates consistently, learning along the way, and prioritizing features based on user feedback. The benefits of focusing on an MVP and scaling it up may vary, but ultimately the purpose is to provide a low-risk testing ground before you invest thousands (or millions!) of dollars into a product before it’s ready to sell. MVP testing can provide cost savings, insights into user-centered design, fast business launches, and even getting early investor buy-in. The insights and investment you’ll reap early on will help you build the dream product you and your customers have been looking for. Therefore, the project manager should support the team to find and execute the MVP, as this will help them deliver value to the customers, test their assumptions, and make iterative improvements based on feedback. This will also reduce the risk of wasting time and resources on features that are not needed or desired by the customers. The other options are not as effective as the MVP approach. Encouraging and motivating the team with project incentives may boost their morale, but it does not address the root cause of the problem, which is the scope and complexity of the project. Subdividing the team to handle different aspects of the project may improve the division of labor, but it does not ensure that the team is working on the right features or that they are aligned with the customer needs. Organizing project execution to satisfy the project sponsor’s request may seem like a good way to meet the expectations of the stakeholder, but it may also lead to over-engineering the product and delivering a solution that is not validated by the market. References:

Understanding the Minimum Viable Product (MVP) in Agile Project Management

MVPs and MBIs - Project Management Institute

Minimum Viable Product (MVP): What is it & Why it Matters - Atlassian

The project manager should use the monitor and control project work process to track, review, and report the progress and performance of the project. This process involves collecting, measuring, and analyzing project data to identify variances from the baseline and take corrective actions if needed. One of the tools and techniques for this process is data analysis, which includes root cause analysis. Root cause analysis is a technique to identify the underlying factors that cause a problem or a deviation from the expected outcome. By conducting root cause analysis, the project manager can understand why some team members are not completing their tasks on time and address the issues accordingly. This could involve providing feedback, coaching, training, or other support to the team members. Communicating the delivery dates more frequently (option A) may not be effective if the team members are facing other challenges or obstacles that prevent them from meeting the deadlines. Mentoring the team members to work in a remote environment (option C) may be helpful, but it is not the best option to resolve the current situation. The project manager should first identify the specific causes of the delays and then provide the appropriate guidance or assistance. Talking to the resource managers and requesting additional resources (option D) may not be feasible or necessary, as it may increase the project cost and complexity. Moreover, adding more resources may not solve the problem if the existing team members are not performing well or have other issues that affect their productivity. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, pages 119-120, 4.4 Monitor and Control Project Work

PMI, PMP Exam Content Outline, 2021, page 9, Domain II: Process, Task 7: Monitor project artifacts and resolve any deviations from the project management plan

PMP Practice Questions #60 - iZenBridge

The project manager should review the terms and conditions of the contract to determine if the maintenance manual was part of the agreed scope and deliverables. If the manual was not included in the contract, the project manager should inform the customer and negotiate a change request to add the manual as a new deliverable. If the manual was included in the contract, the project manager should apologize to the customer and expedite the delivery of the manual as soon as possible. The project manager should also update the risk log to capture the potential impact of this issue on the customer satisfaction, project schedule, and budget. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 12.2.1.1, “Procurement Documentation”

PMBOK® Guide, 6th edition, Section 12.3.3.1, “Change Requests”

PMBOK® Guide, 6th edition, Section 11.6.1.1, “Risk Register”

According to the PMBOK Guide, 7th edition, section 2.2.1, organizational process assets (OPAs) are the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. OPAs include any artifact, practice, or knowledge from any or all of the organizations involved in the project that can be used to execute or govern the project. OPAs also include historical information and lessons learned from previous projects. Therefore, the project manager’s notes should be stored as OPAs, so that they can be accessed and utilized by other project managers in the future. OPAs are inputs to many project management processes and outputs of some project management processes. References:

PMBOK Guide, 7th edition, section 2.2.1, page 37-38

PMBOK Guide, 7th edition

PMP Exam Content Outline

 the project manager should communicate the situation to the appropriate stakeholders who are responsible for managing the supplier relationship and contract. The purchasing department can then take the necessary actions to mitigate the risk of supplier failure or default, such as negotiating new terms, finding alternative suppliers, or terminating the contract. The project manager should not add the situation to the risk register (A) or use the issue log (D) without informing the purchasing department first, as this would not address the root cause of the problem or prevent potential impacts on the project. The project manager should not identify competitors (B) without consulting the purchasing department, as this could violate the existing contract or procurement policies. References:

PMBOK Guide, 7th edition, page 37, section 2.2.6, “Business Environment”

PMBOK Guide, 7th edition, page 39, section 2.2.7, “Governance”

PMBOK Guide, 7th edition, page 41, section 2.2.8, “Lifecycle”

PMBOK Guide, 7th edition, page 43, section 2.2.9, “Tailoring”

PMBOK Guide, 7th edition, page 45, section 2.2.10, “Models, Methods, and Artifacts”

PMBOK Guide, 7th edition, page 47, section 2.2.11, “Project Performance”

PMBOK Guide, 7th edition, page 49, section 2.2.12, “Adaptive Delivery”

PMBOK Guide, 7th edition, page 51, section 2.2.13, “Project Management Office”

PMBOK Guide, 7th edition, page 53, section 2.2.14, “Project Team”

PMBOK Guide, 7th edition, page 55, section 2.2.15, “Stakeholders”

PMBOK Guide, 7th edition, page 57, section 2.2.16, “Information Management”

PMBOK Guide, 7th edition, page 59, section 2.2.17, “Principles”

PMBOK Guide, 7th edition, page 61, section 2.2.18, “Performance Domains”

PMBOK Guide, 7th edition, page 63, section 2.2.19, “Tailoring and Models”

PMBOK Guide, 7th edition, page 65, section 2.2.20, “Standards Plus”

PMBOK Guide, 7th edition, page 67, section 2.2.21, “Glossary”

PMBOK Guide, 7th edition, page 69, section 2.2.22, “References”

PMBOK Guide, 7th edition, page 71, section 2.2.23, “Index”

PMBOK Guide, 7th edition, page 73, section 2.2.24, “Appendix X1: Summary of Key Concepts”

PMBOK Guide, 7th edition, page 75, section 2.2.25, “Appendix X2: Summary of Tailoring Considerations”

PMBOK Guide, 7th edition, page 77, section 2.2.26, “Appendix X3: Summary of Tools and Techniques”

PMBOK Guide, 7th edition, page 79, section 2.2.27, “Appendix X4: Summary of Agile, Iterative, Adaptive, and Hybrid Approaches”

PMBOK Guide, 7th edition, page 81, section 2.2.28, “Appendix X5: Contributors and Reviewers”

PMBOK Guide, 7th edition, page 83, section 2.2.29, “Appendix X6: PMI Code of Ethics and Professional Conduct”

PMBOK Guide, 7th edition, page 85, section 2.2.30, “Appendix X7: Application Area Extensions”

PMBOK Guide, 7th edition, page 87, section 2.2.31, “Appendix X8: Summary of Changes”

PMBOK Guide, 7th edition, page 89, section 2.2.32, “Introduction”

PMBOK Guide, 7th edition, page 91, section 2.2.33, “Performance Domain: Stakeholders”

PMBOK Guide, 7th edition, page 93, section 2.2.34, “Performance Domain: Team”

PMBOK Guide, 7th edition, page 95, section 2.2.35, “Performance Domain: Development Approach and Lifecycle”

PMBOK Guide, 7th edition, page 97, section 2.2.36, “Performance Domain: Planning”

PMBOK Guide, 7th edition, page 99, section 2.2.37, “Performance Domain: Project Work”

PMBOK Guide, 7th edition, page 101, section 2.2.38, “Performance Domain: Delivery”

PMBOK Guide, 7th edition, page 103, section 2.2.39, “Performance Domain: Measurement”

PMBOK Guide, 7th edition, page 105, section 2.2.40, “Performance Domain: Uncertainty”

PMBOK Guide, 7th edition, page 107, section 2.2.41, “Closing”

PMBOK Guide, 7th edition, page 109, section 2.2.42, “Models, Methods, and Artifacts”

The project manager is responsible for ensuring that the project team has the necessary skills and competencies to perform the project work. If there are knowledge gaps in the team, the project manager should communicate the situation to the team and plan for the appropriate training and coaching arrangements to address them. This will help the team to improve their performance and achieve the desired results. The other options are not appropriate because they do not address the root cause of the problem and may have negative consequences for the project. Reporting the situation to upper management and requesting a scope change may not be feasible or acceptable. Hiring new team members and laying off existing ones may disrupt the team dynamics and morale. Communicating the situation to the customer and informing them about potential delays may damage the trust and relationship with the customer. References:

PMBOK Guide 6th Edition, page 335, section 9.2.2.3

PMP Exam Prep, page 265, section 9.2

Disclaimer: This answer is generated by Copilot, an AI companion. It is not intended to be a substitute for professional advice or guidance. Copilot does not guarantee the accuracy, completeness, or validity of the answer. The user is solely responsible for verifying the answer and using it at their own risk. Copilot is not affiliated with PMI or any other organization.

According to the PMBOK Guide, change requests are inevitable in any project and should be managed through an integrated change control process. This process involves analyzing the impact of the change on the project objectives, scope, schedule, cost, quality, risk, and other factors, and then deciding whether to approve or reject the change. If the change is approved, the project manager should update the project management plan and other relevant documents accordingly. The project manager should also communicate and negotiate with the stakeholders, especially the client, about the impact of the change and the possible trade-offs or alternatives. The project manager should not instruct the team to accommodate the changes without proper analysis and approval, as this would violate the project management plan and the agreed scope. The project manager should not review the project charter to identify the agreed scope, as this would not address the issue of the change requests and their impact on the project. The project charter is a high-level document that authorizes the project and defines its objectives, scope, and key stakeholders, but it does not provide the details of how the scope will be managed and controlled. The project manager should not escalate the issue to senior management, as this would imply that the project manager is unable to handle the change requests and their impact on the project. The project manager should only escalate the issue if the change requests are beyond the project manager’s authority or responsibility, or if the client is unreasonable or uncooperative. References: PMBOK Guide, 7th edition, pages 112-113, 118-119, 122-123; Project and Process Tailoring for the PMP® Exam

When a project experiences a delay, it’s crucial to reassess the project plan and identify options to meet stakeholders’ expectations. This involves revisiting the scope and quality of the project. The project manager should explore all possible options to deliver the project within the constraints. This could involve adjusting the project schedule, reallocating resources, or identifying efficiencies in the project processes. It’s important to communicate these changes and their potential impact to all stakeholders. References: PMBOK Guide, 6th Edition, Section 6.7 Control Schedule

According to the PMBOK Guide, project selection is based on the alignment of the project with the organization’s strategic objectives, which include maximizing the business value1. Business value is the net benefit that a project provides to the stakeholders, considering both tangible and intangible factors2. Projects that maximize the business value are more likely to contribute to the organization’s success and sustainability than projects that focus only on duration, revenue, or risk3. References: 1: PMBOK Guide, 7th edition, page 35 2: PMBOK Guide, 7th edition, page 38 3: Project Selection Methods: A Primer for the Project Manager4QUESTION NO: 26

A product owner Goes not regularly attend demonstration ceremonies. As a result, the demonstration ceremonies are constantly rescheduled and the work is impacted in multiple ways. The project manager believes the product owner Is not committed to the project.

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

A. Defined a set of external audits that can expose this situation to the project sponsor

B. Agreed with the product owner on appropriate project governance levels

C. Set a definition of done (DoD) that considers the work as done if not otherwise specified

D. Asked another product owner to attend the demonstrations on behalf of the product owner

Answer: B

According to the PMBOK Guide, project governance is the framework, functions, and processes that guide project management activities in order to create value and meet organizational objectives. Project governance also defines the roles and responsibilities of the project stakeholders, including the product owner, who is the person or group that is responsible for defining and prioritizing the product backlog and accepting the product increments1.

One of the principles of agile project management, as described in the Agile Practice Guide, is to collaborate with customers and stakeholders frequently and throughout the project. This principle implies that the product owner should be actively involved in the project and provide timely feedback and guidance to the project team. The product owner should also attend the demonstration ceremonies, which are events where the project team showcases the product increments to the product owner and other stakeholders and collects their feedback2.

Therefore, the project manager should have agreed with the product owner on appropriate project governance levels, which means defining the expectations, commitments, and communication channels between the project team and the product owner. This would have helped to avoid the situation where the product owner does not regularly attend the demonstration ceremonies and causes delays and disruptions to the project. By agreeing on the project governance levels, the project manager and the product owner could have established a mutual understanding of the value and importance of the demonstration ceremonies and the product owner’s role and responsibility in them.

According to the PMBOK Guide, the project quality control process consists of determining quality requirements for project deliverables and testing, inspecting and reporting to make sure they’re met1. If the project manager realizes that the quality management plan does not include how the final user will perceive the benefits of the new product compared with the actual product, they should submit a change request to analyze a new set of quality tests. This is because the final user tests are part of the user acceptance testing (UAT), which is the final testing stage in software development before production2. UAT is used to get feedback from users who test the software and its user interface (UI) and to verify that the software meets the end-user requirements and expectations2. UAT is usually done manually, with users creating real-world situations and testing how the software reacts and performs2. Therefore, the project manager should not let the product go to market and wait for customer feedback regarding quality (option A), as this would be too late and risky to address any quality issues. The project manager should also not ask the quality manager or the product manager to include the final user tests in the quality management plan (options B and D), as this would be a change to the scope and the schedule of the project, which requires a formal change request and approval from the change control board3. The quality management plan is a document that helps the project manager and the project team execute quality management and quality assurance actions, and it should be aligned with the project management plan4. Any changes to the quality management plan should follow the change management process4. References: 1: Quality Control in Project Management | monday.com Blog 2: What Is User Acceptance Testing (UAT)? - Codecademy 3: The Quality Control Process - ProjectEngineer 4: The Quality Management Plan in Project Management

The RFP is a document that solicits proposals from potential suppliers by describing the project scope, requirements, and evaluation criteria. It is important to ensure that the RFP is clear, accurate, and legally sound to avoid misunderstandings, conflicts, and disputes with the suppliers. Asking the legal team to review the RFP can help the project manager mitigate this risk by ensuring that the RFP complies with the relevant laws, regulations, and contractual terms, and that it protects the interests and rights of both parties12.

The other options are not as effective or relevant for mitigating this risk:

B. Ask the project team to submit the RFP: The project team may not have the necessary expertise or authority to prepare or approve the RFP. Asking the project team to submit the RFP may result in delays, errors, or inconsistencies in the RFP, which could increase the risk of disputes with the suppliers3.

C. Request approval of the RFP from the project sponsor: The project sponsor is the person or group who provides the financial resources and support for the project. The project sponsor may not be directly involved in the procurement process or have the legal knowledge to review the RFP. Requesting approval of the RFP from the project sponsor may not address the risk of disputes with the suppliers, and may also create unnecessary bureaucracy or dependency.

D. Request approval of the RFP from management: Management is the group of individuals who direct and control the organization. Management may not have the time, interest, or expertise to review the RFP. Requesting approval of the RFP from management may not mitigate the risk of disputes with the suppliers, and may also cause delays, conflicts, or micromanagement.

The project manager should compare the achieved results to the contract requirements before obtaining financial, legal, and administrative approval to close the project and transfer the liability. This is because the project manager needs to ensure that the supplier has fulfilled all the contractual obligations and delivered the agreed scope, quality, and performance standards. The project manager should also verify that the supplier has completed all the required documentation, testing, training, and warranty services. The project manager should also review the lessons learned, feedback, and satisfaction surveys from the supplier and the project team. This will help the project manager evaluate the supplier’s performance, identify any issues or disputes, and resolve them before making the final payment and closing the project. The project manager should also communicate with the supplier and the relevant stakeholders about the project closure and the transfer of liability. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 12.3.1, “Close Procurements: Inputs”

PMBOK® Guide, 6th edition, Section 12.3.2, “Close Procurements: Tools and Techniques”

PMBOK® Guide, 6th edition, Section 12.3.3, “Close Procurements: Outputs”

PMI-PBA® Guide, 1st edition, Section 6.4.1, “Evaluate Solution: Inputs”

PMI-PBA® Guide, 1st edition, Section 6.4.2, “Evaluate Solution: Tools and Techniques”

PMI-PBA® Guide, 1st edition, Section 6.4.3, “Evaluate Solution: Outputs”

According to the PMBOK Guide, building trust is one of the intangible stakeholder engagement qualities that project managers should embrace to manage relationships with stakeholders. Building trust means establishing and maintaining a positive and respectful relationship with stakeholders based on honesty, transparency, reliability, and mutual understanding. By allowing team members to attend the weekly progress meeting either from home or the office, the project manager is demonstrating trust in their ability to work effectively and communicate clearly regardless of their location. This can also enhance the team members’ trust in the project manager and their commitment to the project objectives. References: PMBOK Guide, 7th edition, page 273; 10 Principles Of Stakeholder Engagement

 The project manager should conduct a consensus-building session to decide how to approach the next set of work, as this is a collaborative decision-making technique that involves the participation of all team members and stakeholders. The project manager should facilitate the discussion, clarify the objectives, identify the options, evaluate the pros and cons, and reach a mutually acceptable agreement. This will help to resolve the conflict, align the expectations, and ensure the commitment of the team and the stakeholders. The other options are not the first actions that the project manager should take, as they may either delay the decision, bypass the team’s input, or ignore the conflict. References:

[PMBOK Guide], 6th edition, pages 56-57, 376-377, 513-514.

[Professional in Business Analysis (PMI-PBA) Handbook], pages 15-16, 19-20.

According to the PMBOK® Guide, the project manager should ensure that the project benefits are aligned with the business objectives and the needs of the intended users1. One of the best ways to achieve this is to conduct a review with a representative group of users who can provide feedback on the program’s functionality, usability, and value2. This can help the project manager validate the program’s benefits, identify any gaps or issues, and implement any changes or improvements before releasing the program to the public3.

Option A is not the best answer because testing the program only ensures its quality, but not its benefits. Testing the program may reveal technical errors or defects, but it may not capture the user’s perspective or satisfaction4. Option C is not the best answer because meeting with government officials may ensure the program’s compliance, but not its benefits. Meeting with government officials may help the project manager understand the policy requirements and regulations, but it may not reflect the user’s expectations or preferences5. Option D is not the best answer because documenting the features and updating the specifications only ensures the program’s scope, but not its benefits. Documenting the features and updating the specifications may help the project manager control the program’s deliverables, but it may not measure the program’s outcomes or value6. References: 1 PMBOK® Guide, 6th edition, page 332 PMBOK® Guide, 6th edition, page 1503 PMBOK® Guide, 6th edition, page 1234 PMBOK® Guide, 6th edition, page 2875 PMBOK® Guide, 6th edition, page 396 PMBOK® Guide, 6th edition, page 141.

 According to the Project Management Body of Knowledge (PMBOK), one of the key responsibilities of a project manager is to ensure that lessons learned from previous projects are applied to current projects. This helps to avoid repeating the same mistakes and to leverage successful strategies. In this scenario, the project manager should share the lessons learned from the previous project with the team member. This will not only help to resolve the current issue more efficiently but also contribute to the team member’s learning and development. References: PMBOK Guide, 6th Edition, Section 4.4.3.1 - Lessons Learned Register

According to the PMBOK Guide, the project manager should assess the situation to understand how the organization’s culture impacts the decision-making process, and coach the team toward a new model. This is because the project manager is responsible for facilitating the team’s decision-making process and ensuring that it aligns with the agile principles and values1. The project manager should also consider the following factors that may affect the team’s decision-making process2:

The level of empowerment and autonomy given to the team by the organization and the stakeholders

The degree of collaboration and communication among the team members and with other parties

The availability and quality of information and data to support the decision-making process

The complexity and uncertainty of the project environment and the product requirements

The time and resource constraints and the impact of delays on the project outcomes

The potential risks and opportunities associated with the decisions and the alternatives

The feedback and learning mechanisms to evaluate and improve the decision-making process

The project manager should coach the team toward a new model of decision-making that is more agile and adaptive, such as the following3:

Decentralized decision-making: The team members are empowered to make decisions within their scope of work and authority, without waiting for approval from higher levels of management. This can increase the team’s speed, efficiency, and ownership of the decisions.

Collaborative decision-making: The team members work together to make decisions that benefit the project and the stakeholders, rather than competing or conflicting with each other. This can enhance the team’s creativity, innovation, and quality of the decisions.

Data-driven decision-making: The team members use empirical evidence and data to support their decisions, rather than relying on assumptions or opinions. This can improve the team’s accuracy, reliability, and transparency of the decisions.

Iterative decision-making: The team members make decisions in small increments and cycles, rather than in large batches and phases. This can allow the team to adapt to changing conditions and feedback, and to deliver value early and frequently.

Value-based decision-making: The team members make decisions that maximize the value delivered to the customer and the stakeholders, rather than focusing on the cost or the schedule. This can ensure the team’s alignment with the project vision and goals.

 According to the PMBOK Guide, project completion involves verifying that all the project deliverables meet the acceptance criteria and obtaining formal acceptance from the customer. Sometimes, the customer may request changes or modifications to the deliverables, which may affect the project scope, schedule, cost, or quality. In such cases, the project manager should negotiate with the customer to reach a mutually satisfactory agreement that balances the project objectives and the customer expectations. Negotiation is the process of conferring with others to come to terms with them or reach an agreement. The first step in negotiation is to analyze the bounds of the negotiation, which means to identify the best alternative to a negotiated agreement (BATNA), the worst alternative to a negotiated agreement (WATNA), and the zone of possible agreement (ZOPA) for both parties. BATNA is the most advantageous alternative course of action a party can take if negotiations fail and an agreement cannot be reached. WATNA is the worst outcome that a party can expect if negotiations fail. ZOPA is the range of possible outcomes within which an agreement can be reached by both parties. By analyzing the bounds of the negotiation, the project manager can determine the minimum and maximum acceptable outcomes for both parties, and use them as a reference point for making offers and counteroffers. This can help the project manager to avoid deadlock, impasse, or unfavorable outcomes, and to achieve a win-win situation. Therefore, option A is the best answer. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 4: Project Integration Management, pages 123-124

PMBOK Guide, 6th edition, Chapter 12: Project Procurement Management, pages 481-482

PMP Exam Questions | 100% Free PMP Example Questions

The alignment between the project team and stakeholders is crucial for the success of a project. This alignment must be maintained throughout the project’s life cycle, ensuring clarity of scope, risk, schedule, and price at each phase1. In a hybrid project management approach, risks should be reviewed during each iteration and review to ensure alignment between the project team and stakeholders2. This allows for timely identification and mitigation of risks, ensuring that all parties are aware of potential risks and their outcomes2. Regular reviews also facilitate open communication and collaboration, which are key to successful risk management3.

When a project manager identifies that the response action for an issue is insufficient, it is crucial to take immediate action to prevent further complications. The best course of action in this scenario is to meet with the project team to find another solution1. This approach ensures that all team members are aware of the issue and can contribute their expertise and ideas to resolving it. It also promotes transparency and collaboration within the team1. The other options (A, B, C) are also important steps in issue management, but they are not the immediate next steps when a response action has proven to be insufficient2. References: 12

In project management, especially in an agile environment, collaboration and communication are key. When there is a delay in the validation and release of a product due to other priorities, the project manager should work with the IT team to prioritize the tasks. This approach promotes teamwork, ensures everyone is on the same page, and helps to address the issue in a constructive manner. Escalating the issue (option A) might not be the best initial approach as it could create unnecessary tension. Delivering the features without validation (option C and D) could lead to quality issues and is generally not a good practice. References: PMBOK Guide, 6th Edition, Section 9.3.2.1: Team Charter

The graph shows that the project is performing below the baseline for both schedule and cost, which means it is behind schedule and under budget. This indicates that the project is not meeting its planned progress and deliverables, and may have some issues with scope, quality, or resources. The project manager should review the project schedule to identify the root causes of the delays, and take corrective actions to bring the project back on track. The project manager should also monitor the project cost to ensure that it does not exceed the budget, and communicate the status and changes to the stakeholders. References:

PMBOK Guide, 7th Edition, Chapter 8: Performance Measurement and Reporting1

The PMI Guide to Business Analysis, Chapter 5: Planning Business Analysis Work2

Business Analysis for Practitioners: A Practice Guide, Chapter 4: Elicitation and Collaboration3

According to the PMBOK Guide, 6th Edition, Section 9.2.2.1, “Resource calendars specify the availability, capability, and skills of human resources and the availability of equipment and materials.” The project manager should consult the company’s resource calendars to determine the availability and suitability of the resources required for the new project. This will help the project manager to estimate the duration, cost, and risk of the project, as well as to plan the resource allocation and management. The other options are not as relevant or accurate as the resource calendars for this purpose. The company’s historical organizational project artifacts may provide some useful information, but they may not reflect the current situation or the specific needs of the new project. The company’s project responsibility assignment matrix (RAM) may show the roles and responsibilities of the project team members, but it may not indicate their availability or skills. The company’s resource management plan may describe the policies and procedures for managing resources, but it may not provide the details of the individual resources required for the new project. References:

PMBOK Guide, 6th Edition, PMI, 2017, pp. 336-337.

How to Measure Your Project Resource Requirements, MetaPM, 2024, accessed on February 24, 2024.

The project charter is a document that formally authorizes a project or a phase and documents initial requirements that satisfy the stakeholder’s needs and expectations. It provides the project manager with the authority to apply organizational resources to project activities. When a new project manager is assigned to a project, they should refer to the project charter to understand the project objectives, key stakeholders, risks, and the authority delegated to them. References: Project Management Professional (PMP) Reference Materials12.

The project manager should plan a communication method and allow the project team members to virtually interact. This will help to facilitate effective communication, information sharing, feedback, and coordination among the remote project team members. The project manager should also consider the cultural, linguistic, and time zone differences among the team members and use appropriate tools and techniques to overcome the challenges of virtual collaboration. Discussing the concerns with the project sponsor, modifying the project charter, creating a social media group platform, and setting the ground rules are all possible actions that the project manager can take, but they are not the best answer to the question, as they do not directly address the issue of collaboration between the remote project team members. References: = PMBOK Guide, 6th edition, pages 366-367, 378-379, 555-556; Agile Practice Guide, pages 28-29, 32-33; PMP Exam Content Outline, 2020, pages 6-7.

 The project manager is responsible for ensuring that the project complies with all the applicable laws, regulations, standards, and policies of the project location. This includes health and safety requirements, environmental protection, labor laws, permits, licenses, and any other legal obligations. Failing to comply with these requirements could result in legal penalties, fines, sanctions, reputational damage, or project termination. Therefore, the project manager should address this issue as soon as possible and update the project plan accordingly. Injury or loss incidents could delay project deliverables, but this is not the primary reason why the situation is problematic. It is imperative that established performance metrics are met, but this is not directly related to the health and safety requirements. The project manager must follow their employer’s organizational process assets (OPAs), but this does not necessarily mean that they are aligned with the project location’s regulatory requirements. References: = PMBOK Guide, 6th edition, pages 33-34, 89-90, 123-124, 375-376; PMP Exam Content Outline, 2020, pages 8-9.

The project manager should prepare a weekly status report and share it with executive management every week to keep them informed of the project’s progress and performance. This will help to address their concerns and expectations, as well as to provide them with relevant information for decision making. The status report should include key metrics such as schedule, cost, scope, quality, risks, and issues, as well as any changes or deviations from the baseline. The project manager should also communicate the benefits and value of the agile approach, and how it aligns with the project objectives and customer needs12. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 10.4.3.1, page 387

Agile Practice Guide, Chapter 3.3, page 37

 The project manager should perform iterative planning with the team to use the prototype, as this would allow them to adapt to the changing situation and deliver value incrementally. Iterative planning is a technique that involves breaking down the project scope into smaller iterations, each with its own plan, deliverables, and feedback loops. This technique enables the project team to respond to uncertainties, risks, and changes more effectively, and to incorporate lessons learned and stakeholder feedback into the next iteration. In this case, the project manager can use iterative planning to align the team with the new solution, define the requirements and acceptance criteria for the prototype, and monitor and control the integration and testing of the prototype. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide 7th Edition, page 67, section 3.2.2

PMI Agile Practice Guide, page 33, section 3.2.1

PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 14, section 3.3.1.1

 The project manager should evaluate the current effectiveness of the team and define development needs. This is the best option because it allows the project manager to identify the gaps in the team’s skills and knowledge, as well as the opportunities for improvement and learning. By evaluating the team’s performance, the project manager can also provide feedback, recognition, and support to the team members, as well as foster a positive team culture. This option also aligns with the PMBOK® Guide’s guidance on managing project team, which includes assessing team members’ skills, providing training, and enhancing team competencies1.

The other options are not as effective as option B. Option A is not the project manager’s responsibility and may undermine the team’s autonomy and trust. Option C is not realistic and may lead to poor quality and inefficiency. Option D is not flexible and may ignore the team’s preferences and potential. References: 1: PMBOK® Guide, 6th edition, page 349

According to the PMBOK Guide, servant leadership is a key aspect of agile project management. It is a leadership style where the leader, rather than seeking to be served, prioritizes the needs and development of their team members1. Servant leaders help their teams to self-organize, collaborate, and adapt to changing requirements and environments2. One of the practices that support servant leadership in agile project management is the daily standup, also known as the daily scrum. It is a short, time-boxed meeting where the team members synchronize their work and plan for the next 24 hours. The daily standup also provides an opportunity for the team members to share their impediments, risks, and issues, and for the servant leader to facilitate the removal of those obstacles34. By implementing daily standups, the project manager can foster a culture of transparency, feedback, and continuous improvement among the team members, and help them achieve their project goals more effectively and efficiently5. References: 1: PMBOK Guide, 7th edition, page 55 2: A Little Bit of Both1 3: Guide on Servant Leadership in Agile Project Management3 4: 7 Traits of Servant Leadership in Agile Project Management4 5: How to create a project management communication plan5

According to the PMBOK® Guide, a project manager should be able to plan and manage the project schedule, taking into account the availability and capacity of resources, as well as the project constraints and assumptions. When a project involves multiple international locations, the project manager should also consider the cultural and environmental factors that may affect the project performance, such as holidays, working hours, communication preferences, and legal requirements. In this scenario, the project manager realized that some of the key activities were scheduled over the holiday periods in the overseas offices, which caused delays in the project. The project manager should update the schedule to reflect the holidays and share the workload among offices to mitigate schedule slippage. This option demonstrates the project manager’s ability to adjust the schedule based on the actual resource availability and to balance the resource allocation across different locations. Updating the schedule and sharing the workload may also help to maintain the team’s morale and productivity, as well as the stakeholder’s satisfaction. Hiring additional personnel on a temporary basis, requesting that the offices in overseas locations work overtime, or notifying the project sponsor of the delayed completion are not effective or appropriate actions to take in this situation. These options may incur additional costs, risks, or conflicts, and may not address the root cause of the problem. They may also indicate a lack of planning, communication, or collaboration skills on the part of the project manager. References: PMBOK® Guide, 6th edition, pages 191-192, 267-268, 349-350.

 This is the best option because it addresses the root cause of the problem, which is the unclear product requirements. By analyzing the problem with both teams, the project leader can facilitate communication, collaboration, and alignment between them. This can help to clarify the product vision, prioritize the backlog, and identify any gaps or errors in the work done so far. This can also help to improve the quality of the product and the satisfaction of the stakeholders.

The other options are not as effective because they do not address the underlying issue or they may create more problems. For example:

B. Selecting new team members may disrupt the existing team dynamics and introduce more uncertainty and confusion. It may also delay the project and increase the cost.

C. Demanding that the business team define final requirements may create conflict and resentment between the teams. It may also be unrealistic or impractical to expect final requirements in a complex and changing environment.

D. Telling the teams to continue following the initial plan may result in wasted time and resources, as well as low-quality outcomes. It may also ignore the feedback and learning from the previous sprints.

According to the PMBOK Guide, an issue is “a point or matter in question or in dispute, or a point or matter that is not settled and is under discussion or over which there are opposing views or disagreements” (p. 720). Issues can arise from any aspect of the project, such as changes, risks, quality, stakeholders, etc. The issue log is a project document that records and tracks the issues that affect the project, along with their status, resolution, and ownership. The issue log is updated throughout the project as new issues are identified, analyzed, and resolved.

In this question, the change in environmental regulations is an external factor that could affect the project scope, schedule, cost, quality, or other aspects. Therefore, it is an issue that needs to be documented and tracked in the issue log. The project manager should update the issue log as an immediate action to ensure that the issue is properly addressed and communicated to the relevant stakeholders. Updating the issue log will also help the project manager to monitor and control the project performance and take corrective or preventive actions as needed.

Updating the project baseline, the risk management plan, or the change request log are not immediate actions that the project manager should take in this situation. The project baseline is the approved version of the project scope, schedule, and cost that serves as a reference for measuring and reporting the project performance. The project baseline can only be changed through the formal change control process, which requires a change request. The risk management plan is a subsidiary plan of the project management plan that describes how risk management activities will be planned, implemented, and monitored throughout the project. The risk management plan can also be changed through the change control process, if necessary. The change request log is a project document that records and tracks the change requests that are submitted, reviewed, approved, or rejected during the project. A change request is a formal proposal to modify any document, deliverable, or baseline of the project.

The project manager may need to update the project baseline, the risk management plan, or the change request log later, after analyzing the impact of the issue and determining the appropriate response. However, these are not immediate actions that the project manager should take before updating the issue log. References:

PMBOK Guide, 6th edition, Project Management Institute, 2017, pp. 123, 129, 152, 456, 720.

PMP Sample Test Questions, Project Management Institute, 2019, p. 15.

minimum viable product (MVP) is a version of a product that has enough features to satisfy early customers and provide feedback for future development1. The project manager should use an MVP to validate the customer requirements and test the assumptions and hypotheses about the product value and feasibility2. An MVP can help the project manager to learn from the customer feedback and make adjustments to the product scope and design3. Creating product documentation, a survey, or a prototype with all features are not as effective as an MVP in validating the customer requirements and obtaining feedback. References:

1: PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Project Management Institute Inc., 2021, p. 177.

2: PMI, The Standard for Project Management – Seventh Edition, Project Management Institute Inc., 2021, p. 63.

3: PMI, Agile Practice Guide, Project Management Institute Inc., 2017, p. 36.

A relative-weighting approach is a technique that assigns numerical values to the benefits and costs of each product feature, and then calculates a score for each feature by dividing the benefits by the costs. The features with the highest scores are considered the most valuable and are prioritized accordingly. This technique is part of the Collect Requirements process, which involves defining and documenting the stakeholders’ needs and expectations for the project outcome1. To perform this technique effectively, the project manager should ask the team to perform collaborative work that is coordinated by the project manager. This will ensure that the team members share their inputs, opinions, and preferences, and that the project manager facilitates the process and resolves any conflicts or issues. Relying on the expert judgment of the product owner, using a market-based strategy, or engaging the project sponsor are not the best options, as they may not reflect the views and needs of all the stakeholders, or they may introduce bias or external influences into the prioritization process. References: 1 PMBOK® Guide, 6th edition, page 140.

The project manager should review the user roles and update the team charter to ensure that the project team members have clear and balanced responsibilities and expectations for each release. This will help to improve the team performance, collaboration, and accountability. Documenting the risk register, speaking to the customer, and involving the product owner are not directly related to the problem of uneven workload distribution among the team members. References:

PMP Exam Content Outline, Domain II: Process, Task 2: Manage project artifacts and ensure they meet the needs and expectations of key stakeholders.

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 9: Project Resource Management, Section 9.1: Plan Resource Management, Page 313.

Professional in Business Analysis (PBA) Certification Exam Outline, Domain III: Analysis, Task 3: Define Requirements Architecture, Page 13.

 According to the PMBOK Guide, a change request is a formal petition for change in a project. It’s a document that explains what are the changes to be made and the main reasons why they should be implemented1. Change requests can either be submitted by internal or external project stakeholders. When a project manager realizes that some operational project requirements were not captured in the project scope of work, they should issue a change request to include the additional scope, and track the completion of the work items. This is the best way to ensure that the project deliverables meet the customer’s needs and expectations, and that the project scope is aligned with the project objectives. The other options are not the best actions to take in this situation. Issuing a change request to remove items from the scope of work and keep the project on schedule (option A) may compromise the quality and value of the project deliverables, and may result in customer dissatisfaction or rejection. Documenting the issue in the lessons learned document, and discussing this with the project sponsor (option C) may be helpful for future projects, but it does not address the current issue or resolve the gap in the project scope. Arranging to pass the cost to the operational area since the customer will benefit (option D) may create conflicts and resentment among the project stakeholders, and may violate the project budget and contract terms. References: PMBOK Guide, 6th edition, pages 115-116, 123-124.

The first thing that the project manager should do is to review the communications management plan, which is the document that describes how the project information will be communicated to the stakeholders. The project manager should check if the stakeholder’s communication requirements, preferences, and expectations are identified and addressed in the plan. If not, the project manager should update the plan accordingly and ensure that the stakeholder receives the appropriate project status reports. The other options are not the best first actions, as they either do not address the root cause of the problem (lack of communication), or they are premature or unnecessary (updating the stakeholder register or the project management plan). References: PMBOK Guide, page 377-378; PMP Sample Test Questions, question 43

According to the Agile Practice Guide, one of the principles of agile project management is to "build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done."1 Therefore, the project manager should not ignore, punish, or override the team member who has a different opinion, but rather try to understand their perspective and work with them to reach a consensus. This can foster a positive team culture and improve the quality of the sprint goals. References: 1: Agile Practice Guide, page 10.

The project manager should agree on the criteria to prioritize risks before developing a risk response strategy. This is because not all risks have the same level of impact or probability on the project objectives, and therefore require different levels of attention and response. By agreeing on the criteria to prioritize risks, such as expected monetary value, risk score, risk urgency, or stakeholder tolerance, the project manager can rank the risks according to their importance and focus on the ones that pose the most threat or opportunity to the project. This will help the project manager allocate resources, time, and budget more effectively and efficiently to address the risks. The project manager should also involve the relevant stakeholders, such as sponsors, SMEs, and team members, in the risk prioritization process to ensure their input and buy-in. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 11.4.1, “Perform Qualitative Risk Analysis: Inputs”

PMBOK® Guide, 6th edition, Section 11.4.2, “Perform Qualitative Risk Analysis: Tools and Techniques”

PMBOK® Guide, 6th edition, Section 11.4.3, “Perform Qualitative Risk Analysis: Outputs”

PMI-PBA® Guide, 1st edition, Section 5.3.1, “Prioritize Requirements: Inputs”

PMI-PBA® Guide, 1st edition, Section 5.3.2, “Prioritize Requirements: Tools and Techniques”

PMI-PBA® Guide, 1st edition, Section 5.3.3, “Prioritize Requirements: Outputs”

According to the PMBOK Guide, 6th edition, section 4.5.3.1, the project manager is responsible for monitoring and controlling the project work and ensuring that the project is aligned with the business objectives and benefits. The project manager should also communicate the project performance and status to the relevant stakeholders and address any issues or concerns that arise from the project execution. In this scenario, the project manager should first review the established project benefits tracking metrics to assess the current state of the project and compare it with the expected outcomes and success criteria. This will help to identify any gaps or deviations and determine the appropriate actions to take. The other options are either premature or irrelevant, as they do not address the root cause of the problem or respect the authority and scope of the project manager. References: PMBOK Guide, 6th edition, section 4.5.3.1, page 122.

 The project manager should raise a new issue in the issue log and convene SMEs and relevant stakeholders to identify alternatives to address the problem. This is because the inability of the subcontractor to supply a key component is an issue that has already occurred and needs to be resolved as soon as possible. The issue log is a tool for documenting and monitoring the resolution of issues that arise during a project1. The project manager should also involve the SMEs and relevant stakeholders who have the expertise and authority to provide input and guidance on how to deal with the issue. The project manager should not discuss the issue with the project sponsor and request extra time and budget to obtain the component from a different supplier, as this would be premature and may not be the best option. The project manager should not raise a new risk in the risk register, perform a risk assessment, and convene SMEs and relevant stakeholders to plan a risk response, as this would be appropriate for a potential problem that has not yet occurred, not an actual issue that has already happened. The project manager should not submit a change request to the CCB for changes to the performance measurement baseline to obtain the component from a different supplier, as this would be a formal process that requires approval and may not be necessary if the issue can be resolved in other ways. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 4.6.1.1, “Issue Log”

 The project manager should communicate individually with the affected team members to negotiate the decision and confirm their willingness to relocate, as this is the most respectful and ethical way to handle the situation. Relocating team members abroad for six months is a major change that will affect their personal and professional lives, and the project manager should consider their needs, preferences, and concerns before making any final decisions. The project manager should also explain the rationale and benefits of the relocation, and offer any support or incentives that may facilitate the transition. Communicating to the whole team, the HR department, or the team members’ manager may not be appropriate or sufficient, as the project manager should first consult with the team members directly and obtain their consent. These other communication options may also create unnecessary confusion, resentment, or resistance among the team members or other stakeholders. References: PMBOK Guide, 7th edition, pages 111, 112, 113, 114.

According to the PMBOK Guide, the project manager is responsible for ensuring that the project delivers the expected business value and benefits. If the project manager acquires information that indicates a significant reduction in the business value of the project, they should communicate this information to the project sponsor and other key stakeholders, and recommend a reassessment of the project business case and viability. The project sponsor is the ultimate authority to decide whether to continue, cancel, or change the project based on the updated information and analysis. Removing items from the backlog, continuing with the defined scope, or canceling the project without consulting the sponsor are not appropriate actions for the project manager to take in this situation. References: = PMBOK Guide, 7th edition, page 23; PMI, Project Management Professional (PMP) Examination Content Outline, 2021, page 6.

The project manager should conduct a customer demonstration at the end of each build cycle to help the client understand the value delivered during project execution. This is a common practice in agile projects, where the team showcases the working product increment to the customer and solicits feedback. This way, the customer can see the tangible results of each iteration, validate the alignment with their expectations, and provide input for future improvements. This option aligns with the PMI-PBA practice guide, which states that “demonstrations are a key technique for validating requirements and obtaining feedback from stakeholders” (p. 67). The other options are not the best choices because they do not effectively communicate the value of the product to the customer. Including a planned value (PV) calculation in the sprint report for each build cycle (option A) may provide a quantitative measure of the project performance, but it does not show the actual functionality or quality of the product. Providing the customer with the refined specification during each build cycle (option C) may reflect the changes or clarifications made to the technical requirements, but it does not demonstrate the working product or its benefits. Showing the customer a sprint burndown chart for each build cycle (option D) may indicate the progress and velocity of the team, but it does not reveal the features or value of the product. References:

PMI-PBA Practice Guide, p. 67 1

PMBOK Guide, 6th edition, p. 189 2

 According to the PMBOK® Guide, the project vision is a high-level description of the project’s purpose, scope, and objectives. It provides the direction and alignment for the project team and stakeholders. The project vision should be clear, concise, inspiring, and consistent with the organization’s strategy. When the scope has changed significantly and the product owner has been replaced multiple times, the project vision may become unclear or outdated. The team members may feel disassociated from the project and lose motivation and engagement. To ensure team alignment with the goals, the project manager should facilitate a discussion of the vision for the project, involving the new product owner and the team members. This will help to clarify the project’s value proposition, expected outcomes, and success criteria. It will also help to reestablish trust, collaboration, and commitment among the team and the product owner. Asking the new product owner to explain the importance of the project, emailing the team a detailed outline of the business requirements, or reviewing the project charter with the team are not sufficient or effective ways to ensure team alignment with the goals. These options may not address the underlying issues of the team’s disassociation, such as lack of involvement, ownership, or empowerment. They may also not reflect the current state of the project or the organization’s strategy. References: PMBOK® Guide, 6th edition, pages 30-31, 89-90.

 A hybrid approach is a combination of agile and predictive methods that can be applied to different phases or modules of a project. A hybrid approach can be suitable for a project that has both uncertain and certain aspects, such as a long research process followed by incremental delivery of complex equipment. A hybrid approach can allow the project manager to adapt to changing requirements and customer feedback in the agile part, while ensuring quality and control in the predictive part. A hybrid approach can also balance the benefits and challenges of both agile and predictive methods, such as flexibility, speed, risk, scope, and stakeholder satisfaction. References: PMBOK Guide 7th Edition, Chapter 2.2.2; Agile Practice Guide, Section 2.1.2.