PMP PMI Project Management Professional (PMBOK 7th Version) Free Practice Exam Questions (2026 Updated)

 The project manager should evaluate the impacts of the changes that were made to the project without any approval. This is because any change in the scope can affect the other project constraints, such as time, cost, quality, risk, and stakeholder satisfaction. The project manager should use the change management plan and the integrated change control process to assess the impacts of the changes, determine the appropriate actions, and obtain the necessary approvals. The project manager should also communicate with the project team member who made the changes and explain the importance of following the change control procedures. The project manager should not remove the changes without evaluating them, as they may have some value or benefit for the project. The project manager should not add team members to the project without analyzing the resource requirements and availability. The project manager should not update the project documentation with the new scope without validating and approving the changes. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 4.6, pp. 129-131

PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain IV: Traceability and Monitoring, Task 3, p. 13

Business Analysis for Practitioners: A Practice Guide, Section 5.4.2, p. 118

Project documentation is the process of creating, organizing, and maintaining the written information that describes the processes, plans, and activities involved in a project. Project documentation includes documents such as the project charter, the project management plan, the work breakdown structure, the risk register, the issue log, and the status reports. Project documentation serves several purposes, such as project planning, communication, monitoring, control, and evaluation. According to the Professional in Business Analysis Reference Materials1, project documentation should be:

Accurate: The project documents should reflect the true and current state of the project, and avoid any errors, inconsistencies, or ambiguities.

Complete: The project documents should cover all the relevant and necessary aspects of the project, and avoid any gaps, omissions, or redundancies.

Consistent: The project documents should follow the same format, style, terminology, and standards, and avoid any conflicts, contradictions, or variations.

Up to date: The project documents should be updated regularly and timely, and avoid any outdated, obsolete, or irrelevant information.

In this scenario, the project schedule is falling behind and the project manager observes that the project team seems to be spending the majority of their time writing documentation instead of performing project tasks. This indicates that the project documentation process is not efficient, effective, or aligned with the project goals and priorities. The project team may be creating unnecessary, excessive, or irrelevant documents, or may be struggling to keep up with the changes and updates in the project. This could affect the project performance, quality, and stakeholder satisfaction.

Therefore, the best option for the project manager is to review and adapt the appropriate project artifacts. This means that the project manager should:

Review the existing project documents and assess their accuracy, completeness, consistency, and currency.

Identify and eliminate any project documents that are not required, useful, or valuable for the project.

Simplify and streamline the project documentation process and reduce the complexity and volume of the project documents.

Adapt the project documentation process and the project documents to the changing needs and expectations of the project and the stakeholders.

Communicate and collaborate with the project team and the stakeholders on the project documentation process and the project documents.

By reviewing and adapting the appropriate project artifacts, the project manager can ensure that the project documentation process and the project documents are fit for purpose, and that they support and facilitate the project tasks, rather than hinder or distract them.

The other options are not the best choices, because:

Assign a team member to handle the documentation activities: This option implies that the project manager is delegating the responsibility and accountability of the project documentation process and the project documents to a single team member, rather than involving and engaging the whole project team and the stakeholders. This could create a bottleneck, a dependency, or a risk in the project documentation process, and reduce the quality and reliability of the project documents.

Coach the project team to complete the project documentation activities: This option implies that the project manager is providing guidance and support to the project team on how to perform the project documentation activities, rather than addressing the root cause of the problem, which is the inefficiency, ineffectiveness, or misalignment of the project documentation process and the project documents. This could create a false sense of security, a complacency, or a resistance in the project team, and prevent them from improving and adapting the project documentation process and the project documents.

Save all documentation activities until the end of the project: This option implies that the project manager is postponing or ignoring the project documentation activities, rather than recognizing and fulfilling their importance and value for the project. This could create a backlog, a chaos, or a disaster in the project documentation process, and compromise the project performance, quality, and stakeholder satisfaction.

According to the PMBOK Guide, 7th edition, section 14.2.2, “Information radiators are highly visible displays of project information that are easily accessible and frequently updated. They are used to communicate project status and progress to the project team and other stakeholders, especially in agile or hybrid approaches.” Therefore, the project lead should invite the executive to the project’s meeting space to determine if the project information radiators meet their needs, as this is the most effective and transparent way to provide an update on the project’s progress in an agile environment. Providing a link to the project’s shared drive for the executive to search through for any artifacts that are of interest (option A) may not be user-friendly or efficient, as the executive may not know what to look for or how to interpret the artifacts. Reaching out to the PMO for status report templates and providing project updates in that format (option C) may not be aligned with the agile principles or values, as it may introduce unnecessary documentation or bureaucracy. Asking the project sponsor or product owner to provide an update since the project lead should be trying to keep the team free from impediments (option D) may not be appropriate or respectful, as the project lead should also be responsible for communicating with the stakeholders and ensuring their satisfaction. References:

PMBOK Guide, 7th edition, section 14.2.2

PMI-PBA Exam Practice Test and Study Guide, 2nd edition, page 183, question 20

The project manager should use a collaborative or problem-solving strategy to resolve this conflict in the meeting. This strategy involves finding a solution that fully satisfies the concerns of both parties and results in a win-win outcome. The project manager should ensure that both managers understand the requirements and the impact of their contradiction on the project scope, quality, and schedule. The project manager should also facilitate a constructive dialogue between the managers and help them identify and evaluate alternative solutions that can meet the project objectives and satisfy the stakeholders. The project manager should avoid imposing a decision or favoring one side over the other, as this may lead to resentment, resistance, or further conflict.

Option A is not a good choice, because it does not address the root cause of the conflict or seek a resolution. It may also create confusion, ambiguity, or inconsistency in the project deliverable, as well as increase the project risk and complexity.

Option B is not a good choice, because it does not involve the managers in finding a solution or consider their interests and needs. It may also create dissatisfaction, frustration, or hostility among the managers, as well as affect the project quality and stakeholder satisfaction.

Option D is not a good choice, because it does not foster a cooperative or integrative approach to resolving the conflict. It may also create a competitive or adversarial atmosphere in the meeting, as well as ignore the non-monetary or intangible factors that may influence the managers’ preferences and expectations.

 1: Project Management Professional (PMP)® Certification 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition

According to the PMBOK Guide, 7th edition, one of the key activities of the project manager is to implement risk responses to address the issues and opportunities that may affect the project objectives and outcomes. This includes executing contingency plans, which are predefined actions or strategies that are triggered by the occurrence of a risk event. In this scenario, the missing input from the vendor is a risk event that has extended the critical path of the project, which means that the project schedule is at risk of being delayed. Therefore, the project manager should execute a contingency plan to address the issue with the vendor and recover the lost time. Option D is the best answer for this question.

Option A is not the best answer because starting an audit of the vendor’s processes and procedures is not the next thing that the project manager should do. It is a possible action that the project manager may take to identify the root cause of the miscommunication and prevent it from happening again, but it is not a timely or effective action to resolve the current issue. Moreover, starting an audit may not always be feasible or desirable, as it may increase the project costs and risks, and may damage the relationship with the vendor.

Option B is not the best answer because reviewing lessons learned from previous projects with this vendor is not the next thing that the project manager should do. It is a good practice to learn from past experiences and apply them to current projects, but it is not a relevant or helpful action to deal with the current issue. Reviewing lessons learned may not always be accurate or reliable, as the vendor may have changed their processes or procedures since the previous projects.

Option C is not the best answer because making a detailed analysis on vendor issues during the project is not the next thing that the project manager should do. It is a possible action that the project manager may take to monitor and evaluate the vendor’s performance and identify any gaps or improvements, but it is not a proactive or adaptive action to address the current issue. Making a detailed analysis may not always be necessary or appropriate, as it may delay the project delivery and may not reflect the current or future state of the vendor’s situation. References: PMBOK Guide, 7th edition, pages 9-10, 15-16, 25-26, 35-36, 49-50, 59-60.

According to the PMBOK® Guide, the project manager should identify the source of the disagreement among the project stakeholders as the first step to facilitate the approval of project requirements. This is because identifying the source of the disagreement can help the project manager understand the root cause of the conflict, the interests and needs of the stakeholders, and the potential impact of the disagreement on the project objectives and deliverables. By identifying the source of the disagreement, the project manager can then choose an appropriate conflict resolution technique, such as compromising, collaborating, smoothing, forcing, or withdrawing, to resolve the issue and obtain the approval of the project requirements1. The other options are not the first steps to facilitate the approval of project requirements, because:

Reviewing the project charter may help the project manager clarify the project scope, objectives, and high-level requirements, but it does not address the specific source of the disagreement among the stakeholders2.

Performing a stakeholder analysis may help the project manager identify the stakeholders, their roles, expectations, influence, and communication needs, but it does not address the specific source of the disagreement among the stakeholders3.

Holding a team-building event may help the project manager improve the team morale, trust, and collaboration, but it does not address the specific source of the disagreement among the stakeholders4. References: 1: PMBOK® Guide, Sixth Edition, Chapter 9.5.2.1, Conflict Management 2: PMBOK® Guide, Sixth Edition, Chapter 4.1.3.1, Project Charter 3: PMBOK® Guide, Sixth Edition, Chapter 13.1.3.1, Stakeholder Analysis 4: PMBOK® Guide, Sixth Edition, Chapter 9.4.2.4, Team-Building Activities

 The correct answer is C. According to the PMBOK® Guide, project artifacts are any documents or deliverables that are produced as part of the project management processes1. These artifacts can include project plans, reports, baselines, metrics, lessons learned, and other outputs that show the performance and progress of the project and the project team. The project manager should gather these artifacts to provide evidence of the team member’s high performance and contribution to the project success. This will help the project manager to make a strong case for the team member’s promotion to senior management. Compiling key highlights from meeting minutes, asking the team member to write a biography, or calculating the health of the projects are not sufficient or relevant to demonstrate the team member’s skills and competencies as a potential project manager. References: 1: PMBOK® Guide, page 89

According to the PMBOK Guide, the project manager should plan, manage, and monitor the communication activities throughout the project life cycle. The project manager should also consider the stakeholder needs, preferences, and expectations when choosing the communication methods, tools, and technologies. The project manager should also update the communications management plan as needed to reflect any changes in the communication requirements or approach. Therefore, the project manager should update the communications management plan based on the product owner’s preferences and distribute it to the team. This will ensure that the communication is effective, timely, and consistent among the project stakeholders. References: PMBOK Guide, 6th edition, pages 361-362, 368-369.

According to the PMP Exam Content Outline, one of the tasks of the project manager is to “Assess stakeholder needs, interests, values, and influence, and determine the appropriate approach for engaging stakeholders across the project life cycle” (Task 1, Domain I: People). This implies that the project manager should evaluate the engagement needs of stakeholders based on their expectations, requirements, preferences, and level of influence and interest in the project. By doing so, the project manager can tailor the communication and collaboration methods to ensure high involvement from the stakeholders throughout the project. This will help to build trust, manage expectations, and increase stakeholder satisfaction. References:

PMP Exam Content Outline, Domain I: People, Task 1, page 61

PBA Exam Content Outline, Domain II: Planning, Task 3, page 102

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 13: Project Stakeholder Management, Section 13.2: Plan Stakeholder Engagement, page 5133

Business Analysis for Practitioners: A Practice Guide, Chapter 4: Needs Assessment, Section 4.2: Identify Stakeholders, page 694

 According to the PMBOK® Guide 7th Edition, one of the principles of project management is to “focus on value”. This means that the project manager should deliver products, services, or results that meet the needs and expectations of the customer and other stakeholders. One of the ways to achieve this is to use an adaptive or agile approach, which allows for frequent feedback and collaboration with the customer. Working with the product owner to define the minimum viable product(s) (MVPs) is an example of an agile technique that helps to deliver value early and often, and to validate the customer’s requirements. MVPs are versions of the product that have enough features to satisfy the customer’s needs and provide feedback for future development. Therefore, this option is the best approach to remove the impediment of the customer’s unclear requirements. The other options are not as effective because they do not address the root cause of the problem, which is the lack of customer involvement and validation. Following a predictive approach may lead to delivering a product that does not meet the customer’s needs or expectations, and may result in rework or waste. Reinforcing the negotiation and soft skills of the team may help to improve the communication and relationship with the customer, but it does not ensure that the product will deliver value. Developing and monitoring a plan with due dates may help to manage the schedule, but it does not guarantee that the product will satisfy the customer’s requirements. References: : PMBOK® Guide 7th Edition, PMI, 2021, p. 9 : Agile Practice Guide, PMI, 2017, pp. 25-26

 Lessons learned are the documented information that reflects both the positive and negative experiences of a project. They help project managers and teams to learn from their successes and failures, and to apply that knowledge to improve current and future projects. Reviewing the lessons learned from the previous project is a good practice for the project manager to do before initiating a new project, especially if the new project is similar or related to the previous one. By reviewing the lessons learned, the project manager can identify what worked well and what did not work well in the previous project, and use that information to plan, execute, monitor, and control the new project more effectively and efficiently. The project manager can also avoid repeating the same mistakes, leverage the best practices, and incorporate the feedback and recommendations from the previous project stakeholders. This is part of the Develop Project Charter process, which aims to define the new project and authorize the project manager. The other options are not the best choices because they are not the first thing that the project manager should do before initiating a new project. Ensuring the stakeholder engagement plan is accurate and properly documented (option A) is an important activity, but it is done later in the planning phase, after the project charter is approved and the key stakeholders are identified. The stakeholder engagement plan is a component of the project management plan that describes how the project will communicate and interact with the stakeholders. Identifying the risk of implementing the new solution and evaluating the impact on the project (option C) is also an important activity, but it is done later in the planning phase, after the project scope, schedule, and cost are defined. The risk management plan is a component of the project management plan that describes how the project will identify, analyze, prioritize, respond, and monitor the project risks. Creating a lessons learned document for the initiation phase (option D) is a good practice, but it is done at the end of the initiation phase, not at the beginning. The lessons learned document is a project document that records the knowledge gained from the project activities and processes. It is updated throughout the project and finalized at the end of the project. References:

Project Management Professional (PMP) Reference Materials:

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 4: Project Integration Management, pp. 71-123

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 13: Project Stakeholder Management, pp. 513-558

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 11: Project Risk Management, pp. 395-440

Lessons learned - Project Management Institute

Professional in Business Analysis (PBA) Reference Materials:

Business Analysis for Practitioners: A Practice Guide, Chapter 2: Needs Assessment, pp. 25-40

Lessons learned - Project Management Institute

The project manager should schedule a kick-off session to explain the problems of the project and gain approval and support from the stakeholders. This will help to align the expectations, clarify the objectives, and address the concerns of the stakeholders. A kick-off session is a tool and technique of the Develop Project Charter process, which is the first process in the project integration management knowledge area. Sending communications for clarification, demonstrating the performance indexes and recommending corrective actions, or speaking with the sponsor and explaining the situation are all possible actions that the project manager can take after the kick-off session, but they are not the first action that the project manager should take to alleviate the stakeholders’ concerns. References: PMBOK Guide 7th Edition, page 49; Agile Practice Guide, page 26.

According to the PMBOK Guide, a change request is a formal proposal to modify any document, deliverable, or baseline of a project. Change requests can be initiated by any stakeholder, including the project team, and should be processed through the perform integrated change control process.

In this scenario, the project team has identified a potential risk that could affect the quality and schedule of the next iteration of the project. The team has also proposed a solution to mitigate the risk by buying new equipment. This solution would require an increase in the project budget, which is a baseline that needs to be approved by the project sponsor or customer.

Therefore, the project manager should submit a change request to increase the budget and buy new equipment, and follow the change control procedures to obtain the necessary approval and authorization. This would ensure that the project scope, schedule, and quality are not compromised, and that the project stakeholders are aware of and agree with the proposed change.

The other options are not appropriate because:

Checking the project budget to verify if there is enough contingency reserve (option A) is not sufficient to address the issue. Contingency reserves are funds set aside to cover known risks that may or may not occur during the project. Even if there is enough contingency reserve, the project manager still needs to submit a change request to use it and update the project baseline.

Reviewing the cost management plan to determine how to address this issue (option B) is also not sufficient to address the issue. The cost management plan is a component of the project management plan that describes how the project costs will be planned, estimated, budgeted, managed, and controlled. It does not provide specific guidance on how to deal with changes that affect the project budget. The project manager still needs to follow the change control procedures and submit a change request.

Telling the team members that more equipment is not part of the project’s scope (option C) is not a constructive or collaborative way to deal with the issue. The project manager should not ignore or dismiss the team’s input and recommendations, especially if they are based on valid and relevant information. The project manager should respect the team’s expertise and experience, and work with them to find the best solution for the project.

According to the Professional in Business Analysis (PMI-PBA)® Guide, a minimum viable product (MVP) is a version of a product that has enough features to satisfy early customers and provide feedback for future development. A MVP is a way of delivering value to customers quickly and iteratively, while minimizing waste and risk. In this scenario, the project manager is faced with a drastic reduction in the project timeline, from 18 months to six months. This means that the original scope and schedule are no longer feasible, and the project manager needs to find a way to deliver a product that meets the customer’s needs and expectations within the new constraints. Reviewing the project backlog and prioritizing the high-value items that can be delivered in six months is a sensible approach to achieve this goal. The project manager can then work with the stakeholders to define and agree on the MVP that will provide the most value to the customer and the business. This option also allows for flexibility and feedback, as the MVP can be refined and improved based on customer feedback and changing requirements. Planning for overtime, applying crashing and fast tracking, and sharing the risk of failure are options that try to compress the schedule without reducing the scope. These options may increase the cost, quality, and resource risks, and may not be acceptable to the stakeholders or the customer. Seeking approval to triple the project budget and hiring more people is an option that tries to increase the resources without reducing the scope. This option may not be feasible or realistic, as it assumes that the sponsor is willing and able to provide the additional funds, and that the project can benefit from adding more people in a short time. This option may also introduce communication, coordination, and integration challenges, and may not guarantee the delivery of the product in six months. Going over the critical path with stakeholders and explaining why it is not possible to deliver all the scope in the expected timeline is an option that tries to justify the original plan without considering alternatives. This option may not be satisfactory to the stakeholders or the customer, as it does not offer any solution or value proposition. This option may also damage the relationship and trust between the project manager and the stakeholders, and may result in the cancellation or termination of the project. Conclusion: Given the options, Option B stands out as the most viable and effective action. Reviewing the project backlog and coming up with a MVP that fits the expected timeline addresses the customer’s needs and expectations, delivers value quickly and iteratively, and minimizes waste and risk. Among the presented choices, Option B emerges as the optimal solution. PMP Exam Content Outline Mapping Domain Task Process Task 2: Execute the project Topics Covered Minimum Viable Product (MVP) Project Backlog Prioritization Value Delivery References: (Professional in Business Analysis Reference Materials source and documents)

Professional in Business Analysis (PMI-PBA)® Guide, Chapter 5, Section 5.3.1.2

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 5, Section 5.2.2.2

The Standard for Project Management – Seventh Edition, Chapter 3, Section 3.2.2.2

The project manager should take the action of delivering business value as soon as possible as a priority. This is because the project is aimed at increasing the commercial value of the product in a highly competitive market, which means that the project needs to deliver a viable solution that meets the customer needs and expectations quickly and effectively. By delivering business value as soon as possible, the project manager can also obtain early feedback, validate the assumptions and requirements, and make adjustments as needed. This will help to improve the quality, performance, and satisfaction of the product, and to reduce the risk of waste, rework, and delays. The other options are not as important or relevant as delivering business value as soon as possible. Emphasizing the use of Kanban methodology may be helpful, but it is not a priority action, as it is a tool or technique, not a goal or outcome. Kanban is a visual system that helps to manage the flow of work and limit the work in progress, but it does not guarantee the delivery of business value. Ensuring the project sponsor is aware of the go-to market date is a good practice, but it is not a priority action, as it is a communication or reporting activity, not a delivery or execution activity. The go-to market date may also change depending on the feedback and changes in the market. Implementing a plan-do-check-act (PDCA) cycle is a useful approach, but it is not a priority action, as it is a process or framework, not a result or benefit. The PDCA cycle is a method for continuous improvement that involves planning, doing, checking, and acting on the results, but it does not specify what business value to deliver or how to deliver it. References: PMBOK Guide, 6th edition, Chapter 1.2.6, 4.1.3, 5.1.3, Agile Practice Guide, 1st edition, Chapter 2.2.1, 2.3.1

The project manager can use alternatives analysis and cost-benefit analysis to influence the client’s decision to keep the project active. These are two tools or techniques that can help the project manager present different options and their implications to the client, and demonstrate the value and feasibility of the project.

Alternatives analysis is a technique that involves generating, comparing, and evaluating different possible courses of action in order to select the best one1. The project manager can use this technique to show the client the pros and cons of continuing or closing the project, and the impact of each option on the project objectives, scope, schedule, cost, quality, risk, and stakeholder satisfaction. The project manager can also propose alternative solutions or approaches that can address the client’s concerns or issues, and explain how they can be implemented.

Cost-benefit analysis is a technique that involves comparing the expected costs and benefits of a project or an option to determine its economic viability and attractiveness2. The project manager can use this technique to show the client the return on investment (ROI) of the project, and how the benefits outweigh the costs. The project manager can also quantify the costs and benefits of different alternatives, and compare them to the baseline or the status quo. The project manager can also highlight the intangible or qualitative benefits of the project, such as customer satisfaction, reputation, social impact, or strategic alignment.

By using these two tools or techniques, the project manager can influence the client’s decision to keep the project active by providing factual and rational information, appealing to the client’s interests and values, and offering choices and flexibility.

 1: Alternatives Analysis - Project Management Knowledge 2: Cost Benefit Analysis - Project Management Knowledge

According to the PMBOK Guide, the project manager should consider the project delivery approach (predictive, agile, or hybrid) based on the project characteristics, such as complexity, uncertainty, stability, and adaptability. The project manager should also evaluate the impact of any changes to the project delivery approach on the project scope, schedule, cost, quality, risk, and stakeholder satisfaction. Therefore, the project manager should analyze the requirements that will need to be addressed under the agile approach and determine the feasibility, benefits, and drawbacks of switching from the predictive approach. This will help the project manager to make an informed decision and communicate it to the relevant stakeholders. References: PMBOK Guide, 6th edition, pages 19-20, 141-142.

According to the PMBOK Guide, a stakeholder engagement plan is a document that identifies the current and desired levels of stakeholder engagement, and the strategies and actions to increase or maintain stakeholder support throughout the project. A stakeholder engagement plan is an essential tool for managing stakeholder expectations, addressing stakeholder concerns, and resolving stakeholder conflicts. Conflicts between project stakeholders can result in delays, rework, scope changes, or even project failure. Therefore, the project manager should focus on revisiting the stakeholder engagement plan, focusing on specific overlooked stakeholders, to identify the root causes of the conflicts and the best ways to engage them. By doing so, the project manager can improve the stakeholder relationships, align the stakeholder interests, and facilitate the deliverable and output approval process. References:

PMBOK Guide, 7th edition, Chapter 8: Communications, Section 8.3: Manage Communications, pp. 126-1271

PMBOK Guide, 7th edition, Chapter 9: Stakeholders, Section 9.2: Plan Stakeholder Engagement, pp. 141-1431

PMBOK Guide, 7th edition, Chapter 9: Stakeholders, Section 9.3: Engage Stakeholders, pp. 144-1451

Professional in Business Analysis (PMI-PBA) Handbook, Section 5: Exam Content Outline, Domain 2: Planning, Task 2.4: Develop a stakeholder engagement plan, pp. 22-232

The benefits management plan is a document that describes how the benefits of the project will be delivered, measured, and sustained. It includes the benefits identification, analysis, planning, realization, and transition activities. By quantifying the expected tangible and intangible benefits in the benefits management plan for each phase, the business can increase the value of the project by demonstrating how the project contributes to the strategic objectives, customer satisfaction, and competitive advantage of the organization. Quantifying the benefits also helps to monitor and evaluate the performance of the project and the benefits realization process, and to identify and address any gaps or issues that may arise. Quantifying the benefits can also facilitate the communication and reporting of the value of the project to the stakeholders and the senior management. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 4.5.3.1, p. 123

PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain IV: Traceability and Monitoring, Task 2, p. 13

Business Analysis for Practitioners: A Practice Guide, Section 5.3.1, p. 113

The project manager should take two actions to deal with the situation of the neighbors not being satisfied with the project and resisting it. One action is to set up a meeting with neighborhood representatives to win their cooperation. This action can help the project manager to communicate with the neighbors, listen to their concerns and complaints, and explain the benefits and value of the project. The project manager can also use this opportunity to negotiate with the neighbors, offer them some incentives or compensation, and seek their support and feedback for the project. By engaging with the neighbors, the project manager can build trust and rapport with them, and reduce the potential for conflict and disruption12.

Another action is to analyze the situation and find out what is causing the neighborhood’s negative attitude. This action can help the project manager to identify the root causes of the problem, such as lack of information, misunderstanding, fear of change, or dissatisfaction with the project’s impact. The project manager can use tools such as stakeholder analysis, SWOT analysis, or force field analysis to assess the situation and the factors influencing it. By understanding the problem, the project manager can devise appropriate solutions and strategies to address it34. References: = 12 Project Management Challenges and How To Solve Them, Challenge 11: Stakeholder resistance; 8 Steps for Better Issue Management, Step 5: Communicate with the team; PMBOK® Guide, Sixth Edition, pages 513-515, 395-396; 4 Phases of the Project Management Lifecycle Explained, Phase 2: Planning.

Servant leadership is a style of leadership that focuses on serving the needs and interests of the team members, rather than imposing authority or control over them. Servant leaders empower, coach, and facilitate their teams to achieve the project goals, while fostering a culture of trust, collaboration, and innovation. According to the Professional in Business Analysis Reference Materials1, servant leadership is one of the key competencies for project managers, especially in agile environments, where teams are expected to be self-organizing, adaptive, and customer-centric.

In this scenario, the project team evaluated the product’s feasibility of functionality and accelerated testing, which implies that they are following an agile approach to deliver the product incrementally and iteratively, based on customer feedback and value. A minimum viable product (MVP) is a version of the product that has enough features to satisfy the customer’s needs and provide feedback for future development. Finding the MVP is a common practice in agile projects, as it helps to reduce waste, optimize resources, and validate assumptions.

Therefore, the best option for the project manager as a servant leader is to support the team as necessary to find the MVP. This means that the project manager should:

Provide the team with the necessary tools, resources, and guidance to conduct the feasibility and testing activities.

Remove any impediments or obstacles that might hinder the team’s progress or performance.

Encourage the team to collaborate and communicate effectively with each other and with the customer.

Facilitate the team’s learning and improvement through feedback, reflection, and experimentation.

Recognize and appreciate the team’s efforts and achievements.

By supporting the team as necessary to find the MVP, the project manager can demonstrate servant leadership, and help the team to deliver a valuable and quality product to the customer, while meeting the project constraints and expectations.

The other options are not the best choices, because:

Amend the project budget to include MVP testing: This option implies that the project manager is not following the approved schedule management plan, and is making changes to the project scope, cost, and baseline without proper justification or authorization. This could create confusion, conflict, or resistance among the project stakeholders, and jeopardize the project success. Moreover, this option does not reflect servant leadership, as it does not address the needs or interests of the team or the customer.

Submit a change request to the project sponsor for accelerated testing: This option implies that the project manager is not following the agile principles and practices, and is relying on a formal and bureaucratic process to manage changes in the project. This could slow down the project delivery, reduce the team’s autonomy and flexibility, and undermine the customer’s satisfaction and trust. Moreover, this option does not reflect servant leadership, as it does not empower or facilitate the team to find the MVP.

Develop the product as per the schedule to perform integration and testing: This option implies that the project manager is ignoring the team’s evaluation and feedback, and is sticking to a rigid and predetermined plan to deliver the product. This could result in a product that does not meet the customer’s needs or expectations, or that has unnecessary or unwanted features. Moreover, this option does not reflect servant leadership, as it does not support or involve the team in finding the MVP.

According to the PMI Guide to Business Analysis, one of the key competencies of a business analyst is to facilitate collaboration and teamwork among stakeholders. This includes building trust, rapport, and respect among team members, as well as fostering a positive and supportive work environment. The guide also states that “team morale is influenced by the business analyst’s ability to communicate effectively, manage conflict, and motivate others” (p. 41).

One of the ways to build team connections and emotional bonds is to use emotional intelligence, which is defined as “the ability to perceive, understand, and manage one’s own emotions and the emotions of others” (p. 42). Emotional intelligence can help the business analyst to:

Recognize and acknowledge the feelings and perspectives of team members, especially when they are affected by a change or a loss

Express appreciation and gratitude for the contributions and achievements of team members

Provide constructive feedback and coaching to help team members improve their performance and skills

Encourage team members to share their ideas, opinions, and concerns, and listen actively and empathetically

Resolve conflicts and disagreements in a respectful and collaborative manner

Celebrate successes and milestones, and recognize the efforts and challenges of the team

By building team connections and emotional bonds, the business analyst can help to improve team morale and teamwork, as well as increase team engagement, commitment, and productivity.

According to the PMBOK guide, one of the tools and techniques for managing stakeholder engagement is interpersonal and team skills, which include emotional intelligence, influencing, and negotiation skills (p. 529). Emotional intelligence is “the ability to identify, assess, and manage the personal emotions of oneself and other people, as well as the collective emotions of groups of people” (p. 529). Influencing is “the ability to change the opinions, attitudes, or behaviors of others to achieve a desired outcome” (p. 530). Negotiation is “a process of conferring with others to come to terms with them or to reach an agreement” (p. 530). Therefore, the project manager should use these skills to persuade the stakeholder to accept the deliverables based on the project acceptance criteria, and to resolve any conflicts or issues that may arise. The other options are not as effective as persuading the stakeholder, because they either bypass the stakeholder’s authority, create more dependency on the project sponsor, or postpone the problem without solving it. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK guide, pages 529-530

PMI-PBA guide, pages 39-40

 Perform Integrated Change Control is the process of reviewing all change requests, approving changes and managing changes to deliverables, organizational process assets, project documents, and the Project Management Plan, and communicating the decisions1. This process is important to ensure that only approved changes are implemented and that the project remains aligned with the project objectives and stakeholder expectations. In this scenario, the project manager should perform Integrated Change Control to evaluate the impact of the proposed alternative solution on the project scope, schedule, cost, quality, risk, and other aspects. The project manager should also consult with the project sponsor, customer, and other key stakeholders to obtain their approval or rejection of the change request. The project manager should document the change request and its status in the change log and update the project management plan and other relevant documents accordingly. The project manager should also communicate the change and its implications to the project team and other affected parties. By performing Integrated Change Control, the project manager can ensure that the project is managed in a controlled and consistent manner, and that the project deliverables meet the agreed requirements and expectations. References:

How To Successfully Perform Integrated Change Control

6 Steps for an Integrated Change Control Project Management Strategy

Performing Integrated Change Control: PMP Tips

According to the Professional in Business Analysis Reference Materials, team building is a tool and technique used in the Develop Project Team process, which aims to improve the performance of the project team and enhance project outcomes. Team building activities can help the project manager to address the issues that arise from team member changes, such as loss of trust, communication gaps, and conflicts. Team building can also help the project manager to align the team members with the project goals and expectations, and to motivate them to achieve the key performance indicators (KPIs) that measure the team’s progress and success. References:

Professional in Business Analysis Reference Materials, page 176, section 9.3.2.3

PMI PMP Quiz:35 Topic:1 Questions:171-175, question 3

I need to search the Professional in Business Analysis Reference Materials study guide for a comprehensive and detailed explanation. References: I need to search the Professional in Business Analysis Reference Materials source and documents for references.

However, based on the web search results from my internal tool, I can provide you with some possible hints and tips on how to approach this question.

One possible technique to deal with project delays is to use an iterative process, which involves breaking down the project into smaller cycles or iterations, each with its own planning, execution, and evaluation. This allows the project team to adapt to changing requirements, feedback, and risks, and deliver value incrementally. How to use an iterative process for projects | monday.com Blog

Another possible technique is to conduct regular retrospectives, which are meetings where the project team reflects on what went well, what went wrong, and what can be improved in the next iteration. Retrospectives help to identify the root causes of delays, learn from mistakes, and implement corrective actions. 10 Tips to Handle Project Delays - Gantt Chart GanttPRO Blog

A third possible technique is to use risk management strategies, such as avoidance, mitigation, transfer, or acceptance, to deal with the potential or actual threats that cause delays. Risk management involves identifying, analyzing, prioritizing, and responding to risks throughout the project lifecycle. 10 Causes of Projects Delays and How to Manage Them | ActiveCollab

In an agile approach, the project scope is not completely defined upfront, but rather evolves and emerges throughout the project lifecycle. The project manager’s role is to facilitate the collaboration and communication among the project team, the product owner, and the stakeholders, and to ensure that the project delivers value and meets the customer needs. One of the ways to do this is to help the sponsors and stakeholders craft the product vision, which is a high-level description of the product’s purpose, features, and benefits. The product vision provides a clear direction and alignment for the project and guides the development of the product backlog, which is a prioritized list of user stories and other requirements. The project manager should also bring the team and the product owner together to clarify the expectations, assumptions, and constraints of the project, and to review and refine the product backlog regularly. This will help to ensure that the project scope is defined and validated iteratively and incrementally, and that the project delivers the most valuable features to the customer. The other options are not appropriate for an agile approach. Meeting with the general manager and convincing them to return to using predictive approaches would be counterproductive and disrespectful of the company’s decision to adopt agile. Asking for a budget increase to implement a double-check process would be wasteful and unnecessary, as agile relies on frequent feedback and testing to ensure quality and customer satisfaction. Asking the general manager to review every requirement would be micromanaging and interfering with the product owner’s authority and responsibility to prioritize and manage the product backlog. References: PMBOK Guide, 6th edition, Chapter 5.1.2, 5.4.2, 5.6.2, Agile Practice Guide, 1st edition, Chapter 2.2, 2.3, 3.2

According to the PMBOK Guide, 7th edition, one of the key activities of the project manager is to tailor the project delivery approach based on the project characteristics, context, and environment. This means that the project manager should select the appropriate tools, techniques, methods, and artifacts that best suit the project needs and objectives. If the project manager realizes that the project will benefit from using adaptive tools, such as agile or hybrid methods, then the project manager should update the project documents accordingly and plan the first iterative session. This will enable the project team to deliver value incrementally and iteratively, and to respond to changes and feedback more effectively. Option A is the best answer for this question.

Option B is not the best answer because contacting the project sponsor and requesting new team members who are familiar with adaptive projects is not the first thing that the project manager should do. It is a possible action that the project manager may take if the current team lacks the skills or experience to work with adaptive tools, but it is not a necessary or immediate action. Moreover, requesting new team members may not always be feasible or desirable, as it may increase the project costs and risks, and may disrupt the team dynamics and performance.

Option C is not the best answer because confirming team capabilities before introducing adaptive tools and artifacts to the project is not the first thing that the project manager should do. It is a good practice to assess the team’s readiness and ability to work with adaptive tools, but it is not a prerequisite or a determinant for tailoring the project delivery approach. The project manager should base the decision on the project characteristics, context, and environment, not on the team capabilities. Moreover, confirming team capabilities may not always be accurate or reliable, as the team may have different levels of familiarity and confidence with adaptive tools.

Option D is not the best answer because freezing the design stage and looking for an external resource to run iterative design at extra cost is not the first thing that the project manager should do. It is a possible action that the project manager may take if the project is too complex or uncertain to be handled by the internal team, but it is not a recommended or proactive action. Freezing the design stage may delay the project delivery and may not reflect the current or future state of the project requirements or stakeholder needs. Looking for an external resource may increase the project costs and risks, and may reduce the project control and quality. References: PMBOK Guide, 7th edition, pages 9-10, 15-16, 25-26, 35-36, 49-50.

One of the methods to prioritize projects or features is to use a scoring model, which evaluates different aspects of a project or feature and assigns a numeric value to each criterion. In this case, the criteria are the business value and the development effort of each feature. A common way to calculate the score of a feature is to divide the business value by the development effort, which gives the value-to-effort ratio. The higher the ratio, the higher the priority of the feature. Using this method, the scores of the features are:

Feature A: 100 / 20 = 5

Feature B: 80 / 10 = 8

Feature C: 120 / 15 = 8

Feature D: 60 / 5 = 12

Feature E: 40 / 10 = 4

As you can see, Feature D has the highest score, but it also has the lowest business value. Therefore, it may not be the best choice to prioritize first, as it may not align with the strategic goals of the product or the organization. Feature C, on the other hand, has the same score as Feature B, but it has the highest business value among all the features. Therefore, Feature C should be the first feature to prioritize, as it delivers the most value with a reasonable effort.

 The project manager should prioritize the product backlog looking for high business value and low effort, and adjust the project budget and staffing to account for those items, as this is a strategy that aligns with the agile principles of delivering value early and often, and responding to change over following a plan1. By focusing on the most valuable and feasible features, the project manager can maximize the return on investment and customer satisfaction, while minimizing the waste and risk. The project manager should also collaborate with the product owner, the team, and the stakeholders to review and reprioritize the product backlog regularly, and to adapt to the changing requirements and constraints. Reducing the project staff and adjusting the scope and timelines accordingly in support of the budget reduction (option A) may not be a viable strategy, as it could compromise the quality and functionality of the product, and create dissatisfaction and demotivation among the team and the customers. Balancing the project team in order to accommodate the budget challenges, and providing training to mitigate the risk of low performance (option B) may not be a feasible strategy, as it could incur additional costs and time, and disrupt the team dynamics and productivity. Restricting the project scope only to basic critical features and running the project with the current staffing level until all of the budget is consumed (option D) may not be an effective strategy, as it could ignore the feedback and expectations of the customers, and miss the opportunities to deliver incremental value and improve the product. References:

1: Agile Practice Guide, Project Management Institute, Inc., 2017, p. 8.

According to the PMBOK Guide, a root cause analysis is a technique that involves identifying the underlying causes of problems or issues in a project. A root cause analysis can help the project manager and the team to understand the factors that contribute to the negative group behaviors and the lack of motivation and productivity. By conducting a root cause analysis session, the project manager can facilitate a collaborative problem-solving process that involves asking why the problem occurred, finding the root causes, and developing corrective actions to address them. A root cause analysis can also help to improve the team’s communication, trust, and morale, as well as the project’s quality, risk, and stakeholder management. Defining and analyzing performance metrics, escalating poor performance to functional managers, or updating the stakeholder engagement plan are not effective actions for improving the project team’s performance, as they do not address the root causes of the problem, and may create more resentment, frustration, or conflict among the team members. References: PMBOK Guide, Sixth Edition, pages 176, 558; PMI-PBA Guide, First Edition, pages 87, 102.

 Checking the risk register for a prepared response to a resource being suddenly unavailable is a proactive action that the project manager should take to deal with the situation. The risk register is a document that records the identified risks, their causes, impacts, probabilities, and responses. By consulting the risk register, the project manager can see if there is a contingency plan or a fallback plan for the loss of a key resource, and implement it accordingly. Checking if the team member’s activities are sufficiently documented to facilitate handover is another important action that the project manager should take to ensure the continuity and quality of the project work. The team member’s activities may include tasks, deliverables, dependencies, assumptions, constraints, and other information that are relevant to the project scope, schedule, and cost. By reviewing the documentation, the project manager can identify the gaps, risks, and issues that may arise from the absence of the team member, and take appropriate measures to address them. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, Seventh Edition, Section 11.4.3, “Risk Register”

PMBOK Guide, Seventh Edition, Section 4.3.3, “Project Management Plan”

Professional in Business Analysis (PMI-PBA) Guide, Section 4.2.2, “Documentation”

The project manager should take these two actions because they are aligned with the hybrid project management approach, which combines the waterfall and agile methodologies. A hybrid project management approach allows the project manager to plan the high-level project phases using the waterfall method, but execute the work within each phase using the agile method1. This means that the project manager can adapt to changing customer needs and expectations, while still delivering the agreed deliverables within the contract.

By going back to the development team and discussing which second milestone requirements can be performed in the first quarter, the project manager can use the agile method to prioritize and deliver the most valuable features to the customer in an incremental and iterative way. This can help the project manager to show the customer a tangible outcome in the first quarter, while still maintaining the quality and scope of the second milestone.

By asking the customer for their priorities regarding the requirements for the second milestone, the project manager can use the waterfall method to manage the contract and the expectations of the customer. This can help the project manager to negotiate and agree on the changes to the requirements, schedule, and budget of the second milestone, while still meeting the contractual obligations and the customer satisfaction.

The other options are not the best actions to take in this situation. Convince the customer to leave the second milestone in place and not change it may not be possible or desirable, as the customer may have valid reasons to change their expectations and may not be satisfied with the original plan. Escalate the issue to upper management to resolve the problem and suggest a plan may not be necessary or effective, as the project manager should be able to handle the issue with the customer and the development team directly, without involving the senior management. Tell the customer that moving the milestone has a very high impact on the cost of the project may not be enough to persuade the customer to keep the milestone as it is, as the customer may be more concerned about the value and the outcome of the project than the cost.

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

According to the PMBOK® Guide, one of the key skills of a project manager is to manage stakeholder engagement, which includes facilitating collaboration among stakeholders1. Collaboration is essential for global projects, as it enables effective communication, efficiency, decision-making, and creativity among team members from different regions, cultures, and backgrounds2. However, collaboration can also be challenging due to factors such as time zones, language barriers, and cultural differences3. Therefore, the project manager should coordinate a meeting to understand the situation and resolve any conflicts that may arise among the team members. By doing so, the project manager can foster trust, respect, and mutual understanding among the team, and ensure that they are aligned with the project objectives and expectations2. The project manager can use various techniques to facilitate the meeting, such as active listening, brainstorming, negotiation, and problem-solving1. References:

1: PMBOK® Guide – 4th Edition, Chapter 13: Stakeholder Management

2: The Global Project Management Framework

3: Advantages and Challenges of Global Team Collaboration

 The stakeholder register is a project document that identifies and classifies the project stakeholders, their roles, interests, expectations, and influence levels. It is an output of the Identify Stakeholders process, which is the first process in the Project Stakeholder Management knowledge area. The stakeholder register should be updated whenever there are changes in the project environment or stakeholder information, such as a promotion, a change of role, or a change of contact details. Updating the stakeholder register will help the project manager and the project team to communicate effectively and appropriately with the stakeholders, and to manage their expectations and engagement levels throughout the project life cycle.

The project management plan is a comprehensive document that describes how the project will be executed, monitored, and controlled. It integrates and consolidates the subsidiary plans and baselines from the different knowledge areas, such as scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder management. The project management plan is an output of the Develop Project Management Plan process, which is the second process in the Project Integration Management knowledge area. The project management plan should be updated only when there are changes in the project scope, objectives, deliverables, or approach, and when these changes are approved through the Perform Integrated Change Control process. Updating the project management plan for a stakeholder promotion is not necessary, unless it affects the project scope or other aspects of the project.

The stakeholder engagement plan is a subsidiary plan of the project management plan that describes the strategies and actions to increase the support and minimize the resistance of the stakeholders throughout the project. It is an output of the Plan Stakeholder Engagement process, which is the second process in the Project Stakeholder Management knowledge area. The stakeholder engagement plan should be updated when there are changes in the stakeholder engagement levels, needs, or expectations, and when these changes are approved through the Perform Integrated Change Control process. Updating the stakeholder engagement plan for a stakeholder promotion may be required, depending on how it affects the stakeholder’s interest, influence, or power over the project.

The communications management plan is a subsidiary plan of the project management plan that describes the communication methods, formats, frequency, and responsibilities for the project. It is an output of the Plan Communications Management process, which is the first process in the Project Communications Management knowledge area. The communications management plan should be updated when there are changes in the communication requirements, preferences, or channels of the project stakeholders, and when these changes are approved through the Perform Integrated Change Control process. Updating the communications management plan for a stakeholder promotion may be necessary, depending on how it affects the stakeholder’s communication needs or preferences.

Therefore, the correct answer is C. Stakeholder register, as it is the most relevant and appropriate document to update for a stakeholder promotion.

 The project manager should conduct a meeting with the project team to discuss and address the sources of disagreement, as this is a strategy for improving team morale and performance. According to the PMI website, one of the interpersonal and team skills that a project manager should have is conflict management. Conflict management is the process of resolving or reducing disagreements among project stakeholders, such as team members, sponsors, customers, or suppliers. Conflict can arise due to various factors, such as personality differences, communication barriers, resource constraints, or competing interests. If not managed properly, conflict can negatively affect the team morale, productivity, quality, and satisfaction. The project manager should use appropriate conflict resolution techniques, such as problem-solving, compromising, collaborating, smoothing, or forcing, depending on the situation and the desired outcome. The project manager should also facilitate open and constructive communication, encourage feedback and participation, and promote trust and respect among the team members1. By conducting a meeting with the project team, the project manager can identify the root causes and the impact of the disagreement, and work with the team to find a mutually acceptable solution. The project manager can also clarify the project objectives, scope, and requirements, and ensure that the team members understand their roles and responsibilities. By addressing the sources of disagreement, the project manager can improve the team morale and performance, and get the project back on track.

The other options, informing the stakeholders, crashing the project timeline, or issuing a change request, are not the best ways to deal with low team morale and disagreement. Informing the stakeholders may be a necessary communication activity, but it does not solve the problem or improve the situation. Crashing the project timeline may be a schedule compression technique, but it may not be feasible or effective, as it may increase costs, risks, or rework, and may also worsen the team morale and satisfaction. Issuing a change request may be a change management activity, but it may not be necessary or desirable, as it may imply that the project manager is unable to manage the project within the agreed baselines.

 2 Interpersonal and Team Skills - Project Management Institute 1 A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 9.5

According to the PMBOK® Guide, the project manager should identify the source of the disagreement among the project stakeholders as the first step to facilitate the approval of project requirements. This is because identifying the source of the disagreement can help the project manager understand the root cause of the conflict, the interests and needs of the stakeholders, and the potential impact of the disagreement on the project objectives and deliverables. By identifying the source of the disagreement, the project manager can then choose an appropriate conflict resolution technique, such as compromising, collaborating, smoothing, forcing, or withdrawing, to resolve the issue and obtain the approval of the project requirements1. The other options are not the first steps to facilitate the approval of project requirements, because:

Reviewing the project charter may help the project manager clarify the project scope, objectives, and high-level requirements, but it does not address the specific source of the disagreement among the stakeholders2.

Performing a stakeholder analysis may help the project manager identify the stakeholders, their roles, expectations, influence, and communication needs, but it does not address the specific source of the disagreement among the stakeholders3.

Holding a team-building event may help the project manager improve the team morale, trust, and collaboration, but it does not address the specific source of the disagreement among the stakeholders4. References: 1: PMBOK® Guide, Sixth Edition, Chapter 9.5.2.1, Conflict Management 2: PMBOK® Guide, Sixth Edition, Chapter 4.1.3.1, Project Charter 3: PMBOK® Guide, Sixth Edition, Chapter 13.1.3.1, Stakeholder Analysis 4: PMBOK® Guide, Sixth Edition, Chapter 9.4.2.4, Team-Building Activities

 Working with the stakeholders to determine which measurable benefits can be tracked and assigning an accountable person to monitor and report them is the first step to ensure that the value delivered by the hybrid framework is aligned with the business objectives and expectations. The project manager should collaborate with the stakeholders to identify the key performance indicators (KPIs) and metrics that reflect the value of the project outcomes and outputs. The project manager should also assign a responsible person to collect, analyze, and report the data on the benefits realization. Creating a report based on the work breakdown structure (WBS) and updating it on a regular basis is not a sufficient way to track the value delivered by the hybrid framework, as the WBS only shows the scope of the project, not the benefits. Using the same benefits tracking process from the last predictive project and adding this to the monthly status report is not a suitable option, as the hybrid framework may require different methods and measures to track the value delivered. Researching which templates of reports were used the most for this framework and incorporating them into the project is not a proactive approach, as it does not involve the stakeholders’ input and feedback on the value delivered by the hybrid framework. References: Project Management Professional Sample Questions, page 13, question 109. [A Guide to the Project Management Body of Knowledge (PMBOK Guide)], Sixth Edition, page 33, section 1.2.3. [Agile Practice Guide], page 25, section 3.1.1.

According to the PMBOK® Guide, one of the key skills of a project manager is to apply appropriate leadership styles to the needs and demands of various situations1. Leadership styles can range from directive to supportive, depending on the level of authority and involvement of the project manager1. Micromanagement is a type of directive leadership style that involves close supervision and control over the work of the team members2. While micromanagement may be suitable for some situations, such as when the team is new or inexperienced, it can be detrimental for others, such as when the team is senior or skilled2. Micromanagement can cause frustration, demotivation, and resentment among the team members, and hinder their performance and creativity23. Therefore, the project manager should adjust their management style to better fit senior team members, who may prefer more autonomy, trust, and feedback23. The project manager can use various techniques to adapt their management style, such as situational leadership, emotional intelligence, and coaching1 . References:

1: PMBOK® Guide – 4th Edition, Chapter 3: The Role of the Project Manager

2: Micromanager Definition: 25 Signs and How To Deal With One

3: What is micromanaging? 6 warning signs

4 Signs You’re a Micromanager in Your Projects

Obstacles are any factors that hinder the progress or success of a project. They can be internal or external, technical or human, predictable or unforeseen1. Obstacles can cause delays, cost overruns, quality issues, scope changes, stakeholder dissatisfaction, and even project failure2. Therefore, it is essential for project managers to identify, analyze, and resolve obstacles as soon as possible.

One of the best practices for managing obstacles is to prioritize them for resolution. This means that the project manager should evaluate the impact and urgency of each obstacle, and rank them according to their importance and severity3. Prioritizing obstacles helps the project manager to focus on the most critical ones first, and allocate the appropriate resources and actions to address them. Prioritizing obstacles also helps the project manager to communicate the status and progress of obstacle resolution to the project team and stakeholders, and to manage their expectations and feedback4.

The other options are not the best choices for the project manager in this situation. Having the project team work on other activities (option A) may be a temporary workaround, but it does not solve the underlying problem. It may also create more confusion, waste, and rework, and reduce the team’s motivation and productivity5. Implementing plans to remove the obstacles (option B) may be a necessary step, but it should be done after prioritizing the obstacles. Otherwise, the project manager may spend too much time and effort on less important obstacles, and neglect the more critical ones6. Escalating to the project steering committee (option C) may be appropriate in some cases, especially when the obstacles are beyond the project manager’s authority or influence. However, it should not be the first or only option, as it may indicate a lack of initiative, responsibility, or problem-solving skills from the project manager. The project manager should try to resolve the obstacles at their level first, and only escalate when necessary7.

 1: What are the Top 3 Obstacles in Projects? - Project Management Articles … 2: 6 Common Project Management Challenges and How to Overcome Them 3: [How to Prioritize Project Tasks and Risks | Smartsheet] 4: [Project Management: How to Prioritize Issues and Risks | Project …] 5: [How to Overcome Project Management Obstacles | ProjectManager] 6: [How to Prioritize Project Problems and Risks | TeamGantt] 7: Steering Committee: Definition, Roles & Meeting Tips - ProjectManager

 The project manager should focus on determining and aligning performance indicators that will help in assessing successful delivery of the product revamp. Performance indicators are measurable values that demonstrate how effectively a project is achieving its objectives and delivering value to the stakeholders. By defining and aligning these indicators with the marketing team and the executive, the project manager can ensure that the project scope, schedule, cost, quality, and benefits are aligned with the expectations and needs of the customer and the organization. This will also help to monitor and control the project performance, identify and address any issues or risks, and communicate the project status and progress to the relevant stakeholders. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, section 4.1.3.2, page 77

PMP Exam Prep, 10th edition, Rita Mulcahy, page 76

PMP Practice Questions #67 - iZenBridge1

According to the PMBOK Guide, an issue log is a project document that records and tracks any issues that arise during the project and require resolution. It is part of the project communications management process and helps the project manager to monitor and control the project performance. When a key supplier goes bankrupt and cannot supply the contracted material, this is an issue that affects the project scope, schedule, cost, and quality. Therefore, the project manager should first update the issue log with the details of the issue, such as the description, impact, priority, owner, and status. Then, the project manager should act to minimize the impact of the issue by implementing appropriate actions, such as finding alternative suppliers, negotiating new contracts, adjusting the project plan, or requesting changes. The project manager should also communicate the issue and the actions to the relevant stakeholders, such as the project team, the sponsor, the customer, and the supplier. Updating the issue log and acting to minimize the impact are proactive and responsible steps that the project manager should take first to address the issue and ensure the project success. References: PMBOK Guide, A practical approach to supply-chain risk management

According to the PMBOK Guide, an adaptive approach in project management is one that responds to changes and uncertainties in the project environment. Adaptive tools are techniques that enable project managers to plan and execute projects in an iterative and flexible way. Some examples of adaptive tools are agile methods, scrum, kanban, and lean. However, not all projects are suitable for using adaptive tools, and some stakeholders may have different expectations and preferences regarding the project management approach. Therefore, before implementing adaptive tools in a project, the project manager should conduct individual interviews with key stakeholders to understand their concerns, needs, and expectations. This will help the project manager to identify the level of stakeholder engagement, the degree of change tolerance, and the potential risks and benefits of using adaptive tools. Based on the information gathered from the interviews, the project manager should then prepare a communications management plan that defines how the project information will be communicated to the stakeholders, including the frequency, format, and content of the communication. The communications management plan should also include a feedback mechanism that allows the stakeholders to provide their input and feedback throughout the project lifecycle. This will help the project manager to manage the stakeholder expectations, address the stakeholder concerns, and ensure the stakeholder satisfaction with the project outcomes. References:

PMBOK Guide, 7th edition, Chapter 2: Project Performance Domains, Section 2.1: Project Delivery Approach, pp. 23-251

PMBOK Guide, 7th edition, Chapter 3: Project Management Principles, Section 3.5: Engage Stakeholders, pp. 41-421

PMBOK Guide, 7th edition, Chapter 4: Tailoring, Section 4.2: Tailoring Considerations, pp. 51-531

PMBOK Guide, 7th edition, Chapter 8: Communications, Section 8.2: Plan Communications, pp. 123-1251

Professional in Business Analysis (PMI-PBA) Handbook, Section 5: Exam Content Outline, Domain 2: Planning, Task 2.3: Develop a communication management plan, pp. 21-222

 The project manager should do to communicate this message is to contact department managers who are identified as stakeholders, solicit concern, and provide updates to the situation. This is an example of the manage communications process, which involves ensuring timely and appropriate collection, creation, distribution, storage, retrieval, management, monitoring, and control of project information2. By contacting the department managers, the project manager can inform them of the issue and its impact on the project, and seek their feedback and support. The project manager can also provide updates on the status and progress of the corrective measures, and ensure that the expectations and needs of the stakeholders are met. The project manager should use effective communication skills and techniques, such as active listening, empathy, clarity, and transparency, to build trust and rapport with the stakeholders, and to manage any conflicts or issues that may arise.

Option A is not a good choice, because it is not the project manager’s responsibility to ask the vendor to identify the stakeholders affected, create an action plan and determine an implementation date. The project manager should have already identified and engaged the stakeholders in the planning phase, and established clear and agreed-upon roles and responsibilities for the vendor in the procurement documents. The project manager should also monitor and control the vendor’s performance and deliverables, and ensure that they comply with the contract terms and conditions. The project manager should not delegate or outsource their communication duties to the vendor, as this may create confusion, misunderstanding, or mistrust among the stakeholders.

Option B is not a good choice, because it is not a constructive or collaborative way to communicate this message. The project manager should not draft a warning letter to the vendor, ask internal stakeholders to comment, and solicit stakeholder support to hold the vendor accountable, as this may escalate the conflict and damage the relationship with the vendor. The project manager should instead use a more positive and respectful tone, and focus on the facts and solutions, rather than the blame and threats. The project manager should also follow the dispute resolution and escalation procedures specified in the contract, and involve the appropriate parties and authorities, such as the legal department or the sponsor, if necessary.

Option C is not a good choice, because it is not a proactive or realistic way to communicate this message. The project manager should not identify the worst-case scenario, put it into the project risk register, share the register with all project stakeholders, and raise an alert, as this may create panic, anxiety, or demotivation among the stakeholders. The project manager should instead identify and analyze the potential risks and opportunities associated with the issue, and update the risk register accordingly. The project manager should also communicate the relevant and accurate information to the stakeholders, and implement the appropriate risk responses, such as avoiding, mitigating, transferring, or accepting the risk.

 1: Project Management Professional (PMP)® Certification 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition

The correct answer is B. According to the PMBOK® Guide, emotional intelligence is the ability to identify, assess, and manage the personal emotions of oneself and other people, as well as the collective emotions of groups of people1. The project manager demonstrated emotional intelligence by recognizing the team member’s situation, showing empathy and concern, and taking action to accommodate the team member’s needs and preferences. Networking, conflict management, and influencing are also interpersonal skills, but they are not relevant to this scenario. References: 1: PMBOK® Guide, page 704

I need to search the Professional in Business Analysis Reference Materials study guide for a comprehensive and detailed explanation. References: I need to search the Professional in Business Analysis Reference Materials source and documents for references.

However, based on the web search results from my internal tool, I can provide you with some possible hints and tips on how to approach this question.

One possible technique to prioritize product backlog items is the MoSCoW method, which stands for Must have, Should have, Could have, and Won’t have. This method helps to classify the items based on their value, urgency, and dependency. Product Backlog Explained [+ Examples] | Atlassian

Another possible technique is the Kano model, which categorizes the items based on how they satisfy the customer’s needs and expectations. The Kano model distinguishes between five types of items: Must be, One dimensional, Attractive, Performance, and Indifferent. 4 Product Backlog Prioritization Techniques That Work - Perforce Software

A third possible technique is the Cost of Delay, which measures the economic impact of delaying the delivery of an item. The Cost of Delay can be calculated by multiplying the value, urgency, and size of the item. The higher the Cost of Delay, the higher the priority. How To Do Backlog Prioritization Easily [Complete Guide] - Agile Digest

 The project manager should evaluate the situation and identify ways to compress the schedule without impacting baselines, as this is a strategy for handling delays in project programming activities. According to the PMI website, project delays can occur due to various reasons, such as complexity, resource constraints, poor communication, or risk management issues. When a project is behind schedule or at risk of a critical delay, the project manager should analyze the root causes and the impact of the delay, and determine the best course of action to bring the project back on track. One of the possible actions is to compress the schedule, which is a technique to shorten the project duration without changing the project scope. There are two methods of schedule compression: crashing and fast-tracking. Crashing involves adding or adjusting resources, such as people, equipment, or materials, to critical path activities, to reduce their duration. Fast-tracking involves performing critical path activities in parallel or partially in parallel, to reduce their overall duration. Both methods have advantages and disadvantages, and the project manager should weigh them carefully before applying them. The project manager should also monitor and control the schedule performance, and communicate any changes or updates to the stakeholders1.

The other options, asking the team to work overtime, checking the scope, or submitting a change request, are not the best ways to handle delays in project programming activities. Asking the team to work overtime may not be feasible or effective, as it may increase costs, risks, or rework, and may also demotivate or burn out the team members. Checking the scope may help the project manager to verify if there is scope creep, which is the uncontrolled expansion of the project scope, but it may not address the actual causes or consequences of the delay. Submitting a change request may help the project manager to follow the change management process and seek approval from the project sponsor or the change control board, but it may not be necessary or desirable, as it may imply that the project manager is unable to manage the schedule within the agreed baselines.

 1 A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 6.6 2 Business Analysis for Practitioners: A Practice Guide, Chapter 4.3.4 3 How to Manage Project Delays: 6 Effective Tips - ProProfs Project Blog 4 How Can Project Managers Handle Project Delays? - Online Tutorials Library 5 Dealing with delays - Project Management Institute

Contingency control in the project and rebaseline is a process that involves adjusting the project baseline to account for the impact of unforeseen risks. This allows the project manager to update the project scope, schedule, and cost baselines to reflect the current situation and avoid further deviations. Integrated change control in the project is a process that ensures that any changes to the project are reviewed, approved, and communicated to all stakeholders. This helps the project manager to manage the expectations of the project sponsors, customers, and team members, and to maintain the alignment of the project objectives with the business needs. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, Seventh Edition, Section 4.5.3, “Contingency Control”

PMBOK Guide, Seventh Edition, Section 4.6.3, “Integrated Change Control”

The project manager should meet with the subject matter experts (SMEs) to assess the impact of the new regulation on the project objectives, scope, schedule, cost, quality, and risk. The SMEs are the ones who have the knowledge and expertise to understand the implications of the new regulation and how it affects the project deliverables. The project manager should also involve the stakeholders, especially the project sponsor and the customer, in the assessment process to ensure their expectations and requirements are met. The project manager should then use the assessment results to determine the best course of action to address the change, such as modifying the project plan, requesting a change request, or escalating the issue to the appropriate authority. The project manager should follow the change management process as defined in the project management plan and the business analysis plan, and document the changes and their impacts in the project documents and the traceability matrix. The project manager should also communicate the changes and their impacts to the project team and the stakeholders, and obtain their buy-in and support.

The other options are not the best actions to take next, because they do not address the impact of the new regulation on the project objectives and deliverables. Consulting with the project sponsor to discuss a cost increase (option A) may be premature, as the cost impact may not be known until the assessment is done. Acquiring approval for an exception to the implementation of the new regulation (option B) may not be feasible or desirable, as it may compromise the compliance and quality of the project deliverables. Getting approval for the additional budget from the steering committee (option C) may also be premature, as the budget impact may not be known until the assessment is done. Moreover, the budget approval may not be sufficient to address the other impacts of the new regulation, such as scope, schedule, quality, and risk. References:

The PMI Guide to Business Analysis Includes The Standard for Business Analysis, Chapter 5: Solution Evaluation, Section 5.3.3: Assess Solution Limitations

Business Analysis for Practitioners: A Practice Guide, Chapter 7: Solution Evaluation, Section 7.3.3: Assess Solution Limitations

Business Analysis Techniques: 72 Essential Tools For Success, Chapter 5: Strategy Analysis, Section 5.13: Impact Analysis

Seven Steps to Mastering Business Analysis, Chapter 9: Solution Assessment and Validation

The project manager should analyze the reason for the gap in understanding with both sides and negotiate a solution, as this is a strategy for managing stakeholder dissatisfaction in agile projects. According to the Agile Alliance, one of the principles of agile software development is to satisfy the customer through early and continuous delivery of valuable software. However, sometimes the customer or stakeholder may not be satisfied with the product, even if it meets the acceptance criteria and is approved by them. This may happen due to various reasons, such as unclear or changing requirements, miscommunication, unrealistic expectations, or lack of feedback. The project manager should identify the root cause of the dissatisfaction and try to resolve it through dialogue and collaboration. The project manager should also use agile techniques, such as backlog refinement, user stories, sprint reviews, and retrospectives, to ensure that the product delivers value to the stakeholder and aligns with their vision and goals1.

The other options, asking the project team to perform the modifications, asking the stakeholder to submit a change request, or explaining to the stakeholder that the project can be closed, are not the best ways to manage stakeholder dissatisfaction in agile projects. Asking the project team to perform the modifications may not address the underlying issue of the dissatisfaction and may also introduce new risks or defects to the product. Asking the stakeholder to submit a change request may not be feasible or appropriate in an agile environment, where changes are expected and welcomed, as long as they add value to the product and do not compromise the quality or scope2. Explaining to the stakeholder that the project can be closed may not satisfy the stakeholder or improve the relationship, as it may imply that the project manager is not willing to listen to their feedback or concerns.

 3 A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 13 2 Agile Practice Guide, Chapter 2 1 Effective Ways for Stakeholder Management in Agile - Premier Agile 4 How to Explain Agile to Your Stakeholders | Agile Alliance

A hybrid project management methodology is a combination of two or more different approaches to delivering projects, such as waterfall and agile1. Hybrid projects can offer benefits such as flexibility, adaptability, customer satisfaction, and innovation2. However, hybrid projects also require frequent reviews and feedback loops to ensure alignment, collaboration, and quality among the project team and stakeholders3. Therefore, the project manager should explain to the stakeholder the value of attending the iteration reviews, which are opportunities to inspect the project deliverables, provide feedback, identify issues, and plan for the next iteration4. By doing so, the project manager can demonstrate how the stakeholder’s involvement can contribute to the project success and avoid potential rework or waste. References:

Ultimate Guide To Hybrid Project Methodologies & How To Make Them

Hybrid project management – the key to a successful future? - APM

Hybrid project management – a systematic literature review …

TOWARDS A HYBRID PROJECT MANAGEMENT FRAMEWORK: A SYSTEMATIC LITERATURE …

Developing the resource management plan is the first process in the resource management knowledge area. The resource management plan describes how the project resources, including human resources, will be acquired, allocated, developed, managed, and released. One of the components of the resource management plan is the training plan, which identifies the training needs, objectives, methods, and evaluation criteria for the project team members. By developing the resource management plan and ensuring adequate training, the project manager can address the skill gaps of the team members and prepare them for the key tasks later in the project. This will also enhance the team performance, motivation, and satisfaction. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 9.1, pp. 308-313

PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain II: Planning, Task 2, p. 9

Business Analysis for Practitioners: A Practice Guide, Section 3.4.1, p. 66