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

The distribution list for the risk workshop should include the project team members, who are responsible for identifying, analyzing, and responding to the project risks; the consultants from outside the project with experience in the field, who can provide expert judgment and independent perspective on the potential risks and their impacts; and the customer, who is the primary stakeholder and beneficiary of the project and whose expectations and requirements should be considered in the risk management process12.

The other options are not the best choices for the distribution list because:

Functional managers, who are responsible for managing the resources and activities within a specific function or department, may not have direct involvement or interest in the project risk management, unless they are also part of the project team or the project sponsor3.

Engineers, who are involved in the technical design and implementation of the project, may not have sufficient knowledge or authority to address the risks that are beyond their scope of work or expertise4.

Weather experts, who can provide information and forecasts on the weather conditions that may affect the project, may not be relevant or necessary for the risk workshop, unless the project is highly sensitive or dependent on the weather factors5.

Therefore, the most appropriate and comprehensive distribution list for the risk workshop is the one that includes the team members, consultants from outside the project with experience in the field, and the customer. This way, the project manager can ensure that the risk workshop is conducted with the participation and input of the key stakeholders and experts who have the most knowledge, interest, and influence on the project risks and outcomes. ????

I hope this answer was helpful. If you have any other questions, please feel free to ask me. ???? References: 1: Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. 2: Project Management Institute. (2020). Project Management Professional (PMP)® Examination Content Outline. 3: Teamwork. (2021). 10 project management best practices you MUST know. 4: Salapatas, J. N. (2000). Best practices—the nine elements to success. Paper presented at Project Management Institute Annual Seminars & Symposium, Houston, TX. Newtown Square, PA: Project Management Institute. 5: PRACTICE STANDARD FOR PROJECT RISK MANAGEMENT.

Trend analysis is a mathematical technique that uses historical results to predict future outcomes1. It is a project management quality control tool that tracks variances in cost and schedule performance2. In agile projects, trend analysis can help monitor the velocity, quality, and scope of the project deliverables3. A project risk register tracking tool and an issues log are two sources of historical data that can be used for trend analysis. A project risk register tracking tool records the identified risks, their probability, impact, and response strategies. An issues log records the issues that have occurred, their status, and resolution. By extracting data from these two sources, an agile project manager can perform a trend analysis of all the risks that the project has monitored over the past 12 months and provide insights to the project sponsor. The other options are not relevant to trend analysis. Sharing the annual report with the sponsor may not provide enough detail on the risks and their trends. Organizing a stakeholder meeting to brainstorm on general project risks may not reflect the actual data and outcomes of the project. Referring the sponsor to the contract document may not address the sponsor’s request for trend analysis. References: 1: Trend analysis - Wikipedia3, 2: Trend Analysis [Technique] - Project Management Knowledge4, 3: Agile Project Management For Dummies Cheat Sheet - dummies

According to the Agile Testing: A Practical Guide For Testers And Agile Teams1, security and performance testing are two types of nonfunctional testing that are important for agile teams. Security testing ensures that the system is protected from unauthorized access, data loss, or corruption. Performance testing measures how the system responds to different levels of load, stress, and concurrency. These types of testing can be done at different levels of granularity, from unit testing to system testing, and can use tools such as JMeter, LoadRunner, or Selenium.

Story testing is a type of functional testing that verifies that the system meets the acceptance criteria of each user story. User stories are short descriptions of the features or functionalities that the customer wants from the system. Story testing can be done by the developers, testers, or customers, and can use tools such as FitNesse, Cucumber, or SpecFlow.

Tests based on behavior and test-driven development are two approaches that support agile testing practices. Behavior-driven development (BDD) is a technique that uses natural language to describe the expected behavior of the system in different scenarios. Test-driven development (TDD) is a technique that involves writing the tests before the code, and then refactoring the code to make the tests pass. Both BDD and TDD help to clarify the requirements, design the system, and ensure the quality of the code. They can use tools such as JUnit, NUnit, or RSpec.

According to the PMBOK Guide, the project manager should assess the required training per team member as part of the plan resource management process. This process involves identifying and documenting the project roles, responsibilities, skills, and competencies, as well as the training needs of the project team members. The project manager should also consider the project life cycle approach, whether it is predictive, adaptive, or hybrid, and the implications for the team’s knowledge and skills. The project manager should not coach, change, or deliver training to the team members without first assessing their training needs and gaps, as this may not be effective or efficient. References: PMBOK Guide, 7th edition, pages 307-308, 311-312.

Trend analysis is a technique that uses historical data to predict future outcomes. It can help the project manager identify any deviations from the planned schedule, cost, scope, or quality, and take corrective actions accordingly. Schedule analysis, quality control analysis, and root cause analysis (RCA) are also useful techniques, but they do not directly address the question of forecasting future performance.

= PMI PMP certification exam practice question and answer (Q&A) dump with detail explanation and reference

Given the situation where the project manager has spent $80,000 to complete only two actions in three days, it is clear that both the budget and schedule are not on track as planned. The cost performance index (CPI) and schedule performance index (SPI) are both less than 1.0, indicating that the project is over budget and behind schedule. The CPI is calculated as the earned value (EV) divided by the actual cost (AC), and the SPI is the EV divided by the planned value (PV). In this case, the EV is lower than expected because fewer actions have been completed than planned, and the AC is higher than the EV, leading to a CPI of less than 1.0. Similarly, the SPI is less than 1.0 because the project is behind schedule. Therefore, the project manager should reevaluate and prioritize the remaining actions to maximize the use of the remaining budget and time. This may involve identifying which of the remaining actions are most critical to the project’s objectives and finding ways to complete them within the constraints or seeking additional resources or time if necessary.

PMBOK Guide and standards foundational documents; Professional in Business Analysis (PMI-PBA) reference materials123.

According to the PMBOK Guide, an agile approach is suitable for projects that have a high degree of uncertainty and change, as it allows for frequent feedback, adaptation, and value delivery. An agile approach also enables the project team to demonstrate the benefits of the product to the sponsor and stakeholders through working increments or prototypes. Developing requirements and designs to support a faster product release may not address the uncertainty and change aspects of the project, and may compromise quality or scope. Emphasizing the adoption of a predictive approach may not be feasible or effective for a project that has a high degree of uncertainty and change, as it requires a detailed upfront planning and a rigid control of changes. Outsourcing development of the product to a third party may not be the best option for the project sponsor, who wants to see the benefits of the product demonstrated, and may introduce additional risks and challenges for the project management. References: PMBOK Guide, 7th Edition, Section 2.1.2, Agile Approach; Section 2.1.3, Hybrid Approach.

 The project manager is responsible for ensuring that the project complies with all the applicable laws, regulations, standards, and policies of the project location. This includes health and safety requirements, environmental protection, labor laws, permits, licenses, and any other legal obligations. Failing to comply with these requirements could result in legal penalties, fines, sanctions, reputational damage, or project termination. Therefore, the project manager should address this issue as soon as possible and update the project plan accordingly. Injury or loss incidents could delay project deliverables, but this is not the primary reason why the situation is problematic. It is imperative that established performance metrics are met, but this is not directly related to the health and safety requirements. The project manager must follow their employer’s organizational process assets (OPAs), but this does not necessarily mean that they are aligned with the project location’s regulatory requirements. References: = PMBOK Guide, 6th edition, pages 33-34, 89-90, 123-124, 375-376; PMP Exam Content Outline, 2020, pages 8-9.

According to the PMBOK® Guide, an agile coach is a person who guides, mentors, teaches, and facilitates a team in adopting and improving agile practices and principles. The agile coach should also foster a culture of collaboration, trust, feedback, and continuous improvement within the team. When a team member is openly criticized by others during a standup meeting, the agile coach should intervene and address the situation as soon as possible. The agile coach should emphasize the ground rules of the standup meeting, such as respecting each other, being supportive, and focusing on the work. The agile coach should then redirect the attention of the team to today’s activities and impediments, and help them find solutions and remove blockers. This way, the agile coach can prevent the conflict from escalating, maintain a positive team atmosphere, and ensure the team’s progress and alignment. Letting the discussion go on, addressing the team members involved during the next sprint retrospective, or avoiding the discussion by referring to the team charter are not effective ways to deal with the situation. These options may ignore, postpone, or evade the issue, which could harm the team’s morale, performance, and relationships. References: PMBOK® Guide, 6th edition, pages 52, 335, 540-541.

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

The project manager should first meet with the stakeholder to better understand their expectations and update the stakeholder engagement plan. The stakeholder engagement plan is a component of the project management plan that identifies the strategies and actions required to promote productive involvement of stakeholders in project decisions and execution1. By meeting with the stakeholder, the project manager can identify the stakeholder’s information needs, communication preferences, and level of interest and influence on the project. This will help the project manager to tailor the periodic reports and other communication methods to meet the stakeholder’s expectations and increase their satisfaction and support for the project2.

Option A is not the best answer because adding the stakeholder details into the periodic reports and updating the project management plan is a possible action to take after meeting with the stakeholder and understanding their expectations. It is not the first thing to do.

Option B is not the best answer because inviting the stakeholder to all future project review meetings and updating the project management plan is also a possible action to take after meeting with the stakeholder and understanding their expectations. It is not the first thing to do.

Option C is not the best answer because updating the project management plan with the new information and informing all of the relevant stakeholders is a general and vague action that does not address the specific issue of the stakeholder’s complaint. It is not the first thing to do. References: 1: PMBOK Guide, 7th Edition, Section 13.1.3.1, Stakeholder Engagement Plan 2: PMBOK Guide, 7th Edition, Section 13.2.2.4, Communication Requirements Analysis

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, 7th edition, one of the agile principles is to “prioritize work that delivers the most value”. This means that the project manager should help the team and the product owner to rank the requirements in order of importance and urgency, rather than using vague categories such as high, medium, and low. A numerical prioritization system, such as the MoSCoW method (Must have, Should have, Could have, Won’t have) or the 100-point method, can help the team to focus on the most valuable features and avoid confusion and ambiguity. This also aligns with the agile value of “responding to change over following a plan”, as the team can adjust the priority of the requirements based on the feedback and changes from the stakeholders. References: PMBOK Guide, 7th edition, page 14, 15, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, …

A hybrid approach combines elements of both predictive (or traditional) and agile methodologies. It’s important for the project manager to ensure that all team members understand and consistently apply the agile tools and techniques defined in the hybrid methodology. This will help the team to work effectively within the new framework and mitigate the risk of delays in project delivery. References: PMBOK Guide, 6th Edition, Section 1.2.3: Project Management Approaches

 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

The project manager should mentor the team to explain agile principles and create a shared understanding. This will help the team to adopt an agile mindset, embrace the values and practices of agile approaches, and collaborate effectively throughout the project. The project manager should also provide feedback, coaching, and support to the team as they learn and apply agile methods. Evaluating the possibility of managing this project using a predictive approach, submitting a change request for a new team, and hiring a functional manager are not appropriate actions to address the situation, as they do not address the root cause of the confusion or help the team to develop agile competencies. References: = PMBOK Guide, 6th edition, pages 18-19, 27-28, 555-556; [Agile Practice Guide], pages 8-9, 13-14, 27-28; PMP Exam Content Outline, 2020, pages 6-7.

The best way to resolve any stakeholder issues is to communicate with them directly and openly. Setting up a meeting with the stakeholder will allow the project manager to understand their expectations, needs, and concerns, and to negotiate a mutually acceptable solution. Moving to a predictive approach, talking to the team separately, or scheduling a team retrospective will not address the root cause of the problem, which is the stakeholder’s dissatisfaction with the product concept. Moreover, these options may create more confusion, conflict, or delay in the project. References:

PMBOK® Guide, 6th edition, page 518: “The project manager should proactively and regularly engage with stakeholders to understand their needs and expectations, address issues as they occur, manage conflicting interests, and foster appropriate stakeholder engagement in project decisions and activities.”

PMI-PBA® Guide, 1st edition, page 35: “The business analyst should communicate with stakeholders to elicit, analyze, and validate their needs and expectations, and to facilitate collaboration and consensus-building.”

A hybrid approach in project management is a technique that combines elements from different project management frameworks, such as waterfall and agile, to tailor the methodology to best suit the project at hand12. By merging various methods, organizations can capitalize on the strengths of each approach while mitigating their weaknesses3. A hybrid approach allows for a more detailed and nuanced approach to the work, and requires the project manager to facilitate the collaboration and communication among the team members45. Therefore, the best option for the project manager in this scenario is to facilitate the discussion so that the team members can reach a consensus on the comparative size of the backlog items and if they would fit into the next sprint. This way, the project manager can ensure that the team is aligned on the approach, the customer needs are met, and the project goals are achieved.

The question is about a project team that is distributed across two countries with a significant time difference. The project manager needs to improve the interactions and collaboration between the team members in both locations. The best option for the project manager to do this is:

Identify virtual communication methods and arrange for regular team meetings accordingly: This option is effective and feasible in managing a geographically dispersed team. The project manager should identify the appropriate communication methods and tools, such as email, phone, video conferencing, instant messaging, etc., that suit the needs and preferences of the team members. The project manager should also arrange for regular team meetings, such as daily stand-ups, weekly status updates, monthly reviews, etc., that accommodate the time zones and schedules of the team members. The project manager should ensure that the team meetings are well-planned, structured, and facilitated, and that they foster trust, feedback, and engagement among the team members12

The other options are not as effective or feasible as the first option. They are:

Ensure full participation of both the product owner and business SMEs in scope planning sessions: This option is relevant and desirable, but it is not sufficient to improve the interactions between the team members in both countries. The scope planning sessions are only one aspect of the project communication, and they might not occur frequently or regularly. The project manager should also consider other communication methods and events that involve the entire team and address their needs and expectations3

Explore the opportunity to have both teams colocated: This option is ideal but unrealistic. Colocation is the physical proximity of the team members in the same location, which can enhance communication, collaboration, and performance. However, colocation is not always possible or practical, especially for teams that are distributed across different countries. The project manager should consider the costs, benefits, and feasibility of colocation, and weigh them against the alternatives1

Plan for frequent face-to-face meetings: This option is beneficial but costly. Face-to-face meetings are the most effective form of communication, as they allow for direct interaction, non-verbal cues, and rapport building. However, face-to-face meetings are also the most expensive and time-consuming, especially for teams that are located in different countries. The project manager should balance the frequency and duration of face-to-face meetings with the budget and schedule constraints, and complement them with other communication methods and tools1

 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 10, Section 10.1.2.1 2: Business Analysis for Practitioners: A Practice Guide, Chapter 8, Section 8.3.1 3: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 5, Section 5.2.2.1 : Business Analysis for Practitioners: A Practice Guide, Chapter 4, Section 4.2.1 : A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 9, Section 9.1.2.1 : Business Analysis for Practitioners: A Practice Guide, Chapter 8, Section 8.3.2

 In the scenario described, the project team is overwhelmed by the volume of knowledge-sharing emails, which indicates that the current method of communication is not effective. A pull communication method allows team members to access information as needed, rather than being bombarded with emails. This method enables team members to manage their time and resources more effectively by seeking out knowledge when it is convenient for them, thus reducing the overload and improving the manageability of information.

 The servant leader approach is the most effective for empowering team members and facilitating collaboration. This approach focuses on the growth and well-being of people and the communities to which they belong. The servant leader shares power, puts the needs of others first, and helps people develop and perform as highly as possible. This is in line with the PMBOK guide’s principles of project leadership and team management, which emphasize the importance of servant leadership in project management1.

The PMBOK® Guide and the PMP Examination Content Outline discuss the role of the project manager in leading teams and the importance of servant leadership in project management2. The Professional in Business Analysis Reference Materials also highlight the significance of leadership approaches that focus on collaboration and empowerment3.

The best way to ensure that the client is effectively represented in the daily meetings is to provide them with the necessary agile knowledge and skills to participate and collaborate with the vendor team. This can be done by proposing a session for essential agile knowledge transfer, where the vendor project manager can explain the agile principles, values, practices, and tools that will be used in the project. This will help the client team to understand the purpose and benefits of the daily meetings, as well as their roles and responsibilities in them. The other options are not as effective as they either do not address the root cause of the problem (lack of agile knowledge), or they introduce unnecessary changes or delays to the project (realigning the project or recommending training programs). References: PMI Agile Practice Guide, page 14-15; PMBOK Guide, page 18-19

 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

According to the PMBOK Guide, agile project management is an iterative and incremental approach that delivers value to stakeholders frequently and continuously throughout the project. The product owner is responsible for defining and prioritizing the product backlog, which is a list of features and requirements that deliver value to the customer. The project manager should facilitate sprint planning sessions with the product owner and the development team to select the most valuable and feasible items from the product backlog and define the minimum viable product (MVP), which is the smallest version of the product that can be released to validate the customer needs and assumptions. This way, the project manager can align the project activities with the product owner’s interest in having features released during product development over having the product completed in one year. Designing metrics, promoting a productive environment, and creating a reward system are also important aspects of agile project management, but they are not directly related to the product owner’s interest in this question. References:

PMBOK Guide, 7th edition, pages 26-27, 31-32, 36-37, 40-41

PMI-PBA Guide, 2nd edition, pages 25-26, 30-31, 35-36, 40-41

According to the PMBOK Guide, a project manager should recommend to the sponsor to review the results of the team’s supplier evaluation, when faced with the situation of the sponsor requesting to add another supplier who has lower costs but does not always fulfill the project requirements. This is part of the conduct procurements process, which involves obtaining seller responses, selecting a seller, and awarding a contract. The project team should evaluate the potential suppliers based on the source selection criteria, which are the factors used to rate or score seller proposals. The source selection criteria may include cost, quality, technical capability, schedule, risk, references, etc. The project manager should communicate the results of the supplier evaluation to the sponsor and other relevant stakeholders, and explain the rationale behind the team’s preferred suppliers. The project manager should also highlight the risks and trade-offs of choosing a lower-cost supplier who may not meet the project requirements. The project manager should seek the sponsor’s approval and support for the team’s decision, and address any concerns or objections that the sponsor may have. This approach ensures a transparent and objective process for selecting a supplier, and avoids potential conflicts or misunderstandings between the team and the sponsor. References: PMBOK Guide, 6th edition, pages 479-480, 485-486.

According to the PMBOK® Guide, a project manager should be able to lead and support the team in adapting to the changing environment and emerging opportunities. This includes providing coaching and mentoring to the team members, especially when they are transitioning from a predictive to an agile approach. The project manager should also facilitate team training and development, and foster a positive team culture that embraces agility and collaboration. Creating an agile conduct guideline or providing directions to the team members may not be sufficient or effective in addressing the knowledge gaps and changing the culture. Replacing the key team members with new resources may be disruptive and costly, and may not guarantee the success of the transformation. References: PMBOK® Guide, 6th edition, pages 52-53, 334-335.

The project manager should first become aware of any cultural characteristics of the new supplier that could impact negotiation. This is an important step to ensure effective communication and collaboration with the overseas company, as well as to avoid any misunderstandings or conflicts that could arise from cultural differences. By becoming aware of the new supplier’s cultural values, norms, preferences, and expectations, the project manager can adapt their negotiation style and strategy accordingly, and establish a positive and respectful relationship with the new supplier. This option aligns with the PMBOK Guide, 6th edition, which states that “the project manager should be aware of the cultural characteristics of the parties involved in the negotiation and how they may influence the negotiation process and outcome” (p. 480). The other options are not the best choices because they are not the first steps to proceed with the change. Engaging the services of an interpreter who understands the project domain (option A) may be a useful step to facilitate communication with the new supplier, especially if there is a language barrier, but it is not the first step. The project manager should first understand the cultural aspects of the new supplier before engaging an interpreter, as the interpreter may also need to be aware of the cultural nuances and sensitivities. Checking social media to determine if there are any common connections that use the new supplier (option B) may be a helpful step to gather some information or feedback about the new supplier, but it is not the first step. The project manager should first conduct a more formal and reliable assessment of the new supplier’s cultural characteristics, rather than relying on social media, which may not provide accurate or relevant information. Requesting assistance from the procurement department on the next steps (option C) may be a necessary step to proceed with the change, but it is not the first step. The project manager should first prepare themselves for the negotiation with the new supplier by becoming aware of their cultural characteristics, before seeking assistance from the procurement department on the contractual and legal aspects of the change. References:

PMBOK Guide, 6th edition, p. 480 1

PMBOK Guide, 6th edition, p. 489 2

Probabilistic analysis is a technique that involves considering various possible scenarios and their associated probabilities to develop a budget that accounts for future uncertainties. This method is a common practice in project management to address the inherent risks and uncertainties in project budgets. It allows for a more comprehensive and realistic approach to budgeting, particularly in the face of uncertainties1.

According to the PMBOK Guide, a project manager should ensure that the project team applies a long-term solution for an issue that has been resolved during the project life cycle, to prevent it from reoccurring after the project closure. This is part of the control quality process, which involves monitoring and recording the results of quality activities, and implementing corrective actions to address any quality issues. A long-term solution is one that addresses the root cause of the issue and eliminates or reduces the probability of its recurrence. A short-term solution is one that provides a temporary fix or workaround for the issue, but does not resolve the underlying problem. A short-term solution may be acceptable in some situations, but it may also create additional risks or costs in the future. Therefore, a project manager should always consider the long-term implications of any solution and choose the one that best meets the project objectives and stakeholder expectations. References: PMBOK Guide, 6th edition, pages 293-294, 303-304.

According to the PMBOK Guide, project managers should apply adaptive planning and agile practices to respond to changes and uncertainties in complex projects. Adaptive planning involves frequent reviews and adjustments of the project scope, schedule, cost, and quality based on the feedback and learning from the project execution. Agile practices emphasize delivering value to the customer by prioritizing the most important features and requirements and delivering them in increments1.

In this scenario, the project manager faces a situation where one feature cannot be fixed before the go-live date, which impacts the project schedule and quality. The project manager should apply adaptive planning and agile practices to determine the best course of action. The project manager should evaluate the value and importance of the feature to the customer and the project objectives. If the feature is not critical or essential, the project manager should consider delivering the project without the feature and fixing the defects later, after the go-live milestone. This way, the project can still deliver value to the customer and meet the expectations of the stakeholders. The project manager should communicate this decision to the customer and the stakeholders and obtain their agreement and feedback1.

The other options are not as suitable as option D. Option A involves updating the risk management plan and including additional mitigation actions against the feature defects. However, this option does not address the impact on the go-live milestone or the customer value. It also assumes that the feature defects can be mitigated, which contradicts the premise of the question. Option B involves assessing the relevance of the feature and submitting a change request to descope it. However, this option does not consider the customer value or the feedback from the customer and the stakeholders. It also implies that the feature is not important or valuable, which may not be the case. Option C involves improving the control quality process by implementing additional testing to minimize the defects before the go-live milestone. However, this option does not acknowledge the fact that there is no way to resolve the defects before the go-live date, as stated in the question. It also does not consider the impact on the project schedule and cost, or the customer value1.

 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 next review the quality management plan. The quality management plan is a component of the project management plan that describes how the project team will implement the quality policy and satisfy the quality requirements for the project and its deliverables1. It includes the quality standards, quality objectives, quality roles and responsibilities, quality tools and techniques, quality metrics, quality audits, and quality control and validation activities1. By reviewing the quality management plan, the project manager can identify the root cause of the quality issues, determine the corrective and preventive actions, and ensure the compliance with the quality expectations of the key stakeholder.

Option A is not the best answer because reviewing the stakeholder engagement plan is not the next thing to do. The stakeholder engagement plan is a component of the project management plan that identifies the strategies and actions required to promote productive involvement of stakeholders in project decisions and execution2. It is important to review and update the stakeholder engagement plan throughout the project, but it is not the priority when the deliverables are not functioning as expected.

Option C is not the best answer because reviewing the requirements traceability matrix is not the next thing to do. The requirements traceability matrix is a project document that links the project requirements to their origin and tracks them throughout the project life cycle3. It helps to ensure that each requirement adds business value and is aligned with the project objectives. It is useful to review the requirements traceability matrix during the project planning and monitoring, but it is not the main focus when the deliverables are not meeting the quality standards.

Option D is not the best answer because reviewing the work breakdown structure (WBS) is not the next thing to do. The WBS is a project document that decomposes the project scope into smaller, more manageable components called work packages4. It defines and organizes the project work and deliverables. It is helpful to review the WBS during the project planning and execution, but it is not the most relevant document when the deliverables are not functioning as expected. References: 1: PMBOK Guide, 7th Edition, Section 8.1.3.1, Quality Management Plan 2: PMBOK Guide, 7th Edition, Section 13.1.3.1, Stakeholder Engagement Plan 3: PMBOK Guide, 7th Edition, Section 5.2.3.1, Requirements Traceability Matrix 4: PMBOK Guide, 7th Edition, Section 5.4.3.1, Work Breakdown Structure

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

According to the PMBOK Guide, 7th edition, the project success criteria and objectives are the measurable terms that define what the project is intended to achieve. They are usually defined by the customer or sponsor, and agreed upon by the project manager and other stakeholders. They provide the basis for project planning, monitoring, and evaluation. Therefore, the project manager should understand the project success criteria and objectives first, before performing any other actions, to ensure that the project is aligned with the customer’s or sponsor’s expectations and requirements. The project success criteria and objectives are typically documented in the project charter, which is the key output of the Develop Project Charter process. The project charter also contains other information, such as the project purpose, scope, assumptions, constraints, risks, and stakeholders, that the project manager should review and understand. References:

PMBOK Guide, 7th edition, page 33, section 1.3.2, Project Success

PMBOK Guide, 7th edition, page 34, section 1.3.3, Project Success Criteria and Objectives

PMBOK Guide, 7th edition, page 35, section 1.3.4, Project Success Measures

PMBOK Guide, 7th edition, page 37, section 1.4.1, Develop Project Charter

PMBOK Guide, 7th edition, page 38, section 1.4.1.3, Project Charter

According to the Professional in Business Analysis Reference Materials, the project manager should manage the team members’ expectations and ensure that they adhere to the agreements made during the meetings. The project manager should also communicate clearly and respectfully with the team member who is complaining and explain the rationale behind the agreement and the consequences of not following it. The project manager should not arrange or schedule another meeting to revisit the agreement, as this would waste time and resources and undermine the authority of the project manager. The project manager should also not ignore the team member’s behavior, as this could lead to further conflicts and dissatisfaction1 References: 1 Free PMP Questions and Answers – Are You Ready for PMP Exam1

The project manager should first document the client’s responsibility for the integration with the security subsystem as part of the project scope statement. This will help to define the boundaries of the project and clarify the roles and responsibilities of the project team and the client. It will also help to avoid scope creep and manage expectations. Planning the implementation, recording the issue, and informing the client are actions that can be done later, after the scope is clearly defined and agreed upon. References:

PMP Exam Content Outline, Domain II: Process, Task 1: Execute project with the urgency required to deliver business value.

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 5: Project Scope Management, Section 5.3: Define Scope, Page 154.

According to the Agile Practice Guide, one of the principles of agile project management is to "build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done."1 Therefore, the project manager should not ignore, punish, or override the team member who has a different opinion, but rather try to understand their perspective and work with them to reach a consensus. This can foster a positive team culture and improve the quality of the sprint goals. References: 1: Agile Practice Guide, page 10.

 The question is about an agile project, where the team works in iterations or sprints to deliver incremental value to the customer. In such a project, the project manager needs to monitor the team’s performance and knowledge gaps regularly and provide feedback and support. Two project events that can help the project manager to do this are:

Retrospective: This is a meeting held at the end of each sprint, where the team reflects on what went well, what went wrong, and what can be improved in the next sprint. The retrospective allows the team to identify and address any issues or impediments that affect their work, including knowledge gaps. The project manager can facilitate the retrospective and help the team to find solutions or resources to fill the knowledge gaps12

Backlog refinement: This is a process of reviewing and updating the product backlog, which is a prioritized list of features or requirements that the team needs to deliver. The backlog refinement helps the team to clarify and decompose the requirements, estimate the effort and complexity, and plan the upcoming sprints. The project manager can participate in the backlog refinement and help the team to understand the requirements and resolve any ambiguities or uncertainties13

The other options are not as relevant or effective as the retrospective and backlog refinement for the purpose of the question. Requirements analysis is a process of eliciting, analyzing, and validating the requirements, which is usually done before the project starts or during the initiation phase. It is not a specific event that occurs regularly during an agile project4 Sprint planning is a meeting held at the beginning of each sprint, where the team selects the requirements from the product backlog and commits to deliver them within the sprint. It is not a suitable event to assess the team’s knowledge gaps, as it focuses on the scope and schedule of the sprint1 Standup is a daily meeting where the team members share their progress, plans, and problems. It is a useful event to monitor the team’s work and identify any blockers, but it is not enough to address the team’s knowledge gaps, as it is usually brief and focused on the current tasks1

 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 6, Section 6.3.2.2 2: PMI Agile Practice Guide, Chapter 5, Section 5.2.3 3: PMI Agile Practice Guide, Chapter 5, Section 5.2.2 4: Business Analysis for Practitioners: A Practice Guide, Chapter 3, Section 3.1

 The project manager should develop an integrated change management plan to control the situation, as this will help to establish a clear and consistent process for managing and approving change requests throughout the project. An integrated change management plan defines the roles and responsibilities of the change control board (CCB), the criteria and procedures for evaluating and approving change requests, the tools and techniques for tracking and reporting change requests, and the impact of change requests on the project baselines and other project documents. By developing an integrated change management plan, the project manager can ensure that the change request process is transparent, efficient, and aligned with the project objectives and stakeholder expectations. Redefining the communications management plan may not be sufficient, as it only addresses the information needs and communication methods of the project stakeholders, but not the change request process itself. Documenting the risk in the project risk register may not be relevant, as the question does not indicate that the change request process poses a risk to the project. Reviewing the scope defined in the project charter may not be helpful, as it only provides a high-level overview of the project scope, but not the details of the change request process. References: PMBOK Guide, 7th edition, pages 123, 124, 125, 126.

nager should also help the stakeholders understand how the agile principles and practices affect the project’s reporting and metrics2. The project manager should explain that agile reporting focuses on delivering value, responding to change, and satisfying customer needs3. The project manager should also collaborate with the stakeholders to identify the most relevant and meaningful reports and KPIs for the agile project, such as velocity, burn-up or burn-down charts, sprint or product backlog, and customer feedback. References:

1: PMBOK® Guide, 6th edition, section 10.1.3.1

2: PMBOK® Guide, 6th edition, section 1.2.3

3: PMBOK® Guide, 6th edition, section 1.2.2

PMBOK® Guide, 6th edition, section 1.2.4

The project manager should review the user roles and update the team charter to ensure that the project team members have clear and balanced responsibilities and expectations for each release. This will help to improve the team performance, collaboration, and accountability. Documenting the risk register, speaking to the customer, and involving the product owner are not directly related to the problem of uneven workload distribution among the team members. References:

PMP Exam Content Outline, Domain II: Process, Task 2: Manage project artifacts and ensure they meet the needs and expectations of key stakeholders.

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 9: Project Resource Management, Section 9.1: Plan Resource Management, Page 313.

Professional in Business Analysis (PBA) Certification Exam Outline, Domain III: Analysis, Task 3: Define Requirements Architecture, Page 13.

According to best practices in project management, it is essential for the project manager to enforce the terms of the contract. If the updated schedule is a condition for milestone payment, the subcontractor is obligated to provide it, regardless of any verbal agreements with the client. The project manager should inform the subcontractor that in order to comply with the contract and process the payment, the updated schedule must be submitted. This ensures that all contractual obligations are met and that there is a clear record of the work completed, which is necessary for project tracking, reporting, and auditing purposes.

The answer is verified based on the principles found within the PMBOK® Guide and the standards of project management as outlined by the Project Management Institute (PMI). The PMBOK® Guide emphasizes the importance of contract management and the need for proper documentation and adherence to agreed-upon project schedules. Additionally, the Professional in Business Analysis (PMI-PBA) materials highlight the significance of maintaining accurate records and documentation for business analysis and project management activities.

 According to the PMBOK® Guide, the project vision is a high-level description of the project’s purpose, scope, and objectives. It provides the direction and alignment for the project team and stakeholders. The project vision should be clear, concise, inspiring, and consistent with the organization’s strategy. When the scope has changed significantly and the product owner has been replaced multiple times, the project vision may become unclear or outdated. The team members may feel disassociated from the project and lose motivation and engagement. To ensure team alignment with the goals, the project manager should facilitate a discussion of the vision for the project, involving the new product owner and the team members. This will help to clarify the project’s value proposition, expected outcomes, and success criteria. It will also help to reestablish trust, collaboration, and commitment among the team and the product owner. Asking the new product owner to explain the importance of the project, emailing the team a detailed outline of the business requirements, or reviewing the project charter with the team are not sufficient or effective ways to ensure team alignment with the goals. These options may not address the underlying issues of the team’s disassociation, such as lack of involvement, ownership, or empowerment. They may also not reflect the current state of the project or the organization’s strategy. References: PMBOK® Guide, 6th edition, pages 30-31, 89-90.