Pass the PMI Project-Management-Professional PMP Questions and answers with CertsForce

 According to the PMBOK® Guide, stakeholder engagement is the process of communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement in project activities throughout the project life cycle1. The project manager should proactively engage with stakeholders to understand their interests, needs, expectations, and influence on the project, and to manage any conflicts or issues that may arise2.

In this scenario, the project manager is facing a situation where an important stakeholder is dissatisfied with the way the project is being executed and threatens to withdraw support for the project. This could have a negative impact on the project’s success, as the stakeholder may have a high level of power, interest, or influence on the project. The best way to handle this situation is to approach the stakeholder to address the concerns and resolve the issue. The project manager should use effective communication skills, such as active listening, empathy, and feedback, to understand the stakeholder’s perspective and expectations, and to explain the project’s status, progress, and performance. The project manager should also use negotiation and problem-solving techniques to reach a mutually acceptable agreement with the stakeholder and to restore trust and confidence in the project.

Option B is not the best answer because it does not directly address the stakeholder’s concerns or the root cause of the issue. Consulting the risk management plan may help the project manager identify and analyze the potential risks and responses related to stakeholder engagement, but it does not provide a solution or improvement to the current situation. Option C is not the best answer because it does not demonstrate the project manager’s responsibility or accountability for the project. Escalating the issue to the project management office (PMO) may help the project manager obtain guidance or support from the PMO, but it does not ensure that the stakeholder’s concerns are adequately addressed or resolved. Option D is not the best answer because it does not show respect or empathy for the stakeholder. Referring the stakeholder to the project sponsor may help the project manager leverage the sponsor’s authority or influence, but it does not foster a positive relationship or collaboration with the stakeholder. References: 1 PMBOK® Guide, 6th edition, page 5132 PMBOK® Guide, 6th edition, page 515.

 According to the hybrid project management approach, which combines elements of waterfall and agile methodologies, the project manager should facilitate the collaboration and communication among the team members and adjust the scope and schedule as needed12. However, any changes to the product scope should be controlled and evaluated for their impact on the project objectives, risks, quality, and customer satisfaction34. Therefore, the best option for the project manager in this scenario is to follow the proper change control process and evaluate the change for further impact. This way, the project manager can ensure that the change is justified, approved, documented, and communicated to all relevant stakeholders5. The project manager can also assess the potential risks and benefits of the additional feature and take appropriate actions to mitigate or exploit them6.

The other options are not the best ways to avoid this situation in the future. Managing the scope baseline to influence the factors that drive change is a proactive approach to prevent unnecessary or excessive changes, but it does not address the change that has already occurred7. Working with the customer to ensure the feature adds value is a good practice to align the product with the customer needs, but it does not consider the impact of the change on the project constraints or other stakeholders8. Performing frequent reviews with the customer to ensure that the product is working as expected is a useful technique to gather feedback and validate the product quality, but it does not prevent the introduction of new features without proper change control. References: 1: What is the Hybrid Approach in Project Management? | Hygger.io 2: Hybrid Project Management: What is it, Approach & Software - Teamhood 3: [Project Scope Management | Project Management Institute] 4: [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition], p. 131-132 5: [Change Control Process: A Complete Guide - ProjectManager.com] 6: [Project Risk Management | Project Management Institute] 7: [Project Scope Management | Project Management Institute] 8: [Project Stakeholder Management | Project Management Institute] : [Project Quality Management | Project Management Institute] : Project Scope Management | Project Management Institute : A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition : Change Control Process: A Complete Guide - ProjectManager.com : Project Risk Management | Project Management Institute : Project Stakeholder Management | Project Management Institute : Project Quality Management | Project Management Institute

 A project manager who uses a hybrid approach should be able to adapt to changes in the project environment and support the agile principles of delivering value to the customer and embracing change. As a servant leader, the project manager should empower the product owner to make decisions about the product backlog and prioritize the items that deliver the most value. Asking the sponsor to submit a change request to the CCB, accepting the request without consulting the product owner, or reviewing the impact of the change on the schedule management plan baseline are not appropriate actions for a project manager who uses a hybrid approach, as they imply a rigid and bureaucratic process that does not align with the agile mindset. References:

PMBOK Guide, 6th edition, page 18

Agile Practice Guide, page 13

PMI-PBA Exam Content Outline, page 9

[PMI-PBA Handbook], page 10

According to the PMBOK Guide, an agile approach is suitable for projects that have a high degree of uncertainty and change, as it allows for frequent feedback, adaptation, and value delivery. An agile approach also enables the project team to demonstrate the benefits of the product to the sponsor and stakeholders through working increments or prototypes. Developing requirements and designs to support a faster product release may not address the uncertainty and change aspects of the project, and may compromise quality or scope. Emphasizing the adoption of a predictive approach may not be feasible or effective for a project that has a high degree of uncertainty and change, as it requires a detailed upfront planning and a rigid control of changes. Outsourcing development of the product to a third party may not be the best option for the project sponsor, who wants to see the benefits of the product demonstrated, and may introduce additional risks and challenges for the project management. References: PMBOK Guide, 7th Edition, Section 2.1.2, Agile Approach; Section 2.1.3, Hybrid Approach.

According to project management best practices, one of the key elements of successful project implementation is to manage the risks and avoid scope creep12. If there are high-priority issues that require external domain expertise, the project manager should not ignore them, ask the issue reporter to close them, or reduce the project scope. These actions could compromise the quality and value of the project deliverables, and lead to customer dissatisfaction and potential litigation.

Instead, the project manager should review the open issues with the issue reporter and assess the impact and urgency of each issue. Then, the project manager should issue a change request to hire an external domain expert who can help resolve the issues and ensure the project meets the requirements and expectations of the stakeholders. This way, the project manager can maintain the project scope and quality, and manage the risks effectively34.

1: Project Management Best Practices | TeamGantt 2: Project Management Best Practices: 8 Strategies for Success 3: Best practices–the nine elements to success - Project Management Institute 4: 10 project management best practices you MUST know - Teamwork

Adaptive leadership is a practical leadership framework that helps individuals and organizations adapt and thrive in challenging environments. It is being able, both individually and collectively, to take on the gradual but meaningful process of adaptation. It is about diagnosing the essential from the expendable and bringing about a real challenge to the status quo1. A team lead who is highly engaged and involved in a project and is operating without a chain of command or authority levels is demonstrating adaptive leadership by anticipating future needs, articulating those needs to build collective support and understanding, adapting their responses based on continuous learning, and demonstrating accountability through transparency in their decision-making process1.

The other options are not correct because they do not match the description of the team lead. Directive leadership is a style of leadership that involves giving clear and specific instructions to the followers and expecting them to follow them without question2. Commanding leadership is a style of leadership that involves exerting control and authority over the followers and demanding compliance and obedience3. Servant leadership is a style of leadership that involves putting the needs and interests of the followers first and empowering them to grow and develop4. None of these styles reflect the team lead’s behavior of being highly engaged and involved in the project and operating without a chain of command or authority levels. References: 1 5 Principles to Guide Adaptive Leadership, Harvard Business Review2 Directive Leadership Style: Definition, Examples, Pros & Cons, Indeed3 Commanding Leadership Style: Definition, Examples, Pros & Cons, Indeed4 Transformational versus Servant Leadership: A Difference in Leader Focus, Regent University.

According to the PMBOK Guide, 7th edition, one of the principles of project management is to engage stakeholders1. This means that the project manager should communicate effectively with all stakeholders, provide them with relevant information, and address their needs and expectations. In a hybrid project, where some aspects of the project follow a predictive approach and others follow an adaptive approach, the project manager should use a combination of tools and techniques to manage the project artifacts2. One of these tools is a repository or a system that stores and organizes the project artifacts, such as the project schedule, for easy access and retrieval3. The project manager should ensure that all stakeholders have access to the repository and know how to use it to find the project artifacts they need. This will help to avoid confusion, duplication, and inconsistency of information, and to foster collaboration and transparency among the project team and other stakeholders. Therefore, the best answer is C.

According to the PBA Guide, retrospectives are a technique to review the project performance and identify lessons learned, best practices, and improvement opportunities1. Retrospectives are especially useful in agile projects, where they are conducted at the end of each iteration or sprint2. By implementing retrospectives with the vendor, the project manager can ensure that the project team and the vendor share the same understanding of the project goals, requirements, and deliverables. The project manager can also facilitate knowledge transfer and collaboration between the team and the vendor, and address any issues or risks that may affect the project continuity. References: 1: PBA Guide, page 154 2: PMBOK Guide, page 188

A hybrid approach is a combination of predictive and adaptive (or agile) methodologies that can be tailored to suit the project’s needs and context. A hybrid approach can offer the benefits of both approaches, such as clarity, flexibility, responsiveness, and customer satisfaction. However, a hybrid approach also requires careful planning, coordination, and communication among the project stakeholders, especially the project manager, the product manager, and the project sponsor12.

The best option for the project manager to proceed with the project management plan is to explore with the product manager to determine if there are viable opportunities to deliver value incrementally and increase business value. This option can help the project manager to understand the product vision, scope, and requirements, and to identify the areas where an adaptive approach can be applied. It can also help the project manager to collaborate with the product manager and align their expectations and goals. Moreover, it can help the project manager to demonstrate the value of a hybrid approach to the project sponsor and gain their support and approval3 .

The other options are not as effective or relevant for proceeding with the project management plan:

A. Ask the team to assess whether the product specification can be expressed in user stories to enable a Scrum or Kanban approach: User stories are a common tool used in agile methodologies to describe the features and functionalities of a product from the perspective of the end user. They help to capture the user needs, preferences, and value proposition. However, user stories are not the only way to express the product specification, and they may not be suitable for every project or product. Asking the team to assess whether the product specification can be expressed in user stories may not address the project manager’s need to explore the hybrid approach with the product manager and the project sponsor. It may also create confusion or conflict among the team members, who may not be familiar with or comfortable with agile methodologies .

C. Recommend to the project sponsor that a predictive approach is appropriate for the project due to the stable product requirements: A predictive approach is a traditional methodology that follows a linear and sequential process of planning, executing, and controlling the project. A predictive approach is suitable for projects that have stable and well-defined requirements, scope, and deliverables. However, a predictive approach may not be able to accommodate changes, uncertainties, or complexities that may arise during the project. Recommending to the project sponsor that a predictive approach is appropriate for the project may not reflect the project manager’s willingness to explore the hybrid approach, and may also disregard the project sponsor’s request and preference .

D. Ask the product manager whether they are prepared to act as product owner for the project in order to participate in iterative planning and reviews: A product owner is a role in agile methodologies that represents the voice of the customer and the business. A product owner is responsible for defining, prioritizing, and validating the product backlog, and for collaborating with the development team and the stakeholders. A product owner is also involved in iterative planning and reviews, such as sprint planning, sprint review, and sprint retrospective. However, a product owner is not the same as a product manager, and they may have different skills, responsibilities, and expectations. Asking the product manager whether they are prepared to act as product owner for the project may not be appropriate or realistic, and may also imply that the project manager has already decided to adopt an agile methodology without consulting the product manager or the project sponsor .

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, one of the key inputs to the develop project team process is the training needs assessment, which identifies the gaps between the current and desired competencies of the project team members1. The project manager should assess the training requirements and ensure time for professional development training by senior members, as this is a way of enhancing the skills and knowledge of the team members, improving their performance, and increasing their motivation and satisfaction2. This option is also aligned with the Professional in Business Analysis (PMI-PBA) Guide, which states that the business analyst should identify and address the training needs of the project team and stakeholders3. The other options are not appropriate, as they do not address the root cause of the problem, which is the lack of experience and competence of the team members. Increasing the overall project duration may not improve the quality of the project deliverables, and may also increase the project costs and risks. Replacing or removing team members may not be feasible or desirable, as it may disrupt the team dynamics, cause resentment, and create additional work for the project manager. Moreover, these options do not consider the potential of the team members to learn and grow in their roles. References: 1: PMBOK Guide, 6th edition, page 3492: Project Team Training: Proven Key to Organizational Teamwork43: Professional in Business Analysis (PMI-PBA) Guide, 2nd edition, page 97.

According to the PMBOK Guide, the project manager should consider the culture of the organization when choosing a leadership style for a project. The culture of the organization includes its values, norms, beliefs, and expectations that influence how people behave and interact. Different cultures may have different preferences and expectations for leadership styles, such as autocratic, democratic, participative, or laissez-faire. The project manager should adapt their leadership style to the culture of the organization to ensure effective communication, collaboration, and motivation of the project team and stakeholders. References: PMBOK Guide, 6th edition, page 53.

The project manager should first follow the risk response plan. The risk response plan is a component of the project management plan that describes how to implement risk responses for identified risks and opportunities1. It includes the agreed-upon actions and owners for each risk, as well as the budget, schedule, and resources allocated for the risk responses1. By following the risk response plan, the project manager can execute the appropriate actions to minimize the impact of the delay on the critical path activity and the project objectives.

Option B is not the best answer because using the contingency fund is not the first thing to do. The contingency fund is a reserve amount of money or time that is set aside to cover the cost or time impact of known risks2. It is part of the risk response plan, and it should be used only after the risk response actions have been implemented and the residual risk impact has been assessed3.

Option C is not the best answer because preparing a change request is not the first thing to do. A change request is a formal proposal to modify any document, deliverable, or baseline of the project. It should be prepared only after the risk response actions have been implemented and the impact of the delay on the project scope, schedule, cost, or quality has been analyzed.

Option D is not the best answer because updating the risk register is not the first thing to do. The risk register is a project document that records the details of all identified risks, including their description, category, probability, impact, response strategy, and status. It should be updated only after the risk response actions have been implemented and the outcome of the risk response has been evaluated. References: 1: PMBOK Guide, 7th Edition, Section 11.1.3.1, Risk Response Plan 2: PMBOK Guide, 7th Edition, Section 6.5.2.3, Contingency Reserve 3: PMBOK Guide, 7th Edition, Section 11.5.3.1, Implement Risk Responses : PMBOK Guide, 7th Edition, Section 4.6.3.1, Change Requests : PMBOK Guide, 7th Edition, Section 4.6.3.2, Change Control Tools : PMBOK Guide, 7th Edition, Section 11.2.3.1, Risk Register : PMBOK Guide, 7th Edition, Section 11.6.3.1, Monitor Risks

The change management plan is a document that describes how changes to the project will be managed, monitored, and controlled12. It defines the roles and responsibilities of the change control board, the change request process, the criteria for approving or rejecting changes, the impact analysis, and the communication plan for changes34. The change management plan is part of the project management plan, which is the primary source of information for how the project is planned, executed, monitored, controlled, and closed.

The project manager should refer to the change management plan first because it provides the guidelines and procedures for handling changes to the project scope, schedule, cost, quality, or any other aspect of the project. The project manager should follow the change request process to document the proposed change, assess its impact, and submit it to the change control board for approval or rejection. The change management plan also helps the project manager communicate the change to the relevant stakeholders and update the project baselines and plans accordingly.

The schedule management plan, the scope management plan, and the cost management plan are also important documents for managing the project, but they are not the first ones to refer to when a change is requested. These documents describe how the project schedule, scope, and cost will be planned, defined, monitored, controlled, and reported . They are used to establish the project baselines and measure the project performance against them. However, they do not provide the specific steps and criteria for dealing with changes to the project. The project manager should refer to these documents after the change request is approved, to update the project schedule, scope, and cost accordingly and ensure alignment with the project objectives and stakeholder expectations. References: 1: Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. 2: Project Management Institute. (2020). Project Management Professional (PMP)® Examination Content Outline. 3: Teamwork. (2021). 10 project management best practices you MUST know. 4: Salapatas, J. N. (2000). Best practices—the nine elements to success. Paper presented at Project Management Institute Annual Seminars & Symposium, Houston, TX. Newtown Square, PA: Project Management Institute. : Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. : Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. : Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. : Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. : Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. : Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition.

The project manager should update the risk register next. The risk register is a document that records the identified risks, their causes, impacts, probabilities, responses, owners, and other relevant information. Updating the risk register is part of the Monitor Risks process, which involves tracking the identified risks, monitoring residual risks, identifying new risks, executing risk responses, and evaluating their effectiveness. In this scenario, the low availability of the testing facility is a potential risk that could affect the project schedule. Therefore, the project manager should update the risk register with this information and plan appropriate risk responses. This option aligns with the PMBOK Guide, 6th edition, which states that “the risk register is updated as outputs from other risk management processes are completed” (p. 436). The other options are not the best choices because they do not address the risk of the testing facility’s low availability. Updating the issue log (option B) is not appropriate because the issue log is a document that records and monitors the resolution of issues that have occurred or are currently occurring on the project. In this case, the low availability of the testing facility is not an issue yet, but a potential risk that may or may not occur in the future. Updating the lessons learned register (option C) is not relevant because the lessons learned register is a document that captures the knowledge gained from the project, including the challenges, problems, risks, and opportunities encountered and how they were addressed. In this scenario, the project manager has not yet learned any lessons from the testing facility’s low availability, as it is still a potential risk. Updating the project schedule (option D) is premature because the project schedule is a document that presents the planned dates for performing activities and meeting milestones. In this case, the project manager has not yet determined the impact or probability of the testing facility’s low availability, or the risk responses to deal with it. Therefore, updating the project schedule without this information may result in inaccurate or unrealistic estimates. References:

PMBOK Guide, 6th edition, p. 436 1

PMBOK Guide, 6th edition, p. 123 2

According to the PMBOK Guide, 7th edition, an agile project manager is a person who leads and facilitates an adaptive development approach, where requirements and solutions evolve through collaborative efforts of self-organizing and cross-functional teams and their customers. An agile project manager should use the following tools to estimate the time lines for delivery of the initial release:

Backlog grooming: This is a technique used to refine and prioritize the product backlog, which is a list of features and requirements that need to be delivered by the project team. Backlog grooming helps to ensure that the product backlog items are clear, concise, and ready for development. It also helps to estimate the effort and value of each item, and to align them with the product vision and customer needs.

Product backlog: This is the primary source of information for the project team and the product owner, who represents the voice of the customer and defines the product value. The product backlog contains the features and requirements that the project team will deliver in the form of product increments, which are potentially releasable outcomes that provide value to the customer. The product backlog is dynamic and changes as the project progresses and new information emerges.

Minimum viable product (MVP): This is the version of the product that has enough features to satisfy the customer’s needs and provide feedback for future development. The MVP is the first product increment that the project team delivers to the customer, and it represents the minimum scope that the project must achieve. The MVP helps to validate the assumptions and hypotheses about the product value and customer satisfaction, and to guide the subsequent iterations and releases.

By using these tools, the agile project manager can estimate the time lines for delivery of the initial release based on the following factors:

The size and complexity of the product backlog items

The effort and value of each product backlog item

The capacity and velocity of the project team

The feedback and expectations of the customer

The dependencies and risks of the project

Chart, line chart Description automatically generated

The project manager should plan to conduct informal sessions with the stakeholders to educate them about the project objectives, scope, and technology, and to address their concerns and queries. This will help to improve the stakeholders’ awareness, engagement, and buy-in, and to reduce the objections and queries that are wasting time in the meetings. This is part of the Manage Stakeholder Engagement process, which involves communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement1. Requesting stakeholders who understand the technology, recommending a change in technology, or including the issue in the issue log and escalating it are not the best options, as they may alienate the existing stakeholders, compromise the project vision, or escalate a problem that can be resolved at a lower level. References: 1 PMBOK® Guide, 6th edition, page 518.

 Cross-training is a technique that allows team members to share and learn skills from each other. It can enhance team performance, increase flexibility, and reduce risks related to staff turnover or unavailability. It can also improve team cohesion and collaboration. In this scenario, the project manager should allow the engineer and designer to cross-train with each other, as this would benefit both the project and the individuals. The engineer would learn a new skill that is required for the tasks, and the designer would reinforce their existing skill by teaching it. This would also save time and money compared to external training options. Escalating the situation to the engineer’s manager, requesting external training for the engineer, or requesting external training for both the engineer and the designer are not the best choices, as they would not leverage the existing resources and expertise within the team. References: PMBOK Guide, 6th edition, page 339; Professional in Business Analysis (PMI-PBA)® Handbook, page 16.

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 Project Management Professional (PMP)® Examination Content Outline1, one of the tasks under the domain of executing is to “assess and prioritize impact of changes to project scope, schedule, cost, quality, resources, and risks”. This implies that before implementing any change request, the project manager should first evaluate how the change will affect the project objectives and deliverables, and whether the change is aligned with the business case and the stakeholder expectations. The business case is the document that justifies the initiation of a project by providing the expected benefits, costs, risks, and strategic alignment of the project2. Therefore, the project manager should identify how the proposed changes will benefit the project in relation to the business case, and communicate the results of the assessment to the senior management and other relevant stakeholders. This can help to ensure that the changes are necessary, feasible, and beneficial, and that they do not compromise the project scope, quality, or value. References:

1: Project Management Professional (PMP)® Examination Content Outline, page 10

2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, page 29

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, 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.

According to the PMBOK® Guide 6th Edition, the project manager should provide the failed test results along with the agreed-upon acceptance criteria to support their claim to the vendor. This is because the acceptance criteria are the measurable and verifiable standards that define the quality requirements of the project deliverables. The project manager and the vendor should have agreed on the acceptance criteria before signing the contract. Therefore, providing the failed test results along with the acceptance criteria will show the vendor that they have not met their contractual obligations and that they need to take corrective actions to improve the system quality. References: PMBOK® Guide 6th Edition, page 161, section 5.5.2.1; page 287, section 8.2.2.1; page 375, section 12.1.2.1.

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 review the stakeholder engagement plan and inform the stakeholders about the appropriate communication channels and procedures for status reports and change requests. The stakeholder engagement plan describes the strategies and actions to effectively engage stakeholders throughout the project life cycle, based on their needs, expectations, interests, and influence levels. By reviewing and communicating the stakeholder engagement plan, the project manager can ensure that the stakeholders are aware of their roles and responsibilities, the project objectives and scope, the project performance and progress, and the change management process. This will help to avoid confusion, conflicts, and delays in the project and enhance stakeholder satisfaction and support. References: PMBOK Guide, 6th edition, page 513; PMP Exam Content Outline, 2021, page 9.

 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, 6th edition, section 9.4.2.1, the project manager is responsible for managing the project team and ensuring that the team members are performing their assigned roles and responsibilities. The project manager should also monitor and control the project work and address any issues or conflicts that arise among the team members or with other stakeholders. In this scenario, the project manager should talk with project B’s leader to discuss the possible impacts of the frequent requests for assistance on both projects. This will help to clarify the expectations and boundaries of the team members, as well as to identify and resolve any potential conflicts or resource constraints. The other options are either passive or aggressive, as they do not address the root cause of the problem or respect the authority and autonomy of the team members. References: PMBOK Guide, 6th edition, section 9.4.2.1, page 336.

A RAM is a tool that maps the project work packages or activities to the project team members or roles. It helps to define and assign the responsibilities, accountabilities, and authorities of each team member for each project task. It also helps to identify and resolve any gaps, overlaps, or conflicts in the resource allocation. A RAM can be presented in various formats, such as a RACI chart, a RASCI chart, or a linear responsibility chart12.

Developing an approved RAM can help the project manager to manage the team effectively, especially when some team members, such as the site engineers, may not be fully focused on the project due to other priorities or constraints. A RAM can help the project manager to communicate and clarify the expectations and deliverables of each team member, and to monitor and control their performance and progress. A RAM can also help the project manager to coordinate and collaborate with the other stakeholders, such as the production managers, to ensure that the project and the production imperatives are aligned and balanced34.

The other options are not as effective or relevant for managing the team:

B. Commit each team member’s time and deliverables and aim for overall project completion: Committing each team member’s time and deliverables is important, but it may not be sufficient or realistic to manage the team, especially when some team members, such as the site engineers, may have competing or conflicting demands on their time and attention. Aiming for overall project completion is a desirable goal, but it may not be achievable or sustainable without proper planning, communication, and coordination among the team members and the other stakeholders.

C. Continue the project implementation without the site engineers to ensure the schedule is maintained: Continuing the project implementation without the site engineers may not be feasible or advisable, as the site engineers may have critical skills, knowledge, or experience that are essential for the project success. Excluding the site engineers from the project may also create risks, issues, or gaps in the project quality, scope, or integration. Moreover, it may damage the relationship and trust between the project manager and the site engineers, and reduce their motivation and commitment to the project.

D. Contract external resources to fulfill the role of the site engineers who cannot sup-port the project: Contracting external resources may be an option to supplement or replace the internal resources, such as the site engineers, who cannot support the project. However, this option may not be the best or the first choice, as it may involve additional costs, time, or risks for the project. Contracting external resources may also require approval, negotiation, or procurement processes that may delay or complicate the project. Furthermore, it may affect the morale, loyalty, or performance of the internal resources, who may feel threatened, replaced, or undervalued by the external resources.

According to the PMBOK Guide, 6th edition, section 13.2.2.4, stakeholder engagement assessment matrix is a tool that can be used to identify the current and desired levels of engagement for each stakeholder or stakeholder group. The project manager should use this matrix to plan and implement appropriate strategies to increase the support and minimize the resistance of the stakeholders. One of the strategies is to meet with the stakeholder and discuss the impact of the project deliverable on their interests, needs, and expectations. The project manager should also explain the benefits of the deliverable for the organization and the stakeholder, and address any concerns or issues that the stakeholder may have. By doing so, the project manager can increase the stakeholder’s awareness, understanding, and involvement in the project, and foster a positive relationship with them. References: PMBOK Guide, 6th edition, section 13.2.2.4; PMI website

 The project manager should develop an integrated change management plan to control the situation, as this will help to establish a clear and consistent process for managing and approving change requests throughout the project. An integrated change management plan defines the roles and responsibilities of the change control board (CCB), the criteria and procedures for evaluating and approving change requests, the tools and techniques for tracking and reporting change requests, and the impact of change requests on the project baselines and other project documents. By developing an integrated change management plan, the project manager can ensure that the change request process is transparent, efficient, and aligned with the project objectives and stakeholder expectations. Redefining the communications management plan may not be sufficient, as it only addresses the information needs and communication methods of the project stakeholders, but not the change request process itself. Documenting the risk in the project risk register may not be relevant, as the question does not indicate that the change request process poses a risk to the project. Reviewing the scope defined in the project charter may not be helpful, as it only provides a high-level overview of the project scope, but not the details of the change request process. References: PMBOK Guide, 7th edition, pages 123, 124, 125, 126.

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

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 determine the critical requirements to bridge the gap and ensure the project delivers the expected business value. This is because the project manager is dealing with a new and innovative solution that may have unclear or ambiguous scope and expectations. The project manager should review the RFP and identify the key terms and conditions that define the project objectives, deliverables, and constraints. The project manager should also engage with the customer and other stakeholders to elicit, analyze, and prioritize the requirements that are essential for the project success. The project manager should ensure that the critical requirements are aligned with the project vision, scope, and business value, and that they address the compliance issues that may arise in the project context. The project manager should not document the risks and mitigations, as this would be a subsequent step after determining the critical requirements. The project manager should not define the project schedule, as this would be a premature and risky action without having a clear understanding of the project scope and requirements. The project manager should not create a project scope statement, as this would be a formal document that requires the approval of the customer and other stakeholders, and that may not be feasible or appropriate for a new and innovative solution. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 5.2, “Collect Requirements”

PMBOK® Guide, 6th edition, Section 5.3, “Define Scope”

PMBOK® Guide, 6th edition, Section 5.4, “Create WBS”

PMBOK® Guide, 6th edition, Section 5.6, “Control Scope”

 According to the PMBOK Guide, 7th edition, one of the agile principles is to “prioritize work that delivers the most value”. This means that the project manager should help the team and the product owner to rank the requirements in order of importance and urgency, rather than using vague categories such as high, medium, and low. A numerical prioritization system, such as the MoSCoW method (Must have, Should have, Could have, Won’t have) or the 100-point method, can help the team to focus on the most valuable features and avoid confusion and ambiguity. This also aligns with the agile value of “responding to change over following a plan”, as the team can adjust the priority of the requirements based on the feedback and changes from the stakeholders. References: PMBOK Guide, 7th edition, page 14, 15, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, …

A hybrid approach in project management is a technique that combines elements from different project management frameworks, such as waterfall and agile, to tailor the methodology to best suit the project at hand12. By merging various methods, organizations can capitalize on the strengths of each approach while mitigating their weaknesses3. A hybrid approach allows for a more detailed and nuanced approach to the work, and requires the project manager to facilitate the collaboration and communication among the team members45. Therefore, the best option for the project manager in this scenario is to facilitate the discussion so that the team members can reach a consensus on the comparative size of the backlog items and if they would fit into the next sprint. This way, the project manager can ensure that the team is aligned on the approach, the customer needs are met, and the project goals are achieved.

According to the PMBOK Guide, 6th edition, section 11.6.1.1, the project manager is responsible for monitoring and controlling the project risks and ensuring that the project objectives are met. The project manager should also identify and analyze any new or emerging risks that may affect the project performance or scope. In this scenario, the project manager should first work with the team and others in the network to assess and prioritize the obstacles. This will help to determine the impact and probability of each obstacle and decide on the best course of action to address them. The other options are either premature or inappropriate, as they do not address the root cause of the problem or respect the authority and responsibility of the project manager. References: PMBOK Guide, 6th edition, section 11.6.1.1, page 442.

The project manager should first assess the impact of the layoff on the project objectives, scope, schedule, cost, quality, and risk. The project sponsor is the person who provides the resources and support for the project and is accountable for enabling success1. Therefore, the project manager should request a meeting with the project sponsor to discuss the viability of the project and determine the next actions, such as revising the project plan, securing additional resources, or terminating the project. This is the best option among the given choices.

Option B is not the best answer because the project manager should not discuss trade-offs with the customer without consulting the project sponsor first. The project sponsor is the one who authorizes any changes to the project scope or quality1.

Option C is not the best answer because the project manager should not request a meeting with the finance department to increase the budget without consulting the project sponsor first. The project sponsor is the one who approves the project budget and any changes to it1.

Option D is not the best answer because the project manager should not request a meeting with the HR department and demand they find a solution to retain the project team members. This is not a realistic or respectful way to handle the situation. The project manager should work with the project sponsor and the HR department to find the best possible solution for the project and the affected team members2. References: 1: PMBOK Guide, 7th Edition, Section 4.1.2, Project Sponsor Role and Responsibilities 2: PMBOK Guide, 7th Edition, Section 9.1.3, Develop Team: Tools and Techniques

 According to the PMBOK® Guide, a project manager should be able to lead and support the team in achieving the project objectives, as well as manage team conflicts and issues. When a key project team member exhibits a sudden decrease in participation and performance, the project manager should schedule a meeting to discuss recent observations with the team member. This option demonstrates the project manager’s ability to communicate effectively, provide feedback, and address the root cause of the problem. The project manager should also show empathy and respect, and explore possible solutions or support that the team member may need. Reallocating tasks for the team member of concern, organizing a team-building session with all of the team members, or consulting the resource allocation matrix are not effective or appropriate actions to take in this situation. These options may ignore, avoid, or worsen the issue, and may not address the individual needs or concerns of the team member. They may also indicate a lack of leadership, interpersonal, or problem-solving skills on the part of the project manager. References: PMBOK® Guide, 6th edition, pages 52, 335, 349.

According to the PMBOK Guide, 6th edition, section 4.7.3.2, the project closure report should include information on benefits realization, such as who will be responsible for tracking and reporting the benefits, what metrics and indicators will be used to measure the benefits, and when the benefits are expected to be realized. This is consistent with the PMI-PBA Practice Guide, section 2.5.2, which states that the business analyst should document the benefits realization plan and communicate it to the relevant stakeholders. Therefore, the project manager should document this information in the project closure report and ensure that the project sponsor and other stakeholders are aware of it. References:

PMBOK Guide, 6th edition, section 4.7.3.2

PMI-PBA Practice Guide, section 2.5.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.

According to the PMBOK Guide, a project manager should ensure that the project team applies a long-term solution for an issue that has been resolved during the project life cycle, to prevent it from reoccurring after the project closure. This is part of the control quality process, which involves monitoring and recording the results of quality activities, and implementing corrective actions to address any quality issues. A long-term solution is one that addresses the root cause of the issue and eliminates or reduces the probability of its recurrence. A short-term solution is one that provides a temporary fix or workaround for the issue, but does not resolve the underlying problem. A short-term solution may be acceptable in some situations, but it may also create additional risks or costs in the future. Therefore, a project manager should always consider the long-term implications of any solution and choose the one that best meets the project objectives and stakeholder expectations. References: PMBOK Guide, 6th edition, pages 293-294, 303-304.

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.

 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.

According to the PMBOK Guide, the stakeholder register is an output of the Identify Stakeholders process, and it contains information about the project stakeholders, such as their identification, assessment, classification, and engagement levels1. The communications management plan is an output of the Plan Communications Management process, and it describes how the project information will be managed and communicated among the stakeholders, such as the communication requirements, methods, formats, frequency, roles, and responsibilities2. Whenever there is a change in the project team or the stakeholder environment, the project manager should update the stakeholder register and the communications management plan accordingly, to ensure that the new team member or stakeholder is properly identified, analyzed, and engaged3. In this case, the project manager should include the new team member in the stakeholder register and update the communications management plan to reflect the team member’s communication preferences, such as working remotely and being more responsive in face-to-face interactions. This will help the project manager to plan and manage the project communications more effectively and efficiently, and to avoid potential misunderstandings, conflicts, or delays45. References: 1: PMBOK Guide, 7th edition, page 215 2: PMBOK Guide, 7th edition, page 237 3: PMBOK Guide, 7th edition, page 217 4: Project Team Communications4 5: How to create a project management communication plan5

According to the PMBOK Guide, the project manager should use interpersonal and team skills to manage the team and resolve conflicts. One of these skills is conflict management, which involves identifying and addressing the root causes of disagreements among team members. In this case, the project manager should try to understand why the team member is absent from the meetings and what are the possible impacts on the project and the team. The project manager should also communicate the benefits of attending the meetings and encourage the team member to participate more actively. This way, the project manager can foster a collaborative and respectful team environment and avoid potential issues such as poor communication, low morale, or missed deadlines. References: PMBOK Guide, 7th edition, pages 282-283, 287-288.

A change request is a formal proposal to modify any document, deliverable, or baseline of a project. A change request should be submitted when a change is needed due to an external or internal factor, such as a new regulation, a stakeholder request, or an error correction. The Integrated change control process is the process of reviewing and approving all change requests, and managing the changes to the project management plan, project documents, and project baselines. The project manager should submit a change request through the Integrated change control process as the next step after receiving the announcement from the municipality, as this will ensure that the change is properly evaluated, approved, and communicated to the relevant stakeholders. Performing a qualitative risk analysis, updating the issue log, or estimating the associated costs are not the next steps that the project manager should take, as they do not address the need for a change request or the approval of the change. References: [PMBOK® Guide 6th Edition], page 115; Project Management Professional (PMP) Exam Questions for 2022, question 23.

The project manager should first try to understand why the key stakeholder is not attending the meetings and providing false information. The project manager should discuss the communication needs and preferences of the key stakeholder and tailor the communication accordingly. This will help to build trust and rapport with the key stakeholder and ensure that they receive accurate and timely information about the project progress. Creating a new communication artifact, emailing the latest status report, or sharing the meeting recordings may not address the root cause of the problem and may not be effective in engaging the key stakeholder. References: PMBOK Guide, 6th edition, page 524; PMP Exam Content Outline, 2021, page 10.

 The project manager should conduct a kick-off meeting to ensure that all team members have a clear and common understanding of the project vision, goals, objectives, scope, deliverables, and roles and responsibilities. This is especially important for agile projects, where the team is expected to self-organize and collaborate effectively. A kick-off meeting can also help to establish trust, rapport, and alignment among team members who are working remotely or across different time zones and cultures. Scheduling team-building activities, coaching the team members, or continuing the meetings may be helpful, but they are not sufficient to address the gaps in understanding that exist at the beginning of the project. References:

PMBOK® Guide, 6th edition, page 123: “The project kick-off meeting is usually the first time that the project team and key stakeholders meet together. The purpose of the kick-off meeting is to communicate the project vision, objectives, and scope; confirm initial roles and responsibilities; and provide an opportunity for team members to get to know each other.”

PMI-PBA® Guide, 1st edition, page 39: “The business analyst should participate in the project kick-off meeting to ensure that the business needs, objectives, and benefits are clearly articulated and understood by the project team and stakeholders.

According to the PMBOK Guide, 6th edition, section 4.6.1.1, the project manager is responsible for communicating the approved changes to the relevant stakeholders and ensuring that the changes are implemented as planned. The project manager should also manage the expectations of the stakeholders and address any issues or concerns that arise from the changes. In this scenario, the project manager should first meet with the operations manager to explain the background for the change and understand the operation manager’s concerns about the change. This will help to establish a collaborative relationship and resolve any potential conflicts. The other options are either premature or inappropriate, as they do not address the root cause of the problem or respect the authority of the CCB. References: PMBOK Guide, 6th edition, section 4.6.1.1, page 115.