A requirement to obtain three supplier quotes before submitting a purchase request is an internal procurement policy or procedure. In PMP terms, internal policies, templates, procedures, and historical guidance are categorized as Organizational Process Assets (OPAs). Referring to OPAs (D) ensures the project manager follows the organization’s established procurement process, including required documentation, approved supplier lists (if any), quote comparison templates, thresholds, and approval workflows. Enterprise Environmental Factors (EEFs) (C) are external or internal conditions that influence the project (market conditions, regulations, culture), but specific procedural requirements like “three quotes” are classic OPAs. A make-or-buy analysis (A) supports sourcing decisions but does not ensure compliance with the internal rule about quotes once the “buy” path is chosen. Reviewing the SOW (B) clarifies what is being procured, but it doesn’t address the mandated procurement steps. Using OPAs aligns procurement actions with governance, reduces audit/compliance risk, and helps the PM execute procurement efficiently and consistently across projects.

==========

According to the PMBOK Guide, the project manager should use a collaborative or problem-solving approach to handle conflicts, as it results in a win-win situation and enhances the project performance1. The project manager should also communicate with the team members and involve them in the decision-making process, as it fosters trust and commitment2. Therefore, the best option is to meet the team member and try to plan a course of action together. Option A is incorrect because guiding the team member on how to resolve the conflict may not address the root cause of the conflict or the impact on the project schedule. Option B is incorrect because analyzing the project schedule and looking for alternatives may not consider the team member’s perspective or input. Option C is incorrect because performing crashing and/or fast tracking of the schedule may not resolve the conflict or may introduce new risks or issues to the project. References: 1: PMBOK Guide, 6th edition, section 9.5.2.1, p. 363 2: PMBOK Guide, 6th edition, section 9.4.2.3, p. 356

 The project manager should call for a team meeting to identify the root cause for the declining performance, as this is part of managing project team. Managing project team involves tracking team member performance, providing feedback, resolving issues, and managing team changes. By calling for a team meeting, the project manager can engage the team members in problem-solving, address any conflicts or misunderstandings, and motivate them to improve their performance. The other options are not the best ways to improve the situation, as they either ignore, delay, or bypass the team involvement. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 9, Section 9.4

PMP Exam Content Outline, June 2019, Domain III, Task 10

PMP Sample Test Questions, Question 175

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

The project manager should first assess the current state process to understand the existing problems, needs, and opportunities for improvement. This will help to define the scope of the digitization project, which is the sum of the products, services, and results to be delivered by the project. Digitizing the current state process exactly as defined, redefining the current state process to scope the supporting software, or developing the software that will support the current state process are all actions that should be done after defining the project scope, not before. References: PMBOK Guide 7th Edition, page 71; Agile Practice Guide, page 37.

According to the PMP Exam Content Outline, one of the tasks of a project manager in the leading domain is to “Communicate roles, responsibilities, and reporting relationships to team members and stakeholders in order to create a project team environment that fosters performance.” This implies that the project manager should reaffirm the required project obligations directly with the team member who failed to communicate the reason for their absence from three team meetings. The project manager should clarify the expectations and consequences of the team member’s behavior, and provide constructive feedback and coaching to help them improve their communication skills and accountability. The project manager should also document the issue and the actions taken to resolve it, and monitor the team member’s performance and attendance. Reaffirming the project obligations directly with the team member can help to prevent further misunderstandings, conflicts, or delays in the project, and enhance the team member’s engagement and commitment. References:

PMP Exam Content Outline

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 9.4.2.1 and 9.4.3.2

Business Analysis for Practitioners: A Practice Guide, Chapter 4.4.1 and 4.4.2

How do project managers deal with unplanned leaves?1

How to deal with a team member who keeps missing deadlines?2

A sudden loss of talent is a resource constraint that reduces delivery capacity across multiple projects. The most practical recovery action is to reduce scope (A) so the remaining team can still meet critical target dates with available resources. Scope reduction (often via re-prioritization, deferring lower-value features, or reducing nonessential deliverables) directly aligns work with constrained capacity and protects the most important outcomes. Crashing (B) generally requires adding resources, but the scenario describes a talent shortage—resources are not readily available—so crashing is not feasible and may increase cost. Fast-tracking (C) increases parallel work and coordination, which typically raises risk and rework; it also assumes adequate staffing to handle overlapping activities, which is unlikely during resignations. Revising target dates (D) may ultimately be required, but as a “recovery” action, the project manager should first optimize scope to preserve key milestones before seeking schedule changes. Right-sizing scope to capacity is the most direct way to stabilize delivery, reduce missed milestones, and maintain stakeholder confidence.

==========

This question fits the Process domain because it deals with document control, change control, and maintaining the integrity of project management plan versions. PMI describes configuration management as a disciplined process with methodology, systems, and procedures used to control change-related elements. The PMBOK errata also notes that updates to the project management plan occur through formal change control processes, which depend on reliable versioning and document control.

The missing latest version of the project management plan indicates a weakness in version control and document management, so the project manager should improve the configuration management process. That action addresses the root cause by strengthening storage, retrieval, baseline control, and change tracking. Option A is weaker because quality assurance is broader and does not specifically solve version-control failures. Option C is useful for organizational learning but will not directly prevent future document loss. Option D may be appropriate as an immediate administrative step, but it does not prevent recurrence by itself. PMP-style reasoning favors fixing the management system that governs controlled documents, making configuration management the best answer.

When vendors are behind and not communicating, the first step is to increase monitoring and obtain reliable status so the project manager can manage recovery. Daily check-ins (A) are an appropriate short-term control to improve visibility, remove blockers, confirm realistic commitments, and track progress against an agreed recovery plan. This aligns with procurement and stakeholder engagement objectives: establish clear communication cadence and accountability. Immediately extending the schedule (B) is premature and may be unnecessary if recovery actions can bring work back on track; it also weakens urgency. Replacing vendors (C) may not be feasible near a deadline due to onboarding time, contract constraints, and integration risk; it’s typically a later escalation if performance does not improve. Reducing pay (D) is contractual and legal territory; penalties must follow contract terms and are not the first response to a communication problem. Tightened governance and frequent coordination is the most practical first action to protect a near-term deadline.

==========

This is primarily a stakeholder communication and engagement breakdown. The first action is to ensure the communication method is effective for that stakeholder and supports timely approvals. Assessing whether the channels are appropriate and updating them (C) aligns with communications management: selecting the right medium, frequency, format, tools, and escalation path to match stakeholder needs and constraints. If email notifications are unreliable for that stakeholder, the project manager can implement redundancy (tool notifications plus calendar invites, messaging app alerts, dashboard reminders) and confirm receipt for critical approvals. Escalating to IT (A) may help later, but it addresses a potential technical symptom without first fixing the process and ensuring stakeholder accountability. HR training (B) is excessive and unlikely to resolve immediate project governance needs. Replacing the stakeholder (D) is rarely feasible and escalatory; it can damage relationships and typically lies outside the project manager’s authority. Strengthening the communication approach reduces missed sign-offs, prevents further cost impacts, and restores predictable decision-making cadence.

==========

This question is best classified in the People domain because it focuses on collaboration, team alignment, and establishing effective ways of working across groups. PMI’s PMP content emphasizes defining team ground rules, engaging and supporting teams, and building shared understanding about a project. In a hybrid environment, where agile and predictive teams operate differently, the project manager should bring representatives from both teams together to establish shared working rules. Meeting with senior team members from both sides is the best choice because it encourages joint ownership, mutual understanding, and practical coordination mechanisms.

Option A is unbalanced because one team should not impose rules on the other. Option C has the same weakness in the opposite direction. Option D is too top-down and does not promote team buy-in. PMP-style leadership favors collaboration over command-and-control, especially when coordination problems arise between teams using different delivery approaches. Creating joint working rules helps clarify communication channels, handoff expectations, decision paths, and timing of interactions. That makes option B the most effective and PMI-aligned action to improve cooperation and reduce delays in a hybrid project setting.

The project manager should schedule a one-on-one meeting with the team member to talk about the issue and get their cooperation. This is an example of the problem-solving technique, which involves confronting the issue directly and cooperatively to find a mutually acceptable solution1. This technique is usually the most effective way to manage conflict in a project team2. Scheduling a meeting with the team member and their manager to discuss the issue (A) is not a good option since it may create a sense of distrust and resentment in the team member. Talking to the project sponsor about the team member’s attitude (B) is also not advisable since it may escalate the conflict and damage the relationship between the project manager and the team member. Finding another person to replace this team member (D) is not a viable option since it would disrupt the project schedule, budget, and scope. References:

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

2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 9, Section 9.5.2.3

When conflict arises between team members, especially around assumptions or decisions, the project manager should address the root cause while reminding the team of the project’s priorities. Discussing the schedule impact emphasizes collaboration over personal preference.

The PMBOK® Guide – Seventh Edition encourages timely conflict resolution and prioritization of project objectives over individual views.

Option A is not a collaborative or long-term solution.

Option B is extreme and not the first course of action.

Option C may overlook critical input and reduce team trust.

Estimating using historical data from past similar projects (analogous estimating) is a best practice to prevent errors and improve accuracy in cost planning. It helps identify items or tasks that may be overlooked if only current project documentation is used.

According to the PMBOK® Guide – Seventh Edition, past project records and lessons learned are valuable tools for improving cost and scope planning.

Option A is a governance step but doesn’t improve estimation accuracy.

Option B addresses when to update but not how to improve the original estimate.

Option C (padding) is not best practice and may not be acceptable in cost-constrained projects.

The project manager is responsible for ensuring that the project remains aligned with its expected benefits and strategic objectives. If the benefits management plan contains questionable or outdated forecasted values, the correct course of action is to confirm that information with the sponsor and key stakeholders. This ensures alignment before execution continues.

Option B is premature and drastic.

Option C disregards the risk of misalignment with business value.

Option D assumes changes before confirming whether the original forecast is incorrect.

The key Agile principle is early and continuous delivery of valuable software, coupled with constant customer collaboration and feedback. If deliverables are not meeting customer expectations, the root cause is likely a breakdown in feedback loops. Establishing a continuous feedback environment ensures stakeholder input is captured early and often, allowing teams to course-correct before features are completed and delivered.

According to the Agile Practice Guide: “Customer engagement and continuous feedback loops help ensure that the solution meets business needs and expectations.”

Option D (retrospective) is important but retrospective happens after the sprint; Option A (continuous feedback) is more proactive and prevents dissatisfaction before it grows.

 According to the PMBOK Guide, when a team member fails to meet a commitment, the project manager should first seek to understand the reasons for the failure. This involves meeting with the team member to discuss the situation. The goal of this meeting is not to reprimand the team member, but to develop a plan to avoid similar situations in the future. This could involve additional training, adjusting the workload, or improving communication. The other options (A, B, C) might be appropriate in some situations, but they do not address the root cause of the problem and do not provide a proactive solution to prevent similar issues in the future. References: Project Management Body of Knowledge (PMBOK) Guide, 6th Edition, Section 9.5.2.1: Develop Team: Tools and Techniques.

 The project manager should work with the team to determine appropriate project methods and practices and implement them. This is because the project manager’s role is to facilitate the team’s work and to ensure that the project is completed successfully. If the team feels that they need to use some agile tools and methods, the project manager should support them in this, even if these methods are not mentioned in the organizational project management processes. The project manager should also communicate with the organization about the team’s needs and work to incorporate these methods into the organization’s processes. References: Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)–Seventh Edition. Project Management Institute, Inc.

In a situation where a significant portion of the project budget has been reallocated, it’s crucial to reassess the project scope and deliverables. The Minimum Viable Product (MVP) approach allows the project to deliver the most essential features with the remaining resources. This approach is often used in agile or hybrid project management methodologies to ensure that the most valuable features are delivered first, even when resources are limited. References: PMBOK Guide, 6th Edition, Section 5.4.2.1: Define Scope: Tools and Techniques

According to the Agile principles, face-to-face conversation is the most efficient and effective method of conveying information to and within a development team. Therefore, it’s important to have a common understanding and agreement among all team members about the timing of the daily standup. In this scenario, the project lead should facilitate a discussion with the entire team, including the agile coach and technical writer, to decide on a suitable time for the daily standup that respects everyone’s time zones and work schedules. References: Agile Practice Guide, PMI, Chapter 3: Implementing Agile: Creating an Agile Environment, Section: Daily Standup/Meeting. Project Management Professional (PMP) Certification Handbook, PMBOK Guide 6th Edition, Chapter 10: Project Communications Management.

When a stakeholder is unhappy with the result of a fixed-price project, the project manager should review the missed program deliverables with the project team1. This allows the team to understand what went wrong and how they can improve in future projects. It’s important to note that in a fixed-price project, the risk of incurring additional costs to complete performance of the project falls entirely on the supplier1. Therefore, performing any out of scope work that has not been agreed to, such as through a change order process, adds costs to the project1. References: The special challenges of project management under fixed-price contracts

 When a project is experiencing delays due to identified risks, the project manager should revise the project schedule and inform the stakeholders regarding any delays1. This approach ensures transparency and allows stakeholders to adjust their expectations accordingly. It’s also important to analyze the scope that is at risk and divide it into smaller, tangible parts. Setting a very short daily meeting or call with the key leaders of the delivery team to closely monitor progress can also help manage the project schedule effectively1.

When team members frequently experience connectivity issues, it’s important for the project manager to first understand the root cause of the problem before implementing a solution. This could involve investigating whether the issue is related to the time of day, the tools being used, or other factors12. Once the problem is understood, the project manager can develop an action plan to address it. This might involve adjusting meeting times, providing support for technical issues, or exploring alternative communication methods12345. References: 12 Project Management Challenges and How To Solve Them | Indeed.com1; Managing Project Issues – 17 Tips for Project Managers | ProjectPractical.com2; How good team connectivity works - Clockify3; 14 Teamwork Challenges and How To Overcome Them | Indeed.com4; Team Management: The Ultimate Guide - ProjectManager5.

The project manager should first validate the reason for the nonpayment of overtime pay. If the complaint is valid, the project manager should add it as an issue in the issue log. The issue log is a project document where all the issues are recorded and tracked. It is used to document and monitor the status of all issues until they are resolved. References: PMBOK® Guide, 6th Edition, Section 4.3: Direct and Manage Project Work, and Section 11.6: Control Risks.

 In Agile methodologies, it’s important to remember that while each team member may work on specific tasks or “stories,” the team as a whole is responsible for the completion of the sprint. This means that if one story is not completed, it’s a reflection on the team, not just the individual who was working on that story. The Agile leader should emphasize this collective responsibility and encourage team members to help each other in order to ensure the completion of all stories in future sprints. References: PMBOK Guide, 6th Edition, Section 9.3.3.3: Team Performance Assessments. Agile Practice Guide, Section 2.3: Team Roles.

 Emotional intelligence, or EQ, is about understanding and dealing with emotions, both personal and teamwide. In project management, having a high EQ helps build strong relationships, solve problems, and lead teams. Leaders with good EQ can understand how others feel, which builds trust and teamwork. These managers can also effectively control their own emotions, staying calm when projects get tough and making smart decisions. EQ improves communication, helps with working with others, and makes projects a positive place where all members feel important and heard1. References: 24 Must-Have Project Management Skills for Project Managers

The client’s priority is market acceleration by targeting a specific segment first (informal sector traders). Planning the project in phases starting with that segment (A) best aligns delivery sequencing to strategic business value. A phased approach enables early deployment to the most impactful users, faster validation of assumptions (adoption, operations, compliance, support needs), and learning that can shape subsequent phases. This is benefits-driven planning: deliver outcomes that unlock value earlier while managing risk through staged rollout. Splitting into parallel projects (B) may increase coordination risk and dilute focus, especially in a new market where discovery and stakeholder engagement are critical. Creating backlog items (C) is a useful technique, but it is a planning artifact; it doesn’t explicitly ensure that the first delivered increment targets the informal sector as a strategic objective. Executing everything simultaneously per schedule (D) prioritizes plan adherence over value realization and can delay the client’s desired market jump-start. Phasing by highest-value segment supports faster time-to-value, controlled expansion, and better alignment with client strategy.

==========

This question is best classified in the People domain because it deals with stakeholder engagement, communication, and conflict management. PMI’s PMP Examination Content Outline says the project manager should analyze communication needs of all stakeholders, determine appropriate communication methods, and confirm that communication is understood and feedback is received. When team members report that an important stakeholder is difficult to work with, the first PMP-aligned response is to evaluate the situation carefully and identify communication alternatives that may improve the interaction.

Option B moves too quickly into a written complaint without first diagnosing the communication problem. Option C is too confrontational and escalates prematurely. Option D also escalates too early, before the project manager has tried to resolve the issue at the lowest appropriate level. PMI guidance on stakeholder management and communication emphasizes understanding motivations, listening, and choosing communication strategies suited to the situation. Therefore, the best first action is to assess the problem and adjust the communication approach, which reflects professional judgment, active listening, and constructive stakeholder engagement.

The project lead must investigate the client ' s claims to assess the validity of the concerns and the associated penalties. Engaging in fact-finding and documentation review is the first step. If there’s a dispute, negotiation should follow. This approach aligns with the PMBOK® Guide’s guidance on issue management and stakeholder engagement.

Option A is premature and accepts liability without due diligence.

Option C bypasses the client’s concern.

Option D deflects the responsibility and delays resolution.

Comprehensive and Detailed Explanation:

At the close of a project, especially one involving multiple agile streams, the best practice is to conduct a formal lessons learned session (also known as a retrospective or post-mortem). This allows comprehensive collection of what went well, what didn’t, and how to improve future projects.

* B is limited to only one sprint.

* C is not the appropriate forum for final reflections.

* D may provide leadership insights but not team-level experience.

By encouraging the SMEs to meet and come to an agreement together, the project manager is using the Collaborate/Problem-Solve conflict resolution technique. This technique involves working together to find a win-win solution that satisfies all parties.

According to the PMBOK® Guide – Seventh Edition, collaboration is the preferred conflict resolution method because it leads to consensus and long-term solutions.

Option A (Compromise) is a lose-lose approach.

Option C (Synergy) is not an official PMI conflict resolution method.

Option D (Force) is a win-lose approach and not used here.

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.