Free Practice Questions for PMI PMP Exam

The project manager should discuss the issue with the functional manager to understand the reason for the complaint. This is the best option because it shows the project manager’s respect and communication skills, as well as the willingness to resolve the conflict in a constructive way. By discussing the issue with the functional manager, the project manager can also clarify the expectations, roles, and responsibilities of the team member, as well as identify the root cause and possible solutions for the problem. This option also aligns with the PMBOK® Guide’s guidance on managing stakeholder engagement, which includes addressing and resolving issues, and fostering collaboration among stakeholders1.

The other options are not as effective as option B. Option A is not fair and may demotivate the team member and the rest of the team. Option C is not collaborative and may escalate the conflict. Option D is not realistic and may create more interruptions and resistance from the functional manager. References: 1: PMBOK® Guide, 6th edition, page 518

 According to the Project Management Body of Knowledge (PMBOK), one of the key responsibilities of a project manager is to ensure that lessons learned from previous projects are applied to current projects. This helps to avoid repeating the same mistakes and to leverage successful strategies. In this scenario, the project manager should share the lessons learned from the previous project with the team member. This will not only help to resolve the current issue more efficiently but also contribute to the team member’s learning and development. References: PMBOK Guide, 6th Edition, Section 4.4.3.1 - Lessons Learned Register

 Meeting with the project sponsors to align expectations is a crucial step for the project manager to ensure that the project objectives, scope, deliverables, risks, assumptions, and constraints are clear and agreed upon by all the stakeholders. This will also help to establish trust, communication, and collaboration among the sponsors who are from different business units and have different interests and perspectives. The project manager should also review the project charter and the stakeholder register to identify the roles, responsibilities, and expectations of the sponsors and other key stakeholders. Establishing mentoring and coaching sessions, reviewing the knowledge repository for similar projects, and scheduling the project kick-off meeting are all important activities, but they are not the first thing that the project manager should do in this situation. References: = PMBOK Guide, 6th edition, pages 31-32, 513-514; PMP Exam Content Outline, 2020, pages 6-7.

Introverts often prefer to have time to reflect on topics before discussing them in a group setting. By presenting brainstorming topics a day before the session, the project manager can give introverted team members time to process the information and formulate their thoughts. This approach can help to ensure that all team members, regardless of their personality type, are able to contribute fully during the session. References: PMBOK Guide, 6th Edition, Section 9.4 Manage Team

 According to the PMBOK Guide, a project manager and project team should select the appropriate work methods and tools based on the project characteristics, such as the product scope, complexity, uncertainty, and delivery approach1. The work methods and tools should also be aligned with the business need and project constraints, such as the budget, schedule, quality, and resources2. Therefore, the result of the discussion should be an agreed-upon work method and tools that should fit the business need and project constraints. References:

1: PMBOK Guide, 6th edition, Chapter 4: Project Integration Management, p. 74-75

2: PMBOK Guide, 6th edition, Chapter 5: Project Scope Management, p. 131-132

According to the PMBOK Guide, 7th edition, one of the principles of project management is to engage stakeholders1. This means that the project manager should communicate effectively with all stakeholders, provide them with relevant information, and address their needs and expectations. In a hybrid project, where some aspects of the project follow a predictive approach and others follow an adaptive approach, the project manager should use a combination of tools and techniques to manage the project artifacts2. One of these tools is a repository or a system that stores and organizes the project artifacts, such as the project schedule, for easy access and retrieval3. The project manager should ensure that all stakeholders have access to the repository and know how to use it to find the project artifacts they need. This will help to avoid confusion, duplication, and inconsistency of information, and to foster collaboration and transparency among the project team and other stakeholders. Therefore, the best answer is C.

 According to the hybrid project management approach, which combines elements of waterfall and agile methodologies, the project manager should facilitate the collaboration and communication among the team members and adjust the scope and schedule as needed12. However, any changes to the product scope should be controlled and evaluated for their impact on the project objectives, risks, quality, and customer satisfaction34. Therefore, the best option for the project manager in this scenario is to follow the proper change control process and evaluate the change for further impact. This way, the project manager can ensure that the change is justified, approved, documented, and communicated to all relevant stakeholders5. The project manager can also assess the potential risks and benefits of the additional feature and take appropriate actions to mitigate or exploit them6.

The other options are not the best ways to avoid this situation in the future. Managing the scope baseline to influence the factors that drive change is a proactive approach to prevent unnecessary or excessive changes, but it does not address the change that has already occurred7. Working with the customer to ensure the feature adds value is a good practice to align the product with the customer needs, but it does not consider the impact of the change on the project constraints or other stakeholders8. Performing frequent reviews with the customer to ensure that the product is working as expected is a useful technique to gather feedback and validate the product quality, but it does not prevent the introduction of new features without proper change control. References: 1: What is the Hybrid Approach in Project Management? | Hygger.io 2: Hybrid Project Management: What is it, Approach & Software - Teamhood 3: [Project Scope Management | Project Management Institute] 4: [A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition], p. 131-132 5: [Change Control Process: A Complete Guide - ProjectManager.com] 6: [Project Risk Management | Project Management Institute] 7: [Project Scope Management | Project Management Institute] 8: [Project Stakeholder Management | Project Management Institute] : [Project Quality Management | Project Management Institute] : Project Scope Management | Project Management Institute : A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition : Change Control Process: A Complete Guide - ProjectManager.com : Project Risk Management | Project Management Institute : Project Stakeholder Management | Project Management Institute : Project Quality Management | Project Management Institute

 According to the PMBOK Guide, risk management is the process of identifying, analyzing, and responding to project risks. Project risks can be either threats or opportunities. A threat is a negative event or condition that may adversely affect the project objectives, while an opportunity is a positive event or condition that may enhance the project objectives. In this question, the new law is an external risk that poses a threat to the current production processes, but also an opportunity to introduce new products that can meet the customer needs and increase the market share. The project manager should inform the management of this risk and opportunity, and share the proposed products that can take advantage of the situation. This way, the project manager can align the project objectives with the organizational strategy, and seek the support and approval of the management for the changes. This is also consistent with the stakeholder management process, which involves identifying, analyzing, and engaging the stakeholders throughout the project life cycle. The management is a key stakeholder that has high power and interest in the project outcome, and should be kept informed and satisfied. Therefore, option C is the best answer. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 11: Project Risk Management, pages 397-455

PMBOK Guide, 6th edition, Chapter 13: Project Stakeholder Management, pages 513-542

Free PMP Questions and Answers – Are You Ready for PMP Exam?

 This is the best option because it addresses the root cause of the problem, which is the unclear product requirements. By analyzing the problem with both teams, the project leader can facilitate communication, collaboration, and alignment between them. This can help to clarify the product vision, prioritize the backlog, and identify any gaps or errors in the work done so far. This can also help to improve the quality of the product and the satisfaction of the stakeholders.

The other options are not as effective because they do not address the underlying issue or they may create more problems. For example:

B. Selecting new team members may disrupt the existing team dynamics and introduce more uncertainty and confusion. It may also delay the project and increase the cost.

C. Demanding that the business team define final requirements may create conflict and resentment between the teams. It may also be unrealistic or impractical to expect final requirements in a complex and changing environment.

D. Telling the teams to continue following the initial plan may result in wasted time and resources, as well as low-quality outcomes. It may also ignore the feedback and learning from the previous sprints.

According to the PMBOK Guide, the project manager should use interpersonal and team skills to manage the team and resolve conflicts. One of these skills is conflict management, which involves identifying and addressing the root causes of disagreements among team members. In this case, the project manager should try to understand why the team member is absent from the meetings and what are the possible impacts on the project and the team. The project manager should also communicate the benefits of attending the meetings and encourage the team member to participate more actively. This way, the project manager can foster a collaborative and respectful team environment and avoid potential issues such as poor communication, low morale, or missed deadlines. References: PMBOK Guide, 7th edition, pages 282-283, 287-288.

According to the PMBOK Guide, 7th edition, one of the project management principles is to “engage stakeholders to understand their interests and needs”. This means that the project manager should communicate with the stakeholder and clarify the scope, objectives, and expectations of the project. The project manager should also explain the impact of the stakeholder’s interruptions and changes on the team’s performance and morale, and negotiate a mutually acceptable way to handle the stakeholder’s requests. The project manager should also update the stakeholder register and the stakeholder engagement plan to reflect the stakeholder’s influence and engagement level, and monitor the stakeholder’s satisfaction throughout the project. References: PMBOK Guide, 7th edition, page 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48…

 In an iteration-based project, the project team should collaborate with the stakeholders frequently and continuously to ensure that the product meets their expectations and needs. The project team should also identify and resolve any impediments or issues that may affect the delivery of the product. By holding a touchpoint with the marketing team before the demo, the project team could have aligned their expectations, clarified the requirements and constraints, and addressed any potential risks or challenges. This would have helped to avoid the issue of the marketing team needing more iterations to launch the product and not starting their work yet. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 5, Section 5.1.2.1, page 152

PMBOK Guide, 6th edition, Chapter 6, Section 6.2.2.1, page 191

PMBOK Guide, 6th edition, Chapter 13, Section 13.2.2.1, page 507

PMBOK Guide, 6th edition, Appendix X3, Section X3.2.2, page 718

PMI PMP-Project Management Professional Practice Exam Q. 781 to 790

 The project manager should raise a new issue in the issue log and convene SMEs and relevant stakeholders to identify alternatives to address the problem. This is because the inability of the subcontractor to supply a key component is an issue that has already occurred and needs to be resolved as soon as possible. The issue log is a tool for documenting and monitoring the resolution of issues that arise during a project1. The project manager should also involve the SMEs and relevant stakeholders who have the expertise and authority to provide input and guidance on how to deal with the issue. The project manager should not discuss the issue with the project sponsor and request extra time and budget to obtain the component from a different supplier, as this would be premature and may not be the best option. The project manager should not raise a new risk in the risk register, perform a risk assessment, and convene SMEs and relevant stakeholders to plan a risk response, as this would be appropriate for a potential problem that has not yet occurred, not an actual issue that has already happened. The project manager should not submit a change request to the CCB for changes to the performance measurement baseline to obtain the component from a different supplier, as this would be a formal process that requires approval and may not be necessary if the issue can be resolved in other ways. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 4.6.1.1, “Issue Log”

In an agile project, the project manager is responsible for facilitating the collaboration and coordination among the team members, as well as ensuring that the team has the necessary resources and support to deliver value1. One of the key practices of agile project management is to break down large projects into smaller, manageable tasks that can be assigned to different team members and tracked using tools such as task boards or backlogs234. This way, the team can avoid duplication of work, reduce dependencies, and increase transparency and accountability.

If the project manager notices that the team members are sometimes working on the same task, it indicates that there is a lack of clarity or communication about the task assignments. The project manager should address this issue by communicating the task assignments to the team members in a clear and consistent manner, using the appropriate tools and channels. The project manager should also encourage the team members to communicate with each other and update their task status regularly, so that everyone is aware of the progress and potential issues.

The other options are not correct for the following reasons:

B. Verify that the product owner has made the task assignments clear. The product owner is the person who represents the customer’s needs and priorities, and defines the product vision and scope1. The product owner is not responsible for making the task assignments, but rather for providing the team with the product backlog, which is a list of features or requirements that the team can use to create tasks.

C. Confirm that the agile coach has made the task assignments clear. The agile coach is the person who helps the team adopt and improve their agile practices, and provides guidance and feedback on the agile principles and values1. The agile coach is not responsible for making the task assignments, but rather for supporting the team’s self-organization and empowerment.

D. Verify that the team members have made the task assignments clear. The team members are the people who perform the work and deliver the product, and they are expected to be cross-functional and self-organizing1. The team members are responsible for making the task assignments among themselves, based on the product backlog and their skills and availability. However, verifying that the team members have made the task assignments clear is not enough to solve the problem of working on the same task. The project manager should also communicate the task assignments to the team members and ensure that they are aligned and coordinated.

1: Best practices for Agile project management 2: Breaking Down Large Projects Into Tasks in an Agile Process 3: Free Project Task List Templates for Project Management 4: Free Agile Project Plan Template: Plan Efficiently [2023] : Product Owner - Scrum.org : Agile Coach - Scrum.org : Development Team - Scrum.org

The alignment between the project team and stakeholders is crucial for the success of a project. This alignment must be maintained throughout the project’s life cycle, ensuring clarity of scope, risk, schedule, and price at each phase1. In a hybrid project management approach, risks should be reviewed during each iteration and review to ensure alignment between the project team and stakeholders2. This allows for timely identification and mitigation of risks, ensuring that all parties are aware of potential risks and their outcomes2. Regular reviews also facilitate open communication and collaboration, which are key to successful risk management3.

Diagram Description automatically generated

According to the PMBOK Guide, a hybrid project approach is a combination of predictive, agile, and/or iterative methods that best suit the project context and objectives. A hybrid project approach requires the project manager to establish team behavior and develop an understanding of how to work together, as different team members may have different preferences, expectations, and experiences with different project methods. The project manager should facilitate collaboration, communication, and integration among team members, and align them with the project vision, goals, and values. The project manager should also provide feedback, coaching, and recognition to the team members, and foster a culture of trust, respect, and learning. The project manager should not advise the team to adjust their work habits and behaviors to allow for better conflict resolution, as this may imply that the project manager is imposing a single way of working on the team, rather than embracing diversity and flexibility. The project manager should not call a team meeting to discuss team members’ strengths and weaknesses, as this may create unnecessary tension and conflict among team members, and may not address the specific challenges and opportunities of a hybrid project approach. The project manager should not establish rules and regulations for team members with consequences if the goals are not reached, as this may create a rigid and punitive environment that discourages innovation, experimentation, and adaptation, which are essential for a hybrid project approach. References: PMBOK Guide, 7th edition, pages 14-15, 25-26, 32-33; Hybrid Project Management: What You Need to Know

 A definition of ready (DoR) is a set of criteria or conditions that a product backlog item (PBI) must meet to be considered ready to be pulled into the sprint backlog1. A DoR ensures that the PBIs are clear, feasible, valuable, testable, and independent23. By creating a DoR for the backlog items, the project manager can avoid work overruns and ensure that the team can effectively tackle the tasks in the sprint2. References:

Definition of Ready (DoR) [+ Key Components] | Atlassian

Definition of Ready: Keeping Your Backlog in Check - Atlassian Community

Ready or Not? Demystifying the Definition of Ready in Scrum

The graph shows that the project is performing below the baseline for both schedule and cost, which means it is behind schedule and under budget. This indicates that the project is not meeting its planned progress and deliverables, and may have some issues with scope, quality, or resources. The project manager should review the project schedule to identify the root causes of the delays, and take corrective actions to bring the project back on track. The project manager should also monitor the project cost to ensure that it does not exceed the budget, and communicate the status and changes to the stakeholders. References:

PMBOK Guide, 7th Edition, Chapter 8: Performance Measurement and Reporting1

The PMI Guide to Business Analysis, Chapter 5: Planning Business Analysis Work2

Business Analysis for Practitioners: A Practice Guide, Chapter 4: Elicitation and Collaboration3

According to the PMBOK Guide, servant leadership is a key aspect of agile project management. It is a leadership style where the leader, rather than seeking to be served, prioritizes the needs and development of their team members1. Servant leaders help their teams to self-organize, collaborate, and adapt to changing requirements and environments2. One of the practices that support servant leadership in agile project management is the daily standup, also known as the daily scrum. It is a short, time-boxed meeting where the team members synchronize their work and plan for the next 24 hours. The daily standup also provides an opportunity for the team members to share their impediments, risks, and issues, and for the servant leader to facilitate the removal of those obstacles34. By implementing daily standups, the project manager can foster a culture of transparency, feedback, and continuous improvement among the team members, and help them achieve their project goals more effectively and efficiently5. References: 1: PMBOK Guide, 7th edition, page 55 2: A Little Bit of Both1 3: Guide on Servant Leadership in Agile Project Management3 4: 7 Traits of Servant Leadership in Agile Project Management4 5: How to create a project management communication plan5

According to the PMBOK Guide, pull communication is a type of communication that is used when the information is large, complex, or requires a high level of detail, and the recipients can access it at their own discretion. Examples of pull communication include websites, intranets, e-learning, databases, and knowledge repositories. By using pull communication, the project manager can reduce the amount of emails sent to the team and allow them to access the project-related information when they need it. This can also improve the efficiency and effectiveness of the communication process. References: PMBOK Guide, 7th edition, page 286; Business Acumen for the PMP Exam

According to the PMBOK Guide, 6th edition, section 4.6.1.1, the project manager is responsible for communicating the approved changes to the relevant stakeholders and ensuring that the changes are implemented as planned. The project manager should also manage the expectations of the stakeholders and address any issues or concerns that arise from the changes. In this scenario, the project manager should first meet with the operations manager to explain the background for the change and understand the operation manager’s concerns about the change. This will help to establish a collaborative relationship and resolve any potential conflicts. The other options are either premature or inappropriate, as they do not address the root cause of the problem or respect the authority of the CCB. References: PMBOK Guide, 6th edition, section 4.6.1.1, page 115.

According to the PMP Exam Content Outline, one of the tasks under the domain of Stakeholder Management is to manage stakeholder engagement, which includes communicating and interfacing with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement. Stakeholder engagement is the process of involving stakeholders in the project decisions and activities, and ensuring that their interests and concerns are considered and addressed. Stakeholder engagement is crucial for project success, as it can increase stakeholder satisfaction, commitment, support, and trust, as well as reduce conflicts, risks, and resistance to change12.

One of the tools and techniques for managing stakeholder engagement is the stakeholder engagement plan, which is a component of the project management plan. It describes the strategies and actions that will be used to promote productive involvement of stakeholders in decision making and project execution3. The stakeholder engagement plan should include the following elements:

Stakeholder identification and analysis: This involves identifying the key stakeholders of the project, their roles, interests, expectations, influence, and impact on the project, and their current and desired levels of engagement.

Stakeholder engagement assessment matrix: This is a table that shows the changes in the level of engagement of each stakeholder or stakeholder group over time, and the gaps between the current and desired levels of engagement.

Stakeholder engagement strategies: These are the approaches and methods that will be used to increase the level of engagement of stakeholders, such as communication, negotiation, collaboration, consultation, education, etc.

Stakeholder communication plan: This is a document that specifies the information needs and preferences of each stakeholder or stakeholder group, the frequency and mode of communication, the communication channels and methods, the communication roles and responsibilities, and the communication feedback and evaluation mechanisms.

Stakeholder engagement action plan: This is a list of specific actions and activities that will be performed to implement the stakeholder engagement strategies and the stakeholder communication plan, such as conducting meetings, workshops, surveys, interviews, presentations, reports, etc.

One of the best practices for stakeholder engagement is to set clear meeting expectations by sharing agendas in advance. This can help the project manager to obtain participation from key stakeholders who do not usually attend project meetings, by:

Showing respect for the stakeholders’ time and availability, and inviting them to attend only the meetings that are relevant and important for them.

Providing them with the purpose, objectives, topics, and outcomes of the meeting, and how their input and feedback will be valued and used.

Encouraging them to prepare for the meeting, and to raise any questions, issues, or concerns beforehand or during the meeting.

Creating a positive and collaborative atmosphere for the meeting, and facilitating the discussion and interaction among the participants.

Following up with the stakeholders after the meeting, and sharing the meeting minutes, action items, and decisions.

The other options are not correct because they do not address the root cause of the lack of stakeholder participation, which is the low level of engagement. Distributing the communications management plan may not be effective, as the stakeholders may not read it or find it relevant. Rescheduling meetings to align with the stakeholders’ availability may not be feasible, as the stakeholders may have conflicting schedules or priorities. Escalating the issue to senior management may not be appropriate, as the stakeholders may perceive it as a threat or a sign of disrespect. Therefore, the best option is to set clear meeting expectations by sharing agendas in advance, as this can increase the stakeholder engagement and participation in the project meetings. References:

PMP Exam Content Outline

Stakeholder analysis4

Stakeholder engagement plan3

7 Benefits of Stakeholder Participation1

Project Stakeholder Management According to the PMBOK2

 The project manager should conduct a consensus-building session to decide how to approach the next set of work, as this is a collaborative decision-making technique that involves the participation of all team members and stakeholders. The project manager should facilitate the discussion, clarify the objectives, identify the options, evaluate the pros and cons, and reach a mutually acceptable agreement. This will help to resolve the conflict, align the expectations, and ensure the commitment of the team and the stakeholders. The other options are not the first actions that the project manager should take, as they may either delay the decision, bypass the team’s input, or ignore the conflict. References:

[PMBOK Guide], 6th edition, pages 56-57, 376-377, 513-514.

[Professional in Business Analysis (PMI-PBA) Handbook], pages 15-16, 19-20.

The project manager should first consider organizing paired work sessions for the junior and senior economists. This is a proactive and positive way to address the issue of intimidation and improve the performance and confidence of the junior economist. Paired work sessions can also foster collaboration, knowledge sharing, and mentoring among the project team members. This option aligns with the PMI-PBA practice guide, which states that “pairing a less experienced analyst with a more experienced one can be an effective way to transfer skills and knowledge” (p. 44). The other options are not the best choices because they do not address the root cause of the problem and may have negative consequences for the project. Evaluating the performance of the junior economist in the upcoming months (option A) is a reactive and delayed approach that does not provide any immediate support or guidance to the junior economist. Reassigning some of the junior economist’s tasks to other economists (option B) may reduce the workload of the junior economist, but it does not help him or her overcome the intimidation or develop the skills and knowledge needed for the project. Requesting to replace the junior economist with a more experienced economist (option C) may seem like a quick and easy solution, but it may also demoralize the junior economist, disrupt the project team dynamics, and incur additional costs and risks for the project. References:

PMI-PBA Practice Guide, p. 44 1

PMBOK Guide, 6th edition, p. 336 2

The project manager should try to understand why the customer is not clearing the packages for shipment and not participating in the communication calls. This could indicate a lack of interest, satisfaction, or trust in the project or the project team. The project manager should initiate a dialogue with the customer to address their concerns, expectations, and feedback, and to re-establish a positive relationship. This is part of the stakeholder engagement process, which aims to increase the support and minimize the resistance from the stakeholders throughout the project life cycle. The other options are not appropriate because they do not address the underlying problem and may worsen the situation. Requesting a change in the contract or a delivery date extension may create more conflict or confusion with the customer, and informing the customer that subsequent packages cannot be manufactured may jeopardize the project scope and quality. References: PMBOK Guide 6th Edition, pages 513-514, 518-519, 524-525.

The project manager should review the lessons learned registers from the previous projects to identify the root causes of the failures, the best practices that worked, and the recommendations for improvement. This will help the project manager to avoid repeating the same mistakes, to apply the proven methods, and to enhance the project performance. The lessons learned registers are part of the organizational process assets that can be used as inputs for planning and executing the project12. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 4.4.3.1, page 112

Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain II: Planning, Task 7, page 10

According to the PMP Exam Content Outline, one of the tasks under the domain of Business Environment is to plan and manage project compliance, which includes confirming project compliance requirements and classifying compliance categories. Compliance requirements are the rules and regulations that the project must follow to meet the standards of quality, safety, security, and legality. Compliance categories are the types of compliance requirements that apply to the project, such as security, health and safety, regulatory, environmental, etc. Compliance requirements and categories may vary depending on the industry, country, and organization of the project. Therefore, the project manager should not assume that there are no compliance requirements for the project based on the sponsor’s knowledge, but should seek expert advice from the compliance leader, who is the person responsible for ensuring that the project meets the compliance standards and requirements. The compliance leader can help the project manager confirm if there are any compliance requirements for the project, and if so, what they are and how to comply with them. This will help the project manager avoid the risks and consequences of non-compliance, such as fines, penalties, lawsuits, reputation damage, or project failure. The other options are not correct because they do not involve consulting the compliance leader, who is the best source of information and guidance on compliance matters. Checking with the national compliance agency may not be sufficient, as there may be other compliance requirements at the regional, local, or organizational level. Trusting in the expertise of the sponsor may be risky, as the sponsor may not be aware of all the compliance requirements or changes that may affect the project. Conducting independent research may be helpful, but it may not be comprehensive, accurate, or up-to-date, and it may not address the specific needs and context of the project. References:

PMP Exam Content Outline

How compliance in project management works1

3.1 Plan and Manage Project Compliance2

According to the PMBOK Guide, the project manager is responsible for identifying, analyzing, and responding to project risks. One of the tools and techniques for risk management is perform qualitative risk analysis, which involves assessing the probability and impact of identified risks on project objectives. When a risk occurs, such as the change in the wire compatibility, the project manager should first perform qualitative risk analysis to determine the severity and urgency of the risk response. The project manager should also consult with the project team and other relevant stakeholders to evaluate the potential options and alternatives for addressing the risk. One of the possible options is to survey the market for alternative wires with similar characteristics that can be compatible with the machine. This option may require some adjustments in the design or testing of the machine, but it may also preserve the market coverage and customer satisfaction. Therefore, the project manager should investigate the impact of this option with the team and compare it with other possible options before making a decision. References: PMBOK Guide, 6th edition, pages 397-398, 423-424.

The project charter is a document that formally authorizes a project or a phase and documents initial requirements that satisfy the stakeholder’s needs and expectations. It provides the project manager with the authority to apply organizational resources to project activities. When a new project manager is assigned to a project, they should refer to the project charter to understand the project objectives, key stakeholders, risks, and the authority delegated to them. References: Project Management Professional (PMP) Reference Materials12.

 According to the Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, one of the tasks of a business analyst is to “communicate and manage solution scope boundaries and approval processes to stakeholders” (Task 5.2). This implies that any changes to the solution scope should be approved by the relevant stakeholders and follow a predefined process. The PMBOK® Guide2 also states that “the project manager, project team, and other stakeholders are responsible for determining how the project scope will be managed, how scope changes will be integrated into the project, and who will approve the scope changes” (Section 5.6.1). Therefore, the project manager should advise the team not to engage in modifications unless it follows the proper change approval process, as this would ensure that the scope is controlled and aligned with the project management plan. References:

1: Professional in Business Analysis (PMI-PBA)® Examination Content Outline

2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition

The project manager should plan to conduct informal sessions with the stakeholders to educate them about the project objectives, scope, and technology, and to address their concerns and queries. This will help to improve the stakeholders’ awareness, engagement, and buy-in, and to reduce the objections and queries that are wasting time in the meetings. This is part of the Manage Stakeholder Engagement process, which involves communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement1. Requesting stakeholders who understand the technology, recommending a change in technology, or including the issue in the issue log and escalating it are not the best options, as they may alienate the existing stakeholders, compromise the project vision, or escalate a problem that can be resolved at a lower level. References: 1 PMBOK® Guide, 6th edition, page 518.

 According to the Project Management Professional (PMP)® Examination Content Outline1, one of the tasks under the domain of executing is to “assess and prioritize impact of changes to project scope, schedule, cost, quality, resources, and risks”. This implies that before implementing any change request, the project manager should first evaluate how the change will affect the project objectives and deliverables, and whether the change is aligned with the business case and the stakeholder expectations. The business case is the document that justifies the initiation of a project by providing the expected benefits, costs, risks, and strategic alignment of the project2. Therefore, the project manager should identify how the proposed changes will benefit the project in relation to the business case, and communicate the results of the assessment to the senior management and other relevant stakeholders. This can help to ensure that the changes are necessary, feasible, and beneficial, and that they do not compromise the project scope, quality, or value. References:

1: Project Management Professional (PMP)® Examination Content Outline, page 10

2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, page 29

The project manager should clarify expectations by explaining the company culture with the supervisor. The company culture reflects the shared values, beliefs, and norms that influence how people behave and interact in the organization. The project manager should communicate the positive changes that have occurred in the company culture and how they affect the project objectives, scope, quality, and stakeholder satisfaction. The project manager should also seek to understand the supervisor’s leadership style and expectations and try to find a common ground that respects both the company culture and the supervisor’s authority. Asking senior management to move the supervisor, revisiting the company’s organizational culture, or instructing the employees to listen to the supervisor may not resolve the issue and may create more conflict and resentment. References: PMBOK Guide, 6th edition, page 30; PMP Exam Content Outline, 2021, page 8.

According to the Professional in Business Analysis (PMI-PBA)® Examination Content Outline, one of the tasks of a business analyst is to “manage stakeholder collaboration to achieve project objectives” (Task 4.1). This includes “facilitating conflict resolution” and “addressing issues that may impact stakeholder relationships” (Task 4.1.3 and 4.1.4). Therefore, the project manager should explain the impact of the scenario to the project team member and help them understand how their behavior is affecting the project and the client relationship. This is also consistent with the PMI Code of Ethics and Professional Conduct, which states that project managers should “respect the property rights of others” and “act in a manner that is in the best interests of society and the environment” (Section 4.3.1 and 4.3.2). References:

Professional in Business Analysis (PMI-PBA)® Examination Content Outline, PMI, 2018, pp. 23-24.

PMI Code of Ethics and Professional Conduct, PMI, 2006, pp. 5-6.

The Work Breakdown Structure (WBS) is a key project deliverable that organizes the team’s work into manageable sections. The Project Management Body of Knowledge (PMBOK) defines the work breakdown structure as a “deliverable oriented hierarchical decomposition of the work to be executed by the project team.” This option is the most effective way to manage large and complex deliverables that cannot be assigned to a single person. References: PMBOK Guide, 6th Edition, Section 5.4: Create WBS

A hybrid project is a project that combines predictive and adaptive approaches. In such a project, the project manager should ensure that the team receives continuous feedback from customers users to validate the alignment of the deliverables with the expectations. This is a key practice of agile and adaptive methods, which aim to maximize customer satisfaction and value delivery. Updating the project management plan, submitting a change request, or ensuring the team understands all additional project requirements are not steps that would prevent the misalignment of the deliverables with the expectations, but rather actions that could be taken after the problem has occurred. References: [PMI Agile Practice Guide], page 14; [PMBOK® Guide 6th Edition], page 19.

The project manager should address the personal differences and work styles of the team members by meeting with them and agreeing on expectations from each other. This is a proactive way of managing conflict and fostering collaboration among the team members. It also helps to establish a common vision and goals for the project and clarify the roles and responsibilities of each team member. This approach is consistent with the PMI-PBA Domain 5: Solution Evaluation, Task 5.2: Communicate Solution Status, and the PMP Domain 3: People, Task 3.4: Lead a Team. References: (Professional in Business Analysis Reference Materials source and documents)

PMI-PBA Exam Content Outline, Domain 5: Solution Evaluation, Task 5.2: Communicate Solution Status1

PMP Exam Content Outline, Domain 3: People, Task 3.4: Lead a Team2

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 9: Project Resource Management, Section 9.4: Develop Team

According to the PMBOK Guide, the project manager is responsible for managing the project team, which includes developing, leading, motivating, and supporting the team members. One of the tools and techniques for managing the project team is interpersonal and team skills, which include mentoring and coaching. Mentoring and coaching are ways of providing guidance, feedback, and support to the team members to help them improve their performance, skills, and motivation. By providing routine mentoring and coaching, the project manager can identify any issues that may be affecting the team members’ performance, such as stress, burnout, conflict, or lack of recognition, and address them accordingly. This can help maintain the project team’s performance level and prevent further deterioration. References: PMBOK Guide, 6th edition, pages 349-350, 360-361; PMP Sample Test Questions, question 2.

According to the PMBOK Guide, 6th Edition, Section 9.2.2.1, “Resource calendars specify the availability, capability, and skills of human resources and the availability of equipment and materials.” The project manager should consult the company’s resource calendars to determine the availability and suitability of the resources required for the new project. This will help the project manager to estimate the duration, cost, and risk of the project, as well as to plan the resource allocation and management. The other options are not as relevant or accurate as the resource calendars for this purpose. The company’s historical organizational project artifacts may provide some useful information, but they may not reflect the current situation or the specific needs of the new project. The company’s project responsibility assignment matrix (RAM) may show the roles and responsibilities of the project team members, but it may not indicate their availability or skills. The company’s resource management plan may describe the policies and procedures for managing resources, but it may not provide the details of the individual resources required for the new project. References:

PMBOK Guide, 6th Edition, PMI, 2017, pp. 336-337.

How to Measure Your Project Resource Requirements, MetaPM, 2024, accessed on February 24, 2024.

The conflict described is a communication issue within the team. According to the PMBOK Guide, one of the key roles of a project manager is to manage team dynamics and resolve conflicts. In this case, reviewing the ground rules for collaboration within the team can help remind team members of the expected behaviors and communication norms, which can help resolve the issue. Moving a team member to a different team (Option A) may not solve the underlying issue, reporting to supervisors (Option C) may escalate the situation unnecessarily, and modifying the communications management plan (Option D) may not directly address the interpersonal conflict. References: Project Management Body of Knowledge (PMBOK) Guide, 6th Edition, Section 9.5.2.1: Conflict Management

 According to the PMBOK Guide, a change request is a formal petition for change in a project. It’s a document that explains what are the changes to be made and the main reasons why they should be implemented1. Change requests can either be submitted by internal or external project stakeholders. When a project manager realizes that some operational project requirements were not captured in the project scope of work, they should issue a change request to include the additional scope, and track the completion of the work items. This is the best way to ensure that the project deliverables meet the customer’s needs and expectations, and that the project scope is aligned with the project objectives. The other options are not the best actions to take in this situation. Issuing a change request to remove items from the scope of work and keep the project on schedule (option A) may compromise the quality and value of the project deliverables, and may result in customer dissatisfaction or rejection. Documenting the issue in the lessons learned document, and discussing this with the project sponsor (option C) may be helpful for future projects, but it does not address the current issue or resolve the gap in the project scope. Arranging to pass the cost to the operational area since the customer will benefit (option D) may create conflicts and resentment among the project stakeholders, and may violate the project budget and contract terms. References: PMBOK Guide, 6th edition, pages 115-116, 123-124.

The statement of work (SOW) is a document that describes the project scope, deliverables, acceptance criteria, assumptions, and constraints1. It is usually part of the contract between the buyer and the seller2. If the project manager remembers negotiating and agreeing to the deliverable during the tender process, they should look to see if the deliverable is described in the SOW, which would be a contractual obligation for the seller. Requesting a change in the contract, adding the deliverable to the requirements traceability matrix, or terminating the contract are not appropriate actions in this situation. References:

1 PMBOK Guide, 6th edition, page 154

2 PMBOK Guide, 6th edition, page 473

 The forming phase of a project team is when team members are uncertain about the team’s purpose, their roles, and how to work together1. The project manager’s job is to help the team overcome this uncertainty by clarifying the team goals, expectations, and norms2. One of the tools that can help the project manager in this stage is to assess and analyze the personality indicators of the team members, such as the Myers-Briggs Type Indicator (MBTI) or the DiSC profile. These tools can help the project manager understand the preferences, strengths, and weaknesses of each team member, and how they interact with others3. By doing so, the project manager can tailor the team-building activities to suit the needs and preferences of the team, and avoid activities that might cause discomfort, frustration, or conflict among the team members. For example, improvisation theater activities might be fun for some team members who enjoy spontaneity, creativity, and humor, but they might be stressful or awkward for others who prefer structure, planning, and logic. Therefore, the project manager should have assessed and analyzed the personality indicators of the team before choosing such an activity, and consulted with the team members to ensure that they are comfortable and willing to participate. Alternatively, the project manager could have chosen a different team-building activity that is more suitable for the forming stage, such as icebreakers, introductions, or games that help the team members get to know each other better4. References:

1: The 5 Stages of Team Development (Including Examples) | Upwork

2: Forming, Storming, Norming and Performing for Agile teams | Scrum.org

3: Team Development Cycle: From Forming To Performing - Teamhood

4: 45 Team Building Games to Psych Up Your Team [2023] • Asana

 According to the PMBOK Guide, a project manager should manage stakeholder expectations and ensure that the project aligns with the organizational strategy and governance framework1. The project manager should also communicate effectively with the PMO and follow the organizational policies and procedures for reporting2. Therefore, the best option is to meet with the project stakeholders and explain the need to comply with the PMO standards and update the status report format accordingly. This way, the project manager can balance the stakeholder needs and preferences with the organizational requirements and expectations. References:

1: PMBOK Guide, 6th edition, Chapter 13: Stakeholder Management, p. 513-514

2: PMBOK Guide, 6th edition, Chapter 2: The Environment in Which Projects Operate, p. 38-39

The project manager should update and share the guideline document dealing with team communication to ensure that there are no potential misunderstandings among the virtual team members. This is because the guideline document defines the communication requirements, methods, channels, frequency, and protocols for the project team, especially when working remotely or across different locations, cultures, and time zones. The project manager should also involve the new team members in the communication planning process and solicit their feedback and preferences. This will help establish trust, rapport, and collaboration among the team members and foster a shared understanding of the project goals, roles, and expectations. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 10.1.1, “Plan Communications Management: Inputs”

PMBOK® Guide, 6th edition, Section 10.1.3.1, “Plan Communications Management: Outputs - Communications Management Plan”

PMI-PBA® Guide, 1st edition, Section 4.2.1, “Plan Communications: Inputs”

PMI-PBA® Guide, 1st edition, Section 4.2.2, “Plan Communications: Tools and Techniques”

PMI-PBA® Guide, 1st edition, Section 4.2.3, “Plan Communications: Outputs”

According to the PMBOK Guide, 6th edition, section 8.3.3.1, the project manager is responsible for monitoring and controlling the project quality and ensuring that the project deliverables meet the quality requirements. The project manager should also document any quality issues or defects that are identified during the quality control process and take appropriate actions to correct them. In this scenario, the project manager should first update the issue log, identify the involved stakeholders, and assign resources to the corrective actions. This will help to track and resolve the quality issue and prevent further deviations or rework. The other options are either premature or irrelevant, as they do not address the root cause of the problem or respect the authority and scope of the project manager. References: PMBOK Guide, 6th edition, section 8.3.3.1, page 287.

The project manager should use the manage team process to optimize team performance and enhance project activities. This process involves tracking team member performance, providing feedback, resolving issues, and managing team changes. One of the tools and techniques for this process is conflict management, which is the application of resolution techniques to minimize the negative aspects of conflict and enhance the positive aspects of conflict. The project manager should use conflict management skills to resolve the differences with the key resource and build a good working relationship based on trust and respect. This will help ensure project success and foster a collaborative team environment. Monitoring the key resource closely throughout the project, but not letting the project sponsor know about the conflict (option B) may not be effective or ethical, as it may create a sense of distrust and resentment between the project manager and the key resource. It may also prevent the project sponsor from providing support or guidance if needed. Requesting that the key resource’s functional manager work directly with the resource during the project (option C) may not be feasible or appropriate, as it may undermine the project manager’s authority and responsibility. It may also create confusion and conflict among the team members and stakeholders. Discussing this with the project sponsor and requesting that this key resource be replaced on the project (option D) may not be the best option, as it may cause delays and disruptions to the project. It may also damage the relationship between the project manager and the key resource, as well as the key resource’s functional manager. Moreover, the key resource is needed to ensure the completion of a major component for the project, so replacing them may not be easy or desirable. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, pages 349-350, 9.4 Manage Team

PMI, PMP Exam Content Outline, 2021, page 10, Domain II: Process, Task 8: Manage project team members and their assignments

PMP Practice Questions #56 - iZenBridge

According to the PMBOK Guide1, a hybrid approach is a combination of predictive and adaptive (agile) methodologies that suits the needs and context of a project. A hybrid approach can provide flexibility, customer satisfaction, and risk management benefits. However, it also requires a high level of collaboration, communication, and alignment among the project stakeholders, especially the sponsor and the team. Therefore, the project manager should train the marketing team on the hybrid approach and keep their director informed of the progress, benefits, and challenges of using it. This way, the project manager can ensure that the team is competent and confident in applying the hybrid approach, and that the director is aware and supportive of the new direction. The project manager can also use this opportunity to address any concerns or resistance from the director and demonstrate the value of the hybrid approach for the project and the organization.

The other options are not as effective as option C. Option A is not realistic, as the marketing director may not have the time or interest to receive formal training on the hybrid approach. Option B is not respectful, as the marketing team members are not in a position to coach their director. Option D is not appropriate, as the project manager is not the director’s mentor and cannot assume that role without the director’s consent and agreement. References: 1 PMBOK Guide, Seventh Edition, Chapter 2: Value Delivery System, Section 2.3: Tailoring the Delivery Approach, Page 38.

A root cause analysis is a technique that helps identify the underlying factors or causes of a problem or issue in a project12. It involves asking a series of questions, such as why, how, and what, to trace the problem back to its source and prevent it from recurring34. A root cause analysis is a best practice for project management because it helps the project team understand the nature and extent of the problem, find effective solutions, and avoid wasting time and resources on superficial fixes .

The project manager should have the project team perform a root cause analysis first to address the issue of the functionality failure because it will help them determine the exact reason why the functionality did not perform as expected, and what actions are needed to correct it. The other options are not the best practices for the first step to address the issue because:

Updating the issue log and documenting the change are important steps to record and communicate the issue, but they do not help solve the problem or prevent it from happening again .

Reviewing the product specification requirements is a good way to verify the expectations and scope of the project, but it does not help identify the cause of the functionality failure or how to fix it .

Submitting a change request for corrective action is a formal process that requires the approval of the change control board and the alignment with the project baselines and plans, but it does not help diagnose the problem or propose a solution .