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

To address prior tensions and focus the retrospective on constructive improvements, the project manager should set clear expectations for behavior and objectives. A well-structured agenda helps keep the discussion process-oriented and prevents blame. This approach aligns with Agile principles and effective facilitation practices.

Option A prevents open communication and collaboration.

Option B focuses only on leadership, not the whole team.

Option D introduces unnecessary escalation and shifts focus from improvement to contract management.

Conflict resolution starts with understanding the root cause of the issue. Before taking corrective or disciplinary action, the project manager should investigate both sides to identify what is causing the tension. This is essential for resolving the issue constructively and preventing recurrence.

This approach aligns with the PMBOK® Guide – Seventh Edition guidance on conflict management: listen first, then act.

Option A presumes the team member is at fault.

Option B may not be suitable without understanding this context.

Option D is helpful later, not as the first step.

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” (Section 2.1). This implies that the agile project manager should foster a collaborative and self-organizing team culture, where team members share their knowledge and skills with each other, and are able to adapt to changing situations. By asking the team member to work with their peers to knowledge share, the agile project manager can ensure that the team has the necessary information and expertise to continue working on the project, even when the specialized team member is unavailable. This is also consistent with the PMBOK® Guide, which states that “the project manager should facilitate knowledge sharing among the project team and other stakeholders” (Section 4.4.3.3). References:

Agile Practice Guide, Section 2.1

PMBOK® Guide, 6th Edition, Section 4.4.3.3

According to the PMBOK® Guide Seventh Edition, one of the project management principles is to engage stakeholders actively and frequently. This means that the project manager should identify and analyze the needs, expectations, and interests of all stakeholders, and involve them appropriately throughout the project life cycle. The stakeholder register is a document that lists the key stakeholders, their roles, responsibilities, and level of influence on the project. The stakeholder engagement plan is a document that describes the strategies and actions to communicate with, manage, and influence the stakeholders.

In this scenario, the project manager has discovered that the local community was not included in the stakeholder register, which has caused them to oppose the project. This is a serious issue that can affect the project’s performance, reputation, and acceptance. Therefore, the project manager should not disregard these stakeholders, as this would violate the principle of stakeholder engagement and potentially escalate the conflict. The project manager should also not just explain to the community members why they were not included as stakeholders, as this would not address their concerns or expectations. The best option is to update the stakeholder register and revise the stakeholder engagement plan, as this would allow the project manager to acknowledge the community as a stakeholder, assess their impact and interest, and develop appropriate strategies and actions to engage them effectively and proactively. References:

PMBOK® Guide Seventh Edition, page 9

Project Management Principles 9-12, Episode 479: Project Management Principles 9-12 (Free)

 According to the PMBOK Guide, 6th edition, one of the key processes of the Project Stakeholder Management knowledge area is Manage Stakeholder Engagement, which involves communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement. One of the inputs for this process is the stakeholder engagement plan, which identifies the strategies and actions to promote productive involvement of stakeholders in project decisions and activities. By reviewing the stakeholder engagement plan, the project manager can assess the current level of stakeholder engagement and identify the gaps or issues that need to be addressed to overcome the resistance and gain acceptance of the change. References: PMBOK Guide, 6th edition, pages 513-514, 518.

The agile project lead should invite the senior manager to the next planning meeting to ensure that the senior manager’s expectations are aligned with the product vision and backlog. This is consistent with the agile principle of customer collaboration over contract negotiation1. The agile project lead should also explain how the product backlog is prioritized and refined based on the value and feedback from the stakeholders2. Assuring the senior manager that these features will be queued up in the next sprint (A) is not a good option since it may create unrealistic expectations and compromise the quality and scope of the product. Meeting with the team to understand why the senior manager’s features were not included (B) is not relevant since the team is not responsible for defining the product features, but for delivering them. Sending the product roadmap to the senior manager (D) is not sufficient since it may not address the senior manager’s concerns or questions. References:

1: Agile Practice Guide, Chapter 1, Section 1.2.1

2: Agile Practice Guide, Chapter 2, Section 2.3.2.1

 According to the PMI, a hybrid approach is a combination of two or more project methodologies, such as waterfall and agile, to suit the needs of the project. A hybrid approach can offer flexibility, adaptability, and customer focus, while also maintaining some level of predictability, structure, and control. However, a hybrid approach can also pose some challenges, such as stakeholder resistance, misalignment, or confusion. Therefore, the project manager needs to address and remove any obstacles and blockers that may prevent the team from achieving their goals. Obstacles and blockers are issues or impediments that hinder or stop the team’s progress, such as lack of resources, unclear requirements, technical debt, conflicts, communication gaps, etc. The project manager should follow these steps to address and remove obstacles and blockers for the team:

Identify the obstacles and blockers by using various techniques, such as daily stand-up meetings, retrospectives, feedback sessions, surveys, etc.

Analyze the impact, root cause, and priority of the obstacles and blockers by using tools, such as issue logs, risk registers, impact analysis, root cause analysis, prioritization matrix, etc.

Develop and implement solutions to remove the obstacles and blockers by using methods, such as problem-solving, negotiation, escalation, delegation, collaboration, etc.

Monitor and evaluate the effectiveness of the solutions by using measures, such as team velocity, customer satisfaction, quality metrics, etc.

Communicate and report the status and results of the solutions to the relevant stakeholders, such as the team, the sponsor, the customer, etc.

By addressing and removing obstacles and blockers for the team, the project manager can improve the project performance, as well as the team’s productivity, quality, morale, and collaboration.

The other options are not the best choices, because:

Asking stakeholders to communicate with the project manager and not directly with the team would create a communication bottleneck, reduce transparency, and increase the risk of misunderstanding or miscommunication.

Empowering the team members to remove obstacles and blockers would be a good practice, but it would not be sufficient without the project manager’s support, guidance, and intervention, especially if the obstacles and blockers are beyond the team’s authority or capability.

Adding blockers to the issue log and risk management plan would be a necessary step, but it would not be enough without taking action to resolve them. Simply documenting the blockers would not help the team to overcome them or improve their performance. References:

Hybrid Project Management: What is it, Methodology & Software - Teamhood

Agile, Traditional, and Hybrid Approaches to Project Success

Impediments, Obstacles, and Blockers: How to Address and Remove Them

1.7. Address and remove impediments, obstacles, and blockers for the team - KnowledgeMap

1.7 Address and Remove Impediments, Obstacles, and Blockers … - BrainBOK

The agile project leader should explain the new team velocity to the customer and negotiate the scope and schedule of the project accordingly. Team velocity is a measure of the amount of work a team can handle during a single iteration1. It is affected by factors such as team size, skills, experience, and availability2. Since the team has lost two members, the team velocity will likely decrease, which means the team will not be able to deliver the same amount of work as before. The agile project leader should communicate this change to the customer and collaborate with them to prioritize the most valuable features and adjust the release plan3. Updating the restriction log with the new team capacity (A) is not a sufficient action since it does not address the impact on the project scope and schedule. Explaining the new project requirements to the team (B) is also not a good option since it may overload the team and compromise the quality and value of the product. Updating the project budget with the released team members © is not relevant since the budget has already been reduced by the customer. References:

1: Agile Practice Guide, Glossary, page 91

2: Agile Practice Guide, Chapter 2, Section 2.4.2.2

3: Agile Practice Guide, Chapter 2, Section 2.4.2.3

A hybrid approach to project management combines predictive and adaptive methods, such as waterfall and agile, to suit the needs and context of the project. In this case, the project manager can use an agile approach to plan project A in sprints, which are short iterations that deliver incremental value to the customer. By starting with the module that does not require machine learning skills, the project manager can leverage the existing resources and skills of the team, while waiting for the machine learning expert to finish project B. This way, the project manager can avoid delaying project A, compromising project B, or hiring a new resource that may not fit the organizational culture or project requirements. This is consistent with the PMI-PBA practice of planning and monitoring the business analysis work and the PMP practice of executing the project with urgency. References:

PMBOK Guide, 6th edition, page 14, section 1.2.1

Agile Practice Guide, page 8, section 1.2.2

PMI-PBA Exam Content Outline, page 9, task 1.2

PMI-PBA Certification Exam Prep Guide, page 65, section 3.2.2

PMP Exam Content Outline, page 7, task 2.1

PMP Exam Prep, 10th edition, page 32, section 1.4.2

The project manager should review the communications management plan and submit a change request if required. The communications management plan is a document that describes how the project information will be communicated to the stakeholders. It defines the communication requirements, methods, formats, frequency, and responsibilities for each stakeholder group. The project manager should review the communications management plan to understand the current communication expectations and agreements, and to identify any gaps or conflicts between the sponsor’s request and the key team members’ preferences. If the communications management plan needs to be updated to accommodate the sponsor’s request, the project manager should submit a change request and follow the change control process. Negotiating with the key team members to send a daily report and letting the sponsor know that the project cost will increase (option A) may be a possible solution, but it should be done after reviewing the communications management plan and submitting a change request if required. Recommending to the sponsor that performance of the project be reviewed once per week (option B) may not satisfy the sponsor’s needs and expectations, and may also contradict the communications management plan. Evaluating the capacity of each team member to attend daily meetings in person or virtually and reducing the time of each meeting (option D) may be a good practice, but it should also be done after reviewing the communications management plan and submitting a change request if required. References:

PMBOK Guide, 6th edition, page 377-378, section 10.1 Plan Communications Management

PMP Exam Prep, 10th edition, page 474, question 474, answer and explanation

The stakeholder engagement plan and communication strategy are two key documents that guide the project manager in managing stakeholder expectations and interactions. The project manager should review these documents to identify the level of interest and influence of the stakeholder from the legal department, and determine the best way to communicate and involve them in the project. Escalating the issue to the project sponsor may not be necessary or appropriate at this stage, as the stakeholder may not be critical for the project success. Engaging the stakeholder and ensuring all requirements are captured may not be feasible or effective, as the stakeholder may not have any input or interest in the product design. Reviewing the product requirements and updating the stakeholder register may not address the root cause of the stakeholder’s lack of participation, as these documents do not specify how to engage and communicate with the stakeholder. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 13: Stakeholder Engagement, Section 13.2: Plan Stakeholder Engagement, Section 13.3: Manage Stakeholder Engagement, Section 13.4: Monitor Stakeholder Engagement

Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 2: Planning, Task 5: Plan Stakeholder Engagement

Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain 2: Planning, Task 5: Plan Stakeholder Engagement

 The project manager should have allocated additional time for mentoring the intern, as this would have helped the intern to learn faster and perform better. Mentoring is a key practice in agile projects, as it helps to transfer knowledge, skills, and experience from senior to junior team members. It also fosters collaboration, trust, and feedback within the team. By allocating more time for mentoring, the project manager could have ensured that the intern was adequately supported and prepared to take over the critical role. This would have reduced the risk of delays and quality issues in the project. References:

Role of Agile Mentor - PM Majik

Mentoring | Scrum.org

Agile Team Roles: The 7 Most Important People in Agile Project

The project manager should review the terms of the contract in order to determine the next steps. This is part of the Control Procurements process, which involves managing procurement relationships, monitoring contract performance, and making changes and corrections as appropriate1. The project manager should check if the contract has any clauses or penalties for the supplier’s delay or breach of contract, and take appropriate actions to protect the project’s interests and minimize the impact on the schedule. Updating the project team on the delay so that resources can be utilized elsewhere (A) is not a sufficient action since it does not address the root cause of the problem or prevent it from happening again. Analyzing the schedule and looking for fast tracking and crashing alternatives (B) is also not a good option since it may increase the project risk and cost without resolving the issue with the supplier. Updating the lessons learned register to serve as an input for future material transactions (D) is a good practice, but it is not the most urgent action in this situation. References:

1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 12, Section 12.3.3.1

 The best way to formally record the team member’s success in the project documentation is to send a communication to management recognizing the team member’s contributions. This will ensure that the team member’s performance is acknowledged and appreciated by the relevant stakeholders, and that the project documentation reflects the team member’s achievements. The other options are not as effective or appropriate as sending a communication to management. Attaching a note to the project management plan is not a formal way of recording the team member’s success, and it may not be seen by anyone else. Holding a project team meeting may be a good way to celebrate the team member’s contribution, but it does not document it for future reference. Recording the team member’s contribution in the RAM is not relevant, as the RAM is a tool to assign roles and responsibilities, not to measure performance. References:

PMBOK Guide, 7th edition, page 215

PMI-PBA Exam Content Outline, 2018, page 12

The best way to address the complaint is to involve the operations director or a representative from the operations team in the agile process. By inviting them to the validation and sprint meetings, they can provide feedback, clarify requirements, and validate the product increments. This will help to ensure that the product meets the performance indicators and the expectations of the operations department. It will also foster collaboration and transparency among the stakeholders and the project team. References:

What is a Sprint Review? | Scrum.org

What Is a Sprint Review? Goals and Tips for Running This Scrum Event

What is a sprint review? 3 steps to better sprint reviews - Atlassian

What is Stakeholder Management? - ProjectManager

What is Stakeholder Management? | A Step-by-Step Guide - Creately

According to the PMBOK Guide, 6th edition, one of the key processes of the Project Resource Management knowledge area is Develop Team, which involves improving the competencies, interaction, and overall team environment to enhance project performance. One of the tools and techniques for this process is training, which involves providing guidance and instruction to enhance the skills and competencies of the team members. By supporting the team members’ growth and development, the project manager can help them to acquire the necessary knowledge and skills to work effectively in an agile environment, and to adapt to the changes and challenges that may arise during the project. References: PMBOK Guide, 6th edition, pages 336-337, 341.

According to the PMBOK Guide, the project manager should be involved in the procurement process to ensure that the project requirements are clearly defined and communicated to the potential suppliers1. The project manager should also verify that the project objectives are aligned with the business needs and the expectations of the stakeholders before approving an agreement2. Therefore, the best option is to ensure that the requirements for the project are understood and that the objectives are verified before approval of an agreement. Option B is incorrect because informing the project sponsor that there cannot be any changes to the scope of the project is unrealistic and may not account for the possible risks and uncertainties that may arise during the project execution3. Option C is incorrect because notifying the project sponsor that the project manager cannot be involved in the agreement negotiation process is not a proactive or collaborative approach, and may result in a poor or unsuitable agreement for the project. Option D is incorrect because asking the project sponsor to involve the legal department in the negotiation for the project agreement is not the responsibility of the project manager, and may not address the issue of the project manager’s participation in the procurement process. References: 1: PMBOK Guide, 6th edition, section 12.1.3.1, p. 465 2: PMBOK Guide, 6th edition, section 4.1.3.1, p. 89 3: PMBOK Guide, 6th edition, section 5.6.3.1, p. 161 : PMBOK Guide, 6th edition, section 12.2.3.1, p. 473 : PMBOK Guide, 6th edition, section 12.2.3.2, p. 474

According to the PMP Exam Content Outline, one of the tasks of the project manager is to “Manage project team members by negotiating and influencing their assignments, providing feedback, resolving and escalating issues, and managing team development” (Task 9, Domain II: Process). This implies that the project manager should protect the project team from any external interference or distraction that could affect their performance or availability. The project manager should also respect the contractual agreements and scope boundaries of the project, and avoid any unauthorized work or scope creep. Therefore, the project manager should decline the request politely since the issue is unrelated to the project and is not the responsibility of the project team. The project manager should also direct the customer to the appropriate channel or department to handle their request, such as the sales manager or the customer service team. References:

PMP Exam Content Outline, Domain II: Process, Task 9, page 101

PBA Exam Content Outline, Domain III: Analysis, Task 7, page 132

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 9: Project Resource Management, Section 9.4: Manage Team, page 3413

Business Analysis for Practitioners: A Practice Guide, Chapter 5: Requirements Life Cycle Management, Section 5.3: Manage Requirements Traceability, page 97

This is the best option because it allows the project manager to address the current and future needs of the project, while also developing the skills and knowledge of the team. According to Project Management Best Practices for 2024 + Expert Tips, one of the best practices is to “provide your team members with opportunities to learn new skills and grow professionally”. This can increase their motivation, engagement, and productivity, as well as reduce turnover and improve quality.

Option A is not the best option because it may create conflicts or dependencies with another team, and it does not solve the long-term need for an SME in the specific area.

Option C is not the best option because it may incur additional costs and risks, and it does not foster the development of the team.

Option D is not the best option because it does not address the issue at all, and it may delay the project progress and quality.

 A change log is a document that contains the list of changes that are made during the project. It tracks the progress of each change based on its review, approval, implementation, and closure. A change log is a useful tool for communicating the status of change requests to the stakeholders, as it shows the impact and outcome of each change. A risk log, a backlog, and an issue log are different documents that serve different purposes. A risk log records the identified risks, their probability, impact, and response strategies. A backlog is a list of features or tasks that need to be completed in an agile project. An issue log records the issues that arise during the project, their causes, effects, and resolution. References:

Change Log - Project Management Knowledge

Change Log Template - Project Management Docs

Risks, issues, and changes–help, I’m drowning in logs!

 According to the Agile Practice Guide, one of the benefits of agile approaches is that they enable early and frequent delivery of value to the customer and stakeholders1. This can help to build trust and collaboration among the project team and the stakeholders, and also to validate and adapt the project requirements and solutions2. Therefore, the project manager should propose a phased project approach with multiple small interactions and build trust with the stakeholder through frequent value delivery. This will help the stakeholder to see the benefits of agile and overcome their reluctance. The other options are incorrect because:

B. Documenting the request and escalating to upper management to consider a modification of the project charter is not a persuasive strategy, but a confrontational one. It may create resistance and conflict with the stakeholder, and also undermine the project manager’s authority and credibility3.

C. Agreeing on a predictive approach, but applying agile concepts under the project management umbrella is not a transparent or ethical strategy. It may confuse and mislead the stakeholder, and also create inconsistency and ambiguity in the project management processes and practices4.

D. Ensuring the stakeholder that an agile approach will deliver all of the expected results in a shorter period of time is not a realistic or honest strategy. It may create unrealistic expectations and pressure on the project team, and also ignore the uncertainty and complexity of the project environment5. References:

1: Agile Practice Guide, Chapter 2, Section 2.1, page 13

2: Agile Practice Guide, Chapter 2, Section 2.2, page 14

3: PMBOK Guide, 6th edition, Chapter 13, Section 13.3.2.3, page 524

4: PMBOK Guide, 6th edition, Chapter 1, Section 1.2.3, page 7

5: Agile Practice Guide, Chapter 2, Section 2.3, page 15

According to the PMBOK Guide, 6th edition, section 6.4.2.6, the Monte Carlo method is a simulation technique that uses probability distributions and random sampling to compute possible outcomes of cost or schedule estimates.3

The Monte Carlo method can produce different results each time it is run, depending on the input data and the random numbers generated.4

Therefore, the project manager and the stakeholder may have used different input data, assumptions, or scenarios when applying the Monte Carlo method, resulting in different estimations for the budget.4

The project manager and the stakeholder should compare and validate their estimations, and agree on a common baseline for the budget.

The references for this answer are:

1: PMP Exam Questions | 100% Free PMP Example Questions 2: PMP Practice Exam 1 | Free PMP Exam Questions 3: PMBOK Guide, 6th edition, Project Management Institute, 2017, pp. 200-201. 4: [Monte Carlo Simulation: What Is It and How Does It Work? - Palisade] : [Project Cost Management: The Ultimate Guide - ProjectManager.com]

 According to the PMBOK Guide, the product owner is the person responsible for defining and prioritizing the product backlog, and ensuring that the product delivers value to the customer and stakeholders1. The product owner also collaborates with the project team and the project manager to review the work in progress and provide feedback2. Therefore, if a stakeholder has a new requirement or a change request, the correct procedure is to provide it directly to the product owner, who will evaluate it and decide whether to add it to the product backlog or not. The other options are not the correct procedures for new requirements in a hybrid project. The change control board (CCB) is a group of stakeholders who review and approve change requests in a traditional project, but not in a hybrid project that follows agile principles3. The project sponsor is the person or group who provides the financial resources and support for the project, but not the owner of the product requirements or scope. The project manager is the person who leads the project team and manages the project work, but not the person who defines or prioritizes the product backlog. References:

1: PMBOK Guide, 6th edition, page 49

2: PMBOK Guide, 6th edition, page 50

3: PMBOK Guide, 6th edition, page 115

PMBOK Guide, 6th edition, page 33

PMBOK Guide, 6th edition, page 51

 The project manager should mentor the team member and provide the necessary training because this is the best way to help the team member overcome the difficulty and deliver the expected results. Self-organizing teams are empowered to make decisions and collaborate with each other, so the project manager should act as a facilitator and coach rather than a directive leader. The other options are not the best choices because they do not address the root cause of the problem, which is the lack of knowledge or skills in the new technology. Requesting the team member to move to another team (option A) may demotivate the team member and create resentment. Delegating other team members to complete this team member’s tasks (option B) may overload the other team members and reduce the team cohesion. Including this team member in an improvement program through a human resources request (option D) may imply that the team member is underperforming and needs to be disciplined, which may lower the team member’s morale and confidence. References: PMBOK Guide, 6th edition, pages 18, 52, 273, 335. Free PMP Practice Exam Questions - 120 Sample Test Questions. PMI PMP Quiz:82 Topic:3 Questions:406-410.

 This answer is based on the concept of adaptive life cycle or agile project management, which is one of the approaches to managing projects in the PMBOK Guide1. Adaptive life cycle is suitable for projects that have high uncertainty, changing requirements, and complex or innovative products1. The main characteristics of adaptive life cycle are:

Delivering products in iterations or increments, each with a fixed duration and scope1.

Seeking frequent feedback from customers and stakeholders to validate the product value and quality1.

Embracing changes and responding to them quickly and effectively1.

Empowering the project team to make decisions and collaborate with each other1.

A minimum viable product (MVP) is a version of the product that has enough features to satisfy the initial needs of the customers and stakeholders, and to provide feedback for future development2. By focusing on releasing an MVP quickly, the project manager can:

Reduce the risk of wasting time and resources on building a product that does not meet the customer’s expectations or needs2.

Increase the customer’s satisfaction and engagement by involving them in the product development process2.

Learn from the feedback and data collected from the MVP and use them to improve the product in the next iteration2.

Adapt to the changing requirements and market conditions by delivering value incrementally2.

Therefore, option D is the best answer, as it aligns with the adaptive life cycle approach and the benefits of MVP. Option A is not a good answer, as it implies a predictive life cycle or waterfall project management, which is more suitable for projects that have low uncertainty, stable requirements, and well-defined products1. Waiting to start the project execution phase until all requirements and acceptance criteria are clear can result in:

Missing the opportunity to deliver value early and often to the customers and stakeholders1.

Increasing the risk of scope creep, change requests, and rework due to changing customer needs or expectations1.

Reducing the flexibility and responsiveness of the project team to adapt to changes1.

Limiting the collaboration and communication between the project team and the customers and stakeholders1.

Option B is also not a good answer, as it assumes that the customer knows all of the requirements at the beginning of the project, which is unlikely for a brand new product. Asking the customer to include all of the requirements in the project charter can lead to:

Creating a rigid and unrealistic scope that does not reflect the customer’s actual needs or preferences3.

Overwhelming the customer and the project team with too many details and specifications that may not be relevant or necessary3.

Ignoring the feedback and learning opportunities that can arise during the project execution phase3.

Reducing the chances of innovation and creativity by restricting the product features and functions3.

Option C is a better answer than option A and B, as it involves the customer in the requirement elicitation process and prioritizes the most important requirements. However, it is still not the best answer, as it does not address the customer’s concern about extra costs and work. Scheduling a brainstorming session and selecting the top ten most important requirements can still result in:

Spending too much time and resources on planning and analysis, instead of delivering value and testing assumptions.

Failing to validate the requirements with the end users and other stakeholders, who may have different needs or expectations.

Missing the opportunity to learn from the feedback and data collected from the product delivery and use.

Delaying the adaptation and improvement of the product based on the changing requirements and market conditions.

The project manager should address the communication needs of all stakeholders and ensure that they are satisfied with the level and frequency of information they receive. The best way to do this is to discuss the issue with all stakeholders and work on a communications management plan that defines the communication requirements, methods, formats, frequency, and responsibilities for each stakeholder group. This will help to avoid misunderstandings, conflicts, and complaints in the future. Recording the meeting and sharing it with the stakeholders who missed it (option C) is a good practice, but it does not solve the root cause of the problem. Ensuring that the stakeholders who are complaining are present for the next meeting (option B) or changing the meeting time to their time zone (option D) are not feasible or fair solutions, as they may create inconvenience or dissatisfaction for other stakeholders. The project manager should consider the time zones of all stakeholders and try to find a suitable time that works for most of them, or use alternative communication methods such as email, video, or audio recordings. References:

PMBOK Guide, 6th edition, page 377-378, section 10.1 Plan Communications Management

PMP Exam Prep, 10th edition, page 405, question 405, answer and explanation

According to the PMBOK® Guide, 7th edition, 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 disagreements1. Issues can arise from various sources, such as changes, risks, defects, conflicts, or assumptions1. Issues can affect the project performance, scope, quality, schedule, cost, or stakeholder satisfaction1.

An issues log is a project document used to capture and track issues until they are resolved1. The issues log typically contains information such as the issue description, priority, owner, status, resolution, and impact1. The issues log is updated throughout the project life cycle as new issues are identified, analyzed, and resolved1.

In this scenario, the newly assigned project manager is informed by a few key stakeholders that the project has some serious issues. The first thing that the project manager should do to understand the issues is to review the issues log to ensure the issues are captured. This will help the project manager to get an overview of the current state of the project, and to identify the nature, scope, and impact of the issues. It will also help the project manager to verify if the issues have been properly documented, prioritized, and assigned to the responsible parties. Reviewing the issues log will also enable the project manager to plan the next steps to address the issues, such as communicating with the stakeholders, performing root cause analysis, implementing corrective actions, or escalating the issues if needed1.

The other options are not as effective as option B. Option A, escalating the issues to the project sponsor, may be necessary if the issues are beyond the project manager’s authority or control, but it is not the first thing to do. The project manager should first review the issues log to understand the issues and their implications, and then decide if escalation is required or not. Option C, checking the risk management plan to ensure there is a strategy to address the issues, may be helpful, but it is not sufficient. The risk management plan provides guidance on how to manage risks, not issues2. Risks are uncertain events or conditions that may have a positive or negative effect on the project objectives, while issues are certain events or conditions that have already occurred and have a negative effect on the project performance1. Therefore, the risk management plan may not cover all the issues that the project faces, and the project manager should review the issues log instead. Option D, asking the key stakeholders to discuss the issues with the project team, may be beneficial, but it is not the first thing to do. The project manager should first review the issues log to get a clear picture of the issues, and then facilitate the discussion between the stakeholders and the team to resolve the issues.

 1: PMBOK® Guide, 7th edition, page 101 2: PMBOK® Guide, 7th edition, page 113

In an agile project, the project manager should collaborate with the stakeholders and ensure their active involvement in the project. The project manager should meet with the unhappy stakeholder to understand their concern and the business impact of the delayed delivery. The project manager should also reprioritize the product backlog as necessary to accommodate the stakeholder’s needs and expectations. Finally, the project manager should invite the stakeholder to join the sprint planning session, where the team selects the work to be done in the next iteration based on the stakeholder’s feedback and the product owner’s guidance. This way, the project manager can improve the stakeholder’s satisfaction and engagement, and foster a trusting and collaborative relationship. Directing the product owner to drop other work in progress and work on the stakeholder’s requirement as the top-priority item may not be the best option, as it may disrupt the team’s flow and compromise the value delivery. Sharing the prioritized items that the team is working on with the stakeholder and inviting them to join the sprint planning session may not be sufficient, as it does not address the stakeholder’s concern and business impact. Securing some additional funding to recruit more resources to the project team to enable faster delivery may not be feasible or effective, as it may violate the agile principle of simplicity and increase the complexity and communication overhead of the project. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 14: Team, Section 14.2: Enable Team Performance, Section 14.3: Lead the Team

Agile Practice Guide, Chapter 2: Life Cycle Selection, Section 2.2: Implementing Agile: Creating an Agile Environment, Section 2.3: Implementing Agile: Delivering in an Agile Environment

Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 4: Analysis, Task 9: Validate Requirements

[Professional in Business Analysis (PMI-PBA)® Examination Content Outline], Domain 4: Analysis, Task 9: Validate Requirements

According to the PMBOK Guide, one of the key project management processes is stakeholder engagement1, which involves identifying, analyzing, planning, managing, and monitoring the stakeholders’ expectations and involvement throughout the project life cycle2. The project manager should use effective communication and collaboration techniques to ensure that the stakeholders are aligned with the project vision, objectives, scope, and deliverables3. This will help to build trust, resolve conflicts, and enhance stakeholder satisfaction. Meeting with the stakeholders regularly is an example of such a technique, as it allows the project manager to share project information, solicit feedback, address issues, and agree on common goals and plans. This is especially important for a project that involves multiple partners and has to comply with various standards and policies.

The other options are not the best ways to ensure project success, because they do not involve stakeholder engagement or collaboration. Option A is too authoritarian and may create resistance or resentment from the contracting partner. Option B is too passive and may result in loss of control or accountability for the project. Option C is too unilateral and may ignore or conflict with the partners’ needs and expectations. References:

1: PMBOK Guide, 6th Edition, page 513

2: PMBOK Guide, 6th Edition, page 515

3: PMBOK Guide, 6th Edition, page 518

PMBOK Guide, 6th Edition, page 520

PMBOK Guide, 6th Edition, page 524

The project manager should have ensured that the project repository is up to date and contains all the relevant information and documentation related to the project deliverables, such as user stories, acceptance criteria, test cases, design specifications, etc. This way, the remaining team members can access the information they need to continue working on the deliverable, even if a senior team member leaves the organization. This practice is consistent with the agile principle of maintaining a single source of truth and ensuring transparency and collaboration among the team members12. References: 1: PMBOK Guide, 6th Edition, Chapter 4: Project Integration Management 2: Agile Practice Guide, Chapter 3: Life Cycle Selection

 Diversity and inclusion are important for project effectiveness, as they enable diverse perspectives, ideas, and experiences to be shared and valued among the project team and stakeholders. However, diversity and inclusion are not just about demographics, but also about creating a culture of respect, belonging, and empowerment for everyone. To achieve this, the organization needs to provide training and education to the entire workforce, not just to specific teams or departments, to raise awareness, foster understanding, and promote positive behaviors. By doing so, the organization can prevent or reduce potential conflicts, misunderstandings, or biases that may arise from different backgrounds, views, or preferences. Furthermore, the organization can leverage the benefits of diversity and inclusion, such as improved innovation, collaboration, and customer satisfaction. References:

Diversity, Equity, and Inclusion in Project Management

Diversity and Inclusion Are Important for Project Effectiveness

Diversity, Equity, & Inclusion | PMI

According to the PMBOK Guide, 6th edition, one of the key processes of the Project Communications Management knowledge area is Plan Communications Management, which involves determining the information and communication needs of the project stakeholders. One of the tools and techniques for this process is communication requirements analysis, which considers factors such as the availability, frequency, format, and level of detail of the information. By asking the project sponsor what sort of information is needed and agreeing on a frequency for the communication, the project manager is performing communication requirements analysis, which will help to tailor the communications management plan to the specific needs and preferences of the project sponsor. References: PMBOK Guide, 6th edition, pages 361-362, 367.

 The project manager should consult the project team to understand the extent of the training needs for the contractor. This is consistent with the agile value of individuals and interactions over processes and tools1. The project manager should also collaborate with the contractor to provide them with the necessary guidance and coaching on the agile principles and practices2. Asking the project sponsor to replace the contractor since they do not have agile experience (A) is not a good option since it may cause unnecessary delays and costs for the project. Issuing a formal notice to the contractor to obtain an agile certification (B) is also not appropriate since it may create a sense of distrust and resentment in the contractor. Instructing the contractor to receive agile training since the project has already started (D) is not a sufficient action since it does not address the specific needs and expectations of the project team and the contractor. References:

1: Agile Practice Guide, Chapter 1, Section 1.2.1

2: Agile Practice Guide, Chapter 2, Section 2.3.2.2

 This is the best answer because it involves engaging the relevant stakeholders in a constructive dialogue about the importance and benefits of following the project management procedures. According to the PMBOK Guide, project management procedures are part of the organizational process assets that help the project manager and the team to perform their work effectively and efficiently. By initiating a review of the procedures, the project manager can identify the gaps, issues, and opportunities for improvement, as well as communicate the value and rationale of the procedures to the CTO and the team. This can also help to build trust, collaboration, and commitment among the project participants. References: PMBOK Guide, 6th edition, pages 38-39, 541-542.

According to the PMBOK Guide, the portfolio management office (PMO) is responsible for ensuring that the projects and programs within the portfolio are aligned with the organizational strategy and objectives. The project manager should demonstrate the project alignment to the organizational strategy by showing how the project delivers value and benefits to the organization and its stakeholders. This may include presenting the project business case, benefits management plan, stakeholder analysis, and other relevant documents that justify the project’s existence and contribution. Demonstrating the project alignment to the organizational strategy is the best way to continue the project and avoid suspension by the PMO. Meeting with the project team and revising the project goals (A) may not be effective if the project is already in alignment with the organizational strategy and the PMO is not aware of it. Updating the project charter to make it align with organizational strategy (B) may not be feasible or ethical if the project charter has already been approved and authorized by the project sponsor and other key stakeholders. Escalating the issue with the project sponsor to request support (D) may be a possible action, but not the best one, as it may create conflict or resentment between the project sponsor and the PMO. The project manager should first try to resolve the issue with the PMO directly by demonstrating the project alignment to the organizational strategy. References: PMBOK Guide, 6th edition, pages 33-34, 75-76, 129-130.

The project management team should review the project plan to evaluate if any updates should be made in response to the news that a competitor has released the latest version of a program. The project plan is a document that describes how the project will be executed, monitored, and controlled. It includes the project scope, schedule, cost, quality, resources, communications, risks, procurements, and stakeholder management plans. The project management team should assess the impact of the competitor’s release on the project’s objectives, deliverables, assumptions, constraints, and risks. The project management team should also consult with the project sponsor, customer, and other key stakeholders to determine their expectations and preferences regarding the project’s scope and quality. The project management team should then decide if any changes or updates are needed to the project plan to ensure the project’s success and value. The project management team should follow the change management process to request, analyze, approve, and implement any changes to the project plan.

The other options are not the best actions for the project management team to take in this situation. Crashing the existing schedule with additional resources to deliver more features may not be feasible or effective, as it may increase the project’s cost, complexity, and risk. It may also not address the customer’s needs or the market’s demand, as the features may not be relevant or valuable. The project management team should not rush to add more features without validating their necessity and feasibility. Stopping the project immediately as the market opportunity has already been missed may be premature and wasteful, as it may disregard the project’s benefits and potential. It may also damage the project’s reputation and stakeholder’s trust. The project management team should not abandon the project without evaluating its viability and value. Continuing with the project plan and target delivery date as expected may be unrealistic and risky, as it may ignore the competitor’s influence and the customer’s feedback. It may also result in delivering a product that is outdated or inferior. The project management team should not proceed with the project plan without reviewing its alignment and suitability. References:

PMBOK® Guide, 6th Edition, Chapter 4, Section 4.2, “Develop Project Management Plan”

PMBOK® Guide, 6th Edition, Chapter 4, Section 4.6, “Perform Integrated Change Control”

PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 4, Section 4.2, “Developing the Project Management Plan” 1

 In an agile project, the product owner is responsible for defining and prioritizing the product backlog, and the team is responsible for delivering the product increment based on the sprint backlog. If the product owner identifies that some key features are missing from the product increment, the project manager should collaborate with the product owner and the team to plan the next sprint and adjust the backlog accordingly. Extending the sprint timeline (A) would violate the time-boxed nature of agile sprints and disrupt the rhythm and cadence of the project. Informing the product owner that the issue needs to be escalated (B) would not solve the problem, but rather create unnecessary conflict and bureaucracy. Initiating the change request process (D) would not be appropriate for an agile project, as changes are expected and welcomed throughout the project lifecycle, and do not require formal approval or documentation. References: PMBOK Guide, 7th edition, page 91; Agile Practice Guide, page 14.

 According to the PMBOK Guide, an agile project is an adaptive life cycle project that follows an iterative and incremental approach. In an agile project, the project manager facilitates collaboration and empowers the team to deliver value. When an unidentified risk becomes an issue, the project manager should help the team review the project approach and initiate the corrective actions to address the issue and prevent recurrence. Asking the sponsor to approve an additional iteration or money is not agile, as it implies that the project scope or budget is fixed and cannot accommodate changes. Asking the team to include the contingency plan in the iteration backlog is not appropriate, as the contingency plan should have been developed before the risk occurred and should be executed as soon as possible. References: PMBOK Guide, 6th edition, pages 18-19, 456-457, 686-687.

The team should ask the product owner to prioritize the item with the customer, as the product owner is responsible for managing the product backlog and ensuring that it reflects the customer’s needs and expectations. The product owner should collaborate with the customer to understand the value and urgency of the enhancement, and decide whether to add it to the product backlog, modify an existing item, or defer it to a later time. The team should not refine and estimate the enhancement, add it to the product backlog, or start working on it without the product owner’s approval, as this may violate the agile principle of customer collaboration and the role of the product owner as the sole authority for the product backlog. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 14: Team, Section 14.2: Enable Team Performance, Section 14.3: Lead the Team

Agile Practice Guide, Chapter 2: Life Cycle Selection, Section 2.2: Implementing Agile: Creating an Agile Environment, Section 2.3: Implementing Agile: Delivering in an Agile Environment

Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 4: Analysis, Task 9: Validate Requirements

Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain 4: Analysis, Task 9: Validate Requirements

According to the PMBOK Guide, a Scrum team is a self-organizing, cross-functional team that delivers value in short iterations called sprints. A burndown chart is a graphical representation of the work remaining versus time. An impediment is anything that prevents the team from achieving its sprint goal. The project manager, or Scrum Master, is responsible for facilitating the Scrum process and removing impediments that hinder the team’s progress and performance. The project manager should take two actions to manage impediments and improve the team’s velocity when a burndown chart indicates that the project is behind schedule. The first action is to look for processes that cause bottlenecks and slow down the team’s agility. This will help to identify and eliminate any unnecessary or inefficient steps, rules, or procedures that hamper the team’s ability to deliver value quickly and effectively. The second action is to work with the team to remove impediments as quickly as possible. This will help to resolve any issues, risks, or conflicts that affect the team’s work, and to provide any support, guidance, or resources that the team needs to complete their tasks. Looking for processes that cause bottlenecks and slow down the team’s agility and working with the team to remove impediments as quickly as possible are the two best actions that the project manager should take in this situation. Assigning the items with high complexity to senior developers (B) may not be optimal or fair, as it may create an imbalance in the team’s workload, skills, and collaboration. Empowering the team to make decisions to remove impediments © may be a good practice, but not an action that the project manager should take, as it is part of the team’s self-organization and autonomy. Moving the items with high complexity to the last iterations (E) may not be feasible or advisable, as it may increase the project risk, scope creep, and technical debt. References: PMBOK Guide, 6th edition, pages 18, 177-178, 541-542.D

 According to the PMBOK Guide, agile project management is an iterative and incremental approach that delivers value to the customer frequently and responds to changes quickly. One of the principles of agile project management is to maximize the amount of work not done, which means eliminating waste and focusing on the most valuable features. The product backlog is a prioritized list of features or requirements that the project team delivers in iterations or sprints. The project manager, in collaboration with the product owner and the stakeholders, should prioritize the product backlog based on the business value and the effort required to deliver each item. By doing so, the project manager can ensure that the project delivers the highest value possible within the budget constraints. The project manager should also adjust the project budget and staffing to account for the prioritized items, and communicate the changes to the project team and the stakeholders. The project manager should not balance the project team, restrict the project scope, or reduce the project staff, as these strategies may compromise the quality, value, or customer satisfaction of the project deliverables. References:

PMBOK Guide, 6th edition, pages 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…

PMI-PBA Guide, pages 15, 16, 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…

The project manager should follow the Monitor and Control Project Work process, which involves tracking, reviewing, and reporting the progress and performance of the project, as well as managing changes and issues that arise. One of the main outputs of this process is the work performance reports, which provide information on the project status, progress, forecasts, issues, risks, and corrective actions. The project manager should use these reports to communicate with the relevant stakeholders and manage their expectations regarding the impact of the component delay on the project schedule. The project manager should also assess the component delay and determine the appropriate response strategy, such as requesting a change, implementing a contingency plan, or escalating the issue to senior management. The project manager should not perform a detailed analysis of the release content for each component of the solution (B), as this is not relevant to the current issue and may waste time and resources. The project manager should not propose a new design of the solution to replace the external component with an internal one ©, as this may introduce new risks, costs, and scope changes that may not be feasible or acceptable to the stakeholders. The project manager should not ask for expedited delivery of the component to mitigate the risk of schedule delays (D), as this may not be possible or realistic, and may also increase the cost and quality risks of the project. References:

PMBOK Guide, 6th edition, pages 105-106, 112-113, 123-124

PMP Exam Content Outline, 2020, pages 9-10, 13-14

PMP Sample Test Questions, 2019, page 5

According to the PMBOK Guide, the project manager is responsible for ensuring that the project deliverables meet the acceptance criteria and obtaining formal acceptance of the deliverables from the customer or sponsor1. The project manager should also involve the relevant stakeholders in the validation and acceptance process to ensure their satisfaction and buy-in2. Therefore, the best option is to set up a meeting with stakeholders to validate and confirm acceptance of the deliverables. Option A is incorrect because the project sponsor is not the only stakeholder who needs to approve the deliverables. Option B is incorrect because updating the project management plan and marking the milestone as completed are actions that should be done after obtaining formal acceptance, not before. Option C is incorrect because asking the vendor to validate the agreement for any deviations is not a sufficient way to ensure the quality and compliance of the deliverables. References: 1: PMBOK Guide, 6th edition, section 4.6.3.2, p. 123 2: PMBOK Guide, 6th edition, section 13.4.2.2, p. 529