PMP PMI Project Management Professional (2025 Version) Free Practice Exam Questions (2025 Updated)

 When facing the potential departure of a key team member during the last iteration of a hybrid project, it is important for the project manager to engage directly with the individual to understand their concerns and reasons for wanting to leave. This aligns with the PMI’s guidance on stakeholder engagement and team dynamics. By having a meeting with the team member, the project manager can explore the underlying issues and work on possible solutions or contingencies that may persuade the team member to stay or ensure a smooth transition if their departure is inevitable1.

In an Agile environment, risk management is a continuous process that involves identifying, analyzing, and responding to risks throughout the project lifecycle. While Agile projects may not have as formalized a risk management process as traditional projects, it is still essential to have a structured approach to identify and manage risks. Creating a risk register allows the project manager and the team to document and track risks, ensuring that they are reviewed and managed appropriately. This approach aligns with the Agile principle of continuous improvement and adaptation, as risks can be reassessed and responses can be adjusted in each iteration or sprint.

When facing challenges with virtual team members being unable to join regular project update meetings, the immediate corrective action should involve direct communication with those team members to understand their constraints and revise the communications management plan accordingly. This approach is proactive and collaborative, aiming to find a feasible solution that accommodates the diverse locations and schedules of the team members, ensuring that everyone can participate in the project updates234.

When the project manager identifies that the delay on the critical path was caused by the client, it is essential to formally document this and then seek a discussion with the client. This supports transparency, allows for resolution, and protects the contractor from inappropriate penalties.

Per the PMBOK® Guide – Seventh Edition and PMI's Contract Management standards, documenting the root cause and opening a dialogue is the first proper step in addressing contractual disputes.

Option B is a valid legal step, but only after engagement and documentation.

Option C refers to an internal party (sponsor) who may not be relevant here.

Option D may support analysis but does not immediately address the contractual issue.

 In situations where there is a conflict regarding project governance, it is important for the project manager to facilitate a discussion between the parties involved. Arranging a meeting with the project team member and the project sponsor to discuss the concerns and work towards a consensus is a proactive approach. This allows for open communication, ensures that all viewpoints are heard, and works towards a collaborative solution. It aligns with conflict resolution techniques that emphasize problem-solving and collaboration12. References: This response is based on conflict resolution strategies recommended in the PMBOK Guide and the standards of practice for project management and business analysis1234.

For a project with a long timeline and complex scope, where the client requires both a high-level, long-term plan and the ability to add features incrementally, a hybrid approach is suitable. Starting with a predictive approach allows the project manager to establish a clear structure and plan using a work breakdown structure (WBS). This sets the foundation for the project’s scope, deliverables, and milestones. Transitioning to an agile approach for execution enables the project to adapt to changes and deliver value incrementally, which meets the client’s need for immediate functionality and continuous improvement. This hybrid method leverages the strengths of both approaches: the clarity and predictability of a predictive approach and the flexibility and responsiveness of an agile approach12.

In an agile project environment, when a new obstacle is identified that impacts the project backlog, it is essential to address it promptly to maintain the flow of work. Reprioritizing the backlog allows the team to adjust their focus on the most critical items that deliver value while managing the blocker effectively12. This approach is in line with the agile principle of responding to change over following a plan, as it enables the team to adapt their priorities based on new information and challenges that arise during the project1.

In Agile projects, it is essential to involve stakeholders and keep them informed about the project’s progress. The sprint review meetings are designed for this purpose, as they provide a platform for the team to demonstrate the work completed during the sprint and gather feedback. Inviting stakeholders to these meetings every 2 weeks aligns with Agile best practices of maintaining regular feedback loops and ensuring stakeholder engagement1. This approach allows stakeholders to see firsthand the project’s progress and contribute their insights, which can be invaluable for the project’s success.

 In situations where the project scope contains items that are well-defined and others that are complex and not fully understood, it is advisable to use a hybrid approach. The well-defined items can be managed using a predictive approach, which relies on a clear understanding of the scope, allowing for detailed planning and control. For the complex items, an agile approach is more suitable as it allows for iterative development, where the scope can be clarified and adjusted as more information is uncovered through progressive elaboration. This approach aligns with the PMBOK guide’s emphasis on tailoring the project management processes to the needs of the project, which may include varying degrees of uncertainty and complexity12.

When a risk such as country-wide power cuts materializes and impacts the project timeline, the project manager should first analyze the impact of the issue on the project’s objectives, including scope, time, cost, and quality. After assessing the impact, a change request should be submitted to update the project schedule, reflecting the new timeline and any adjustments to the project plan. Additionally, the project manager should extend the project deadline accordingly and ensure that the project schedule is updated to reflect this delay. This ensures that all stakeholders are aware of the changes and that the project plan remains accurate and up-to-date. It is also essential to log the risk in the risk register and collaborate with the risk owner to implement the planned mitigation actions, preventing further impact on the project123456789101112131415161718.

 In the context of PMP, when a project encounters technical impediments that could potentially delay deliverables, it is crucial to document and track these issues formally. Updating the issue log is a standard practice in project management, as it ensures that all stakeholders are aware of the impediments and the actions being taken to resolve them. This approach aligns with the principles of communication and transparency in project management, as outlined in the PMBOK® Guide and other PMP reference materials. It allows for a structured method to prioritize and address the issues, facilitating better decision-making and resource allocation to resolve the impediments1.

Personas are fictional characters created based on the behaviors and motivations of real people. They are used in user-centered design to visualize the users and their needs in detail, allowing for a deeper understanding and empathy towards the user. This technique helps in designing tools and systems that strongly appeal to the users by considering their persona, which is crucial for the success of any project that involves user interaction123.

 In an agile project that is part of a larger program with interconnected projects, it is essential to have a high-level plan to monitor dependencies. This ensures that all projects within the program are aligned and that dependencies are managed proactively. The PMI’s guidance on agile project management recognizes the importance of visibility and coordination among projects to manage dependencies effectively12. By developing a high-level plan, the project manager can facilitate collaboration and communication across projects, which is crucial for identifying and addressing potential issues early on.

The project manager should prioritize compliance with the regulatory requirements while exploring ways to accelerate the project timeline. This can be achieved by employing project acceleration strategies such as optimizing resources, streamlining processes, and identifying bottlenecks123. It is essential to maintain adherence to regulations to avoid legal issues and ensure the product’s successful launch. Seeking an exception or bypassing the regulatory process could lead to significant risks and is not advisable.

When faced with a significant change that impacts the project scope or environment, such as the termination of operating systems, the first action should be to engage with stakeholders to assess the impact. This is in line with the agile principle of collaboration and early stakeholder engagement. By scheduling a session with stakeholders, the project manager can gather insights on the implications of the change, which is essential for informed decision-making and planning. This approach is supported by the PMBOK® Guide, which emphasizes the importance of stakeholder engagement and communication when dealing with project changes. Additionally, the Professional in Business Analysis (PBA) materials highlight the need for business analysis to understand the requirements and constraints of the stakeholders, which is critical in this scenario to determine the next steps for the project.

The kick-off meeting is a critical step in the project management process, as it aligns the project team with the project’s objectives and establishes a common understanding among stakeholders. In the context of a multinational company launching a digital transformation project, it is practical to use digital or virtual tools for the kick-off meeting. This approach not only minimizes geographic boundaries, enabling participation from all regions and business lines, but also aligns with the digital nature of the project itself. It is a cost-effective solution that can foster collaboration and communication without the need for travel, which is especially relevant given the global scope of the project.

When external business influences cause changes in business parameters, the project manager should request an update of the project requirements to reflect these changes. This ensures that the project remains aligned with current business objectives and can deliver value as intended. It is a proactive approach that allows for the project to adapt to changing circumstances, which is a key aspect of effective project management. The PMBOK Guide emphasizes the importance of continuously monitoring and controlling project work to ensure that project objectives are met and that project work aligns with the business needs2.

 In an Agile environment, the project manager’s role is to lead the team, set the project goals and objectives, and ensure successful project delivery1. When a team that has been working together in a co-located setting is suddenly dispersed due to unforeseen circumstances, it can disrupt the team dynamics and impact the project’s progress2. To keep the team performing as effectively as possible, the project manager should provide the team with virtual collaboration software and training on the software to minimize disruption2. This approach enables the team to continue collaborating and communicating effectively, thereby maintaining their performance2. References: 2, 1

 In an agile environment, it is crucial for all team members to collaborate and contribute to problem-solving. While the expertise of a subject matter expert (SME) is valuable, it is also important to foster a team culture where collaborative problem-solving is encouraged. This helps in building a self-organizing team that is capable of addressing challenges collectively. The project manager should guide the SME to share their knowledge in a way that empowers the team to learn and grow together, rather than directing solutions based on individual experience alone.

The stakeholder engagement plan should include all stakeholders who have been identified as having needs and a potential impact on the project. This includes both supporters and those who may oppose the project, as understanding and addressing the concerns of all stakeholders is crucial for the success of the project. The PMBOK Guide emphasizes the importance of identifying all relevant stakeholders and managing their engagement throughout the project life cycle12. This approach ensures that the project manager has a comprehensive understanding of the stakeholder landscape and can develop strategies to engage with them effectively, which is essential for navigating complex projects such as the construction of a nuclear power plant.

The PMBOK® Guide emphasizes the importance of a comprehensive change management plan that addresses all aspects of change within a project, including those not contractually specified. By ensuring that the change management plan reflects the requirement for the client’s engineer to review all changes, the project manager can proactively address potential issues and align expectations with the client’s needs. This approach is consistent with best practices in managing project changes and stakeholder engagement, as it helps in preventing misunderstandings and conflicts related to change approvals12. References: PMBOK® Guide – Sixth Edition; “PMBOK Guide Change Management Process For PMP Exam” article by PM-by-PM1; “Change Control Board: Roles, Responsibilities & Processes” article by ProjectManager.com2.

Implementing short cycles for inspection and providing feedback is aligned with the principles of servant leadership and agile project management. Servant leadership emphasizes flexibility, empathy, and empowering team members to adapt and thrive1. It involves facilitating the team’s success by ensuring open communication and stakeholder engagement2. In the context of agile project management, short cycles or iterations allow for regular assessment of the project’s progress and early detection of potential issues, which aligns with the PMBOK® Guide’s principle of engaging with stakeholders3. This approach allows the project manager to address the stakeholder’s concerns by demonstrating progress and managing risks proactively.

The Schedule Performance Index (SPI) is a measure used in project management to indicate how efficiently the project team is using its time. It’s calculated by dividing the earned value (EV) by the planned value (PV). In this case, the team planned to complete 40 story points (PV), but only completed 30 story points (EV). Therefore, the SPI would be calculated as follows: SPI = EV / PV = 30 / 40.

 When a major feature is requested by the project sponsor that significantly impacts the project’s delivery date and budget, the project manager should communicate these impacts to the stakeholders. This involves presenting the results of the impact analysis and negotiating for the necessary resources and time to accommodate the new feature. This approach ensures that the stakeholders are fully informed of the implications and can make decisions based on the project’s best interest. It aligns with the PMBOK guide’s emphasis on stakeholder engagement and communication as key aspects of effective change management1.

After resolving quality issues with deliverables, it is essential for the project manager to conduct a lessons learned session. This process is part of the knowledge area of Project Quality Management, which emphasizes the importance of continuous improvement. Conducting lessons learned helps the team understand what went wrong, why it went wrong, and how similar problems can be prevented in the future. It is a proactive step to enhance the quality of future deliverables and processes.

When a project manager learns that resources initially promised for a project are being reallocated to another priority project, the best course of action is to perform an impact analysis. This analysis will help understand the effects of the resource reallocation on the current project’s schedule, budget, scope, and quality. It is a critical step in project resource management, as it allows the project manager to make informed decisions on how to proceed with the project, whether it involves negotiating for the return of resources, adjusting the project plan, or identifying new resources. The impact analysis is part of the monitoring and controlling process group, where project performance is measured to manage changes to the project scope, schedule, and costs123.

The planning phase is the stage where detailed project planning occurs, including the development of schedules, timelines, and milestones. According to the PMBOK® Guide, during the initiation phase, the project manager works with stakeholders to define the project at a high level. Concrete dates for the most important project milestones are typically established during the planning phase, as this is when the project’s scope, activities, resources, and timelines are defined in detail12.

 When a project budget is cut, it’s important for the project manager to collaborate with the team to assess the impact of the change on the project1. This involves understanding how the budget cuts will affect different aspects of the project, including the scope, schedule, and quality. The project manager should then work with the team to develop an updated project plan that takes into account the reduced budget2. This approach aligns with the principles of servant leadership, which emphasize collaboration, team empowerment, and shared decision-making. References: 

https://project-management.com/what-to-do-if-your-project-runs-over-budget-and-how-to-prevent-it/

A cost baseline is the approved version of the projected costs for the entire project. It is fixed, and, along with other aspects of the project baseline, is used as a benchmark for the rest of the project1. A cost baseline includes the cost estimates for all the tasks on the project schedule, plus the contingency reserves for identified risks (known unknowns)2. A cost budget is the cost baseline plus the management reserves for unidentified risks (unknown unknowns)2. Therefore, before determining the cost baseline, the project manager needs to add contingency into the budget to account for inflation and other changes that may affect the project costs. This is different from looking at a previous project, requiring stakeholder approval, or revising the project timeline and scope, which are not necessary steps for creating a cost baseline. References:

3: What Exactly is a Cost Baseline in Project Management? | Runn

2: Project Cost Management: Cost Baseline vs Budget for PMP Exam

According to the Project Management Body of Knowledge (PMBOK) Guide, one of the key activities in the project initiation process is to identify the project stakeholders and their requirements1. This includes the documentation requirements for the project, such as the format, content, quality, frequency, and distribution of the project documents2. By confirming the documentation requirements with the stakeholders at the beginning of the project, the project manager can ensure that the project documentation will meet the expectations and needs of the stakeholders, as well as comply with any regulatory or contractual obligations3. This will also help the project manager to plan, execute, monitor, and control the project documentation throughout the project life cycle4. Conducting a document review, updating the project templates, and implementing a new change control policy are all important activities for managing project documentation, but they are not sufficient to ensure that the project documentation will fulfill the regulatory requirements. The project manager needs to confirm the documentation requirements with the stakeholders first, and then use these activities to support the documentation process. References:

1: PMBOK Guide, 6th edition, page 30

2: PMBOK Guide, 6th edition, page 89

3: PMBOK Guide, 6th edition, page 112

4: PMBOK Guide, 6th edition, page 123

 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

The project manager should recommend the product owner prioritize the missing work higher because it is needed for the initial launch of the new product. The product owner is responsible for defining and prioritizing the product backlog, which is a list of features and requirements that the customer wants to have in the product. The product owner should ensure that the product backlog reflects the customer’s needs and preferences, as well as the project’s scope and objectives. The project manager should collaborate with the product owner and provide guidance and support on the product backlog management. The project manager should also communicate with the agile team and facilitate their involvement and feedback on the product backlog. The project manager should advise the product owner to prioritize the missing work higher because it is essential for the minimum viable product (MVP), which is a version of the product that has enough features and functionality to satisfy the customer’s needs and expectations. The MVP is the main goal of the initial launch of the new product, as it allows the project team to deliver value to the customer early and often, and to obtain feedback and validation for the product. The project manager should explain to the product owner the importance and benefits of delivering the MVP, and the risks and consequences of delaying or omitting the missing work. The project manager should also help the product owner to balance the competing demands and trade-offs of the product backlog, and to align the product backlog with the project’s vision, goals, and strategy.

The other options are not the best actions for the project manager to take in this situation. Letting the project team pull the recommended work from the bottom of the backlog to maximize value creation may cause confusion and inconsistency in the product backlog, as well as conflict and distrust between the product owner and the agile team. The product owner is the sole authority for defining and prioritizing the product backlog, and the agile team should respect and follow the product owner’s decisions. The project manager should not undermine the product owner’s role or authority, but rather support and facilitate the collaboration and communication between the product owner and the agile team. Analyzing and reprioritizing the backlog and providing the decision to the product owner and team may also undermine the product owner’s role and authority, as well as violate the agile principles and values. The project manager should not impose their own decisions or opinions on the product backlog, but rather advise and assist the product owner in making informed and effective decisions. The project manager should also not act as a intermediary or a gatekeeper between the product owner and the agile team, but rather enable and encourage direct and frequent interaction and feedback among them. Empowering the product owner by supporting the decision and instructing the team to follow the prioritization as provided may ignore the agile team’s input and feedback, as well as jeopardize the project’s success and quality. The project manager should not blindly support the product owner’s decision or instruct the agile team to follow the prioritization as provided, especially if the decision or the prioritization is not aligned with the project’s scope and objectives, or the customer’s needs and expectations. The project manager should challenge and question the product owner’s decision or prioritization if it is not based on valid and relevant criteria or data, or if it does not deliver the maximum value to the customer and the project. The project manager should also listen and consider the agile team’s input and feedback, as they have the technical expertise and experience to perform the work and to deliver the product. References:

PMBOK® Guide, 6th Edition, Appendix X3, Section X3.2.2.4, “Prioritized Product Backlog”

PMBOK® Guide, 6th Edition, Appendix X3, Section X3.2.2.6, “Minimum Viable Product”

PMBOK® Guide, 6th Edition, Chapter 13, Section 13.2.2.1, “Stakeholder Engagement Plan”

PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 12, Section 12.2, “Agile Project Management” 1

A statement of work (SOW) is a formal document that outlines the specific tasks, deliverables, and requirements of a project. It serves as a contractual agreement between a vendor and a client, providing a comprehensive description of the work to be performed. A SOW is used to document the project deliverables when outsourcing work to external parties, as it defines the scope, schedule, quality, and payment terms of the project. A SOW can also include a work breakdown structure (WBS), which is a hierarchical decomposition of the project deliverables into smaller, manageable components. References:

What Is a Statement of Work (SOW)? - Coursera

Statement Of Work Ultimate Guide: Simple Definition & Template

What Is a Statement of Work? Definition & Examples - ProjectManager

The project manager should evaluate the impact the new regulations will have on the project and submit a change request, as this is part of performing integrated change control. Performing integrated change control involves reviewing all change requests, approving changes, and managing changes to the deliverables, organizational process assets, project documents, and the project management plan. By evaluating the impact of the new regulations, the project manager can determine how the project scope, schedule, cost, quality, and risks will be affected, and propose the necessary changes to align the project with the new standards. The other options are not the best ways to handle this situation, as they either ignore, delay, or bypass the change control process. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 4, Section 4.6

PMP Exam Content Outline, June 2019, Domain II, Task 7

PMP Sample Test Questions, Question 372

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, an issue log is a project document that records and tracks any issues that arise during the project and how they are resolved. It is part of the project communications management knowledge area and the monitor communications process. A project manager should update the issue log whenever a new issue is identified, analyzed, or resolved. Updating the issue log and defining the mitigation strategy is the immediate action that the project manager should take to improve the situation of a new team member impacting the project performance. This will help to document the issue, communicate it to the relevant stakeholders, and plan how to address it effectively. Communicating the issue to the human resources department (A) may be a subsequent action, but not the immediate one. Providing additional training to the new hire (B) may be a possible mitigation strategy, but not an action to take before updating the issue log. Increasing team cohesiveness by sharing information and experiences openly © may be a good practice for team development, but not a direct response to the issue at hand. References: PMBOK Guide, 6th edition, pages 377-378, 529-530.

According to the PMBOK Guide, 6th edition, page 141, the project manager should engage with stakeholders throughout the project life cycle to ensure that their needs and expectations are met. When there are changes in the stakeholder environment, such as new or replaced stakeholders, the project manager should identify them and assess their impact on the project. The project manager should also review and prioritize the new requirements with the stakeholders and analyze how they affect the project scope, schedule, cost, quality, and risk. The project manager should then follow the change control process to submit, evaluate, approve, and implement the change requests that are needed to accommodate the new requirements. This approach ensures that the project manager maintains effective communication, collaboration, and alignment with the stakeholders, and delivers a product, service, or result that meets their needs and expectations.

The other options are not the best choices because they do not address the new requirements in a proactive and collaborative manner. Option B is not the best choice because it implies that the project manager is trying to avoid the new requirements and resist the change, which could create conflict and dissatisfaction among the stakeholders. Option C is not the best choice because it implies that the project manager is accepting all the new requirements without analyzing their impact and feasibility, which could lead to scope creep, unrealistic expectations, and poor quality. Option D is not the best choice because it implies that the project manager is imposing a rigid and inflexible approach to the project, which could alienate the new stakeholders and jeopardize their support and engagement.

 Earned value (EV) is a technique that measures the performance of a project by comparing the actual work completed with the planned work. It can help the PMO to report the project’s health in terms of schedule and cost variance, as well as the schedule and cost performance index. EV can be applied to both predictive and adaptive (agile) projects, as long as the project scope, schedule, and budget are defined and measurable. The PMO can use agile progress, such as the number of features delivered, user stories completed, or story points earned, as an input to calculate the EV KPls. This way, the PMO can provide upper management with the traditional reports that they are used to, while also reflecting the agile nature of the projects. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 7, Section 7.4.2.1

Practice Standard for Earned Value Management – Second Edition, Chapter 3, Section 3.2.3

Agile Practice Guide, Chapter 5, Section 5.4.2

An earned value analysis (EVA) is a tool that measures the project performance in terms of scope, schedule, and cost. It compares the planned value (PV), the earned value (EV), and the actual cost (AC) of the project work to determine the variances and the indexes. By conducting an EVA, the project manager can identify the root causes of the project delay and cost overrun, and take corrective actions accordingly. An EVA can also help the project manager communicate the project status and progress to the stakeholders more effectively and objectively. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 7, Section 7.4.2.1

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

PMP Sample Test Questions, Question 2

According to the PMBOK guide, the definition of done (DoD) is a clear and concise list of requirements that a deliverable must adhere to for the team to consider it complete1. The DoD helps to ensure that the customer’s expectations are met and that the quality standards are maintained2. The PMI-PBA guide also states that the business analyst should collaborate with the customer and the team to define and validate the acceptance criteria for each feature3. Therefore, the best way for the project manager to avoid the situation of features being rejected by the customer is to ensure that the DoD is well defined and complete for future iterations, and that it aligns with the customer’s needs and preferences. References:

1: PMBOK guide, page 207

2: PMBOK guide, page 286

3: PMI-PBA guide, page 131

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

The product owner is a key stakeholder in an agile project, who is responsible for defining and prioritizing the product backlog, providing feedback and acceptance for each product increment, and maximizing the value of the product and the work of the development team1. The product owner is not expected to focus on the cost or budget of the project, but rather on the value and quality of the product. The project manager should have worked with the product owner to clarify their role and expectations, and to explain the purpose and scope of the agile ceremonies, such as sprint planning, daily stand-up, sprint review, and sprint retrospective2. These ceremonies are meant to facilitate collaboration, communication, and adaptation among the project team and the product owner, not to report on the budget or cost of the project. The other options are not relevant or effective in changing the product owner’s behavior. References: 1: PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Project Management Institute Inc., 2021, p. 177. 2: PMI, Agile Practice Guide, Project Management Institute Inc., 2017, pp. 50-53.

 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, a project budget is the authorized amount of funds allocated to the project. The project budget is derived from the cost baseline, which is the aggregation of the estimated costs of individual activities or work packages. The project budget should reflect the project scope, schedule, resources, risks, and quality requirements. A project manager should review the base budget model with the team leaders in each country to establish an independent budget for each phase when delivering a highly customizable software solution in multiple countries with significantly different cultures. This will help to account for the variations in the project requirements, constraints, assumptions, and risks in each country and phase, and to ensure the accuracy and adequacy of the project budget. Reviewing the base budget model with the team leaders in each country to establish an independent budget for each phase is the best action that the project manager should do next in this situation. Overestimating costs and underestimating revenues to include the impacts of different cultural elements (B) may not be realistic or reliable, as it may create a false sense of security, waste resources, or reduce profitability. Applying the company’s operational budgeting model © may not be suitable or applicable, as it may not capture the specific characteristics and challenges of the project. Asking the project management office (PMO) to review the draft budget (D) may be a possible action, but not the next one, as it may be premature or ineffective without reviewing the base budget model with the team leaders in each country first. References: PMBOK Guide, 6th edition, pages 235-236, 260-261.

The project manager should educate the new sponsor about the agile approach for project delivery, which is an iterative and adaptive way of working that focuses on delivering value to the customer and responding to change. The project manager should also explain how agile teams are self-organized, meaning that they have the autonomy and authority to plan, execute, and monitor their own work, without excessive control or interference from the sponsor or other stakeholders. The project manager should emphasize the benefits of self-organization, such as increased motivation, collaboration, innovation, and quality. The project manager should also clarify the role and responsibilities of the sponsor in agile projects, which include providing vision, funding, support, and feedback, but not micromanaging or dictating the work of the team. 123 References:

1: What is agile project management? - APM

2: What is Agile? - Project Management Institute

3: Role of Project Sponsor in Agile Project Management - PM Majik

 The project manager should make sure the analyst has regular pairing meetings with the other team member throughout task execution, as this is part of developing project team. Developing project team involves improving the competencies, interaction, and environment of the team members to enhance project performance. By making sure the analyst has regular pairing meetings, the project manager can facilitate knowledge sharing, collaboration, and mentoring among the team members, and address the analyst’s concerns and needs. The other options are not the best ways to handle this situation, as they either ignore, transfer, or delay the analyst’s concerns and development. References: (Professional in Business Analysis Reference Materials source and documents)

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

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

PMP Sample Test Questions, Question 186

The project manager should address this concern with the functional managers to ensure there will be no further delays in the project. The functional managers are the managers who have authority over the team members in their respective functional areas, such as engineering, marketing, finance, etc. The functional managers are responsible for assigning and releasing the team members to the project, as well as providing them with the necessary training, support, and feedback. The project manager should communicate and coordinate with the functional managers to ensure that the team members are available and committed to the project, and that they are not distracted or overloaded by other nonproject-related tasks. The project manager should also explain to the functional managers the impact of their emails on the team’s productivity and morale, and request them to respect the team’s priorities and schedules. The project manager should also seek the support and intervention of the project sponsor or the senior management, if needed, to resolve any resource conflicts or issues.

The other options are not the best actions for the project manager to take in this situation. Asking the product owner to speak with the functional managers to ensure future requirements come through the product owner is not relevant or effective, as it does not address the current problem of the team members receiving emails from their functional managers to support other nonproject-related tasks. The product owner is the person who represents the customer’s voice and defines and prioritizes the product backlog, which is a list of features and requirements that the customer wants to have in the product. The product owner is not involved in the resource management or allocation of the project, and may not have the authority or influence to negotiate with the functional managers. Logging this as a risk in the risk register and continuing to monitor the issue at subsequent meetings is not proactive or sufficient, as it does not prevent or mitigate the negative impact of the team members receiving emails from their functional managers to support other nonproject-related tasks. The risk register is a document that records the identified risks, their causes, impacts, probabilities, responses, and owners. The project manager should not just document and monitor the issue, but also take action to resolve it as soon as possible. Scheduling a meeting with all of the functional managers to resolve the resource conflicts may be too time-consuming and complicated, as it may involve multiple parties and perspectives. The project manager should not wait for a meeting to address the issue, but rather contact the functional managers individually and directly, and seek their cooperation and understanding. References:

PMBOK® Guide, 6th Edition, Chapter 9, Section 9.2, “Plan Resource Management”

PMBOK® Guide, 6th Edition, Chapter 9, Section 9.3, “Acquire Resources”

PMBOK® Guide, 6th Edition, Chapter 9, Section 9.5, “Control Resources”

PMBOK® Guide, 6th Edition, Chapter 11, Section 11.4, “Plan Risk Responses”

PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 8, Section 8.2, “Planning Resources” 1

 According to the PMP Exam Content Outline, one of the tasks of the project manager is to “Assess and prioritize impact on project scope, schedule, cost, quality, and risks of approved changes, and determine cause and effect relationships” (Task 5, Domain II: Process). This implies that the project manager should evaluate the impact of any change that affects the project performance, such as the removal of a key team member. By doing so, the project manager can identify the potential consequences and benefits of the change, and look for alternatives to mitigate the negative effects or enhance the positive ones. The project manager should also submit a change request if required, to update the project management plan and baselines accordingly. This will help to maintain the project alignment with the objectives and expectations of the stakeholders. References:

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

PBA Exam Content Outline, Domain IV: Evaluation, Task 4, page 152

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 4: Project Integration Management, Section 4.6: Perform Integrated Change Control, page 1233

Business Analysis for Practitioners: A Practice Guide, Chapter 6: Traceability and Monitoring, Section 6.4: Manage Changes to Requirements, page 117

The project manager plays the role of a mediator in this situation, as this is part of managing stakeholder engagement. Managing stakeholder engagement involves communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement. By scheduling a meeting with the two stakeholders, the project manager acts as a neutral third party who facilitates the discussion and helps them reach a mutually acceptable solution. The other options are not the best ways to describe the project manager’s role, as they either imply a biased, authoritative, or passive approach to conflict resolution. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 13, Section 13.3.2.4

PMP Exam Content Outline, June 2019, Domain II, Task 9

PMP Sample Test Questions, Question 393

According to the PMBOK Guide, one of the key roles of the project manager in an agile environment is to facilitate collaboration among stakeholders and the team. This helps to manage conflicts, clarify requirements, and align expectations. The project manager should also promote the agile values and principles, such as customer satisfaction, responding to change, and delivering value incrementally. By doing so, the project manager can help move the project forward and ensure the delivery of a high-quality product that meets the customer’s needs. (PMBOK Guide, 6th edition, pp. 53-54) References:

PMBOK Guide, 6th edition, Chapter 3: The Role of the Project Manager, Section 3.3: The Project Manager’s Sphere of Influence, pp. 53-54

Agile Practice Guide, Chapter 2: An Introduction to Agile, Section 2.2: Agile Manifesto Values and Principles, pp. 10-13

The project manager should request the project sponsor prioritize and if necessary, allocate additional budget so the team can work on a single project. This is because working on multiple projects at the same time can reduce the team’s focus, productivity, quality, and morale. It can also increase the risk of delays, errors, conflicts, and rework. Agile approaches require dedicated and cross-functional teams that can deliver value in short iterations. Therefore, the project manager should seek the support of the project sponsor to ensure that the team has the necessary resources and time to work on one project at a time. Providing an incentive plan so the team members will work more unaccounted hours on multiple projects (option B) is not a good solution, as it may lead to burnout, stress, and dissatisfaction among the team members. It may also violate the labor laws and ethical standards. Brainstorming with the team members on how they can deliver on multiple projects within the given budget (option C) is a possible option, but it may not be realistic or feasible, as it may compromise the quality and scope of the projects. Instructing the team members to spread evenly across projects so mistakes will not occur within the current budget (option D) is not a good option, as it may create confusion, duplication, and inconsistency among the team members. It may also prevent the team from forming, storming, norming, and performing as a cohesive unit. References:

PMBOK Guide, 6th edition, page 52-53, section 2.4.2 Project Team

[Agile Practice Guide], page 26-27, section 3.1.1 Team Composition

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

 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.

According to the PMBOK Guide, one of the tools and techniques for collecting requirements is prototypes1. This involves developing a preliminary version or model of the product, service, or result that is expected from the project, and using it to elicit feedback from the stakeholders. By discussing the project scope statement with the key stakeholder and building prototypes, the project manager can improve the stakeholder’s engagement, as well as clarify and validate the requirements, reduce changes, and enhance satisfaction1. The other options are not appropriate, as they do not address the issue of the stakeholder’s frequent requests for changes to the project scope. Discussing the WBS, updating the project backlog, or updating the project charter are all possible actions that could be taken after collecting the requirements, depending on the project methodology and life cycle. References:

1: PMBOK Guide, 6th edition, page 149

The project manager should review the operations manager’s concerns and ensure these concerns are addressed, as this is part of managing stakeholder engagement. Stakeholder engagement involves communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement. By reviewing and addressing the concerns, the project manager can increase the stakeholder satisfaction and support for the project, as well as avoid potential conflicts and delays. The other options are not the best ways to handle this situation, as they either ignore, escalate, or document the concerns without resolving them. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 13, Section 13.3

PMP Exam Content Outline, June 2019, Domain II, Task 9

PMP Sample Test Questions, Question 163

QUE : A self-organizing team is a team that has the autonomy and authority to manage its own work and make its own decisions. A self-organizing team is also expected to adapt to changing situations and learn new skills as needed. Therefore, the best management decision for this situation is to provide opportunity for team members to learn and adjust to the new technology, rather than moving them, adding new members, or re-assigning the project. This will help the team overcome the learning curve and improve their velocity in the future. It will also foster trust, collaboration, and innovation within the team. Providing opportunity for team members to learn and adjust to the technology is consistent with the agile principles and values, which emphasize continuous improvement, customer satisfaction, and team empowerment. It is also covered in the PMBOK Guide under the Develop Team process, and in the PMI-PBA Exam Content Outline under Domain III: Analysis. References:

PMBOK Guide, 7th edition, page 247

PMI-PBA Exam Content Outline, 2018, page 11

Agile Manifesto

STION NO: 184 DRAG DROP

Drag the interpersonal skill on the left to the correct scenario on the right.

Answer:

 The project manager should request an architecture review as the first step to address the design flaw that may potentially impact the final quality. An architecture review is a process of evaluating the design of a system or a product against a set of criteria, such as requirements, standards, best practices, and quality attributes. An architecture review can help to identify and resolve design issues, risks, and gaps, as well as to ensure alignment with the project objectives and stakeholder expectations. By requesting an architecture review, the project manager can involve the relevant experts, such as the new architect, the previous architect (if possible), the quality assurance team, and the customer, to assess the impact of the design flaw and to propose and agree on the necessary changes. This will also help to update the project scope, schedule, cost, and quality baselines accordingly. References:

Architecture Reviews - an overview | ScienceDirect Topics

Architecture Review Process - SEBoK

Architecture Review - The Open Group

Design Flaw Attacks - an overview | ScienceDirect Topics

DESIGN FLAWS: FLAWS BY DESIGN? / The Design Society

The project manager should evaluate the impact to the users and create a plan to address it, as this is part of identifying stakeholders. Identifying stakeholders involves identifying the people, groups, or organizations that could impact or be impacted by the project, and analyzing their expectations, interests, and influence. By evaluating the impact to the users, the project manager can determine their needs, requirements, and potential issues, and create a plan to engage them effectively and manage their expectations. The other options are not the best ways to handle this situation, as they either ignore, assume, or delegate the stakeholder identification process. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 13, Section 13.1

PMP Exam Content Outline, June 2019, Domain I, Task 2

PMP Sample Test Questions, Question 382