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

 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 project manager should follow the risk management plan that was developed during the planning phase of the project. The risk management plan should include a risk register that identifies the potential risks, their probability and impact, and the planned responses for each risk. Since the labor union contract negotiation was documented as a risk, the project manager should log the issue and execute the risk response plan that was prepared for this situation. This may involve implementing contingency plans, fallback plans, or workarounds to minimize the negative effects of the risk on the project objectives. The other options are not appropriate because they do not follow the risk management plan or they introduce new risks or changes to the project scope, schedule, or budget. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 11: Project Risk Management, pp. 397-441.

PMP® Examination Practice Questions: 400 Practice Questions and Answers to help you Pass, Question 400, p. 401.

 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 agile leader should develop working agreements with the team to address the trouble and disputes they are facing. Working agreements are a set of guidelines or norms that the team agrees to follow to improve their collaboration, communication, and performance. They help to establish a shared understanding of the team’s values, expectations, and behaviors. They also help to resolve conflicts, clarify roles and responsibilities, and foster trust and respect among the team members. Developing working agreements with the team is a participatory and iterative process that involves the input and feedback of all team members. The agile leader should facilitate this process and ensure that the working agreements are aligned with the agile principles and practices. Escalating the issue to the team’s manager (option A) is not a good option, as it may undermine the team’s autonomy and empowerment. Removing some of the team members (option B) is also not a good option, as it may disrupt the team’s dynamics and morale. Reviewing the roles and responsibilities document (option C) is a useful step, but it may not be sufficient or effective to address the root causes of the trouble and disputes. References:

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

[Agile Practice Guide], page 27, section 3.1.2 Working Agreements

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

According to the PMP Exam Content Outline, one of the tasks of a project manager in the leading domain is to “Empower team members and stakeholders by providing them with the level of authority to complete the assigned activities and resolve issues in order to enhance project performance.” This implies that the project manager should empower team members to participate in decision-making and take ownership of actions, especially in megaprojects that involve multiple stakeholders from different geographical areas and cultural backgrounds. Empowering team members can improve team productivity by increasing their motivation, commitment, creativity, and accountability. It can also foster a culture of collaboration, trust, and respect among the diverse team members and stakeholders. Empowering team members can also help the project manager to cope with the complexity and uncertainty of megaprojects, as team members can act more autonomously and responsively to the changing project environment. References:

: PMP Exam Content Outline

: A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 9.4.2.3 and 9.4.3.1

: Business Analysis for Practitioners: A Practice Guide, Chapter 4.5.1 and 4.5.2

: Megaprojects – Concepts, Strategies, and Practices for Success1

: The Three Secrets of Megaproject Success: Clear Strategic Vision, Total Alignment, and Adapting to Complexity2

According to the PMBOK Guide, a design change is a type of change request that modifies the product or service specifications, features, or functions. A design change might potentially add value to the project, but it might also affect the project scope, schedule, cost, quality, risk, and other aspects. Therefore, the project manager should not accommodate, consult, or convince the client without following the change management process. The change management process involves identifying, analyzing, documenting, presenting, deciding, communicating, and implementing the change request. The project manager should make transactional decisions focusing on the project goals, which means assessing the feasibility, desirability, and priority of the change request, and preparing a recommendation for the change control board (CCB). The CCB is the formal recognized group that reviews, evaluates, and takes decision on change requests. The CCB can approve, partially approve, or reject the change request based on the project goals, objectives, and constraints. The project manager should communicate the decision of the CCB to the client and implement the approved changes accordingly. References:

PMBOK Guide’s Change Management Process For PMP Exam

Change Log - Project Management Knowledge

Project Management Change Request Form & Process

Change Log Template - Project Management Docs

 According to the PMBOK® Guide, the project manager is responsible for closing the project or phase, which includes verifying that all the project deliverables are completed and accepted, updating the project records and documents, releasing the project resources, and communicating the project closure to the stakeholders. Performing administrative closure of the project ensures that the project is formally completed and closed, and that the project budget is finalized and closed as well. This will prevent any confusion or issues with the accounting manager or other parties in the future. Conveying task completion information to accounting may be part of the project closure process, but it is not sufficient to close the project budget. The project manager should also update the project status, financial records, and lessons learned. Closing the procurement process properly is necessary for projects that involve contracts or agreements with external vendors or suppliers, but it is not the only aspect of closing the project. The project manager should also close the internal aspects of the project, such as deliverables, resources, and stakeholder satisfaction. Completing the transition process is relevant for projects that produce products, services, or results that need to be transferred to the operations or maintenance teams, but it is not the only activity for closing the project. The project manager should also ensure that the project objectives are met, the project scope is verified, and the project performance is evaluated. References: PMBOK® Guide, Sixth Edition, Chapter 4, Section 4.7 (Close Project or Phase) and Appendix X3, Table X3-1 (Project Closure Checklist)

According to the PMI Guide to Business Analysis, emotional intelligence is the ability to perceive, understand, and manage one’s own and others’ emotions. It is an essential skill for agile teams, as it helps to foster collaboration, trust, communication, and feedback. A project leader who invests in developing the team’s emotional intelligence can help to motivate the team members, resolve conflicts, and improve performance. Asking the unmotivated team member to take a short leave, reducing the number of meetings, or sending the team member to another team are not effective solutions, as they do not address the root cause of the problem or help the team member to improve their motivation and engagement. References:

PMI Guide to Business Analysis, pages 38-39, 2.4.3 Emotional Intelligence

PMI-PBA Sample Questions, question 10, answer A

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

According to the PMBOK Guide, requirements elicitation is the process of identifying and communicating with stakeholders to determine what their needs and expectations are for the project. Requirements elicitation helps to ensure that the project delivers value to the stakeholders and meets their requirements. In this scenario, the project manager should have applied requirements elicitation techniques, such as interviews, workshops, surveys, or observation, to involve the stakeholders consistently in the requirements process and to clarify and validate their needs and expectations. This would have helped to avoid the situation of conflicting and changing information from the stakeholders and to gain their buy-in and support for the project. References: PMBOK Guide, 6th edition, page 140-141. PMP Sample Test Questions, question 4. Free PMP Questions and Answers, question 4. Free PMP Practice Exam Questions, question 4.

 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

According to the PMBOK® Guide, the project manager is responsible for leading and directing the project team and ensuring that the project objectives are met. Therefore, the project manager should not delegate the decision-making authority to the team or the sponsor without analyzing the impacts and creating a plan for team decision making. The project manager should also consider the risks, issues, and stakeholder expectations that may arise during their absence and communicate the plan to the relevant parties. Postponing the vacation to a different time may not be feasible or desirable for the project manager, and it may also affect their work-life balance. Allowing the team to make decisions to stay on schedule may result in scope creep, quality issues, or conflicts among team members. Asking the project sponsor to make any necessary decisions may undermine the project manager’s authority and credibility, and it may also burden the sponsor with additional work. References: PMBOK® Guide, Sixth Edition, Chapter 9, Section 9.4.2.3 (Team Decision Making) and Chapter 13, Section 13.3.2.4 (Project Manager)

According to the PMBOK Guide, a servant leader is a leadership style that focuses on serving the needs of the team, empowering them, and creating a culture of trust, collaboration, and ownership. A servant leader should also motivate and inspire the team, especially when they face challenges or fatigue. If some team members are starting to complain about the length of the project, creating a risk for lack of performance at this critical stage, the project manager should schedule a team event with the project sponsor to highlight the importance of the project and recognize the work of the team. This will help the project manager to mitigate the risk by showing appreciation and gratitude to the team, reinforcing the project vision and value, and boosting the team morale and engagement. Scheduling a team event with the project sponsor is also a way of celebrating the team’s achievements and rewarding them for their efforts. Meeting with the team to reinforce their responsibilities and the consequences if the project deliverables are not completed on time is not a servant leader approach, as it may demotivate and pressure the team, and create a negative atmosphere. Applying additional controls to the project deliverables to ensure that all milestones are achieved on time is not a servant leader approach, as it may micromanage and constrain the team, and reduce their autonomy and creativity. Contacting the functional manager to ensure that team motivation remains high until the end of the project is not a servant leader approach, as it may delegate the responsibility and authority of the project manager, and undermine the relationship and trust between the project manager and the team. References: PMBOK Guide, 6th edition, pages 56-57, 686-687, 723-724.

 According to the PMBOK Guide, an iterative-based strategy is a release strategy that delivers the product incrementally over multiple iterations, each adding more functionality and value. This strategy allows the project team to obtain early feedback from the customers and stakeholders, and to adapt to changing requirements and priorities. In this scenario, the project manager should recommend an iterative-based strategy to maximize value by releasing the product to each country as it is finalized and ready for release in that country. This will help to meet the specific requirements of each country, and to deliver value faster and more frequently. References: PMBOK Guide, 6th edition, page 19-20. PMP Questions page 515, question 515. PMP Practice Exam, question 4.

To answer this question, we need to calculate the earned value (EV), the planned value (PV), and the actual cost (AC) of the project based on the given information. Then, we can compare them to determine the project status in terms of schedule and cost performance.

The earned value (EV) is the monetary value of the work completed so far. It can be calculated by multiplying the percent complete of the project by the budget at completion (BAC), which is the total approved budget for the project. The BAC can be obtained by adding the approved work package cost estimates, the contingency reserves, and the management reserves. In this case, the BAC is:

BAC=9500+500+(10%×500)=10550

The EV is then:

EV=50%×10550=5275

The planned value (PV) is the monetary value of the work that was planned to be completed by a certain date. It can be calculated by multiplying the planned percent of the project by the BAC. In this case, the PV is:

PV=40%×10550=4220

The actual cost (AC) is the monetary value of the work actually performed. It is given as:

AC=4500

To determine the project status, we can use the cost variance (CV) and the schedule variance (SV) formulas. The CV is the difference between the EV and the AC, and it indicates whether the project is under budget or over budget. A positive CV means the project is under budget, while a negative CV means the project is over budget. The CV is:

CV=EV−AC=5275−4500=775

The SV is the difference between the EV and the PV, and it indicates whether the project is ahead of schedule or behind schedule. A positive SV means the project is ahead of schedule, while a negative SV means the project is behind schedule. The SV is:

SV=EV−PV=5275−4220=1055

From the CV and SV values, we can conclude that the project is under budget and ahead of schedule. To find the percentage of deviation from the planned cost and schedule, we can use the cost performance index (CPI) and the schedule performance index (SPI) formulas. The CPI is the ratio of the EV to the AC, and it measures the cost efficiency of the project. A CPI greater than 1 means the project is under budget, while a CPI less than 1 means the project is over budget. The CPI is:

CPI=ACEV​=45005275​=1.17

The SPI is the ratio of the EV to the PV, and it measures the schedule efficiency of the project. A SPI greater than 1 means the project is ahead of schedule, while a SPI less than 1 means the project is behind schedule. The SPI is:

SPI=PVEV​=42205275​=1.25

From the CPI and SPI values, we can calculate the percentage of deviation from the planned cost and schedule by subtracting 1 and multiplying by 100. The percentage of deviation from the planned cost is:

(CPI−1)×100=(1.17−1)×100=17%

The percentage of deviation from the planned schedule is:

(SPI−1)×100=(1.25−1)×100=25%

Therefore, the project cost is 17% lower than planned, and the project schedule is 25% ahead of planned. Among the given options, the closest one is B. The project cost is 10% lower than planned.

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

 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

According to the PMBOK Guide, one of the tools and techniques for the Plan Risk Management process is the review of lessons learned from previous projects. This helps the project manager to identify potential risks, causes, and responses for the current project. By studying and applying the lessons learned from the failed project, the project manager can avoid repeating the same mistakes and improve the project performance. This is also consistent with the principle of continuous improvement and organizational learning. References: PMBOK Guide, 6th edition, page 397-398. PMP Sample Test Questions, question 3. Free PMP Exam Practice Questions, question 3. PMP Questions page 485, question 485.

According to the PMI-PBA guide, one of the key competencies of a business analyst is to facilitate collaboration and negotiation among stakeholders1. This is especially important in agile projects, where the business analyst may also act as the project manager or product owner2. The PMBOK guide also states that the project manager should foster a collaborative project team environment that enhances individual and team performance3. Therefore, the best way for the project manager to influence the agile team is to express trust in their ability to deliver value and meet the project objectives, rather than imposing authority, control, or additional resources. References:

1: PMI-PBA guide, page 16

2: PMI-PBA guide, page 23

3: PMBOK guide, page 59

Velocity is a measure of the amount of work a team can complete in a given iteration. It is calculated by dividing the total number of story points completed by the team by the duration of the iteration. Velocity can vary from iteration to iteration due to various factors such as team size, complexity of work, technical issues, etc. Therefore, it is not advisable to use a single iteration’s velocity as a baseline for future planning. Instead, the project manager should ask the product owner to look at a minimum of four to eight iterations and use the average or median velocity as a more reliable indicator of the team’s performance. This way, the product owner can replan the velocity for the next iteration based on the team’s current performance and adjust the scope and schedule accordingly. This is consistent with the agile principle of responding to change over following a plan and the PMI-PBA practice of planning and monitoring the business analysis approach. References:

PMBOK Guide, 6th edition, page 18, section 1.2.3.2

Agile Practice Guide, page 36, section 3.3.2

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

PMI-PBA Certification Exam Prep Guide, page 63, section 3.2.1

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, hybrid project management is a technique where high-level project phases are planned using the waterfall approach, and project phase work (actual tasks) execution is done the Agile way1. Hybrid project management is getting more attention as it offers the flexibility to combine the best practices from both waterfall and agile methodologies2. One of the benefits of hybrid project management is that it allows the project team to adapt to changing requirements and customer needs, which are common in projects with a high level of uncertainty3. However, this also requires the project manager to adopt a different role than in a traditional waterfall project. Instead of being a central authority who directs and controls the project, the project manager should act as a facilitator, coach, and servant leader who supports and empowers the project team to do the work4. This means that the project manager should trust the team’s expertise and experience, delegate decision-making authority, provide feedback and guidance, and remove any impediments that hinder the team’s progress5. By doing so, the project manager can foster a collaborative and agile culture that enhances the team’s performance and satisfaction6.

Therefore, the best way for the project manager to address the issue of losing control of the project is to adopt the role of supporting and empowering the project team to do the work (option C). This will help the project manager to cope with the uncertainty and complexity of the project, and to leverage the team’s skills and knowledge. Modifying the daily standup meetings to include project status reporting (option A) may not be effective, as it may disrupt the purpose and flow of the standup meetings, which are meant to be brief and focused on the team’s progress, issues, and plans. Escalating the issue to the change control board (CCB) and asking for advice (option B) may not be appropriate, as the CCB is usually responsible for reviewing and approving changes to the project scope, schedule, cost, or quality, not for providing guidance on the project management approach. Changing the approach for the project to a predictive approach (option D) may not be feasible or desirable, as it may not suit the nature and context of the project, and it may cause resistance and confusion among the project stakeholders. References:

1: PMBOK® Guide, 6th edition, p. 19

2: Teamhood, Hybrid Project Management: What is it, Approach & Software

3: The Digital Project Manager, Ultimate Guide To Hybrid Project Methodologies & How To Make Them

4: PMBOK® Guide, 6th edition, p. 54

5: PMI, Agile Practice Guide, p. 21

6: PMI, Agile Practice Guide, p. 22

[7]: PMI, Agile Practice Guide, p. 50

[8]: PMBOK® Guide, 6th edition, p. 115

[9]: PMBOK® Guide, 6th edition, p. 18

 According to the PMBOK Guide, project artifacts are any documents or information that are produced or consumed by a project, such as plans, reports, contracts, deliverables, etc. Project artifacts should be archived at the end of the project or phase for future reference, lessons learned, audits, or legal purposes. The project management office (PMO) is a centralized entity that oversees the management of projects, programs, and portfolios, and provides guidance, standards, policies, and procedures for project management. The project manager should consult with the PMO for guidance on how to archive the project artifacts for the cancelled project, as the PMO may have specific requirements or best practices for this process. The project manager should not comply with the project sponsor’s request to not archive the project artifacts, as this may violate organizational policies, contractual obligations, or ethical principles. The project manager should not archive the project artifacts on his or her local computer, as this may compromise the security, accessibility, or quality of the information. The project manager should not document the project sponsor’s instructions as the archived project artifacts, as this may not capture the full scope, history, or outcome of the project. References:

PMBOK Guide, 6th edition, pages 33, 89, 123, 126, 129, 686

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…

According to the PMBOK Guide, a sprint retrospective is a meeting held at the end of each sprint to review the work done, identify the lessons learned, and plan the improvements for the next sprint1. The project manager should document the lessons learned and implement the improvements in the next sprint to ensure continuous improvement and customer satisfaction2. The other options are not the next step for the project manager. Facilitating a daily standup is a regular activity during the sprint, not after it3. Organizing a demonstration of the changes is done at the end of each sprint to show the product increment to the customer and stakeholders. Requesting that all team members think of ideas to improve processes is not a specific action, but a general expectation. References:

1: PMBOK Guide, 6th edition, page 188

2: PMBOK Guide, 6th edition, page 189

3: PMBOK Guide, 6th edition, page 186

: PMBOK Guide, 6th edition, page 187

: PMBOK Guide, 6th edition, page 190

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

 According to the PMBOK Guide, quality assurance is the process of auditing the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used. Quality assurance helps to identify and correct any deficiencies in the project processes and deliverables. In this scenario, the project manager should perform quality assurance to review the processes against the quality management plan and identify the gaps that led to the missing documents and approvals. This will help to ensure that the project is compliant with the quality standards and prevent future nonconformities. References: PMBOK Guide, 6th edition, page 288-289. PMP Questions page 495, question 495. How To Find The Correct Answer On PMP Exam Questions.

The project manager should identify adequate change management tools to conduct the project, as this will help them to manage the changes to the product baseline in a flexible and efficient way. Change management tools are methods, techniques, or software that help to plan, execute, monitor, and control changes in a project. Some examples of change management tools are change request forms, change logs, configuration management systems, traceability matrices, and change impact analysis. By using these tools, the project manager can ensure that the changes are properly documented, evaluated, approved, implemented, and communicated. This will also help to minimize the risks and costs associated with the changes, and to maintain the quality and scope of the product. References:

Change Request Form: Definition, Types, Process & Tools

Change Log Template - Project Management Docs

Configuration Management: What is it and why is it important?

Traceability Matrix in Software Testing with Example Template

Change Impact Analysis - an overview | ScienceDirect Topics

According to the PMBOK® Guide, the project manager is responsible for identifying, analyzing, and responding to project risks, and documenting them in the risk register (Section 11.1). If the project manager discovers that the same team has been missing delivery dates in previous projects, this indicates that there is a potential risk that may affect the project schedule and performance. The project manager should include this in the risk register, and assign a probability and impact rating, a risk owner, and a risk response strategy. This will help the project manager to monitor and control the risk, and to take appropriate actions if the risk occurs. This is also consistent with the Professional in Business Analysis (PMI-PBA)® Examination Content Outline, which states that one of the tasks of a business analyst is to “identify and analyze risks and opportunities related to the business need, requirements, and recommended solutions” (Task 3.5). References:

PMBOK® Guide, 6th Edition, Section 11.1

Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Task 3.5

According to the PMBOK Guide, a business case is a document that provides the justification for undertaking a project or an additional scope, based on the estimated costs, benefits, and risks. A project manager should develop a business case and submit it to the client when they realize that some minor changes could deliver significant benefits to the client early. This will help to communicate the value proposition of the changes, and to seek the client’s approval and support. Developing a business case and submitting it to the client is the best approach that the project manager should take in this situation. Concentrating on the current project milestones (A) may not be optimal or beneficial, as it may miss the opportunity to enhance the client satisfaction and project outcomes. Updating the project management plan for this new work (B) may not be feasible or ethical, as it may violate the project scope, schedule, and budget baselines, and the agreed-upon project objectives and deliverables. Making all the changes and then showing the client the results (D) may not be appropriate or acceptable, as it may create scope creep, increase project risks, and damage the trust and relationship with the client. References: PMBOK Guide, 6th edition, pages 33, 75, 129.

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 PMBOK® Guide, the project manager is responsible for managing the project changes and ensuring that they are aligned with the project objectives and stakeholder expectations. Therefore, the project manager should evaluate the impact of the decision to switch from a cloud-based system to a dial-up service on the project scope, schedule, cost, quality, risk, and communication. The project manager should then communicate the impact analysis and the potential alternatives to the management and seek their approval or guidance. Agreeing with management and continuing working the project management plan may not be the best option, as it may result in poor project performance, stakeholder dissatisfaction, or ethical issues. The project manager should not blindly accept the decision without analyzing its consequences and exploring other options. Meeting with management about their decision and asking them to get another project manager may be unprofessional and irresponsible. The project manager should not abandon the project or escalate the issue without trying to resolve it first. Replacing some of the team members that work virtually to help the company save money may not be feasible or desirable. The project manager should consider the impact of losing valuable team members, the cost and time of hiring and training new ones, and the effect on the team morale and productivity. References: PMBOK® Guide, Sixth Edition, Chapter 4, Section 4.6 (Perform Integrated Change Control) and Chapter 13, Section 13.3.2.4 (Project Manager)

According to the PMBOK Guide, an impediment board is a visual tool that tracks the impediments or blockers that prevent the team from completing their work1. The project manager should create an entry in the impediment board and assign it to the person or team responsible for resolving it. This will help the project manager monitor the progress of the impediment resolution and communicate it to the stakeholders. The other options are not the best actions for the project manager to do. Inviting the project team to a swarming session to define a solution is a technique that can be used to address complex or urgent problems, but it is not appropriate for an issue that is outside the project team’s control2. Leveraging the network of the former department and asking for help is a possible way to expedite the completion of the task, but it is not a formal or transparent way to manage the impediment. Escalating the issue to the product owner to define the next steps is not the project manager’s responsibility, as the product owner is mainly concerned with the product vision and value, not the project execution3. References:

1: PMBOK Guide, 6th edition, page 570

2: PMBOK Guide, 6th edition, page 571

3: PMBOK Guide, 6th edition, page 49

 According to the PMBOK Guide, the project steering committee is a group of senior stakeholders who provide strategic direction, guidance, and support to the project. The project steering committee is also responsible for resolving high-level issues and risks that may affect the project. In this scenario, the project manager should escalate the issue of funding access to the project steering committee, as they have the authority and influence to resolve it. The project steering committee can help to expedite the funding process, negotiate with the finance department, or find alternative sources of funding. This will help to avoid further delays and ensure the project can proceed with the procurement process. References: PMBOK Guide, 6th edition, page 33-34. PMP Questions page 524, question 524. [Project Steering Committee: Roles and Responsibilities].

The project manager should ensure that the product owner collaborates with the compliance officer to review the user stories in the product backlog and ensure that they meet the regulatory requirements. This is consistent with the agile principle of satisfying the customer through early and continuous delivery of valuable software. The project manager should also monitor the compliance status of the product backlog items and communicate any risks or issues to the relevant stakeholders. The project manager should not have the team consult with the compliance officer to update the DoD for the past sprint, as this would be a waste of time and resources. The project manager should not have the product owner consult with the CCB, as this would introduce unnecessary bureaucracy and delay the delivery of value. The project manager should not have the scrum master organize a weekly meeting with the compliance officer, the product owner, and the project team, as this would reduce the autonomy and self-organization of the team. References:

PMP Exam Content Outline (2021), Domain II: Process, Task 2: Execute project with the urgency required to deliver business value, p. 101

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 5: Project Scope Management, Section 5.4.2.1: Product Backlog, p. 1542

Agile Practice Guide, First Edition, Chapter 2: Life Cycle Selection, Section 2.2.1: Scrum, p. 213

Professional in Business Analysis (PBA) Examination Content Outline (2018), Domain III: Analysis, Task 1: Elicit Requirements, p. 14

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]

The project manager should describe to the team members how specific tools and techniques can be used to finish on time, as this will help them understand the rationale behind the rigorous process and how it can benefit the project. This will also demonstrate the project manager’s respect for the team’s expertise and autonomy, and foster a collaborative and supportive environment. The other options are not as effective or appropriate as describing the tools and techniques to the team. Crashing the project schedule and asking the team to work overtime may increase the risk of errors, burnout, and resentment. Motivating the team by offering incentives may not address the root cause of the resistance, and may create a sense of coercion or manipulation. Convincing the team to use a specific methodology may not be feasible or suitable for the project, and may undermine the team’s self-organization and creativity. References:

PMBOK Guide, 7th edition, page 249

PMI-PBA Exam Content Outline, 2018, page 11

 According to the PMBOK Guide, the project manager is responsible for managing the project information and ensuring that it is appropriately distributed, stored, and protected. The project manager should also adhere to the policies and procedures regarding the confidentiality and security of the project information. If the project sponsor requests technical specifications for a project-related component that he or she does not have the authorization to see, the project manager should first meet with the project sponsor as soon as possible to discuss the matter further and understand the reason behind the request. The project manager should also explain the implications of disclosing the specifications without proper authorization and try to resolve the issue amicably. Updating the issue log, creating a stakeholder engagement plan, or providing the specifications with some information removed are possible actions that the project manager can take after meeting with the project sponsor, depending on the outcome of the discussion. However, they are not the first actions that the project manager should take in this situation. References: PMBOK Guide, 6th edition, pages 376-377, 395-396.

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

 According to the PMBOK® Guide, the project manager is responsible for managing the project resources, including human resources, and ensuring that they have the necessary skills and competencies to perform the project work. Therefore, the project manager should identify the sources and specifics of the knowledge gap from the interns and new recruits, and put them into groups and assign a SME as a mentor. These actions will help the project manager to address the root cause of the problem, provide effective learning and coaching opportunities for the interns and new recruits, and leverage the expertise and experience of the SMEs. Hiring more SMEs and informing the human resources manager to lay off the nonperforming interns and new recruits may not be feasible or ethical. The project manager should try to resolve the issue within the existing project team, rather than replacing or firing the team members. Initiating a project change request for additional budget to train the interns and new recruits may not be possible or timely. The project manager should try to use the available resources and budget, rather than requesting more funds. Ignoring the issues with the project and trying to deliver the project successfully without asking for training funds may not be realistic or responsible. The project manager should not overlook the knowledge gap that may affect the project quality, scope, or schedule, but rather seek to close the gap and improve the team performance. References: PMBOK® Guide, Sixth Edition, Chapter 9, Section 9.2 (Develop Team) and Section 9.3 (Manage Team)QUESTION NO: 449

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 manager should meet with the project team to assess their current skills and identify any gaps or training needs that may affect the project execution. This is part of the Plan Resource Management process, which involves determining the project roles, responsibilities, required skills, and reporting relationships1. Sending the list to the project team and asking them to get training on the required skills (A) is not a proactive or effective way of managing the project resources. Asking the functional manager to review the resource pool and recommend the right individuals to join the team (B) is not feasible since the project team has already been assigned. Discussing the list with the project sponsor to confirm that the resources have the required skills © is not the responsibility of the project sponsor, who is mainly concerned with the project benefits and alignment with the strategic objectives2. References:

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

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

According to the PMBOK Guide, 6th edition, one of the key processes of the Project Stakeholder Management knowledge area is Identify Stakeholders, which involves identifying the people, groups, or organizations that could impact or be impacted by the project, and analyzing their expectations, interests, and influence. One of the outputs of this process is the stakeholder register, which contains information such as the identification, assessment, and classification of the project stakeholders. By reviewing the stakeholder register, the project manager can gain insight into the expectations of the specific client team member who is requesting trivial information, and understand the possible reasons behind their behavior, such as lack of trust, low engagement, or hidden agenda. This will help the project manager to plan and implement appropriate strategies to manage the stakeholder’s expectations and requests, and avoid unnecessary conflicts or delays in the project. References: PMBOK Guide, 6th edition, pages 509-510, 515.

According to the PMBOK® Guide, 7th edition, one of the principles of project management is to collaborate with stakeholders and team members1. This principle emphasizes the importance of establishing and maintaining a shared understanding of the project vision, objectives, and expectations among all project participants. It also suggests that project managers should foster a team culture that supports collaboration, trust, learning, and adaptation1.

In an agile project, the team rules are a set of agreements that define how the team will work together, communicate, and deliver value2. The team rules should be established at the beginning of the project and reviewed periodically to ensure they are still relevant and effective2. The team rules should also be aligned with the agile values and principles, such as responding to change over following a plan and individuals and interactions over processes and tools3.

In this scenario, the project manager observes that the team is having problems meeting their goals in the second iteration. This could indicate that the team rules are not clear, not followed, or not suitable for the current situation. Therefore, the best course of action for the project manager is to provide feedback to the team and conduct a meeting to review the team rules. This will help the team to identify and resolve any issues or conflicts that are affecting their performance, and to update or modify the team rules as needed. This will also help the new team member who does not have agile experience to understand and adapt to the team’s way of working.

The other options are not as effective as option A. Option B, conducting a retrospective meeting to find a root cause, is a good practice for agile teams, but it is usually done at the end of each iteration, not in the middle. A retrospective meeting is also focused on evaluating the past iteration and identifying improvement actions for the next one, not on reviewing the team rules. Option C, requesting agile training for the new member, may be helpful, but it does not address the immediate problem of the team’s performance. It also assumes that the new member is the only source of the problem, which may not be true. Option D, coaching the new team member in agile methodology, is also a good practice, but it is not the primary responsibility of the project manager. The project manager should delegate the coaching task to a more experienced team member or a mentor, and focus on facilitating the team’s collaboration and alignment.

 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.

 The project manager should meet with the team member’s functional manager to try to remove the impediment that is preventing the team member from completing their user story. The project manager should explain the impact of the delay on the project scope, schedule, and quality, and negotiate a solution that would allow the team member to resume their work on the user story as soon as possible. This approach is consistent with the agile principle of removing impediments and enabling self-organizing teams12. References: 1: PMBOK Guide, 6th Edition, Chapter 5: Project Scope Management 2: Agile Practice Guide, Chapter 2: An Agile Mindset

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.

According to the PMBOK Guide, 6th edition, section 5.6.2, the project manager should perform an impact analysis when a change request is received, to assess the potential effects on the project scope, schedule, cost, quality, resources, risk, and other aspects.3

The project manager should also communicate the impact analysis to the relevant stakeholders, such as the project sponsor, the product owner, the customer, and the team, to facilitate the decision making process and obtain their agreement on the change.3

The project manager should not accept or reject the change request without performing an impact analysis, as this may lead to unrealistic expectations, missed deadlines, scope creep, or stakeholder dissatisfaction.3

The project manager should not ask the product owner to prioritize the new request without performing an impact analysis, as this may disrupt the agile team’s work and compromise the quality of the deliverables.4

The project manager should not call the stakeholder to tell them that the final product schedule must be extended without performing an impact analysis, as this may damage the trust and relationship with the stakeholder and cause them to lose confidence in the project.

The references for this answer are:

1: Discuss Exam PMP Topic 2 Question 499 Discussion | Actual4test 2: Free PMP Practice Exam Questions - 120 Sample Test Questions 3: PMBOK Guide, 6th edition, Project Management Institute, 2017, pp. 149-152. 4: Agile Practice Guide, Project Management Institute, 2017, pp. 37-38. : [Managing Stakeholder Expectations for Project Success: A Knowledge Integration Framework and Value Focused Approach, Ori Schibi, 2013, pp. 97-98.](https://www.pmi.org/learning