PMI PMP Dumps

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

• PMBOK Guide, 6th edition, pages 33, 89, 123, 126, 129, 686
• PMI-PBA Guide, pages 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53…

 According to the PMBOK Guide, the project manager is responsible for managing the project work according to the project management plan and implementing approved changes1. If the project manager discovers that the blueprints received from the client appear incomplete, the first thing to do is to consult with the client to determine if project execution should be continued or if changes are needed. The client is the source of the project requirements and the ultimate authority on the project scope2. The other options are not the best actions for the project manager to do first. Rescheduling the project execution date is a change that requires a formal change request and approval from the change control board3. Continuing project execution using the current blueprints from the client may result in rework, waste, or defects if the blueprints are not accurate or complete4. Escalating this issue to the project sponsor is not the first step, as the project sponsor is not the owner of the project requirements or scope. References:

• 1: PMBOK Guide, 6th edition, page 95
• 2: PMBOK Guide, 6th edition, page 141
• 3: PMBOK Guide, 6th edition, page 115
• 4: PMBOK Guide, 6th edition, page 149
• : PMBOK Guide, 6th edition, page 33

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

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

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

References:

• PMBOK Guide, 6th edition, pages 141-142, 161-162, 171-172
• PMP Exam Questions - Part 17 (Q 161-170), YouTube video by Certify Me Now
• [PMP Exam Prep: 100% Coverage for PMP Exam Success], Udemy course by Joseph Phillips

According to the PMBOK Guide, the project manager should use a participatory approach to develop the project schedule, involving the team members who will perform the work1. This will increase the accuracy and reliability of the schedule estimates, as well as the commitment and ownership of the team2. Therefore, the best option is to organize a planning session with the development team and use their estimations to complete the schedule. Option B is incorrect because changing the delivery date for the project schedule based on the availability of a new contractor may not be feasible or acceptable to the stakeholders. Option C is incorrect because asking the sponsor to provide the desired completion date for project activities may not reflect the realistic effort and duration required to complete the work. Option D is incorrect because using expert judgment to estimate all of the tasks may not account for the variability and uncertainty of the work, and may not involve the input and feedback of the team members. References: 1: PMBOK Guide, 6th edition, section 6.1.2.5, p. 191 2: PMBOK Guide, 6th edition, section 6.5.2.4, p. 218

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

 The stakeholder engagement plan is a subsidiary plan of the project management plan that identifies the strategies and actions required to promote productive involvement of stakeholders in project decisions and execution. It is a dynamic document that should be updated throughout the project as stakeholder needs and expectations change. The project manager should explain to the key stakeholder that their needs will be updated in the stakeholder engagement plan and that their continued participation is important for the project success. References: PMBOK Guide, 7th edition, section 13.2.3.1; Professional in Business Analysis (PMI-PBA) Guide, 2nd edition, section 4.2.3.1.

The stakeholder engagement plan and communication strategy are two key documents that guide the project manager in managing stakeholder expectations and interactions. The project manager should review these documents to identify the level of interest and influence of the stakeholder from the legal department, and determine the best way to communicate and involve them in the project. Escalating the issue to the project sponsor may not be necessary or appropriate at this stage, as the stakeholder may not be critical for the project success. Engaging the stakeholder and ensuring all requirements are captured may not be feasible or effective, as the stakeholder may not have any input or interest in the product design. Reviewing the product requirements and updating the stakeholder register may not address the root cause of the stakeholder’s lack of participation, as these documents do not specify how to engage and communicate with the stakeholder. References:

• A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 13: Stakeholder Engagement, Section 13.2: Plan Stakeholder Engagement, Section 13.3: Manage Stakeholder Engagement, Section 13.4: Monitor Stakeholder Engagement
• Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 2: Planning, Task 5: Plan Stakeholder Engagement
• Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain 2: Planning, Task 5: Plan Stakeholder Engagement

According to the PMBOK Guide, a project manager is responsible for leading and motivating the project team and ensuring their engagement with the project. A project manager should create an environment that encourages leadership, translates ambitions into growth opportunities, and rewards overtime workers when working with a project team composed of recent university graduates. This will help to inspire, empower, and recognize the team members, and to align their personal and professional goals with the project objectives. Creating an environment that encourages leadership, translates ambitions into growth opportunities, and rewards overtime workers is the best action that the project manager should take in this situation. Providing clear direction on the work to be done and its alignment to the major objectives of the organization, using technology to communicate (A) may be a necessary action, but not sufficient to ensure the team’s engagement, as it may not address their needs, interests, and expectations. Establishing a clear hierarchical environment and allowing them to navigate through the project faster using social networks (B) may not be effective or appropriate, as it may create a rigid or bureaucratic structure, and undermine the team’s collaboration and communication. Fostering proactive decision making and developing a hierarchy to approve decisions based on different levels of complexity © may be a good practice, but not the best one, as it may not create a conducive environment for the team’s development and growth. References: PMBOK Guide, 6th edition, pages 349-350, 361-362.

 A change log is a document that contains the list of changes that are made during the project. It tracks the progress of each change based on its review, approval, implementation, and closure. A change log is a useful tool for communicating the status of change requests to the stakeholders, as it shows the impact and outcome of each change. A risk log, a backlog, and an issue log are different documents that serve different purposes. A risk log records the identified risks, their probability, impact, and response strategies. A backlog is a list of features or tasks that need to be completed in an agile project. An issue log records the issues that arise during the project, their causes, effects, and resolution. References:

• Change Log - Project Management Knowledge
• Change Log Template - Project Management Docs
• Risks, issues, and changes–help, I’m drowning in logs!

According to the PMBOK Guide, 6th edition, one of the key processes of the Project Integration Management knowledge area is Close Project or Phase, which involves finalizing all activities across all of the project management process groups to formally complete the project or phase. One of the tools and techniques for this process is benefits transition, which involves transferring the ownership of the project’s benefits to the assigned business owner or sponsor, who will be responsible for sustaining and enhancing the value of the project outcomes. By confirming ownership for ongoing value realization, the project manager can ensure that the project team members understand the benefits of the project features and how they will be measured and monitored after the project closure. References: PMBOK Guide, 6th edition, pages 123-124, 129.

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

• PMBOK Guide, 6th edition, page 18, section 1.2.3.2
• Agile Practice Guide, page 36, section 3.3.2
• PMI-PBA Exam Content Outline, page 9, task 1.1
• PMI-PBA Certification Exam Prep Guide, page 63, section 3.2.1

The project manager should implement a project management information system (PMIS) to avoid this situation in the future. A PMIS is a system that provides the tools and techniques to gather, integrate, and disseminate the outputs of project management processes. A PMIS can help the project manager and the team to manage the project documents, such as the requirements document, and ensure that they are updated, controlled, and shared in a timely and consistent manner. A PMIS can also facilitate collaboration and communication among the project team and other stakeholders, and reduce the risk of errors, conflicts, and rework. Encouraging better team communication by positioning team members closer together may not be enough, as it does not address the issue of document management and version control. Updating the communications management plan to ensure correct delivery of the latest version may not be effective, as it does not provide the tools and techniques to implement the plan. Restricting team members from sending the requirements documents via email may not be feasible or appropriate, as it may limit the flexibility and accessibility of the project information. References:

• A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 4: Integration, Section 4.4: Manage Project Knowledge, Section 4.5: Monitor and Control Project Work
• Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 2: Planning, Task 6: Plan Business Analysis Information Management
• Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain 2: Planning, Task 6: Plan Business Analysis Information Management

 The project manager should share the organization’s decision with the team and make plans to adopt an agile approach in the upcoming project because this is the best way to align the team with the new direction and prepare them for the change. Agile approaches are based on values and principles that emphasize collaboration, flexibility, and customer satisfaction, which may differ from the traditional predictive methods that the team is used to. Therefore, the project manager should communicate the rationale and benefits of the agile approach, and involve the team in planning and executing the project using agile practices and tools. The other options are not the best choices because they do not support the organization’s decision or the project sponsor’s preference. Preparing a risk report that captures the probability and impact of risks, and then sharing it with the project sponsor (option A) may imply that the project manager is resistant or skeptical about the agile approach, and may not address the team’s readiness or capability. Making a request to human resources for new team members who have agile experience (option C) may undermine the existing team’s skills and motivation, and may not be feasible or necessary. Asking the project sponsor to change the approach back to predictive as that is the team’s strength (option D) may contradict the organization’s strategy and the project sponsor’s authority, and may not reflect the project manager’s willingness to learn and adapt. References: PMBOK Guide, 6th edition, pages 18-19, 686-687. Exam PMP topic 1 question 434 discussion. Episode 434: The PMP® Exam is Changing on 1 July 2020.

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

According to the PMBOK Guide, a change request is a formal proposal to modify any document, deliverable, or baseline. Change requests are processed through the Perform Integrated Change Control process, which involves reviewing, analyzing, approving, or rejecting changes. The project manager should follow the change management process and work with procurement if needed to deal with the new requirement from the key stakeholder. The project manager should assess the impact of the change on the project scope, schedule, cost, quality, risk, and other aspects, and obtain approval from the appropriate authority before implementing the change. The project manager should also communicate the change to the subcontracting company and negotiate any contractual modifications if necessary. The project manager should not engage an arbitrator, add the change to the next sprint, or allocate resources to work on the new feature immediately, as these actions may bypass the change management process, create conflicts, or disrupt the project plan. References:

• PMBOK Guide, 6th edition, pages 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153…
• PMI-PBA Guide, pages 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53…

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

• 1: PMBOK guide, page 207
• 2: PMBOK guide, page 286
• 3: PMI-PBA guide, page 131

 The project manager should plan for incremental and iterative delivery based on feedback from the marketing and sales team because this is an example of adaptive development approach, which is suitable for projects with high uncertainty and changing requirements. By delivering value in increments and iterations, the project manager can validate the assumptions and benefits of the project, and adjust the scope and direction as needed. This way, the project manager can address the stakeholders’ concerns and ensure that the project delivers the most efficient and effective sales channels for the organization. References:

• PMBOK® Guide, 6th edition, page 18, section 1.2.3.2
• PMI-PBA Guide, 1st edition, page 13, section 1.3.2.2
• PMP Sample Test Questions, question 1
• Free PMP Practice Exam Questions, question 1
• PMP Questions page 484, question 484

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

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

• PMP Exam Content Outline, Domain I: People, Task 1, page 61
• PBA Exam Content Outline, Domain II: Planning, Task 3, page 102
• A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 13: Project Stakeholder Management, Section 13.2: Plan Stakeholder Engagement, page 5133
• Business Analysis for Practitioners: A Practice Guide, Chapter 4: Needs Assessment, Section 4.2: Identify Stakeholders, page 694

According to the PMBOK Guide, the project manager is responsible for managing the project resources, including materials, and ensuring that they are available and delivered on time. The project manager should also monitor and control the project risks, and implement appropriate responses when they occur. If one important material is still not on site and the delivery date is approaching, the project manager should engage the project team to look for alternatives to find a solution. This means that the project manager should involve the team members who have the relevant expertise, knowledge, and skills to identify and evaluate possible options to overcome the problem, such as using a substitute material, changing the design or scope, or negotiating with the supplier or the client. Engaging the project team to look for alternatives to find a solution will help the project manager to leverage the collective intelligence and creativity of the team, and to find the best solution that meets the project objectives and satisfies the stakeholders. Recording it in the risk register is not a sufficient action, as it does not address the problem or prevent the delay. The project manager should have identified and recorded this risk earlier, and developed a contingency plan to deal with it. Asking the client to help solve the problem is not a good option, as it may damage the relationship and trust between the project manager and the client, and imply that the project manager is not capable of managing the project. The project manager should communicate the problem to the client, but not rely on the client to solve it. Starting procuring this material from another supplier is a risky and costly option, as it may not guarantee the quality, availability, or delivery of the material, and it may incur additional expenses and contractual issues. The project manager should consider this option only after exhausting other alternatives, and with the approval of the relevant stakeholders. References: PMBOK Guide, 6th edition, pages 355-356, 441-442, 456-457.

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

• PMBOK Guide, 6th edition, Chapter 13, Section 13.1
• PMP Exam Content Outline, June 2019, Domain I, Task 2
• PMP Sample Test Questions, Question 382

According to the PMBOK Guide1, project communication management includes the processes of planning, managing, and monitoring project communications. The first process, plan communications management, involves determining the information and communication needs of the project stakeholders, such as the sponsor. The project manager should have analyzed the sponsor’s communication requirements, such as the type, format, frequency, and level of detail of the information they need, as well as their preferred communication channels and methods. By doing so, the project manager could have designed and implemented a communication system that meets the sponsor’s expectations and needs, and avoids any dissatisfaction or complaints. The other options are not the best preventive actions, as they are either reactive or irrelevant. Confirming that the portal is providing adequate information, verifying that the project team is following the communications management plan, and ensuring the sponsor had the necessary skills to use the portal are all actions that could be taken after the situation has occurred, but they do not address the root cause of the problem, which is the lack of alignment between the communication system and the sponsor’s requirements. References:

• A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition
• Project Communication Management - Five Steps | PMI
• ProjectManagement.com - Project Communication Management

The project manager should gather relevant cultural data and engage members in discussions covering their work ethics because this is the best way to avoid uncertainty in the project due to different cultures. Cultural differences can affect the communication, collaboration, and performance of a virtual team, and may lead to misunderstandings, conflicts, or delays. Therefore, the project manager should collect and analyze information about the cultural backgrounds, preferences, and expectations of the team members, and use this data to design and implement appropriate communication and management strategies. The project manager should also facilitate open and respectful dialogue among the team members, and encourage them to share their work values, norms, and practices. This can help to build trust, rapport, and mutual understanding within the team, and foster a positive and productive work environment. The other options are not the best choices because they do not address the root cause of the problem, which is the lack of cultural awareness and sensitivity. Starting the project and adding any uncertainty that arises to the risk register (option A) may be too reactive and insufficient, as it does not prevent or mitigate the potential issues caused by cultural differences. Dissolving the virtual team and building a colocated team (option B) may be impractical or impossible, as it may depend on the availability, budget, and scope of the project. Building a culturally neutral team that will not be affected by cultural differences (option D) may be unrealistic or undesirable, as it may ignore or suppress the diversity and richness of the team members’ cultures, and may also violate the agile principle of valuing individuals and interactions over processes and tools. References: PMBOK Guide, 6th edition, pages 52, 273, 335, 686-687. PMP Questions page 447. PMP Practice Exam | Free PMP Practice Questions.

 This is the best answer because it involves engaging the relevant stakeholders in a constructive dialogue about the importance and benefits of following the project management procedures. According to the PMBOK Guide, project management procedures are part of the organizational process assets that help the project manager and the team to perform their work effectively and efficiently. By initiating a review of the procedures, the project manager can identify the gaps, issues, and opportunities for improvement, as well as communicate the value and rationale of the procedures to the CTO and the team. This can also help to build trust, collaboration, and commitment among the project participants. References: PMBOK Guide, 6th edition, pages 38-39, 541-542.

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

• PMP Exam Content Outline (2021), Domain II: Process, Task 2: Execute project with the urgency required to deliver business value, p. 101
• A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 5: Project Scope Management, Section 5.4.2.1: Product Backlog, p. 1542
• Agile Practice Guide, First Edition, Chapter 2: Life Cycle Selection, Section 2.2.1: Scrum, p. 213
• Professional in Business Analysis (PBA) Examination Content Outline (2018), Domain III: Analysis, Task 1: Elicit Requirements, p. 14

According to the PMBOK Guide, the project management plan is a formal, approved document that defines how the project is executed, monitored, and controlled1. It integrates and consolidates all of the subsidiary plans and baselines from the project management processes1. One of the subsidiary plans is the procurement management plan, which describes how the project will acquire goods and services from outside the performing organization2. The procurement management plan should include the procurement strategy, the types of contracts, the procurement documents, the source selection criteria, the roles and responsibilities, the make-or-buy decisions, and the assumptions and constraints2. Therefore, the project manager should have communicated the project management plan, including the procurement management plan, to the procurement division earlier in the project to ensure the purchase of the specific equipment. The other options are not the best actions for the project manager to have done earlier in the project. Communicating the project charter to the procurement division may not be sufficient, as the project charter only provides the high-level description of the project and its boundaries, not the details of the procurement activities3. Including a procurement division member on the project team may not be necessary or feasible, as the project team may have limited authority or influence over the procurement division’s policies and procedures. Reminding the project sponsor about the procurement division’s reputation is not a constructive or professional way to deal with the issue, as it may create conflict or resentment between the parties. References:

• 1: PMBOK Guide, 6th edition, page 89
• 2: PMBOK Guide, 6th edition, page 463
• 3: PMBOK Guide, 6th edition, page 77
• : PMBOK Guide, 6th edition, page 33
• : PMBOK Guide, 6th edition, page 558

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

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

• PMBOK® Guide, 6th Edition, Section 11.1
• Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Task 3.5

According to the PMBOK® Guide, 7th edition, an issue is a point or matter in question or in dispute, or a point or matter that is not settled and is under discussion or over which there are opposing views or disagreements1. Issues can arise from various sources, such as changes, risks, defects, conflicts, or assumptions1. Issues can affect the project performance, scope, quality, schedule, cost, or stakeholder satisfaction1.

An issues log is a project document used to capture and track issues until they are resolved1. The issues log typically contains information such as the issue description, priority, owner, status, resolution, and impact1. The issues log is updated throughout the project life cycle as new issues are identified, analyzed, and resolved1.

In this scenario, the newly assigned project manager is informed by a few key stakeholders that the project has some serious issues. The first thing that the project manager should do to understand the issues is to review the issues log to ensure the issues are captured. This will help the project manager to get an overview of the current state of the project, and to identify the nature, scope, and impact of the issues. It will also help the project manager to verify if the issues have been properly documented, prioritized, and assigned to the responsible parties. Reviewing the issues log will also enable the project manager to plan the next steps to address the issues, such as communicating with the stakeholders, performing root cause analysis, implementing corrective actions, or escalating the issues if needed1.

The other options are not as effective as option B. Option A, escalating the issues to the project sponsor, may be necessary if the issues are beyond the project manager’s authority or control, but it is not the first thing to do. The project manager should first review the issues log to understand the issues and their implications, and then decide if escalation is required or not. Option C, checking the risk management plan to ensure there is a strategy to address the issues, may be helpful, but it is not sufficient. The risk management plan provides guidance on how to manage risks, not issues2. Risks are uncertain events or conditions that may have a positive or negative effect on the project objectives, while issues are certain events or conditions that have already occurred and have a negative effect on the project performance1. Therefore, the risk management plan may not cover all the issues that the project faces, and the project manager should review the issues log instead. Option D, asking the key stakeholders to discuss the issues with the project team, may be beneficial, but it is not the first thing to do. The project manager should first review the issues log to get a clear picture of the issues, and then facilitate the discussion between the stakeholders and the team to resolve the issues.

References: 1: PMBOK® Guide, 7th edition, page 101 2: PMBOK® Guide, 7th edition, page 113

According to the PMBOK Guide, one of the key principles of agile project management is to deliver value to the customer early and often1. This can be achieved by using an iterative and incremental approach, where the project team delivers working increments of the product at the end of each iteration or sprint2. The project team should also demonstrate the built portion of the product to the stakeholders and obtain their feedback and acceptance3. Therefore, the best option is to include demonstrations of the built portion of the product at the end of every sprint. Option A is incorrect because preparing performance value reports for the business on an ongoing basis may not be the most effective way to illustrate the project business value, as it may not reflect the actual functionality and usability of the product. Option C is incorrect because preparing a project report for the stakeholders and distributing it weekly may not be sufficient or timely to show the progress and value of the product, as it may not include the stakeholder input and validation. Option D is incorrect because confirming the minimum viable product (MVP) and demonstrating it to the business when it is ready may not be consistent with the agile principle of delivering value early and often, as it may delay the stakeholder feedback and satisfaction. References: 1: PMBOK Guide, 6th edition, section 1.2.3, p. 8 2: PMBOK Guide, 6th edition, section 6.2.2.1, p. 177 3: PMBOK Guide, 6th edition, section 6.2.2.4, p. 178

The project management team should review the project plan to evaluate if any updates should be made in response to the news that a competitor has released the latest version of a program. The project plan is a document that describes how the project will be executed, monitored, and controlled. It includes the project scope, schedule, cost, quality, resources, communications, risks, procurements, and stakeholder management plans. The project management team should assess the impact of the competitor’s release on the project’s objectives, deliverables, assumptions, constraints, and risks. The project management team should also consult with the project sponsor, customer, and other key stakeholders to determine their expectations and preferences regarding the project’s scope and quality. The project management team should then decide if any changes or updates are needed to the project plan to ensure the project’s success and value. The project management team should follow the change management process to request, analyze, approve, and implement any changes to the project plan.

The other options are not the best actions for the project management team to take in this situation. Crashing the existing schedule with additional resources to deliver more features may not be feasible or effective, as it may increase the project’s cost, complexity, and risk. It may also not address the customer’s needs or the market’s demand, as the features may not be relevant or valuable. The project management team should not rush to add more features without validating their necessity and feasibility. Stopping the project immediately as the market opportunity has already been missed may be premature and wasteful, as it may disregard the project’s benefits and potential. It may also damage the project’s reputation and stakeholder’s trust. The project management team should not abandon the project without evaluating its viability and value. Continuing with the project plan and target delivery date as expected may be unrealistic and risky, as it may ignore the competitor’s influence and the customer’s feedback. It may also result in delivering a product that is outdated or inferior. The project management team should not proceed with the project plan without reviewing its alignment and suitability. References:

• PMBOK® Guide, 6th Edition, Chapter 4, Section 4.2, “Develop Project Management Plan”
• PMBOK® Guide, 6th Edition, Chapter 4, Section 4.6, “Perform Integrated Change Control”
• PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 4, Section 4.2, “Developing the Project Management Plan” 1

Team velocity is a measure of the amount of work a team can complete in a given time period, usually a sprint or iteration. It is calculated by adding up the story points or effort estimates of the user stories that were completed and accepted during the sprint. Team velocity can help project managers and teams to plan, monitor, and improve their performance and delivery. However, team velocity can vary due to various factors, such as changes in scope, team size, team skills, dependencies, risks, and impediments. Impediments are any issues or obstacles that prevent the team from achieving their goals or performing at their optimal level. Impediments can be internal or external, technical or non-technical, and can affect the team’s productivity, quality, morale, or collaboration. Some examples of impediments are: lack of resources, unclear requirements, technical debt, bugs, conflicts, communication gaps, etc. Therefore, it is important for the project manager and the team to identify, track, and resolve impediments as soon as possible, to avoid negative impacts on the team velocity and the project outcome. One of the best ways to do this is to use the daily standup meeting, which is a short, time-boxed, and focused meeting where the team members share their progress, plans, and problems. The standup meeting can help the project manager and the team to: - Align on the sprint goals and priorities - Monitor the team’s progress and performance - Identify any impediments or risks that are affecting or could affect the team’s velocity - Assign ownership and accountability for resolving the impediments - Collaborate and support each other to overcome the challenges - Adapt and adjust the plan as needed to meet the sprint and project objectives By using the standup meeting to assess impediments and problems, the project manager can help the team to improve their velocity and meet the next review gate goal. The other options are not the best choices, because: - Increasing the sprint duration to allow the team more time would violate the agile principle of delivering value in short and frequent iterations, and would not address the root causes of the low velocity. - Prioritizing the contents of the backlog and removing some stories would reduce the scope and quality of the project, and would not solve the impediments that are affecting the team’s velocity. - Creating a change request to modify the gate review goals would delay the project delivery and increase the cost and risk of the project, and would not improve the team’s performance or velocity. References:

• Velocity Chart in Project Management – What Is It and How Do You Use It?
• What is Velocity in Agile?
• Velocity - Project Management Knowledge
• PMP Questions velocity
• How to Calculate Team Velocity
• What is team velocity and how to calculate it

Retrospective results are the outputs of the retrospective meeting, which is a ceremony that is performed at the end of every sprint or iteration in an agile project. The retrospective meeting is an opportunity for the team to reflect on what went well, what could be improved, and how to implement the improvement actions in the next sprint or iteration. The retrospective results can help the project manager to identify the risks and opportunities for the event planning, and to update the risk register accordingly. 12345 References:

• 1: ProjectManagement.com - Retrospectives
• 2: A Guide To Effective Retrospectives By Project Managers
• 3: Retrospective - BrainBOK
• 4: Retrospective - Lovepmp
• 5: Retrospective - InLoox

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

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

According to the Professional in Business Analysis (PMI-PBA)® Examination Content Outline, one of the tasks of a business analyst is to “facilitate conflict resolution within the team to ensure that team members work effectively together” (Task 5.4). This implies that the project manager should also address any interpersonal issues that may affect the team performance and morale. By setting up a meeting with the distracted team member, the project manager can show empathy, listen to their concerns, and help them resolve any problems they may have. This is also consistent with the PMBOK® Guide, which states that “the project manager should manage conflict in a constructive manner, and help to develop a collaborative project team environment” (Section 9.4.2.3). References:

• Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Task 5.4
• PMBOK® Guide, 6th Edition, Section 9.4.2.3

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

• PMBOK Guide, 6th edition, Chapter 9, Section 9.3
• PMP Exam Content Outline, June 2019, Domain III, Task 9
• PMP Sample Test Questions, Question 186

The project manager should always monitor and control the project schedule and make adjustments as needed to ensure timely completion of the project. If the project manager identifies that some activities can be done faster by other resources, they should review the work allocation and reassign some tasks to shorten the critical path. The critical path is the longest sequence of activities that determines the project duration. By reducing the duration of the critical path activities, the project manager can avoid delays and meet the project deadline. This is also consistent with the principle of optimizing resources and minimizing waste, which is part of the PMI Talent Triangle®. References:

• PMBOK Guide 7th Edition, page 131
• Agile Practice Guide, page 50
• PMI Talent Triangle® 1

According to the PMBOK Guide, the project manager should be involved in the procurement process to ensure that the project requirements are clearly defined and communicated to the potential suppliers1. The project manager should also verify that the project objectives are aligned with the business needs and the expectations of the stakeholders before approving an agreement2. Therefore, the best option is to ensure that the requirements for the project are understood and that the objectives are verified before approval of an agreement. Option B is incorrect because informing the project sponsor that there cannot be any changes to the scope of the project is unrealistic and may not account for the possible risks and uncertainties that may arise during the project execution3. Option C is incorrect because notifying the project sponsor that the project manager cannot be involved in the agreement negotiation process is not a proactive or collaborative approach, and may result in a poor or unsuitable agreement for the project. Option D is incorrect because asking the project sponsor to involve the legal department in the negotiation for the project agreement is not the responsibility of the project manager, and may not address the issue of the project manager’s participation in the procurement process. References: 1: PMBOK Guide, 6th edition, section 12.1.3.1, p. 465 2: PMBOK Guide, 6th edition, section 4.1.3.1, p. 89 3: PMBOK Guide, 6th edition, section 5.6.3.1, p. 161 : PMBOK Guide, 6th edition, section 12.2.3.1, p. 473 : PMBOK Guide, 6th edition, section 12.2.3.2, p. 474

According to the PMBOK® Guide Seventh Edition, one of the agile practices that can be used in a predictive environment is incremental delivery. This means that the project delivers value to the customer or end user in small increments throughout the project life cycle, rather than waiting until the end of the project to deliver the final product. Incremental delivery allows the project to respond to changing requirements, reduce risks, and increase customer satisfaction. To support incremental delivery, the project manager should also perform frequent backlog refinement, which is the process of reviewing, prioritizing, and updating the list of features or requirements that the project team will work on. Backlog refinement helps the project manager and the team to align their work with the customer’s needs and expectations, and to adjust the scope and schedule accordingly. References:

• PMBOK® Guide Seventh Edition, page 29
• Agile Practice Guide, page 13

 According to the PMBOK Guide, the project manager should follow the change management process to handle any change request, regardless of the source or nature of the change. The change management process involves identifying, analyzing, documenting, presenting, deciding, communicating, and implementing the change request. The first step in this process is to validate the proposed change’s impact on the project, which means assessing how the change would affect the project scope, schedule, cost, quality, risk, and other aspects. This would help the project manager to determine the feasibility, desirability, and priority of the change request, and to prepare a recommendation for the change control board (CCB). The project manager should not check the budget, accept, or refuse the change request without validating its impact first, as these actions would bypass the change management process and could lead to negative consequences for the project. References:

• PMBOK Guide’s Change Management Process For PMP Exam
• Change Management Process for Project
• Managing Change in Organizations: A Practice Guide

According to the PMBOK Guide, the project manager should use a collaborative or problem-solving approach to handle conflicts, as it results in a win-win situation and enhances the project performance1. The project manager should also communicate with the team members and involve them in the decision-making process, as it fosters trust and commitment2. Therefore, the best option is to meet the team member and try to plan a course of action together. Option A is incorrect because guiding the team member on how to resolve the conflict may not address the root cause of the conflict or the impact on the project schedule. Option B is incorrect because analyzing the project schedule and looking for alternatives may not consider the team member’s perspective or input. Option C is incorrect because performing crashing and/or fast tracking of the schedule may not resolve the conflict or may introduce new risks or issues to the project. References: 1: PMBOK Guide, 6th edition, section 9.5.2.1, p. 363 2: PMBOK Guide, 6th edition, section 9.4.2.3, p. 356

According to the PMBOK Guide, scope management in agile projects is different from scope management in predictive life cycle projects. In agile projects, the scope is not fixed or detailed at the beginning of the project, but rather it is progressively elaborated and refined throughout the project. Agile projects use an adaptive and iterative approach to deliver value to the customer in short and frequent increments, called sprints or iterations. Agile projects use techniques such as user stories, product backlog, story mapping, story points, and minimum viable product (MVP) to define, prioritize, estimate, and validate the scope. Therefore, the project manager should spend a short amount of time defining the scope and building prototypes to refine the requirements, rather than creating a detailed scope baseline or a rigid plan. By doing so, the project manager can:

• Involve the customer and the team in defining and clarifying the scope
• Incorporate feedback and changes quickly and easily
• Deliver the most valuable features and functionalities first
• Reduce waste and rework
• Increase customer satisfaction and trust

The other options are not the best choices, because:

• Creating a scope baseline and putting the rest as backlog activities would limit the flexibility and responsiveness of the project, and would not allow the scope to evolve based on customer needs and feedback.
• Estimating the work the team can complete and defining story sizes to keep the project under control would be part of the scope management process, but not the only or the best way to manage and control the scope. The project manager should also prioritize, validate, and adjust the scope as the project progresses.
• Developing a plan to complete more work in less time would not be realistic or sustainable, and would compromise the quality and value of the project. The project manager should focus on delivering the right work, not more work. References:
• Scope Management | PMI
• Agile Scope Management: Refactor Your PMP - LeadingAgile
• Considerations for Agile/Adaptive Projects | PMP - GreyCampus

According to the PMBOK Guide, an iteration is a fixed time period during which a set of activities are performed to deliver a potentially releasable product increment. In an agile or hybrid environment, the project manager should encourage the team to continuously inspect and adapt their processes and practices to improve their performance and deliver value to the customer. If a team member suggests a new method of doing things that provides no value to the end customer, but may help the team to work more efficiently, the project manager should consider the change because it will help the team work more efficiently. This means that the project manager should evaluate the benefits and costs of the proposed change, and determine if it is worth implementing. The project manager should also consult with the team and the product owner to get their feedback and approval. The change should not be immediately added to the product backlog, as it may disrupt the prioritization and planning of the customer requirements. The change should not be presented to the project sponsor for approval, as it is not a significant change that affects the project scope, schedule, or budget. The change should not be rejected because it adds no value to the end customer, as it may add value to the team and the project by improving the team’s efficiency and quality. References: PMBOK Guide, 6th edition, pages 18-19, 686-687, 723-724.

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

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

• Architecture Reviews - an overview | ScienceDirect Topics
• Architecture Review Process - SEBoK
• Architecture Review - The Open Group
• Design Flaw Attacks - an overview | ScienceDirect Topics
• DESIGN FLAWS: FLAWS BY DESIGN? / The Design Society

The project manager should address the team member’s concerns by using a problem-solving approach, which involves identifying the root cause of the conflict, generating and evaluating alternative solutions, and implementing the best option. The project manager should set up a discussion with the team lead and the team member to facilitate open and honest communication, listen to both sides of the story, and help them reach a mutually acceptable resolution. This is consistent with the principle of leading with empathy and respect, which is part of the PMI Talent Triangle®. References:

• PMBOK Guide 7th Edition, page 133
• Agile Practice Guide, page 48
• PMI Talent Triangle® 1

According to the PMBOK Guide, the portfolio management office (PMO) is responsible for ensuring that the projects and programs within the portfolio are aligned with the organizational strategy and objectives. The project manager should demonstrate the project alignment to the organizational strategy by showing how the project delivers value and benefits to the organization and its stakeholders. This may include presenting the project business case, benefits management plan, stakeholder analysis, and other relevant documents that justify the project’s existence and contribution. Demonstrating the project alignment to the organizational strategy is the best way to continue the project and avoid suspension by the PMO. Meeting with the project team and revising the project goals (A) may not be effective if the project is already in alignment with the organizational strategy and the PMO is not aware of it. Updating the project charter to make it align with organizational strategy (B) may not be feasible or ethical if the project charter has already been approved and authorized by the project sponsor and other key stakeholders. Escalating the issue with the project sponsor to request support (D) may be a possible action, but not the best one, as it may create conflict or resentment between the project sponsor and the PMO. The project manager should first try to resolve the issue with the PMO directly by demonstrating the project alignment to the organizational strategy. References: PMBOK Guide, 6th edition, pages 33-34, 75-76, 129-130.

Answer steps

Graphical user interface Description automatically generated

 The project manager should take these two actions to align customer expectations with the current situation of the project. The sprint velocity is a measure of how much work the agile team can complete in a sprint. By reviewing the updated sprint velocity with the customer, the project manager can show the impact of losing two team members on the project schedule and scope. The customer can then adjust their expectations accordingly and provide feedback on the project progress. The prioritized backlog is a list of features and requirements that the customer wants to have in the product. By asking the product owner to review the prioritized backlog with the customer, the project manager can ensure that the most valuable and important features are delivered first. The customer can also reprioritize the backlog items based on their changing needs and preferences. This way, the project manager can deliver early results that meet the customer’s satisfaction.

The other options are not the best actions to align customer expectations. Asking the agile team to review and update the quality management plan with the customer is not relevant to the budget reduction or the early results. The quality management plan defines the quality standards, criteria, and methods for the project. It is not a tool for communicating the project status or scope with the customer. Reviewing the impediments log with the customer is not a good practice, as it may expose the internal issues and challenges of the agile team. The impediments log is a record of the obstacles and problems that the agile team faces during the project. It is used by the agile team and the scrum master to identify and resolve the impediments. The customer does not need to know the details of the impediments log, as it may affect their trust and confidence in the project team. Sending a detailed project management plan to the customer is not appropriate for an agile project, as it may imply a fixed and rigid approach to the project. The project management plan is a formal document that describes how the project will be executed, monitored, and controlled. It is not suitable for an agile project, as it does not accommodate the changes and uncertainties that occur during the project. An agile project relies on frequent and informal communication, collaboration, and feedback with the customer, rather than a detailed project management plan. References:

• PMBOK® Guide, 6th Edition, Chapter 6, Section 6.7, “Control Schedule”
• PMBOK® Guide, 6th Edition, Chapter 13, Section 13.2, “Plan Stakeholder Engagement”
• PMBOK® Guide, 6th Edition, Appendix X3, Section X3.2.2.3, “Sprint Velocity”
• PMBOK® Guide, 6th Edition, Appendix X3, Section X3.2.2.4, “Prioritized Product Backlog”
• PMBOK® Guide, 6th Edition, Appendix X3, Section X3.2.2.5, “Impediments Log”
• PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 12, Section 12.2, “Agile Project Management” 1

The project manager should promote an environment where everybody knows what their contribution means to the project as a whole because this is the best way to have a highly engaged team. Agile projects are based on values and principles that emphasize collaboration, flexibility, and customer satisfaction, which require the team members to be motivated, committed, and empowered. Therefore, the project manager should communicate the vision, goals, and expectations of the project, and help the team members understand how their work adds value to the project and the organization. The project manager should also encourage the team members to share their ideas, feedback, and concerns, and involve them in decision-making and problem-solving. This can help to create a sense of ownership, accountability, and pride within the team, and foster a positive and productive work culture. The other options are not the best choices because they do not support the agile approach or the team engagement. Being clear with directions and assignments so people stay focused and engaged with their work (option A) may imply that the project manager is using a directive or authoritarian style, which may limit the team’s autonomy and creativity. Designing a reward system to get people motivated by recognizing significant individual contributions from the last sprint (option C) may help to acknowledge and appreciate the team members, but it may also create competition and conflict within the team, and may not align with the agile principle of valuing the team’s performance over the individual’s performance. Encouraging continuous rotation of roles among team members to keep people motivated throughout project delivery (option D) may help to diversify and enhance the team’s skills and knowledge, but it may also disrupt the team’s stability and efficiency, and may not consider the team members’ preferences and strengths. References: PMBOK Guide, 6th edition, pages 18-19, 52, 273, 335, 686-687. [PMP Questions page 467]. PMP Practice Exam | Free PMP Practice Questions.

 According to the PMBOK Guide, quantitative risk analysis is a process that numerically analyzes the effect of identified risks on overall project objectives. It is usually performed on risks that have been prioritized by the qualitative risk analysis process. Quantitative risk analysis requires specialized skills and tools, such as statistical analysis, simulation, and modeling. Therefore, not every project team member may have the knowledge or experience to perform this task. If the project manager encounters such a situation, the best option is to help the team member to perform the quantitative risk analysis through coaching, mentoring and training. This way, the project manager can ensure that the team member learns the necessary skills and techniques, and can contribute to the risk management process. This also aligns with the project manager’s responsibility to develop the project team and enhance their competencies. Option A is not the best answer because contacting the PMO and requesting another team member may cause delays and disruptions in the project schedule and team dynamics. Option B is not the best answer because escalating the issue to the functional manager may not solve the problem, and may create conflict between the project manager and the functional manager. Option D is not the best answer because performing the quantitative risk analysis for the team member may not be feasible or efficient, and may deprive the team member of the opportunity to learn and grow. References: PMBOK Guide, 6th edition, pages 431-432, 440-441.

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

• What Is a Statement of Work (SOW)? - Coursera
• Statement Of Work Ultimate Guide: Simple Definition & Template
• What Is a Statement of Work? Definition & Examples - ProjectManager

 The project manager should schedule a virtual meeting so onsite and remote stakeholders can attend at the same time because this is the most efficient and effective way to communicate the project objectives, scope, deliverables, and expectations to all the relevant stakeholders. A virtual meeting can also facilitate interaction and feedback among the participants, and foster a sense of collaboration and commitment. The other options are not the best choices because they do not ensure that all the stakeholders are informed and engaged at the same level. Emailing all stakeholders with the objectives of the project and asking for feedback (option A) may not reach all the stakeholders, or may not elicit timely or adequate responses. Waiting for a date when all required attendees can be available onsite (option B) may cause unnecessary delays and risks to the project. Running separate meetings to accommodate everyone’s schedule (option C) may create inconsistencies and confusion among the stakeholders, and increase the workload and complexity for the project manager. References: PMBOK Guide, 6th edition, pages 367-368, 376-377. PMP Sample Test Questions. PMP Questions page 417.

According to the PMBOK Guide, an agile approach is based on delivering value in small increments and iterations, rather than in one large deliverable at the end of the project1. This allows the project team to incorporate feedback, changes, and learning into the product or service, and to reduce rework and dissatisfaction2. Therefore, the project manager should adopt an incremental cycle of delivering value to the customer, and align the project objectives and scope with the customer needs and expectations. The other options are incorrect because:

• A. Decreasing the scope of the portfolio and sending new solutions to the customer is not an agile strategy, but a reactive one. It may imply that the project team is not able to deliver the agreed scope, or that they are not collaborating with the customer to understand their requirements and preferences.
• B. Delivering a schedule with the portfolio timeline and delivery to the customer is not an agile strategy, but a predictive one. It may imply that the project team is following a rigid and fixed plan, rather than responding to changes and uncertainties in the project environment.
• D. Preparing deliveries with more details to satisfy the customer is not an agile strategy, but a waterfall one. It may imply that the project team is focusing on documentation and specifications, rather than on working products and solutions. References:
• 1: PMBOK Guide, 6th edition, Chapter 1, Section 1.2.3, page 7
• 2: PMBOK Guide, 6th edition, Chapter 3, Section 3.8, page 52
• : Agile Practice Guide, Chapter 2, Section 2.1.1, page 13
• : Agile Practice Guide, Chapter 2, Section 2.2, page 14

 The project manager should meet with the stakeholders to recommend the use of a time and materials (T&M) contract to address the problem, as this type of contract is more suitable for agile projects that have changing requirements and priorities. A T&M contract allows the buyer to pay the seller based on the actual hours of work and the cost of materials, rather than a fixed price. This can provide more flexibility and adaptability for the project, and reduce the risk of budget overrun. The other options are not as effective or appropriate as recommending a T&M contract. Sending a detailed status report may inform the stakeholders of the issue, but it does not propose a solution. Submitting a change request may increase the funding, but it does not address the root cause of the problem, which is the mismatch between the contract type and the project approach. Waiting until the next gate review meeting may delay the resolution of the problem, and increase the likelihood of further deviation from the EAC. References:

• PMBOK Guide, 7th edition, page 163
• PMI-PBA Exam Content Outline, 2018, page 10
• PMP question 391

The project manager should use Monitor Communications techniques to ensure that the communication needs of the project and its stakeholders are met. This involves collecting and analyzing feedback from stakeholders, reviewing the effectiveness and quality of the communication activities, and identifying and resolving communication issues. By doing so, the project manager may discover the reasons why some stakeholders are not fully comprehending the status of the project based on the reports that are being circulated, and may initiate changes to the communications management plan to address them. For example, the project manager may decide to use a different report format, frequency, or distribution method that suits the needs and preferences of the new stakeholders. Adding the issue to the issue log and determining the corrective action (option A) is a possible outcome of Monitor Communications, but not the best answer. Creating a fishbone diagram to determine the root cause for the misunderstanding (option B) is a tool that can be used in Monitor Communications, but not the only one. Sharing the communications management plan and reminding all stakeholders of the agreed-upon reporting templates (option D) is not likely to solve the problem, as it may imply that the new stakeholders are at fault for not understanding the reports, rather than acknowledging that the communication needs may have changed. References:

• PMBOK Guide, 6th edition, page 386-387, section 10.2 Manage Communications
• PMP Exam Prep, 10th edition, page 415, question 415, answer and explanation

 The project manager should consult the project team to understand the extent of the training needs for the contractor. This is consistent with the agile value of individuals and interactions over processes and tools1. The project manager should also collaborate with the contractor to provide them with the necessary guidance and coaching on the agile principles and practices2. Asking the project sponsor to replace the contractor since they do not have agile experience (A) is not a good option since it may cause unnecessary delays and costs for the project. Issuing a formal notice to the contractor to obtain an agile certification (B) is also not appropriate since it may create a sense of distrust and resentment in the contractor. Instructing the contractor to receive agile training since the project has already started (D) is not a sufficient action since it does not address the specific needs and expectations of the project team and the contractor. References:

• 1: Agile Practice Guide, Chapter 1, Section 1.2.1
• 2: Agile Practice Guide, Chapter 2, Section 2.3.2.2

 The project manager should first assess the organization’s culture, readiness, and maturity to adopt agile methods, as well as the nature and complexity of the projects. Based on this assessment, the project manager can then propose the most suitable agile practices and frameworks that can be tailored to the organization’s context and needs. This approach will help to ensure a smooth and successful transition to agile, as well as to address any potential resistance or challenges. Organizing agile workshops, requesting training, or advising the PMO manager to continue with predictive approaches are not the best ways to initiate the adoption of agile, as they do not consider the organization’s current situation and capabilities. References: 1, 2, 3

• 1: PMI. (2020). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Newtown Square, PA: Project Management Institute, Inc. Chapter 1, Section 1.2.3.2, p. 9.
• 2: PMI. (2020). PMP Sample Test Questions (correct answers are bolded). Retrieved from 3
• 3: PMI. (2017). Agile Practice Guide. Newtown Square, PA: Project Management Institute, Inc. Chapter 2, Section 2.1, pp. 13-14.

According to the PMBOK Guide, when using an agile approach, the project manager needs to have a clear understanding of the product vision, the product roadmap, and the product backlog1. The product vision is a brief statement that describes the desired outcome of the project and the value it will deliver to the customers and stakeholders2. The product roadmap is a high-level overview of the product features and deliverables, along with the planned timeline and milestones3. The product backlog is a prioritized list of the product requirements, user stories, and other work items that need to be completed by the project team. These three factors help the project manager to align the project objectives with the customer needs, plan and execute the project iteratively and incrementally, and deliver value early and often1. The other options are not relevant for an agile approach, as they are more suitable for a predictive or waterfall approach. Key performance indicators (KPIs) are metrics that measure the performance of the project against the project objectives. Schedule performance index (SPI) is a ratio of the earned value to the planned value, indicating how well the project is progressing according to the schedule. These factors are not essential for delivering a product using an agile approach, as they focus more on the adherence to the plan rather than the delivery of value. References:

• 1: PMBOK Guide, 6th edition, page 18
• 2: PMBOK Guide, 6th edition, page 156
• 3: PMBOK Guide, 6th edition, page 157
• : PMBOK Guide, 6th edition, page 158
• : PMBOK Guide, 6th edition, page 33
• : PMBOK Guide, 6th edition, page 267

According to the PMBOK Guide, 6th edition, one of the key processes of the Project Communications Management knowledge area is Plan Communications Management, which involves determining the information and communication needs of the project stakeholders. One of the tools and techniques for this process is communication requirements analysis, which considers factors such as the availability, frequency, format, and level of detail of the information. By asking the project sponsor what sort of information is needed and agreeing on a frequency for the communication, the project manager is performing communication requirements analysis, which will help to tailor the communications management plan to the specific needs and preferences of the project sponsor. References: PMBOK Guide, 6th edition, pages 361-362, 367.

The project manager should review the team culture and the personality traits of the individual to address status update gaps. This will help to understand the root cause of the problem and find ways to improve the communication and collaboration within the team. The project manager should also foster a trusting and respectful environment where team members feel comfortable to share their challenges and feedback. Creating a safe space for status updates, reviewing the team status updates more thoroughly, or supporting team inclusion and changing the format of status updates are all possible actions that the project manager can take after reviewing the team culture and the personality traits of the individual, but they are not the first action that the project manager should take to rectify this situation. References: Agile Practice Guide, page 27; PMBOK Guide 7th Edition, page 95.

 In an agile project, the product owner is responsible for defining and prioritizing the product backlog, and the team is responsible for delivering the product increment based on the sprint backlog. If the product owner identifies that some key features are missing from the product increment, the project manager should collaborate with the product owner and the team to plan the next sprint and adjust the backlog accordingly. Extending the sprint timeline (A) would violate the time-boxed nature of agile sprints and disrupt the rhythm and cadence of the project. Informing the product owner that the issue needs to be escalated (B) would not solve the problem, but rather create unnecessary conflict and bureaucracy. Initiating the change request process (D) would not be appropriate for an agile project, as changes are expected and welcomed throughout the project lifecycle, and do not require formal approval or documentation. References: PMBOK Guide, 7th edition, page 91; Agile Practice Guide, page 14.

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

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

• PMBOK Guide’s Change Management Process For PMP Exam
• Change Log - Project Management Knowledge
• Project Management Change Request Form & Process
• Change Log Template - Project Management Docs

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

• 1: What is agile project management? - APM
• 2: What is Agile? - Project Management Institute
• 3: Role of Project Sponsor in Agile Project Management - PM Majik

 The new project manager should encourage participation in decision making and empower the team to improve their motivation and engagement. This is a key aspect of managing human resources in a project, as it fosters trust, collaboration, and ownership among the team members. The project manager should also communicate the project vision, goals, and expectations clearly and regularly to align the team and provide feedback and recognition. These actions can help the project manager to build a high-performing team and enhance the project performance.

The other options are not the best choices for the new project manager. Ensuring everyone performs their assigned tasks as planned may not address the root cause of the team’s lack of direction and enthusiasm. It may also imply a micromanagement style that can demoralize the team further. Organizing frequent team building sessions and updating the risk register are good practices, but they are not sufficient to improve the team’s morale and commitment. They should be complemented by other actions that involve and empower the team. Meeting with the project sponsor and proposing a corrective action for the project may be necessary if the project is facing serious issues, but it does not directly address the team’s situation. The project manager should first try to understand and resolve the team’s concerns before escalating them to the sponsor. References:

• PMBOK® Guide, 6th Edition, Chapter 9, Section 9.4, “Manage Project Team”
• PMBOK® Guide, 6th Edition, Chapter 9, Section 9.4.2.3, “Interpersonal and Team Skills”
• PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 8, Section 8.3, “Managing Resources” 1

Customer communication management (CCM) is the strategy to improve the creation, delivery, storage and retrieval of outbound communications with customers1. CCM is essential for building and maintaining customer relationships, enhancing customer satisfaction and loyalty, and delivering value to customers2. One of the key aspects of CCM is to understand the customer’s preferences, needs, expectations, and feedback regarding the communication channels, frequency, content, and tone3. This requires the project manager to conduct a stakeholder analysis and identify the customer’s company culture, which is the set of shared values, beliefs, norms, and practices that influence how the customer behaves and communicates4. By understanding the customer’s company culture, the project manager can tailor the communication approach to suit the customer’s style and avoid any annoyance or misunderstanding5.

Therefore, the first thing the project manager should have done to prevent the customer’s leadership team from being annoyed about the frequency of email updates is to understand the customer’s company culture (option A). This would help the project manager to determine the optimal communication frequency and method for the customer, and to align the communication plan with the customer’s expectations. Updating the communications management plan (option B), analyzing customer interest and engagement (option C), or scheduling weekly update meetings (option D) are possible actions that the project manager could take after understanding the customer’s company culture, but they are not the first thing to do. References:

• 1: Gartner, Customer Communications Management (CCM)
• 2: ClickUp, What is Customer Communication Management (CCM)?
• 3: QuestionPro, Customer Communication Management: Strategies for Success
• 4: PMBOK® Guide, 6th edition, p. 513
• 5: PMBOK® Guide, 6th edition, p. 376

According to the PMBOK Guide, 7th edition, section 4.3.2.1, when a project faces a technical issue that requires specialized knowledge or expertise, the project manager should consult with external subject matter experts (SMEs) and the team to find a solution. External SMEs are individuals or groups who have specialized knowledge or skills related to a specific aspect of the project, such as aerospace design. They can provide valuable insights, recommendations, and guidance to the project team. The project team consists of the project manager and the project staff who are responsible for performing the project work. They have the most knowledge and experience about the project and its deliverables. The project manager should involve both the external SMEs and the team in the discussion of the technical issue, as they can contribute different perspectives and ideas to resolve the issue. The project manager should also communicate the issue and the proposed solution to the project sponsor and other relevant stakeholders, but they do not need to be part of the initial meeting.

References:

• PMBOK Guide, 7th edition, section 4.3.2.1
• PMP Exam Content Outline, Domain II: Process, Task 5

 The best way to formally record the team member’s success in the project documentation is to send a communication to management recognizing the team member’s contributions. This will ensure that the team member’s performance is acknowledged and appreciated by the relevant stakeholders, and that the project documentation reflects the team member’s achievements. The other options are not as effective or appropriate as sending a communication to management. Attaching a note to the project management plan is not a formal way of recording the team member’s success, and it may not be seen by anyone else. Holding a project team meeting may be a good way to celebrate the team member’s contribution, but it does not document it for future reference. Recording the team member’s contribution in the RAM is not relevant, as the RAM is a tool to assign roles and responsibilities, not to measure performance. References:

• PMBOK Guide, 7th edition, page 215
• PMI-PBA Exam Content Outline, 2018, page 12

 Diversity and inclusion are important for project effectiveness, as they enable diverse perspectives, ideas, and experiences to be shared and valued among the project team and stakeholders. However, diversity and inclusion are not just about demographics, but also about creating a culture of respect, belonging, and empowerment for everyone. To achieve this, the organization needs to provide training and education to the entire workforce, not just to specific teams or departments, to raise awareness, foster understanding, and promote positive behaviors. By doing so, the organization can prevent or reduce potential conflicts, misunderstandings, or biases that may arise from different backgrounds, views, or preferences. Furthermore, the organization can leverage the benefits of diversity and inclusion, such as improved innovation, collaboration, and customer satisfaction. References:

• Diversity, Equity, and Inclusion in Project Management
• Diversity and Inclusion Are Important for Project Effectiveness
• Diversity, Equity, & Inclusion | PMI

 According to the PMBOK Guide, a root cause analysis is a technique used to identify the underlying reasons for the occurrence of a problem or a deviation from the expected performance. It is part of the monitor and control project work process, which involves tracking, reviewing, and reporting the project progress and performance, and implementing corrective or preventive actions as needed. A root cause analysis can help the project manager to understand the causes of the budget shift and to take appropriate actions to address them. It can also help to prevent similar problems from happening again in the future. Adjusting the original budget estimates, negotiating the project changes, or reviewing the activity duration are possible actions that the project manager can take after performing a root cause analysis, but they are not the first step to do when faced with a significant budget shift. References:

• PMBOK Guide, 6th edition, pages 121-122, 4.5 Monitor and Control Project Work
• PMBOK Guide, 6th edition, pages 686-687, Root Cause Analysis
• PMP Sample Test Questions, question 1, answer D

 The project manager should refer to the requirements traceability matrix to verify whether the customer’s claims are valid or not. The requirements traceability matrix is a grid that links product requirements from their origin to the deliverables that satisfy them1. It helps to ensure that each requirement adds business value by linking it to the business and project objectives2. It also provides a means to track requirements throughout the project life cycle, helping to ensure that requirements approved in the project scope statement are delivered at the end of the project3. Revising the project scope baseline (B) is not a good option since it would imply accepting the change requests without verifying their validity. Escalating the change request to the project sponsor © is also not advisable since the project manager should first analyze the situation and propose a solution. Reviewing the approved project charter (D) is not relevant since the project charter does not contain the detailed product requirements. References:

• 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Glossary, page 717
• 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 5, Section 5.2.3.1
• 3: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 5, Section 5.6.3.1

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

• A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 7, Section 7.4.2.1
• Practice Standard for Earned Value Management – Second Edition, Chapter 3, Section 3.2.3
• Agile Practice Guide, Chapter 5, Section 5.4.2

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

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

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

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

References: 1: PMBOK® Guide, 7th edition, page 9 2: PMBOK® Guide, 7th edition, page 95 3: Agile Manifesto, 4

 According to the PMBOK® Guide, the project manager should include projected inflation rates in the budget estimate for a long-term project that will be executed over several years. This is because inflation rates affect the purchasing power of the project funds and the cost of resources over time. By including projected inflation rates, the project manager can account for the changes in the value of money and the cost of goods and services, and adjust the budget accordingly. This is part of the Estimate Costs process, which involves developing an approximation of the monetary resources needed to complete the project activities. References: (Professional in Business Analysis Reference Materials source and documents)

• PMBOK® Guide, 6th edition, Chapter 7, Section 7.2, Estimate Costs
• PMP Exam Prep, 10th edition, Rita Mulcahy, Page 223, Estimate Costs

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

• : PMP Exam Content Outline
• : A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 9.4.2.3 and 9.4.3.1
• : Business Analysis for Practitioners: A Practice Guide, Chapter 4.5.1 and 4.5.2
• : Megaprojects – Concepts, Strategies, and Practices for Success1
• : The Three Secrets of Megaproject Success: Clear Strategic Vision, Total Alignment, and Adapting to Complexity2

The project manager should use the alignment of the project with the benefits management plan as an indicator that the project is actually delivering value because this is the best way to measure the project’s contribution to the organization’s strategic objectives and expected outcomes. The benefits management plan defines the benefits that the project is expected to deliver, the metrics and targets to evaluate them, the roles and responsibilities for benefits realization, and the timeline and process for benefits review and transition. By comparing the project’s performance and deliverables with the benefits management plan, the project manager can assess the value of the project and identify any gaps or issues that need to be addressed. The other options are not the best choices because they do not necessarily reflect the value of the project. Stakeholders’ satisfaction with the current status (option A) may be subjective and biased, and may not consider the long-term benefits of the project. The project being under budget and on schedule (option B) may indicate the project’s efficiency and adherence to the plan, but it does not guarantee the project’s effectiveness and alignment with the business needs. The project being aligned with the project charter (option C) may show the project’s compliance with the initial scope, objectives, and assumptions, but it does not account for any changes or updates that may affect the project’s value proposition. References: PMBOK Guide, 6th edition, pages 33-34, 75-76, 129-130. PMP Questions page 457. PMP Practice Exam | Free PMP Practice Questions.

The definition of done (DoD) is a clear and concise list of requirements that a deliverable must meet to be considered complete and acceptable by the main stakeholder. The DoD helps to ensure that the quality standards are met and that the deliverables are aligned with the stakeholder’s expectations. The project manager should reinforce the DoD during sprint planning so that the team has a common understanding of what needs to be done and how to do it. This will help to prevent the deliverables from being rejected during the next iteration. Submitting a change request to prioritize resolutions for the quality issue (option A) may be necessary, but it does not address the root cause of the problem, which is the lack of clarity and agreement on the DoD. Assuring that the product backlog is properly prioritized to avoid dependencies that cause rejection (option C) is a good practice, but it does not ensure that the deliverables will meet the quality specifications. Creating a dedicated sprint to complete all of the pending specifications from previous sprints (option D) may be a viable option, but it may also delay the project and increase the cost. The best option is to reinforce the DoD and ensure that the team delivers what the stakeholder expects. References:

• PMBOK Guide, 6th edition, page 176, section 5.4.2.1 Definition of Done
• [Agile Practice Guide], page 54, section 4.2.2.1 Definition of Done
• PMP Exam Prep, 10th edition, page 425, question 425, answer and explanation

 An issue is a point or matter in question or in dispute, or a point or matter that is not settled and is under discussion or over which there are opposing views or disagreements. An issue log is a project document that provides a mechanism for recording and communicating issues that arise during a project. It also helps to monitor their resolution. According to the PMBOK Guide, the first step in managing issues is to identify and document them in the issue log. The issue log should include information such as issue description, type, priority, owner, due date, status, and resolution. Updating the issue log will help the project manager to track and resolve the issue of the government-owned area, and communicate it to the relevant stakeholders. Identifying an alternative site, issuing a change request, or updating the risk register are possible actions that may be taken after the issue is documented and analyzed, depending on the impact and urgency of the issue. References: : PMBOK Guide, 6th edition, page 89 : PMBOK Guide, 6th edition, page 558 : PMP Sample Test Questions

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

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

• PMBOK® Guide, 6th Edition, Chapter 9, Section 9.2, “Plan Resource Management”
• PMBOK® Guide, 6th Edition, Chapter 9, Section 9.3, “Acquire Resources”
• PMBOK® Guide, 6th Edition, Chapter 9, Section 9.5, “Control Resources”
• PMBOK® Guide, 6th Edition, Chapter 11, Section 11.4, “Plan Risk Responses”
• PMP Project Management Professional Exam Study Guide: 2021 Exam Update, 10th Edition, Chapter 8, Section 8.2, “Planning Resources” 1

In an agile project, the project manager should collaborate with the stakeholders and ensure their active involvement in the project. The project manager should meet with the unhappy stakeholder to understand their concern and the business impact of the delayed delivery. The project manager should also reprioritize the product backlog as necessary to accommodate the stakeholder’s needs and expectations. Finally, the project manager should invite the stakeholder to join the sprint planning session, where the team selects the work to be done in the next iteration based on the stakeholder’s feedback and the product owner’s guidance. This way, the project manager can improve the stakeholder’s satisfaction and engagement, and foster a trusting and collaborative relationship. Directing the product owner to drop other work in progress and work on the stakeholder’s requirement as the top-priority item may not be the best option, as it may disrupt the team’s flow and compromise the value delivery. Sharing the prioritized items that the team is working on with the stakeholder and inviting them to join the sprint planning session may not be sufficient, as it does not address the stakeholder’s concern and business impact. Securing some additional funding to recruit more resources to the project team to enable faster delivery may not be feasible or effective, as it may violate the agile principle of simplicity and increase the complexity and communication overhead of the project. References:

• A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 14: Team, Section 14.2: Enable Team Performance, Section 14.3: Lead the Team
• Agile Practice Guide, Chapter 2: Life Cycle Selection, Section 2.2: Implementing Agile: Creating an Agile Environment, Section 2.3: Implementing Agile: Delivering in an Agile Environment
• Professional in Business Analysis (PMI-PBA)® Handbook, Section 2.3: Domains and Tasks, Domain 4: Analysis, Task 9: Validate Requirements
• [Professional in Business Analysis (PMI-PBA)® Examination Content Outline], Domain 4: Analysis, Task 9: Validate Requirements

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” (Section 2.1). This implies that the agile project manager should foster a collaborative and self-organizing team culture, where team members share their knowledge and skills with each other, and are able to adapt to changing situations. By asking the team member to work with their peers to knowledge share, the agile project manager can ensure that the team has the necessary information and expertise to continue working on the project, even when the specialized team member is unavailable. This is also consistent with the PMBOK® Guide, which states that “the project manager should facilitate knowledge sharing among the project team and other stakeholders” (Section 4.4.3.3). References:

• Agile Practice Guide, Section 2.1
• PMBOK® Guide, 6th Edition, Section 4.4.3.3

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

• 1: PMI-PBA guide, page 16
• 2: PMI-PBA guide, page 23
• 3: PMBOK guide, page 59

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

• Feature A: 100 / 20 = 5
• Feature B: 80 / 10 = 8
• Feature C: 120 / 15 = 8
• Feature D: 60 / 5 = 12
• Feature E: 40 / 10 = 4

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

References:

• Project Prioritization Process: 5 Strategies to Prioritize Your Projects
• 5 Steps to Master Requirements Prioritization

The project manager should ensure that relevant stakeholders and expectations are identified and assess the component delay. This is because the project manager needs to communicate with the stakeholders about the impact of the delay on the project objectives, scope, schedule, cost, and quality, and seek their feedback and support. The project manager also needs to evaluate the component delay and its root cause, and determine the best course of action to address the issue. Asking for expedited delivery, performing a detailed analysis, or proposing a new design are possible actions that the project manager may take after ensuring stakeholder identification and assessment, depending on the outcome of the evaluation. However, they are not the best actions to take in this situation, as they may not address the stakeholder needs and expectations, or may introduce unnecessary changes or risks to the project. References: = PMBOK Guide, 6th edition, page 513, section 10.1.1.1 (Stakeholder Identification); page 518, section 10.1.3.1 (Stakeholder Register); page 520, section 10.2.1.1 (Stakeholder Analysis); page 524, section 10.2.3.1 (Stakeholder Engagement Assessment Matrix); page 526, section 10.3.1.1 (Communication Requirements Analysis)

The project manager should take two actions to deal with the situation of the neighbors resisting the project and threatening legal action. One action is to publish information on the city’s website about the benefits that the new tram station will bring, such as improved transportation, reduced traffic, increased safety, and enhanced economic development. This action can help to inform and educate the public about the project’s value proposition and address any misconceptions or concerns that the neighbors may have. The project manager can also use other communication channels, such as social media, newsletters, or press releases, to reach a wider audience and increase awareness and support for the project12.

Another action is to register this situation as a risk and develop a mitigation plan. A risk is an uncertain event or condition that can have a positive or negative effect on the project’s objectives. The situation of the neighbors opposing the project and threatening legal action is a negative risk that can potentially cause delays, cost overruns, reputation damage, or even project cancellation. The project manager should identify and document this risk in the risk register, along with its probability, impact, and priority. The project manager should also develop a mitigation plan to reduce the likelihood or severity of the risk. The mitigation plan may include actions such as engaging with the neighbors, negotiating with them, offering them compensation, or seeking legal advice34. References: = PMBOK® Guide, Sixth Edition, pages 376-377, 414-415; 8 Steps for Better Issue Management, Step 5: Communicate with the team; PMBOK® Guide, Sixth Edition, pages 395-396, 443-444; Project Risk Management - A Quick Guide, Step 3: Plan Risk Responses.

According to the Professional in Business Analysis (PMI-PBA)® Guide, stakeholder communication is the process of planning, managing, and monitoring the exchange of information among project stakeholders. Stakeholder communication should be customized based on the stakeholders’ needs, preferences, expectations, and level of involvement. In this scenario, the project manager should have customized stakeholder communications based on the key stakeholder’s needs. This would have helped the project manager to keep the key stakeholder informed, engaged, and satisfied throughout the project, and to address any issues, concerns, or feedback that the key stakeholder may have. This would have also helped to avoid the situation where the key stakeholder rejected a feature deliverable due to lack of involvement or awareness. Involved the key stakeholders in the decision-making process, analyzed the changes in stakeholder attributes, or documented the project vision and objectives are actions that should be taken as part of the stakeholder communication plan, not as a substitute for it. These actions do not address the root cause of the situation, which is the inadequate stakeholder communication. References: (Professional in Business Analysis Reference Materials source and documents)

• Professional in Business Analysis (PMI-PBA)® Guide, Chapter 2, Section 2.4.1.1
• A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 10, Section 10.2.2.1
• The Standard for Project Management – Seventh Edition, Chapter 3, Section 3.2.2.1

According to the PBA Guide, the project manager should employ collaborative discussions as the primary tool to gain an understanding of the risks for an agile project1. Collaborative discussions are interactive sessions that involve the project team and other relevant stakeholders to identify, analyze, prioritize, and respond to project risks1. Collaborative discussions can take various forms, such as brainstorming, interviews, focus groups, surveys, or retrospectives1. Collaborative discussions enable the project manager to leverage the collective knowledge and experience of the participants, foster a shared understanding of the project risks, and promote a risk-aware culture within the project team1. Collaborative discussions are especially suitable for agile projects, as they support the agile principles of communication, collaboration, feedback, and adaptation2. Collaborative discussions can be conducted throughout the project life cycle, as part of the agile events such as sprint planning, daily scrum, sprint review, or sprint retrospective3. Collaborative discussions can also be integrated with other risk management tools, such as probability assessments, risk avoidance workshops, or interviews with the project champion, to enhance the quality and effectiveness of the risk management process1. References:

• 1: PBA Guide, Chapter 4, Section 4.3.2.1, Page 88
• 2: Agile Manifesto
• 3: Making Risk Management for Agile Projects Effective

This answer is based on the PMBOK® Guide, which is one of the reference materials for the PMP exam1, and the PMI Guide to Business Analysis, which is one of the reference materials for the PMI-PBA exam2. According to the guides, the project manager is responsible for managing the project team, which includes developing, leading, and motivating the team members, as well as resolving any conflicts or issues that may arise among them12. The project manager should also establish and enforce the ground rules for the project team, which are the agreed-upon standards of behavior and expectations for the team members, such as communication protocols, decision-making processes, meeting guidelines, and conflict resolution methods12. When the project manager observes that two team members have been arguing with each other openly at meetings and bypassing the project manager to influence the sponsor, this indicates a serious breach of the ground rules and a potential threat to the project performance and harmony. The project manager should take the following two actions to address this situation:

• Reiterate ground rules at the next meeting and ensure that all team members are clear about these rules. This action will remind the team members of their roles and responsibilities, and the expected norms of conduct for the project team. It will also reinforce the authority and accountability of the project manager, and the importance of following the agreed-upon procedures for communication and decision-making. This action will help to prevent further escalation of the conflict and restore trust and respect among the team members12.
• Address the behavioral issue with each team member. This action will allow the project manager to understand the root cause of the conflict, and the perspectives and interests of each team member. It will also enable the project manager to provide constructive feedback, coaching, or counseling to each team member, and to facilitate a collaborative resolution that satisfies both parties and aligns with the project objectives. This action will help to improve the performance and morale of the team members, and to foster a positive and productive team culture12.

The other options are not appropriate because they do not address the problem effectively or ethically. Asking the team members to work it out themselves is not a responsible or proactive approach, as it may lead to further deterioration of the relationship and the project outcomes. Discussing this situation with other project managers and asking for advice is not a confidential or respectful way to handle the issue, as it may expose the team members to gossip or criticism, and undermine their trust and credibility. Discussing the behavior directly with their managers and requesting them to correct the behavior is not a fair or empowering way to deal with the issue, as it may create a perception of blame or punishment, and damage the rapport and autonomy of the team members. References:

• PMBOK® Guide
• PMI Guide to Business Analysis

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

• PMBOK Guide, 6th edition, section 4.1.3.2, page 77
• PMP Exam Prep, 10th edition, Rita Mulcahy, page 76
• PMP Practice Questions #67 - iZenBridge1

 According to the PBA Guide, the product owner is the person who is responsible for defining and prioritizing the product backlog, which contains the requirements for the project. The product owner also provides feedback and acceptance for the deliverables produced by the development team. Therefore, the project manager should work with the product owner to clarify the requirement and the acceptance criteria for the task, as they are the best source of information and authority for the project scope. This is also consistent with the agile principles of collaboration, customer satisfaction, and responding to change. References:

• PBA Guide, Chapter 2, Section 2.3.1, Roles and Responsibilities of the Product Owner
• PBA Guide, Chapter 3, Section 3.2.1, Product Backlog
• PBA Guide, Chapter 4, Section 4.3.2, Feedback and Acceptance
• PMBOK Guide, Chapter 13, Section 13.2.2.1, Agile/Adaptive Environments
• PMBOK Guide, Appendix X3, Section X3.2, Agile Principles

Team velocity is a measure of a team’s effective productivity and capacity in agile development. It indicates the amount of work a team can accomplish in a given sprint, usually expressed in story points1. Team velocity can vary from sprint to sprint due to various factors, such as team size, complexity, dependencies, quality, and external interruptions2. Therefore, it is important for the project manager to monitor and review the team velocity over the last several sprints and use the average or trend as a basis for planning and forecasting future sprints3. By adjusting the plan according to the team velocity, the project manager can help the team avoid overcommitting or underdelivering, and set realistic and achievable sprint goals4.

The other options are not the best choices for the project manager in this situation. Switching to a Kanban approach (option A) may not solve the problem of sprint failures, as Kanban is a different agile framework that does not use fixed-length iterations or predefined roles. Kanban focuses on visualizing the workflow, limiting the work in progress, and optimizing the flow of value5. While Kanban can help the team improve efficiency and flexibility, it may not be suitable for every project or organization, and it may require a significant change in the team’s culture and processes. Asking the project sponsor to approve overtime (option C) may not be a sustainable or effective solution, as it may lead to burnout, lower quality, higher costs, and reduced motivation among the team members6. Replacing junior team members with more experienced ones (option D) may not be feasible or desirable, as it may disrupt the team’s dynamics, trust, and collaboration. It may also create resentment, conflict, and turnover among the team members. Negotiating the project scope to compensate for the budget gap may not be aligned with the project’s objectives, stakeholders’ expectations, or agile principles7.

References: 1: What is team velocity and how to calculate it - LogRocket Blog 2: Home - Team Velocity - Fueled by Apollo 3: How to Calculate Team Velocity in Agile Project Management 4: [How to Use Team Velocity to Plan Sprints | monday.com Blog] 5: Kanban - A brief introduction | Atlassian 6: [The Impact of Overtime on Productivity and Quality in Agile Teams] 7: [Agile Manifesto Principles | Agile Alliance]

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

• PMBOK Guide, 7th edition, Chapter 2: Project Performance Domains, Section 2.1: Project Delivery Approach, pp. 23-251
• PMBOK Guide, 7th edition, Chapter 3: Project Management Principles, Section 3.5: Engage Stakeholders, pp. 41-421
• PMBOK Guide, 7th edition, Chapter 4: Tailoring, Section 4.2: Tailoring Considerations, pp. 51-531
• PMBOK Guide, 7th edition, Chapter 8: Communications, Section 8.2: Plan Communications, pp. 123-1251
• Professional in Business Analysis (PMI-PBA) Handbook, Section 5: Exam Content Outline, Domain 2: Planning, Task 2.3: Develop a communication management plan, pp. 21-222

 The project manager should hold a stakeholder meeting to align timelines and scope expectations. This is because the project manager needs to manage the stakeholder’s expectations and ensure that they understand the implications of their request. The project manager should explain the current project schedule, the assumptions and constraints that were considered, and the risks and opportunities that are involved. The project manager should also discuss the possible alternatives to meet the stakeholder’s request, such as crashing, fast-tracking, or scope reduction, and their pros and cons. The project manager should seek the stakeholder’s input and feedback, and try to reach a mutually agreeable solution that satisfies the project objectives and the stakeholder’s needs. The project manager should also update the project documents, such as the project management plan, the schedule baseline, and the scope baseline, to reflect the agreed changes, and communicate them to the relevant stakeholders.

The other options are not correct because they do not address the issue of stakeholder alignment and communication, which is essential for project success. Crashing the schedule to shorten the timeline while keeping the scope unchanged might be a possible option, but it would increase the project cost and risk, and might not be acceptable to the stakeholder. Updating the cost management plan to allocate more resources to the project to finish the scope earlier might be another option, but it would also increase the project cost and complexity, and might not be feasible or effective. Reducing the scope of the project by removing activities and shortening the timeline might be another option, but it would compromise the project value and quality, and might not meet the stakeholder’s requirements. References: PMBOK Guide, 6th edition, section 6.6, page 215, PMP Exam Prep, 10th edition, page 180

According to the PMP Exam Content Outline, one of the tasks for managing project work is to provide relevant stakeholders with project information and updates on cost, schedule, scope, and quality1. The business analyst is a relevant stakeholder who needs to learn about the financial and scheduling aspects of project management. Providing the business analyst with access to the financial and scheduling information is the best way to support their learning and involvement in the project. Assigning resources to coach the business analyst may not be feasible or necessary, as the business analyst may have their own methods and preferences for learning. Asking the business analyst to focus on their work allocation for the needs of the project may not address their learning objectives or expectations. Creating reports to inform the business analyst about the schedule and project cost may not be sufficient or timely, as the business analyst may need more detailed or updated information. References:

• 1: PMP Exam Content Outline, Domain III: Business Environment, Task 4: Manage project changes by following the change management plan in order to achieve project objectives.

 These two actions can help prevent the team from being unqualified, because they can enhance the skills and competencies of the team members who lack the technical skill needed to build the product. Encouraging working in pairs and knowledge sharing can foster collaboration and learning among the team members, and allow the team member who has the technical skill to transfer it to others through coaching, mentoring, or feedback. Facilitating a training event with an external trainer can provide a formal and structured way of teaching the team members the technical skill, and ensure that they have the necessary knowledge and practice to apply it to the project. These actions can also improve the team performance, morale, and confidence, and reduce the dependency on one team member. The other options are not effective actions to prevent the team from being unqualified, because they may not address the skill gap or the project requirements, or they may create more problems or risks. Excluding the activities from the roadmap may not be possible or desirable, and it may affect the scope, quality, or benefits of the project. Teaching the entire team the new skill may not be feasible or efficient, and it may overload the project manager or the team member who has the skill. Increasing the time estimates on the activities that require such abilities may not be realistic or accurate, and it may delay the project schedule or increase the project cost. References: Project Resource Management - PMBOK Guide, What Actions Can the Project Manager Take to Ensure Effective Teamwork?

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.

Making work visible using kanban boards is a technique that helps to manage the flow of work and identify bottlenecks or impediments. Kanban boards show the status of each work item, the priority, the assignee, and the dependencies. This way, the project manager can monitor the progress of the software development, communicate with the team and the stakeholders, and resolve any issues that arise. Applying lean manufacturing to limit the team’s work is not a suitable option, as it does not address the root cause of the delays or impediments. Increasing retrospectives to deliver results fast is not a realistic solution, as it may compromise the quality of the software and the team’s morale. Incorporating small batches of work into the project is a good practice for agile projects, but it does not solve the problem of lack of information or communication. References: Project Management Professional Sample Questions, page 10, question 84. [A Guide to the Project Management Body of Knowledge (PMBOK Guide)], Sixth Edition, page 188, section 6.2.2.4. [Agile Practice Guide], page 51, section 4.2.2.

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 activities1. The project manager should review and update the stakeholder engagement plan to address the needs and expectations of the newly appointed technical manager, who is a key stakeholder for the project. The project manager should also communicate with the technical manager to understand the information gaps and provide the necessary updates on the project deliverables. Updating the issue log and escalating to the project sponsor (option A) may not be the best first action, as it could create unnecessary conflict and damage the relationship with the client. Identifying the lack of information as a risk and updating the risk register (option B) is not appropriate, as the situation is not a potential uncertain event that could affect the project objectives, but rather a current issue that needs to be resolved. Scheduling more frequent meetings with the technical manager (option C) may help to improve the communication, but it does not address the root cause of the problem, which is the inadequate stakeholder engagement plan. References:

• 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Project Management Institute, Inc., 2017, p. 518.

The project manager should review the historical information and lessons learned from last year’s project to justify the new budget estimate. This is because the project manager used an analogous estimating technique, which is based on the costs of similar projects in the past. By reviewing the historical information and lessons learned, the project manager can explain to the project sponsor how the costs of the new project were derived, what assumptions and risks were considered, and how the three-point estimating technique was applied. This can help the project sponsor understand the rationale behind the budget estimate and increase their confidence in its accuracy and validity. The project manager can also use this opportunity to discuss the benefits and value of the new project and how it aligns with the organizational strategy and objectives. References: PMBOK Guide, 6th edition, section 7.2.2.4, page 262, Free PMP® Exam Sample Question 04 (Earned Value)

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

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

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

• Recognize and acknowledge the feelings and perspectives of team members, especially when they are affected by a change or a loss
• Express appreciation and gratitude for the contributions and achievements of team members
• Provide constructive feedback and coaching to help team members improve their performance and skills
• Encourage team members to share their ideas, opinions, and concerns, and listen actively and empathetically
• Resolve conflicts and disagreements in a respectful and collaborative manner
• Celebrate successes and milestones, and recognize the efforts and challenges of the team

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

References:

• PMI Guide to Business Analysis. (2017). Newtown Square, PA: Project Management Institute.
• Keep Your Team Motivated When a Project Goes Off the Rails. (2023). Harvard Business Review.
• How Team Morale Affects Employee Performance [2023]. (2022). Asana.

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

• PMBOK® Guide, 6th edition, Section 9.1, pp. 308-313
• PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain II: Planning, Task 2, p. 9
• Business Analysis for Practitioners: A Practice Guide, Section 3.4.1, p. 66

According to the PMBOK Guide, conflict management is the process of identifying and addressing differences that, if left unresolved, could affect project performance1. The project manager should use appropriate conflict resolution techniques to facilitate constructive interactions among stakeholders and foster a collaborative project environment2. One of the conflict resolution techniques is collaborating, which involves incorporating multiple viewpoints and insights from different perspectives, and leads to consensus and commitment3. In the given scenario, the project manager should use a direct, collaborative approach with the technician and supervisor to understand the root cause of the conflict, address their concerns, and find a mutually acceptable solution that does not compromise the project objectives. This approach would also help to improve the relationship and trust between the technician and supervisor, and enhance their performance and motivation. References:

• 1: PMBOK Guide, 6th edition, p. 504
• 2: PMBOK Guide, 6th edition, p. 505
• 3: PMBOK Guide, 6th edition, p. 507

• According to the PMBOK Guide, the quality management plan is a component of the project management plan that describes how the project quality will be planned, assured, controlled, and managed. It also includes the quality standards, quality metrics, quality tools, quality roles and responsibilities, and quality audits.
• In this scenario, the project manager should review the quality management plan to understand the requirements and expectations for the regulatory labels, the process and criteria for inspecting and verifying them, the actions and responsibilities for resolving any nonconformities, and the documentation and reporting of the quality results.
• The other options are not appropriate because:

References:

• [PMBOK Guide] - A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Project Management Institute, Inc., 2021.

According to the Scrum Guide, an impediment is any factor that blocks or slows down the Developers in their creation of a valuable piece of software in a Sprint, or that restricts the team in achieving its intrinsic level of progress1. Therefore, the scenarios that are impediments are:

• A team member talking about a user story that is not on the Scrum board: This indicates that the team is not focused on the Sprint Goal and the Sprint Backlog, which are the sources of alignment and commitment for the Developers. Talking about a user story that is not on the Scrum board can also cause confusion, distraction, and waste of time for the team2.
• A technology that blocks agile capabilities: This implies that the team is facing a technical issue that prevents them from delivering a potentially releasable Increment of value at the end of the Sprint, or from collaborating effectively with the Product Owner and other stakeholders. A technology that blocks agile capabilities can also hinder the team’s ability to inspect and adapt their work and process3.
• A lack of team empowerment and an inability to self-organize: This suggests that the team is not able to make decisions and take actions that are best suited for achieving the Sprint Goal and delivering value to the customer. A lack of team empowerment and an inability to self-organize can also affect the team’s motivation, creativity, and productivity.

The scenarios that are not impediments are:

• A team member talking about a user story that is on the Scrum board: This indicates that the team is engaged in the Sprint work and is discussing the details and progress of a user story that is part of the Sprint Backlog. Talking about a user story that is on the Scrum board can also foster communication, collaboration, and transparency within the team.
• A review of the backlog at daily standup meetings: This implies that the team is using the daily standup meetings as an opportunity to inspect the Sprint Backlog and adapt their plan accordingly. A review of the backlog at daily standup meetings can also help the team identify any impediments or risks that may affect their Sprint work.

References: 1: Scrum Guide, November 2020, p. 9 2: The Scrum Master as an Impediment Remover, Scrum.org, April 2016, 1 3: Navigating Impediments, Scrum.org, October 2020, 2 : Solving Impediments as a Scrum Team, Scrum.org, August 2018, 3 : Scrum Guide, November 2020, p. 10 : Scrum Guide, November 2020, p. 11

These two actions can help mitigate the risk of staff turnover during the course of a large multi-year project, because they can increase the satisfaction, motivation, and loyalty of the project team members. A recognition program can show appreciation and gratitude for the team members’ efforts and achievements, and provide positive reinforcement for their desired behavior. Training, mentoring and coaching can improve the skills and performance of the team members, and provide them with opportunities for learning and growth. These actions can also foster a positive and collaborative team culture, and enhance the trust and communication between the project manager and the team members. The other options are not effective actions to mitigate the risk of staff turnover, because they may not address the root causes or consequences of the risk, or they may create more problems or risks. Increasing the trained staff to create back-up for resources may not be feasible or cost-effective, and it may create redundancy, confusion, or conflict among the team members. Meeting with management to discuss dividing the project into smaller projects may not be possible or desirable, and it may affect the scope, quality, or benefits of the project. Convincing senior management to hire third-party staff may not be beneficial or reliable, and it may increase the complexity and risk of the project. References: Positive Reinforcement | PMI - Project Management Institute, [The Mindful Project Manager’s Guide To Team Motivation: 11 … - Planio].

 According to the PMBOK Guide, 7th edition, one of the principles of project management is to collaborate with stakeholders. This means that the project manager should maintain effective communication and engagement with the project stakeholders throughout the project life cycle, especially during changes and transitions. When the customer’s project manager changes during the final stage of a project, the project manager should review the latest project status report and update the stakeholders, including the new customer’s project manager, on the project progress, deliverables, issues, risks, and closure activities. This will help to ensure a smooth handover, alignment of expectations, and timely completion of the project closure process. The project manager should also seek feedback and confirmation from the stakeholders on the project outcomes and satisfaction. References: PMBOK Guide, 7th edition, page 9, Principle 2: Collaborate with Stakeholders; page 31, Section 2.3.1, Project Stakeholders; page 41, Section 2.5.2.1, Project Status Report.

According to the PMBOK Guide, the project manager should ensure that all the required approvals are received per the organizational procedures before implementing any project deliverables. This is part of the control quality process, which involves validating and verifying that the project deliverables meet the quality standards and requirements. By obtaining the necessary approvals, the project manager can avoid any liabilities, penalties, or disputes that may arise from the implementation of the project deliverables. The project manager should not rely on resolving defects, completing tasks, or documenting results alone, as these may not be sufficient to ensure that the project deliverables are acceptable and compliant with the organizational policies and regulations. References: PMBOK Guide, 7th edition, pages 237-238, 241-242.

 An agile project manager would like to convert the requirements document into epics, capabilities, features and stories in order to create a product backlog that can be prioritized and refined by the agile team and the product owner. The product backlog is a dynamic and evolving artifact that represents the customer’s needs and expectations for the product. To estimate the story duration, the agile project manager should use the team’s historical data and empirical evidence from previous iterations. The agile project manager should also involve the team members who will perform the work in the estimation process, as they have the best knowledge and expertise about the tasks and the complexity involved. The agile project manager should estimate the story duration in one iteration, as this is the timebox for delivering a potentially releasable product increment. Estimating the story duration in one iteration allows the agile project manager to plan and monitor the iteration progress, adjust the scope and priorities based on feedback and changes, and ensure that the team delivers value to the customer in a timely manner. Estimating the story duration in more than one iteration would introduce uncertainty and risk, as the team’s velocity, the customer’s requirements, and the product’s quality might change over time. Estimating the story duration in less than one iteration would not be feasible, as the team would not have enough time to complete the work and validate the results. References: PMBOK Guide, 6th edition, Section 6.2, 6.3, 6.4, 6.5, Agile Practice Guide, Section 3.2, 3.3, 4.2, 4.3

A project artifact is any document, deliverable, or output that is produced during the project life cycle. Examples of project artifacts include the project charter, the project management plan, the risk register, the issue log, the change log, the status reports, and the lessons learned. According to the Professional in Business Analysis Reference Materials1, project artifacts should be validated to ensure that they are accurate, complete, consistent, and up to date. Validation can be done by reviewing, inspecting, testing, or auditing the artifacts, and by involving the relevant stakeholders, such as the project team, the sponsor, the customer, or the quality assurance team.

In this scenario, the project manager notices that the version of the risk register used by the project team members is different from the one the project manager is using. This indicates that the risk register has not been validated properly, and that there is a lack of configuration management and version control. Configuration management is the process of identifying, tracking, controlling, and auditing the changes made to the project artifacts throughout the project life cycle. Version control is the technique of maintaining and labeling the different versions of the project artifacts, and ensuring that only the latest and approved version is used by the project team and stakeholders. According to the PMBOK Guide2, configuration management and version control are part of the Monitor and Control Project Work process, which is the responsibility of the project manager.

Therefore, the correct answer is C. Validated the project artifacts. The project manager should have validated the project artifacts, such as the risk register, to ensure that they are correct and current, and that they reflect the actual status and progress of the project. The project manager should have also implemented configuration management and version control procedures, such as using a configuration management system, a document management system, or a project management software, to track and manage the changes made to the project artifacts, and to communicate and distribute the latest versions to the project team and stakeholders.

The other options are not the best choices, because:

• Referred to the communications management plan: The communications management plan is a document that describes how the project information will be communicated to the project team and stakeholders, such as the frequency, mode, content, and responsibility of communication. While referring to the communications management plan could help the project manager understand how the project artifacts are shared and updated, it does not address the root cause of the issue, which is the lack of validation and configuration management of the project artifacts.
• Validated the issue log: The issue log is a document that records and tracks the issues that arise during the project, such as conflicts, errors, defects, or deviations. While validating the issue log could help the project manager identify and resolve the issues that affect the project performance, quality, or scope, it does not address the root cause of the issue, which is the lack of validation and configuration management of the project artifacts.
• Performed expert judgment: Expert judgment is a technique that involves using the knowledge and experience of experts to provide guidance, advice, or recommendations for the project. While performing expert judgment could help the project manager obtain insights and best practices for managing the project artifacts, it does not address the root cause of the issue, which is the lack of validation and configuration management of the project artifacts.

References:

• Professional in Business Analysis Reference Materials.
• A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Sixth Edition, Chapter 4: Project Integration Management.

 A self-organizing team is a team that has the authority and autonomy to decide how to perform their work, without being directed or controlled by external factors. A self-organizing team is able to adapt, collaborate, and innovate, and deliver value to the customer and the organization. According to the Professional in Business Analysis Reference Materials1, self-organizing teams are based on trust, collaboration, and empowerment of individuals.

In this scenario, a new team member is added to a self-organizing team, but the new team member is reluctant to speak and take part in team discussions or decisions. This could indicate that the new team member is not comfortable, confident, or familiar with the team culture, dynamics, or expectations. This could affect the team performance, cohesion, and satisfaction.

Therefore, the best two actions that the team should take to engage this new team member are:

• Revisit the team’s discussion on team behaviors and norms: This action can help the new team member to understand the team values, principles, and rules that guide the team’s work and interactions. It can also help the team to clarify and align their expectations, roles, and responsibilities, and to address any issues or conflicts that may arise. By revisiting the team behaviors and norms, the team can create a shared vision and a sense of belonging for the new team member, and foster trust and respect among the team members.
• Coach the new team member to improve engagement with the team: This action can help the new team member to develop the skills, knowledge, and confidence to participate and contribute to the team’s work and decisions. It can also help the new team member to receive feedback, support, and guidance from the team, and to learn from their experiences and best practices. By coaching the new team member, the team can empower and motivate the new team member, and enhance their performance and satisfaction.

The other options are not the best choices, because:

• Report to the project manager about the new team member’s behavior: This action can undermine the autonomy and self-organization of the team, and create a dependency and a hierarchy that may conflict with the team culture and values. It can also damage the trust and relationship between the team and the new team member, and make the new team member feel isolated, judged, or rejected. Instead of reporting to the project manager, the team should try to resolve the issue internally, and involve the project manager only if necessary or requested.
• Force the new team member to participate in activities that are considered easy: This action can demotivate and discourage the new team member, and make them feel undervalued, underestimated, or patronized. It can also prevent the new team member from developing their full potential and skills, and from delivering value to the team and the customer. Instead of forcing the new team member, the team should encourage and support the new team member, and assign them tasks that are challenging, meaningful, and aligned with their interests and abilities.
• Facilitate an open discussion on all ideas and perspectives: This action can be helpful and beneficial for the team in general, but it may not be enough or appropriate for the new team member, who may not feel ready or willing to share their ideas and perspectives with the team. It may also put pressure or stress on the new team member, and make them feel overwhelmed or intimidated by the team’s expectations or opinions. Instead of facilitating an open discussion, the team should create a safe and supportive environment for the new team member, and respect their pace and preferences.

References:

• Self-Organizing Teams: A Complete Guide.

The project manager should do first to manage the budget is to meet with the project team to analyze the actual cost to determine deviations. This is the first step in the control cost process, which involves monitoring the status of the project to update the project costs and manage changes to the cost baseline2. By analyzing the actual cost, the project manager can identify the causes and sources of the cost variance, and evaluate the impact and implications on the project performance and objectives. The project manager can also use various tools and techniques, such as earned value analysis, forecasting, and variance analysis, to measure and report the cost performance and status2. Based on the analysis, the project manager can then decide on the appropriate actions and responses to bring the project back on track, such as requesting additional funds, reducing scope, adjusting resources, or implementing corrective or preventive actions2.

Option A is not a good choice, because it is premature and passive. The project manager should not ask the project sponsor for assistance in getting the budget back on track before analyzing the actual cost and determining the deviations. The project manager should first understand the nature and extent of the cost variance, and then present the facts and data to the project sponsor, along with possible solutions and recommendations. The project manager should also demonstrate their own initiative and responsibility in managing the budget, rather than relying on the project sponsor to solve the problem.

Option C is not a good choice, because it is pessimistic and irresponsible. The project manager should not inform the stakeholders that the project will be finished over budget before analyzing the actual cost and determining the deviations. The project manager should first assess the situation and explore the options to improve the cost performance and meet the budget expectations. The project manager should also communicate the cost status and issues to the stakeholders in a timely and transparent manner, and seek their feedback and support, rather than delivering bad news without any justification or action plan.

Option D is not a good choice, because it is hasty and presumptuous. The project manager should not issue a change request including the analysis to increase the budget before analyzing the actual cost and determining the deviations. The project manager should first verify the accuracy and validity of the cost data, and evaluate the feasibility and necessity of increasing the budget. The project manager should also consider the impact of the change request on the project scope, schedule, quality, and stakeholder satisfaction, and obtain the approval of the change control board before implementing the change2.

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

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

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

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

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

 The project manager should ensure that the team has a common understanding of agile, as this is a key factor for the success of agile projects. Having a common understanding of agile means that the team members and stakeholders share the same vision, values, principles, and practices of agile, and can collaborate effectively and efficiently. Having a common understanding of agile also helps to avoid confusion, conflicts, and waste that may arise from using different agile methodologies or applying them inconsistently. The project manager should facilitate the creation of a common understanding of agile by providing training, coaching, mentoring, and guidance to the team and stakeholders, and by establishing clear and transparent communication channels and feedback loops. References:

• PMBOK Guide, 6th edition, page 27: “The project manager should ensure that all project stakeholders have a common understanding of the project objectives, approach, deliverables, and expected outcomes.”
• PMBOK Guide, 6th edition, page 28: “The project manager should ensure that the project team and other stakeholders are familiar with the chosen agile approach and practices, and that they receive the necessary training and coaching.”
• PMBOK Guide, 6th edition, page 29: “The project manager should foster collaboration among team members and stakeholders, and promote self-organization and empowerment within the team.”
• PMBOK Guide, 6th edition, page 30: “The project manager should establish an environment where feedback is welcome and encouraged, and where learning and improvement are continuous.”

According to the PMBOK Guide, a sprint cycle is a time-boxed iteration of a fixed duration that delivers a potentially releasable product increment. A sprint cycle consists of four events: sprint planning, daily scrum, sprint review, and sprint retrospective. The purpose of a sprint cycle is to create a rhythm of work that allows the team to deliver value to the customer in a predictable and sustainable way.

The PMI Guide to Business Analysis states that one of the roles of a project manager is to manage stakeholder expectations and ensure alignment of project objectives with business needs. The project manager is also responsible for facilitating communication and collaboration among the project team and other stakeholders, as well as resolving conflicts and issues that may arise during the project.

Therefore, if the project sponsor is consistently changing the prioritization of modular work packages, the project manager should set up a meeting with the sponsor to explain the importance of keeping a strict sprint cycle. The project manager should:

• Clarify the project scope and objectives, and how they are aligned with the business needs and the sponsor’s vision
• Explain the benefits of a sprint cycle, such as delivering value faster, improving quality, increasing feedback, and reducing risk
• Highlight the challenges and risks of changing the scope frequently, such as disrupting the team’s workflow, reducing their morale and motivation, increasing technical debt, and compromising the quality and usability of the product
• Negotiate with the sponsor to establish a clear and stable prioritization criteria for the work packages, and agree on a process for managing changes and requests
• Involve the project team and the product owner in the prioritization and planning process, and ensure their input and feedback are considered and valued
• Document and communicate the agreed scope, priorities, and changes to all the stakeholders, and monitor and control the project performance and progress

By setting up a meeting with the sponsor to explain the importance of keeping a strict sprint cycle, the project manager can:

• Build trust and rapport with the sponsor, and demonstrate their understanding and respect for the sponsor’s perspective and needs
• Educate the sponsor about the agile principles and practices, and how they can help achieve the project goals and deliver value to the customer
• Influence the sponsor to adopt a more collaborative and flexible approach to the project, and to respect the team’s autonomy and expertise
• Minimize the impact of scope changes on the project schedule, budget, quality, and risk
• Enhance the team’s morale and teamwork, and foster a positive and supportive work environment

References:

• PMBOK Guide. (2017). Sixth edition. Newtown Square, PA: Project Management Institute.
• PMI Guide to Business Analysis. (2017). Newtown Square, PA: Project Management Institute.
• How to Manage Scope Creep in Agile Projects. (2023). ProjectManager.com.
• How to Deal with Constantly Changing Requirements. (2023). Scrum.org.

Creating internal projects to provide internships for the students is a change in the project scope that requires approval from the customer and other stakeholders. Therefore, the project manager should create a change request with the scope of the new internal projects and submit it to the Perform Integrated Change Control process1. The change request should include the rationale, benefits, risks, and impacts of the proposed change on the project objectives, deliverables, schedule, cost, quality, and resources. The project manager should also update the project management plan and other relevant documents to reflect the change in scope.

To plan and execute the new internal projects, the project manager should create a work breakdown structure (WBS) of the new scope with the internal projects2. A WBS is a hierarchical decomposition of the project scope into manageable deliverables and work packages. A WBS helps the project manager to define, organize, and monitor the project work, as well as to allocate resources, assign responsibilities, and estimate costs and durations. The project manager should involve the project team and the interns in creating the WBS to ensure their buy-in and commitment.

To ensure that the internal projects meet the customer’s expectations and the project’s quality standards, the project manager should manage the quality of the delivery3. Quality management involves planning, implementing, and controlling quality activities to ensure that the project deliverables conform to the requirements and specifications. The project manager should use quality tools and techniques, such as quality checklists, audits, inspections, testing, and reviews, to measure and improve the quality of the internal projects. The project manager should also document and communicate the quality results and feedback to the project team, the interns, the customer, and other stakeholders.

References:

• How To Successfully Perform Integrated Change Control
• Work Breakdown Structure (WBS) in Project Management
• Quality Management - Project Management Institute

A hybrid approach is a combination of two or more project management methodologies, such as Waterfall and Agile, that aims to create a new and better model for a specific project123. A hybrid approach can be beneficial for projects that have high complexity, uncertainty, and changing requirements, as it allows for more flexibility, speed, and customer satisfaction. However, a hybrid approach also requires a high level of collaboration and communication among the project team members, as they need to adapt to different processes and practices depending on the project phase and situation. Therefore, a project manager who is experienced in agile should allocate time to mentor the team on how to work in a hybrid way, such as by explaining the benefits and challenges of the approach, providing guidance and feedback, facilitating team meetings and retrospectives, and resolving any conflicts or issues that may arise. This will help the team to develop the skills and mindset needed to work effectively and efficiently in a hybrid environment. References: 

 According to the PMBOK Guide, 7th edition, one of the principles of project management is to focus on value. This means that the project manager should ensure that the project delivers the most valuable outcomes to the stakeholders, especially the customer. In an agile project, the sprint goal is a short-term objective that aligns with the customer’s needs and expectations. The sprint backlog is a list of tasks that the development team commits to complete within the sprint to achieve the sprint goal. If the developers want to deviate from the sprint backlog and work on something else, the project manager should remind them of the importance of focusing and meeting the sprint goal. The project manager should also facilitate a discussion with the product owner and the development team to clarify the priority and value of the tasks in the sprint backlog and the refactoring work. The project manager should help the team to balance the trade-offs between delivering the sprint goal and improving the quality of the product. References: PMBOK Guide, 7th edition, page 9 (Principles of Project Management); page 71 (Focus on Value); page 137 (Agile Project Delivery); page 139 (Sprint Goal and Sprint Backlog)

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

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

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

• Provide the team with the necessary tools, resources, and guidance to conduct the feasibility and testing activities.
• Remove any impediments or obstacles that might hinder the team’s progress or performance.
• Encourage the team to collaborate and communicate effectively with each other and with the customer.
• Facilitate the team’s learning and improvement through feedback, reflection, and experimentation.
• Recognize and appreciate the team’s efforts and achievements.

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

The other options are not the best choices, because:

• Amend the project budget to include MVP testing: This option implies that the project manager is not following the approved schedule management plan, and is making changes to the project scope, cost, and baseline without proper justification or authorization. This could create confusion, conflict, or resistance among the project stakeholders, and jeopardize the project success. Moreover, this option does not reflect servant leadership, as it does not address the needs or interests of the team or the customer.
• Submit a change request to the project sponsor for accelerated testing: This option implies that the project manager is not following the agile principles and practices, and is relying on a formal and bureaucratic process to manage changes in the project. This could slow down the project delivery, reduce the team’s autonomy and flexibility, and undermine the customer’s satisfaction and trust. Moreover, this option does not reflect servant leadership, as it does not empower or facilitate the team to find the MVP.
• Develop the product as per the schedule to perform integration and testing: This option implies that the project manager is ignoring the team’s evaluation and feedback, and is sticking to a rigid and predetermined plan to deliver the product. This could result in a product that does not meet the customer’s needs or expectations, or that has unnecessary or unwanted features. Moreover, this option does not reflect servant leadership, as it does not support or involve the team in finding the MVP.

References:

• Servant Leadership in Project Management.

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

 The project manager should mentor the new team member on the methodology the project team is using. The new team member may be used to the Scrum approach, which involves daily standup meetings where each team member reports their progress, challenges, and plans for the day. However, the project team may be following a different methodology that does not require such frequent and informal communication. The project manager should explain to the new team member the rationale, benefits, and expectations of the chosen methodology, and how it differs from Scrum. The project manager should also provide feedback and guidance to the new team member on how to adapt to the new work environment and collaborate effectively with the rest of the team. By mentoring the new team member, the project manager can help them integrate into the project team and reduce the frustration and confusion among the team members123. References: = PMBOK® Guide, Sixth Edition, pages 349-350, 368-369; Agile Practice Guide, pages 28-29, 50-51; How to Mentor a New Team Member.

 The project manager should evaluate the consequences and meet with the client to explain the possible scenarios. This is because the project manager needs to balance the competing demands of scope, time, cost, quality, and stakeholder satisfaction. The project manager should not hire the resource without the client’s approval, as this would violate the terms of the contract and the trust relationship. The project manager should not ask the client for a meeting and explain that the task will not be performed, as this would compromise the project objectives and quality standards. The project manager should not try to accomplish the task internally by leveling resources from other projects, as this would create risks and dependencies for both projects and potentially affect their performance. The project manager should evaluate the consequences of not hiring the external resource, such as the impact on the project schedule, quality, scope, and risks. The project manager should also identify alternative solutions, such as negotiating with the client, finding another resource, or modifying the project plan. The project manager should then meet with the client and explain the possible scenarios, highlighting the benefits and drawbacks of each option. The project manager should seek the client’s input and feedback and try to reach a mutually agreeable solution that satisfies the project requirements and the client’s expectations. References: PMBOK Guide, 6th edition, section 4.2, page 89, PMP Exam Prep, 10th edition, page 106

According to the PMBOK Guide, the project manager should facilitate the removal of impediments that may hinder the team’s progress and performance. The project manager should also encourage the team to collaborate and self-organize to find the best solutions for the project issues. Therefore, the project manager should conduct a brainstorming session with the team to identify the root cause of the technical issue, generate possible alternatives, and select the most suitable one. The project manager should then add the solution to the current sprint backlog and monitor its implementation and effectiveness. References: PMBOK Guide, 6th edition, pages 18, 37, 273, 287.

According to the PMBOK Guide, the project manager should select the most appropriate life cycle approach for the project based on various factors, such as the project objectives, scope, complexity, uncertainty, risk, delivery strategy, stakeholder involvement, and team preferences. The project manager should not select a life cycle approach based solely on the team’s experience, as this may not suit the project characteristics and requirements. The project manager should not register all requirements into a backlog or split the requirements into two separate projects before determining the best way to manage the project. These actions may be done later, depending on the chosen life cycle approach. References: PMBOK Guide, 7th edition, pages 45-46, 49-50.

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

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

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

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

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

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

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

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

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

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

• One possible technique to prioritize product backlog items is the MoSCoW method, which stands for Must have, Should have, Could have, and Won’t have. This method helps to classify the items based on their value, urgency, and dependency. Product Backlog Explained [+ Examples] | Atlassian
• Another possible technique is the Kano model, which categorizes the items based on how they satisfy the customer’s needs and expectations. The Kano model distinguishes between five types of items: Must be, One dimensional, Attractive, Performance, and Indifferent. 4 Product Backlog Prioritization Techniques That Work - Perforce Software
• A third possible technique is the Cost of Delay, which measures the economic impact of delaying the delivery of an item. The Cost of Delay can be calculated by multiplying the value, urgency, and size of the item. The higher the Cost of Delay, the higher the priority. How To Do Backlog Prioritization Easily [Complete Guide] - Agile Digest

According to the PMBOK® Guide, quality management is the process of ensuring that the project meets the needs and expectations of the stakeholders1. Quality management involves planning, managing, and controlling quality activities throughout the project life cycle1. A predictive approach to quality management is based on the assumption that the project requirements and scope are well-defined and stable, and that the quality standards and criteria are established upfront1. A predictive approach relies on sequential phases, such as initiation, planning, execution, monitoring and controlling, and closing, and evaluates the quality of the products at the end of each phase1. However, a predictive approach may not be suitable for projects that face high uncertainty, complexity, or change, as it may result in rework, delays, or customer dissatisfaction12.

A hybrid approach to quality management is a combination of predictive and adaptive methods, such as agile, that allows the project manager to tailor the quality practices to the specific needs and characteristics of the project23. A hybrid approach enables the project manager to balance the trade-offs between predictability and flexibility, and to deliver value to the customer in an iterative and incremental manner23. A hybrid approach requires the project manager to understand the context and interdependencies of the process from the team members and then define improvements23. By doing so, the project manager can leverage the expertise and feedback of the team members, who are closest to the work and the customer, and identify the best ways to enhance the quality of the products and the process23. The project manager can use various techniques to understand and improve the process, such as process mapping, value stream mapping, root cause analysis, and continuous improvement123. References:

• 1: PMBOK® Guide – 4th Edition, Chapter 8: Quality Management
• 2: A Guide to Hybrid Project Management: Blending Agile and Waterfall
• 3: How to Do Hybrid Right

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

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

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

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

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

A hybrid approach combines predictive and adaptive elements to deliver projects. In a hybrid approach, the project manager can break down the requirements into smaller and manageable chunks, and prioritize them based on their value and risk. This way, the project manager can deliver the most important and uncertain requirements first, and get feedback from the stakeholders and customers. This feedback can help clarify the unclear requirements and improve the quality of the project deliverables. The project manager can also adjust the delivery plan based on the changing requirements and environment. A hybrid approach is suitable for projects that have some degree of uncertainty and complexity, and that need to respond to changing customer needs and expectations. References:

• A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Seventh Edition, Chapter 2: Value Delivery System, Section 2.3: Delivery Approaches, pp. 31-35
• Project Management Professional (PMP) Handbook, Section 2.2: PMP Exam Content Outline, Domain II: Process, Task 1: Plan and manage project scope, pp. 14-15
• Hybrid Project Management: What It Is & How to Implement It, by Simplilearn, published on February 10, 2020

This answer is based on the PMI Guide to Business Analysis, which is one of the reference materials for the PMI-PBA exam1, and the PMP Examination Content Outline, which is based on the Project Management Professional (PMP) objectives and content2. According to these sources, one of the key principles of agile project management is to empower the team to self-organize and self-manage their work, rather than assigning tasks or dictating solutions34. Empowering the team means giving them the authority, responsibility, and accountability to make their own decisions on how to perform the tasks, within the agreed-upon scope, quality, and schedule criteria34. Empowering the team also means providing them with the necessary resources, tools, information, and support to enable them to deliver value to the customer34. Empowering the team can promote collaboration, innovation, ownership, motivation, and satisfaction among the team members, as well as improve the quality and speed of the project outcomes34. The other options are not correct because they do not foster empowerment and accountability among the team. Assigning the tasks individually based on the role of the team member may ensure expertise on the subject, but it may also create silos, dependencies, and bottlenecks in the team, and reduce the flexibility and adaptability of the team to changing customer needs34. Encouraging and assigning the team to perform demos of their products or software with the customers may increase the feedback and validation of the project deliverables, but it may not necessarily empower the team to make their own decisions on how to perform the tasks, especially if the functional manager or the project manager still controls the scope, quality, and schedule of the project34. Encouraging the team to keep the product owner involved when choosing ways to resolve the given task may enhance the alignment and communication between the team and the product owner, but it may also undermine the autonomy and creativity of the team, and create a dependency on the product owner for every decision34. References:

• PMP Examination Content Outline - January 2021
• The PMI Guide to Business Analysis
• Business Analysis for Practitioners: A Practice Guide
• Professional in Business Analysis Reference Materials

According to the PMBOK Guide, the project manager should manage stakeholder expectations by communicating and working with stakeholders to meet their needs and address issues as they occur. This includes understanding the stakeholder’s concerns, interests, and expectations, and providing timely and accurate information to keep them informed and satisfied. By working to understand the key stakeholder’s concerns and providing feedback in regular project status reports, the project manager can maintain a positive relationship with the stakeholder and avoid unnecessary interruptions and conflicts. References: PMBOK Guide, 6th edition, page 540-541, section 13.3.2.4 Manage Stakeholder Engagement: Data Analysis.

The risk register is an artifact that records the identified risks, their probability and impact, their status, and their response plans. It also tracks the risk triggers, which are the indicators or warning signs that a risk is about to occur. By sharing the risk register with the stakeholder, the project manager can show when a risk may potentially become an issue, based on the risk triggers and the risk status. The risk register also helps the project manager and the stakeholder to monitor and control the risks and their impacts throughout the project life cycle. References:

• The PMI Guide to Business Analysis Includes The Standard for Business Analysis, Chapter 4: Business Analysis Planning and Monitoring, Section 4.3.4: Plan Risk Management
• Business Analysis for Practitioners: A Practice Guide, Chapter 4: Planning the Business Analysis Approach, Section 4.6: Risk Management Plan
• Business Analysis Techniques: 72 Essential Tools For Success, Chapter 6: Business Analysis Planning and Monitoring, Section 6.6: Risk Analysis and Management
• Seven Steps to Mastering Business Analysis, Chapter 7: Requirements Analysis, Section 7.4: Risk Analysis

The project manager should ask an experienced team member to coach the new team member, as this is a strategy for developing the skills and performance of the new team member. According to the PMI website, coaching is one of the interpersonal and team skills that a project manager should have. Coaching is a process of providing guidance, feedback, and support to help someone improve their abilities and achieve their goals. By asking an experienced team member to coach the new team member, the project manager can leverage the knowledge and expertise of the existing team, and foster a culture of learning and collaboration. The project manager can also monitor the progress and results of the coaching, and provide recognition and rewards to both the coach and the coachee.

The other options, asking the new team member to follow the team ground rules, asking an experienced team member to identify a replacement, or asking the new team member to reassess their own capabilities, are not the best ways to deal with a new team member who is not making the expected progress on an assigned task. Asking the new team member to follow the team ground rules may help the new team member to understand the expectations and norms of the team, but it does not address the specific issues or challenges that the new team member is facing. Asking an experienced team member to identify a replacement may be a drastic and demotivating measure, that may not be feasible or fair to the new team member. Asking the new team member to reassess their own capabilities may be a constructive feedback, but it does not provide any support or assistance to the new team member.

References: 1 Interpersonal and Team Skills - Project Management Institute 2 A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 9.4.2.4 3 Business Analysis for Practitioners: A Practice Guide, Chapter 5.3.3

 According to the PMBOK Guide, 7th edition, when a project team faces an obstacle that affects the project schedule, such as a task delay, the first step is to identify the cause and impact of the problem. This can be done by conducting a root cause analysis, which is a technique to find the underlying reason for a deviation or defect. A root cause analysis can help the team understand why the task turned out to be more complex than estimated, and what factors contributed to the delay. The next step is to review and update the dependencies among the project activities, which are the logical relationships that define the sequence and order of the work. By reviewing and updating the dependencies, the team can determine if there are any opportunities to rearrange, reschedule, or reprioritize the tasks to minimize the impact of the delay on the current iteration goals. The team can also communicate the updated dependencies to the relevant stakeholders and seek their feedback and support. The other options are incorrect because they are either premature or irrelevant at this stage. Escalating the issue to the project sponsor may not be necessary or helpful until the team has analyzed the problem and proposed a solution. Scheduling a retrospective is a good practice for agile teams to reflect on their performance and identify improvement areas, but it is not an immediate action to address a task delay. Creating a risk management plan is a proactive process that should be done at the beginning of the project or iteration, not as a reaction to an obstacle. References: PMBOK Guide, 7th edition, pages 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300; Dealing with delays; Project Management Professional (PMP)® Articles

 The project manager should first meet with the project team to understand the issue and define actions. This is because the project manager needs to analyze the root cause of the problem, identify the impact on the project scope, schedule, cost, and quality, and determine the best course of action to resolve the issue. Raising a change request, escalating the issue, or conducting a quality audit are possible actions that the project manager may take after meeting with the project team, depending on the outcome of the analysis. However, they are not the first steps that the project manager should take in this situation. References: = PMBOK Guide, 6th edition, page 152, section 4.3.1.1 (Work Breakdown Structure); page 121, section 4.2.3.1 (Project Scope Statement); page 115, section 4.1.3.1 (Project Charter); page 112, section 4.1.2.2 (Project Sponsor)

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.

References: (Professional in Business Analysis Reference Materials source and documents)

• Agile Testing: A Practical Guide For Testers And Agile Teams, Lisa Crispin and Janet Gregory, Addison-Wesley Professional, 2009
• Scrum Testing: A Detailed Guide to Testing on an Agile Team, Testim, Accessed on January 29, 2024
• Agile Testing Best Practices & Why They Matter, Atlassian, Accessed on January 29, 2024

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

 A virtual workspace is a tool that allows team members to collaborate and communicate online, regardless of their physical location. A virtual workspace can help the project manager and the team to share information, documents, updates, feedback, and ideas in real time. A virtual workspace can also enhance the team’s trust, cohesion, and productivity. By encouraging all team members to use a virtual workspace, the project manager can ensure that everyone is on the same page and has access to the latest project information. The project manager can also monitor the team member’s progress and provide support if needed12.

Talking to the team member about their engagement and taking appropriate action is another option that can help the project manager in this situation. The project manager should try to understand the reasons behind the team member’s lack of communication and details, such as lack of motivation, skills, resources, or clarity. The project manager should also provide constructive feedback and guidance to the team member, and set clear expectations and goals for their performance. The project manager should also follow up with the team member regularly and recognize their achievements. If the team member does not improve their communication and details, the project manager may need to escalate the issue to the functional manager or consider reassigning the work to another resource34. References: = 12 Project Management Strategies To Improve Efficiency, Strategy 6: Use a virtual workspace; 8 Steps for Better Issue Management, Step 5: Communicate with the team; PMBOK® Guide, Sixth Edition, pages 368-369, 376-377; Agile Practice Guide, pages 28-29, 50-51.

 Knowledge transfer is the process of sharing relevant and valuable information, skills, and experiences among project team members and stakeholders. It is essential for agile projects, as they require frequent collaboration, communication, and feedback among the project team and other parties. Knowledge transfer can help the new team member to understand the project vision, scope, objectives, deliverables, requirements, and processes, as well as the roles and responsibilities of the project team and the customer. It can also help the new team member to learn from the best practices, lessons learned, and challenges faced by the previous team member and the rest of the team. The project manager should schedule knowledge transfer sessions with the new team member, involving the previous team member (if possible), the other team members, the customer representative, and any other relevant stakeholders. The knowledge transfer sessions should be interactive, engaging, and tailored to the specific needs and interests of the new team member. The project manager should also assign less complex tasks to the new team member, to allow them to gain confidence, competence, and familiarity with the project work and the agile approach. The project manager should provide feedback, coaching, and support to the new team member, and monitor their progress and performance. This is part of the Manage Team process, which aims to optimize the project team’s performance and interaction. The other options are not the best choices because they do not facilitate effective knowledge transfer and integration of the new team member into the project team. Assigning the new team member the same tasks that were assigned to the previous team member who they replaced (option A) may be unrealistic, as the new team member may not have the same level of skill, experience, and knowledge as the previous team member. It may also create confusion, frustration, and conflict among the team members and the customer. Sending technical documentation to the new team member and scheduling training for the next iteration (option C) may be helpful, but it is not sufficient to provide the new team member with the contextual and practical knowledge that they need to perform effectively on the project. It may also delay the new team member’s contribution and involvement in the project work. Having the new team member complete all of the company’s mandatory training (option D) may be a requirement, but it is not specific to the project and may not cover the agile principles and techniques that are relevant for the project activities. References:

• Project Management Professional (PMP) Reference Materials:
• Professional in Business Analysis (PBA) Reference Materials:

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

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

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

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

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

Skipping project retrospectives can have negative impacts on the project performance, quality, and team morale. Project retrospectives are important for identifying and analyzing the strengths, weaknesses, opportunities, and threats of the project, and for implementing corrective and preventive actions to improve the project outcomes and processes. By reducing the time for preparation and discussion, the project manager could cause the following issues:

• A lot of discussions that yield no results or possibly too many results: Without proper preparation, the project manager and the team may not have a clear agenda, objectives, and scope for the retrospective. This could lead to unfocused, irrelevant, or redundant discussions that do not produce any meaningful insights or action items. Alternatively, the project manager and the team may try to cover too many topics or issues in a short time, resulting in superficial, incomplete, or overwhelming analysis and recommendations.
• A focus on the negative and a disinterest in further improvements: Without sufficient time for discussion, the project manager and the team may not be able to explore the root causes, impacts, and solutions of the project problems in depth. This could lead to a negative and blame-oriented attitude, where the team members only focus on the failures and faults of the project, and do not appreciate the successes and achievements. This could also lead to a loss of interest and motivation for further improvements, as the team members may feel that the retrospective is a waste of time, or that the project issues are too complex or difficult to resolve.

The attendance list is important because it is evidence that risk review meetings were held with the appropriate project team members, as this is a requirement of the risk management plan. The risk management plan defines how risk management activities will be performed, recorded, and monitored throughout the project, and it also identifies the roles and responsibilities of the project team members and stakeholders in relation to risk management. The attendance list shows who participated in the risk review meetings, which are periodic meetings to review and update the risk register, the risk response plan, and the risk metrics. The attendance list also helps to ensure that the risk review meetings are effective and efficient, as it allows the project manager to follow up with the attendees on their assigned actions and to communicate the results of the meetings to the relevant stakeholders. References:

• PMBOK Guide, 6th edition, page 414: “The risk management plan is a component of the project management plan that describes how risk management activities will be structured and performed.”
• PMBOK Guide, 6th edition, page 415: “The risk management plan should document the roles and responsibilities of individuals and groups for each risk management process, as well as their availability, competency, and authority levels.”
• PMBOK Guide, 6th edition, page 443: “Risk review meetings are held periodically to review and update the risk register, the risk response plan, and the risk metrics. The frequency of these meetings is determined by the project manager and the project team based on the project needs and the level of risk exposure.”
• PMBOK Guide, 6th edition, page 444: “The project manager should document the results of the risk review meetings and communicate them to the project team and other stakeholders as appropriate.”

The best option for the project manager in this situation is to provide mentoring to the newly appointed team leader. Mentoring is a process of using experienced members of the organization to provide personal support and guidance to less experienced members of the staff. Mentoring can help the team leader to develop the necessary skills and competencies to manage the team effectively, to overcome challenges, and to achieve the project goals. Mentoring can also foster a positive and collaborative work environment, where the team leader and the team members can learn from each other and share feedback. The project manager can use various techniques and tools to mentor the team leader, such as setting clear expectations, providing regular coaching, giving constructive feedback, sharing best practices, facilitating problem solving, and recognizing achievements. The other options are not as effective as option D. Option A is not feasible, as it may not be possible to find a senior team leader who is available and willing to take over the project. Option B is not proactive, as it only reports the problem, but does not offer any solution. Option C is not empowering, as it undermines the team leader’s authority and responsibility, and may create resentment and demotivation among the team members. References: (Professional in Business Analysis Reference Materials source and documents)

• PMBOK® Guide – Sixth Edition, Chapter 9: Project Resource Management, Section 9.4.2.3: Interpersonal and Team Skills1
• Mentoring - Key Competency for Program and Project Professionals2
• How to Improve Your Project Leadership with Coaching and Mentoring3

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

• Reviewing the project charter may help the project manager clarify the project scope, objectives, and high-level requirements, but it does not address the specific source of the disagreement among the stakeholders2.
• Performing a stakeholder analysis may help the project manager identify the stakeholders, their roles, expectations, influence, and communication needs, but it does not address the specific source of the disagreement among the stakeholders3.
• Holding a team-building event may help the project manager improve the team morale, trust, and collaboration, but it does not address the specific source of the disagreement among the stakeholders4. References: 1: PMBOK® Guide, Sixth Edition, Chapter 9.5.2.1, Conflict Management 2: PMBOK® Guide, Sixth Edition, Chapter 4.1.3.1, Project Charter 3: PMBOK® Guide, Sixth Edition, Chapter 13.1.3.1, Stakeholder Analysis 4: PMBOK® Guide, Sixth Edition, Chapter 9.4.2.4, Team-Building Activities

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

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

• One possible technique to deal with project delays is to use an iterative process, which involves breaking down the project into smaller cycles or iterations, each with its own planning, execution, and evaluation. This allows the project team to adapt to changing requirements, feedback, and risks, and deliver value incrementally. How to use an iterative process for projects | monday.com Blog
• Another possible technique is to conduct regular retrospectives, which are meetings where the project team reflects on what went well, what went wrong, and what can be improved in the next iteration. Retrospectives help to identify the root causes of delays, learn from mistakes, and implement corrective actions. 10 Tips to Handle Project Delays - Gantt Chart GanttPRO Blog
• A third possible technique is to use risk management strategies, such as avoidance, mitigation, transfer, or acceptance, to deal with the potential or actual threats that cause delays. Risk management involves identifying, analyzing, prioritizing, and responding to risks throughout the project lifecycle. 10 Causes of Projects Delays and How to Manage Them | ActiveCollab

According to the PMBOK Guide, the project lead should manage stakeholder expectations and engagement throughout the project life cycle. The project lead should also support the agile team’s decisions and authority regarding the product scope and releases. The agile team is responsible for delivering valuable and functional products to the customer in short iterations. Therefore, the project lead should work with the stakeholder to understand what the concerns are while at the same time conveying the benefits of incremental deliveries. The project lead should also communicate the value proposition and the vision of the product to the stakeholder and seek their feedback and collaboration. References: PMBOK Guide, 6th edition, pages 18, 37, 51-52, 286-287.

According to the PMBOK Guide, the project closing process group consists of two processes: close project or phase and close procurements. The close project or phase process involves confirming that the project or phase scope and requirements have been met, obtaining formal acceptance of the final product, service, or result from the customer, and transferring the ownership and responsibility of the deliverables to the assigned stakeholders. The close procurements process involves completing and settling each contract, including resolving any open items, and closing each contract applicable to the project or phase. Therefore, the project manager should review the deliverable requirements, check the customer approval criteria, and proceed accordingly to close the project or phase. Asking the customer to issue a change request, meeting with the customer to reach agreement on the scope, or contacting the project sponsor for help are not appropriate actions during the closing process, as they imply that the project scope is not finalized or agreed upon, which should have been done during the planning and executing processes. References: PMBOK Guide, Sixth Edition, pages 123-124, 377-378; PMI-PBA Guide, First Edition, pages 209-210.

This is because the project manager should take action to resolve the issues that are hindering the project progress, rather than avoiding them, escalating them, or delaying them. Implementing plans to remove the obstacles may involve using a variety of problem-solving strategies, such as root cause analysis, brainstorming, negotiation, conflict resolution, and risk management3 .

The other options are not the best choices because:

• A. Have the project team work on other activities: This is a passive and ineffective approach that does not address the root cause of the problem. It may also create more issues in the future, such as rework, schedule delays, scope creep, and quality defects.
• C. Escalate to the project steering committee: This is a last resort option that should only be used when the project manager has exhausted all other means to remove the obstacles. Escalating to the project steering committee may indicate a lack of authority, responsibility, or competence of the project manager. It may also create unnecessary bureaucracy, conflict, and delay in the decision-making process.
• D. Prioritize the obstacles for resolution: This is a necessary but not sufficient step to remove the obstacles. Prioritizing the obstacles helps the project manager to focus on the most critical and urgent issues, but it does not guarantee that they will be resolved. The project manager still needs to implement plans to remove the obstacles after prioritizing them.

I hope this helps you with your question. If you need more information, you can visit the following links:

• [PMI’s Project Management Professional (PMP) certification]
• [PMI’s A Guide to the Project Management Body of Knowledge (PMBOK Guide), 7th edition]
• 6 Obstacles to Any Project and How to Clear Them
• Impediments, Obstacles, and Blockers: How to Address and Remove Them
• 5 Ways to Overcome Project Obstacles

 A cross-functional team is a group of people with different skills and expertise who work together to achieve a common goal. A cross-functional team is beneficial for agile projects, as it enables the team to deliver value faster, collaborate better, and adapt to changing requirements and customer feedback. When a planned activity becomes more complex, the best approach is to have the cross-functional team work together to complete the activity, as this allows the team to leverage their diverse skills and knowledge, share ideas and solutions, and overcome challenges and risks. The team can also communicate and coordinate more effectively, and ensure that the quality and scope of the activity are met. This is part of the Execute Project Work process, which aims to perform the activities that produce the project deliverables. The other options are not the best choices because they do not utilize the full potential and capacity of the cross-functional team. The team facilitator gets support from external team members (option A) may introduce more complexity and dependency, as the external team members may not be familiar with the project context, objectives, and processes. The team members bring in a specialist to help them (option B) may be helpful, but it may also create a bottleneck and dependency, as the specialist may not be available or accessible when needed. The product owner moves it to the product backlog (option C) may delay the delivery and value of the activity, as the product backlog is a prioritized list of features and requirements that the team will work on in future iterations. It may also create dissatisfaction and frustration among the team and the customer. References:

• Project Management Professional (PMP) Reference Materials:
• Professional in Business Analysis (PBA) Reference Materials:

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

 The project manager should encourage frequent small team meetings with two or three team members to overcome the challenge of finding a suitable time for the daily standup. This is because the daily standup is an important agile practice that helps the team to coordinate their work, share progress, identify impediments, and plan the next steps. However, when the team members are located in different time zones, it can be difficult to schedule a common time that is convenient for everyone. Therefore, the project manager should facilitate smaller and more frequent meetings among the team members who are in the same or adjacent time zones, and ensure that the information is communicated and documented across the whole team. This way, the project manager can maintain the benefits of the daily standup while respecting the team members’ availability and preferences.

The other options are not correct because they do not address the issue of coordination and communication among the team members. Giving up the daily standup and replacing it with a daily report would reduce the interaction and collaboration among the team members, and might lead to delays, misunderstandings, and conflicts. Letting the team members decide themselves if they want to join the meeting would create inconsistency and confusion, and might result in some team members being left out or uninformed. Requiring all team members to join the daily standup regardless of the meeting time would impose an unfair and unrealistic burden on some team members, and might affect their motivation, productivity, and quality of work. References: Agile Practice Guide, section 4.2.1, page 47, PMP Exam Prep, 10th edition, page 100

The project manager should collaborate with the compliance team member to review and prioritize the requirement’s delivery, as this is a way to manage the change request and ensure that the project meets the compliance standards and expectations. The project manager should also communicate the impact of the change on the project scope, schedule, cost, and quality to the project sponsor and other stakeholders, and obtain their approval and support. The project manager should not ask the team to include the compliance requirement in the current sprint and deliver it (choice A), as this would disrupt the sprint planning and execution, and create scope creep and quality issues. The project manager should not add the new compliance requirement to the backlog as the technical team does not have any capacity (choice B), as this would delay the delivery of the compliance requirement and expose the project to legal and regulatory risks. The project manager should not include the compliance lead in the stakeholders list and wait for the next status meeting (choice C), as this would not address the urgency and importance of the compliance requirement, and it would not involve the compliance lead in the decision-making and problem-solving process. References:

• PMBOK Guide, 6th edition, page 115: “A change request is a formal proposal to modify any document, deliverable, or baseline.”
• PMBOK Guide, 6th edition, page 119: “The project manager should review all change requests, assess their impact on the project, and either approve them or submit them to the change control board (CCB) or other decision-making authority for approval or rejection.”
• PMBOK Guide, 6th edition, page 120: “The project manager should communicate the approved change requests to the project team and other stakeholders, and update the project management plan and other project documents accordingly.”
• PMBOK Guide, 6th edition, page 39: “Compliance requirements are the set of standards or regulations that the project must adhere to, such as health, safety, security, performance, environmental, or quality standards.”

An implementation strategy is a document that describes the necessary steps for the execution of a project1. An implementation strategy enables the project manager to manage the changes required with minimum disruption to the organization and its various stakeholders, also addressing the concerns of stakeholders outside the project team2. Before developing an implementation strategy, the project manager should review the business case and consider the environmental and regulatory factors that may affect the project in the new country, such as political, economic, social, technological, legal, and environmental aspects3. The project manager should also identify the high-level risks and assumptions that may impact the project scope, schedule, cost, quality, and resources4. These factors will help the project manager to define the project objectives, deliverables, scope, and requirements, as well as to select the appropriate project management methodology, tools, and techniques for the project.

Evaluating the environmental and regulatory factors and identifying high-level risks and assumptions should be considered first when developing an implementation strategy, as they provide the foundation for the project planning and execution. Acquiring project resources from the new country, monitoring the risks closely, and ensuring the project sponsors’ agreement are important activities, but they should be done after the initial assessment of the project environment and context.

References:

• 1: What Is an Implementation Plan? (Template & Example Included)(https://www.projectmanager.com/blog/implementation-plan)
• 2: Implementation Planning - the Critical Step | PMI(https://www.pmi.org/learning/library/implementation-planning-critical-step-5118)
• 3: Budget Proposal Templates: 5 Steps to Secure Funding [2023] • Asana(https://asana.com/resources/project-integration-management)
• 4: PMBOK Guide, 6th edition, page 395
• : PROJECT MANAGEMENT IMPLEMENTATION - PMAlliance, Inc(https://pm-alliance.com/project-management-implementation/)

 The project manager should establish dialogue with stakeholders on the project constraints, assumptions, and critical inputs, as this is a key activity of the Identify Stakeholders process1. By engaging with the stakeholders, the project manager can understand their needs, expectations, interests, and influence levels, as well as identify any potential issues or risks that may affect the project. This will help the project manager to develop an appropriate stakeholder engagement plan and communication strategy, as well as to manage the stakeholder expectations and relationships throughout the project life cycle. Examining the plans, processes, policies, and knowledge that are specific to the organization undertaking the project (option A) is part of the Develop Project Charter process2, which is performed before the Identify Stakeholders process. This activity may help the project manager to understand the organizational context and environment, but it does not address the specific concerns of the external stakeholders. Convincing senior management to close the project since the project lacks sponsorship and is considered to be high risk (option C) is not a viable option, as it contradicts the project manager’s role and responsibility to initiate, plan, execute, monitor, and close the project. Moreover, it does not consider the potential benefits and value of the project, nor the possible ways to mitigate the risks and challenges. Hosting a project team meeting, then updating the risk register and the project management plan (option D) is an activity of the Monitor and Control Project Work process3, which is performed after the project has been planned and executed. This activity may help the project manager to track the project performance and implement corrective actions, but it does not address the specific concerns of the external stakeholders. References:

• 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Project Management Institute, Inc., 2017, p. 513.
• 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Project Management Institute, Inc., 2017, p. 77.
• 3: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Project Management Institute, Inc., 2017, p. 95.

The project manager should prioritize and estimate the milestones for the high-level requirements based on historical data, as this is a way to initiate the project planning process and align the project with the program objectives. The project manager should also use progressive elaboration and rolling wave planning techniques to refine the project scope, schedule, and cost as more information becomes available from the other projects within the program. The project manager should not escalate to the management team to increase the timeline (choice A), as this would imply that the project manager is not able to manage the project uncertainty and complexity. The project manager should not wait for the other project estimates before planning the schedule (choice B), as this would delay the project initiation and execution, and create dependencies on external factors. The project manager should not ask the PMO to estimate the tasks for all the projects and share the project management plan (choice D), as this would undermine the project manager’s authority and responsibility, and create confusion and inconsistency among the project teams and stakeholders. References:

• PMBOK Guide, 6th edition, page 17: “Projects within a program are related through the common outcome or collective capability. If the projects are not interdependent or mutually supportive, they may not belong in the program.”
• PMBOK Guide, 6th edition, page 18: “Program management focuses on the project interdependencies and helps to determine the optimal approach for managing them.”
• PMBOK Guide, 6th edition, page 176: “Progressive elaboration involves continuously improving and detailing a plan as more detailed and specific information and more accurate estimates become available.”
• PMBOK Guide, 6th edition, page 177: “Rolling wave planning is an iterative planning technique in which the work to be accomplished in the near term is planned in detail, while the work in the future is planned at a higher level.”

The resource management plan is a subplan of the project management plan that describes how the project resources will be acquired, allocated, managed, and controlled. It also defines the roles and responsibilities of the project team members and the skills required for the project activities. The project manager should review the resource management plan with the new team member to clarify their expectations and provide guidance on how to perform their assigned tasks. Additionally, the project manager should provide mentoring to the new team member if necessary, to help them develop their skills and competencies, and to integrate them into the project team. This is part of the Develop Team process, which aims to improve the team members’ performance and interaction. The other options are not the best choices because they do not address the root cause of the new team member’s confusion, which is the lack of familiarity with the project and their role. Advising the new team member to enroll in project management training (option A) may be helpful, but it is not specific to the project and may not cover the skills and knowledge needed for the project activities. Instructing the new team member to review the RACI matrix before asking for help (option B) may be seen as dismissive and unhelpful, and it does not provide enough information about the project scope, objectives, deliverables, and stakeholders. Advising the new team member to review the project charter and stakeholder engagement plan (option C) may be useful, but it is not sufficient to explain the resource management plan and the expectations for the new team member’s role and performance. References:

• Project Management Professional (PMP) Reference Materials:
• Professional in Business Analysis (PBA) Reference Materials:

The project manager should inform the sponsor and document the request in the stakeholder engagement plan, as this is the best way to handle the situation without compromising the project scope, budget, or schedule. The sponsor can then decide how to deal with the key stakeholder’s request, and the project manager can update the stakeholder engagement plan accordingly. This will also help the project manager to maintain a positive relationship with the key stakeholder and avoid any potential conflicts or misunderstandings.

According to the PMBOK Guide, the project manager should identify the project stakeholders by using various sources of information, such as historical records, organizational charts, stakeholder registers, and lessons learned from previous projects. Lessons learned from previous projects can provide valuable insights into the stakeholder’s expectations, needs, interests, influence, and potential impact on the project. By using lessons learned from the previous project as a guide, the project manager can create a more accurate and comprehensive stakeholder register for the current project, which will help in planning and managing stakeholder engagement. References: PMBOK Guide, 6th edition, page 511-512, section 13.1.1.2 Identify Stakeholders: Data Gathering.

According to the Agile Practice Guide, one of the principles of agile project management is to “respond to change over following a plan” 1. This means that agile teams should be able to adapt to changing requirements and market conditions, and deliver value to the customer as quickly as possible. Adding the competitor’s functionalities to the product backlog (option A) may not be the best way to respond to change, as it may increase the scope and complexity of the project, and delay the delivery of the product. Asking the sponsor to add more people to the team (option B) may also not be effective, as it may disrupt the team dynamics and communication, and cause the Brooks’ law effect, which states that “adding manpower to a late software project makes it later”. Asking the team to increase the velocity to launch the product as soon as possible (option D) may compromise the quality and sustainability of the product, and put undue pressure on the team. Therefore, the best option is to help the team to find a new approach to launch the product as soon as possible (option C), which may involve prioritizing the most valuable features, reducing the technical debt, applying lean principles, and collaborating with the customer and other stakeholders. References: 1: Agile Practice Guide, Chapter 2: An Introduction to Agile, page 13 2: The Mythical Man-Month: Essays on Software Engineering, by Frederick P. Brooks Jr., page 25

• A user focus group is a group of potential or actual customers who provide feedback on a product or service. User focus groups can help project managers understand the needs, preferences, and expectations of the target market, as well as identify any problems or issues with the product or service12.
• Defining a user focus group as external stakeholders with a high influence on outcomes means that the project manager recognizes the importance of involving the users in the project initiation and planning phases. By doing so, the project manager can ensure that the project aligns with the user requirements and delivers value to the customers34.
• Defining a user focus group as external stakeholders also implies that the project manager will communicate with them regularly, solicit their feedback, and incorporate their suggestions into the project scope, schedule, budget, and quality5 . This can help prevent customer dissatisfaction and negative feedback, as well as increase customer loyalty and retention .

References:

1: What is a Focus Group? Definition, Examples, and Benefits 2: Focus Groups: What They Are and How to Use Them 3: Project Stakeholder Management - Project Management Institute 4: Stakeholder Analysis and Mapping: A Guide for Beginners 5: How to Manage Stakeholder Expectations in Project Management : [The Importance of Communication in Project Management] : [Customer Satisfaction: The Ultimate Guide] : [How to Increase Customer Loyalty: 5 Strategies for Success]

According to the PMBOK Guide, closing a project or phase is the process of finalizing all activities across all of the project management process groups to formally complete the project or phase1 One of the main outputs of this process is the final product, service, or result transition, which involves transferring the ownership and accountability of the project deliverables to the customer, sponsor, or other designated entity1 Another important output is the project documents updates, which involves archiving all the project documents following the organization’s accepted practices so that they can be used in other future projects1 Archiving the project documents ensures that the project information is properly stored, organized, and accessible for future reference, lessons learned, audits, or legal purposes2 Some examples of project documents that should be archived are the project charter, the project management plan, the project scope statement, the work breakdown structure, the project schedule, the project budget, the quality reports, the risk register, the issue log, the change log, the stakeholder register, the lessons learned register, and the project closure report12

In the given scenario, the project manager is instructed by the project sponsor to immediately close the project and to move on to another project. The project manager should complete the critical task of archiving all the project documents before closing the project. This will ensure that the project information is preserved and available for future use, and that the project closure is done in a systematic and consistent manner2

The other options are not the best choices for the following reasons:

• Option A: Ensure that the whole team is appropriately recognized and organize a project farewell party to celebrate the project success and closure. This option suggests recognizing the project team and celebrating the project success and closure. While this is a good practice to motivate and appreciate the project team, it is not the most critical task that the project manager should complete before closing the project. The project manager should first ensure that the project deliverables are transferred to the customer or sponsor, and that the project documents are archived, before organizing any recognition or celebration events2
• Option B: Update and close both the risk register and issue log with the latest updates, and save them in the organization’s project management information system (PMIS). This option suggests updating and closing the risk register and issue log, and saving them in the PMIS. While this is a necessary task to document and communicate the status and resolution of the project risks and issues, it is not the only task that the project manager should complete before closing the project. The project manager should also update and archive other project documents, such as the project charter, the project management plan, the project scope statement, the work breakdown structure, the project schedule, the project budget, the quality reports, the change log, the stakeholder register, the lessons learned register, and the project closure report12
• Option D: Meet with the project sponsor and advise that the new project might be difficult to undertake because the current project is not yet complete. This option suggests meeting with the project sponsor and advising that the new project might be difficult to undertake because the current project is not yet complete. While this is a valid concern that the project manager should raise with the project sponsor, it is not the most critical task that the project manager should complete before closing the project. The project manager should first finalize all the activities and deliverables of the current project, and archive all the project documents, before moving on to another project2

References: 1: PMBOK Guide, 7th edition, Chapter 3: Doing the Work, Section 3.6: Close the Project or Phase, pp. 80-81 2: PMBOK Guide, 7th edition, Chapter 3: Doing the Work, Section 3.6.2: Close the Project or Phase: Outputs, pp. 82-83

 Cross-training is a technique that allows team members to share and learn skills from each other. It can enhance team performance, increase flexibility, and reduce risks related to staff turnover or unavailability. It can also improve team cohesion and collaboration. In this scenario, the project manager should allow the engineer and designer to cross-train with each other, as this would benefit both the project and the individuals. The engineer would learn a new skill that is required for the tasks, and the designer would reinforce their existing skill by teaching it. This would also save time and money compared to external training options. Escalating the situation to the engineer’s manager, requesting external training for the engineer, or requesting external training for both the engineer and the designer are not the best choices, as they would not leverage the existing resources and expertise within the team. References: PMBOK Guide, 6th edition, page 339; Professional in Business Analysis (PMI-PBA)® Handbook, page 16.

 According to the PMBOK® Guide, an agile team is a cross-functional group of people that is self-organized and empowered to deliver the project objectives. The agile team should have the following characteristics1:

• They are collaborative and work together as a cohesive unit
• They have generalizing specialists who can perform multiple roles and tasks
• They are co-located or use effective communication tools to overcome geographic barriers
• They are adaptive and responsive to changing requirements and feedback
• They are empowered and accountable for their work and decisions Therefore, the best option for the project leader is to choose a team whose members have more general aptitudes and can collaborate on different tasks, as this aligns with the agile principles and values. References: 1 PMBOK® Guide, 6th edition, page 21.

 The project manager should work with the team to analyze which processes are suitable to use and define them in the ground rules. This will help to resolve the conflict by creating a common understanding of the project processes, expectations, and norms among the team members from different companies. The project manager should also facilitate communication and collaboration among the team members and foster a positive team culture. Avoiding the conflict, reviewing the historical information, and asking the team to use company B’s processes are not effective ways to resolve the conflict, as they do not address the root cause of the problem or involve the team in the decision-making process. References: = PMBOK Guide, 6th edition, pages 48-49, 343-344, 368-369; PMP Exam Content Outline, 2020, pages 6-7.

The project manager should have kept documentation in the PMIS and shared it with appropriate stakeholders. The PMIS is an information system consisting of the tools and techniques used to gather, integrate, and disseminate the outputs of project management processes1. It is used to support all aspects of the project from initiating through closing, and can include both manual and automated systems1. By keeping documentation in the PMIS, the project manager can ensure that the project information is updated, consistent, accessible, and secure. The project manager can also use the PMIS to communicate and collaborate with the relevant stakeholders, such as the project team, the sponsor, the customer, and the auditors2.

Option A is not the best answer because reviewing the risk register to identify a response plan for the audit is a reactive and not a proactive way to handle documentation for the project. The project manager should have anticipated and planned for the audit as part of the project risk management process3.

Option B is not the best answer because assigning a project team member to ensure all project documentation was updated is not a sufficient or efficient way to handle documentation for the project. The project manager should have established a clear and consistent process for updating and maintaining the project documentation, and used the PMIS to facilitate and automate this process4.

Option C is not the best answer because updating the project management plan regularly and having it securely shared with all stakeholders is only a partial way to handle documentation for the project. The project management plan is a formal, approved document that defines how the project is executed, monitored, and controlled. It is an important part of the project documentation, but not the only one. The project manager should have also updated and shared other project documents, such as the project schedule, the project budget, the project status reports, and the project deliverables. References: 1: PMBOK Guide, 7th Edition, Section 4.1.3.2, Project Management Information System 2: PMBOK Guide, 7th Edition, Section 10.1.3.3, Communication Methods, Models, and Channels 3: PMBOK Guide, 7th Edition, Section 11.1.3.1, Risk Management Plan 4: PMBOK Guide, 7th Edition, Section 4.4.3.1, Project Documents Updates : PMBOK Guide, 7th Edition, Section 4.1.3.1, Project Management Plan : PMBOK Guide, 7th Edition, Section 4.1.4.1, Project Documents

The project manager should use the monitor and control project work process to track, review, and report the progress and performance of the project. This process involves collecting, measuring, and analyzing project data to identify variances from the baseline and take corrective actions if needed. One of the tools and techniques for this process is data analysis, which includes root cause analysis. Root cause analysis is a technique to identify the underlying factors that cause a problem or a deviation from the expected outcome. By conducting root cause analysis, the project manager can understand why some team members are not completing their tasks on time and address the issues accordingly. This could involve providing feedback, coaching, training, or other support to the team members. Communicating the delivery dates more frequently (option A) may not be effective if the team members are facing other challenges or obstacles that prevent them from meeting the deadlines. Mentoring the team members to work in a remote environment (option C) may be helpful, but it is not the best option to resolve the current situation. The project manager should first identify the specific causes of the delays and then provide the appropriate guidance or assistance. Talking to the resource managers and requesting additional resources (option D) may not be feasible or necessary, as it may increase the project cost and complexity. Moreover, adding more resources may not solve the problem if the existing team members are not performing well or have other issues that affect their productivity. References: (Professional in Business Analysis Reference Materials source and documents)

• PMBOK Guide, 6th edition, pages 119-120, 4.4 Monitor and Control Project Work
• PMI, PMP Exam Content Outline, 2021, page 9, Domain II: Process, Task 7: Monitor project artifacts and resolve any deviations from the project management plan
• PMP Practice Questions #60 - iZenBridge

According to the PMBOK Guide, 6th edition, section 11.6.1.1, the project manager is responsible for monitoring and controlling the project risks and ensuring that the project objectives are met. The project manager should also identify and analyze any new or emerging risks that may affect the project performance or scope. In this scenario, the project manager should first work with the team and others in the network to assess and prioritize the obstacles. This will help to determine the impact and probability of each obstacle and decide on the best course of action to address them. The other options are either premature or inappropriate, as they do not address the root cause of the problem or respect the authority and responsibility of the project manager. References: PMBOK Guide, 6th edition, section 11.6.1.1, page 442.

According to the PMBOK Guide, the project manager is responsible for developing the project schedule and estimating the activity durations. One of the tools and techniques for estimating activity durations is decomposition, which involves subdividing the project work packages into smaller, more manageable components called activities. By breaking down the project into smaller tasks, the project manager can better understand the scope, complexity, and dependencies of the work, and apply more accurate and reliable estimation methods. This will also help the project manager to identify and manage the risks and uncertainties associated with the project schedule. Therefore, the project manager should break down the project into smaller tasks and estimate the durations of the activities as the next step. References: PMBOK Guide, 6th edition, pages 191-192, 201-202.

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.

A communications management plan is a document that defines how important information will be communicated to stakeholders throughout the project12. It should include the purpose, methods, frequency, and roles of communication, as well as any contractual obligations that may affect the communication process12.

By ensuring that the communications management plan covers contractual obligations, the project manager can avoid any confusion or conflict between the subcontractors and the client, as well as establish clear expectations and boundaries for communication. This can help improve the quality and efficiency of communication, as well as the overall success of the project12.

1: How to Create a Project Management Communication Plan 2: How to create a project management communication plan - Lucidchart

 The project manager should reinforce the value of documenting and approving all change requests and ask the customer to issue these through the agreed channels. This is because change requests are formal proposals to modify any aspect of the project and should follow the change management plan, which defines how changes will be monitored, controlled, and approved. The project manager should also communicate with the project team member and remind them of the change management process and their roles and responsibilities. This will help prevent unauthorized changes that could impact the project scope, schedule, cost, quality, or risk. The project manager should also update the issue log and the lessons learned register to document the incident and the actions taken. References: (Professional in Business Analysis Reference Materials source and documents)

• PMBOK® Guide, 6th edition, Section 4.6.1, “Perform Integrated Change Control: Inputs”
• PMBOK® Guide, 6th edition, Section 4.6.3.1, “Perform Integrated Change Control: Outputs - Change Requests”
• PMBOK® Guide, 6th edition, Section 4.6.3.2, “Perform Integrated Change Control: Outputs - Project Management Plan Updates”
• PMBOK® Guide, 6th edition, Section 4.6.3.3, “Perform Integrated Change Control: Outputs - Project Documents Updates”
• PMI-PBA® Guide, 1st edition, Section 6.3.1, “Trace Requirements: Inputs”
• PMI-PBA® Guide, 1st edition, Section 6.3.2, “Trace Requirements: Tools and Techniques”
• PMI-PBA® Guide, 1st edition, Section 6.3.3, “Trace Requirements: Outputs”

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

The project manager should use the collaborate/problem solve technique to resolve this issue, as it involves finding a mutually beneficial solution that satisfies the interests of both the senior and junior team members. This technique is also known as confronting or integrating, and it is the preferred technique for managing conflicts on a project. The project manager should facilitate a constructive dialogue between the two team members, identify the root cause of the conflict, and help them reach a common understanding and agreement. This way, the project manager can maintain a positive team environment and foster collaboration and trust among the team members. References: (Professional in Business Analysis Reference Materials source and documents)

• PMBOK Guide 6th Edition, page 368, section 9.5.2.1
• PMI Practice Standard for Project Risk Management, page 37, section 3.5.2.1
• PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 13, section 3.2.1.1

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.

 The project manager should perform iterative planning with the team to use the prototype, as this would allow them to adapt to the changing situation and deliver value incrementally. Iterative planning is a technique that involves breaking down the project scope into smaller iterations, each with its own plan, deliverables, and feedback loops. This technique enables the project team to respond to uncertainties, risks, and changes more effectively, and to incorporate lessons learned and stakeholder feedback into the next iteration. In this case, the project manager can use iterative planning to align the team with the new solution, define the requirements and acceptance criteria for the prototype, and monitor and control the integration and testing of the prototype. References: (Professional in Business Analysis Reference Materials source and documents)

• PMBOK Guide 7th Edition, page 67, section 3.2.2
• PMI Agile Practice Guide, page 33, section 3.2.1
• PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 14, section 3.3.1.1

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, stakeholder engagement is the process of identifying the people, groups, or organizations that could impact or be impacted by the project, analyzing their expectations and influence, and developing appropriate strategies to effectively engage them in project decisions and execution. Stakeholder engagement is especially important for projects that involve virtual teams, as they may face challenges such as communication barriers, cultural differences, lack of trust, and low visibility. By performing stakeholder engagement with the virtual team, the project manager can ensure that the team members are aware of the project objectives, requirements, and deliverables, and that they receive timely and constructive feedback, recognition, and support. This can help improve the team’s performance, motivation, and collaboration, and ultimately lead to better project outcomes. References: PMBOK Guide, 6th edition, pages 513-514, 540-541; PMP Practice Exam, question 4.

 According to the PMBOK® Guide, communication process control is the process of monitoring and controlling communications throughout the entire project life cycle to ensure the information needs of the project stakeholders are met1. It involves ensuring that the communication management plan is effective and updated as needed, managing the flow of information, resolving communication issues, and implementing approved changes to the communication methods or tools1.

In this scenario, the project manager should first revisit the communication process control to identify and address the root cause of why different draft versions of the design document were distributed to the meeting participants. This could involve reviewing the communication management plan, the configuration management plan, the change management plan, and the project documents updates to ensure that the communication process is aligned with the project objectives and stakeholder expectations. The project manager should also implement corrective actions to prevent the recurrence of such communication errors and improve the quality and consistency of the project information.

Options B, C, and D are possible actions that the project manager could take after revisiting the communication process control, but they are not the first step to ensure that this does not happen again. Option B is a preventive action that could help avoid confusion and ambiguity among the stakeholders, but it does not address the underlying issue of how different draft versions were shared in the first place. Option C is a detective action that could help identify the source of the problem, but it does not provide a solution or improvement to the communication process. Option D is a corrective action that could help resolve the current situation, but it does not prevent future occurrences of the same problem. References: 1 PMBOK® Guide, 6th edition, page 377-378.

The project manager should determine the value of the vendor’s bid by calculating the expected monetary value (EMV) of the bid. The EMV is the product of the probability and the impact of a risk event or opportunity1. In this case, the vendor’s bid has two possible outcomes: a cost overrun of US$100,000 with a 65% probability, or a cost saving of US$50,000 with a 35% probability. The EMV of the bid is calculated as follows:

EMV = (0.65 x 100,000) - (0.35 x 50,000) = 47,500

The value of the vendor’s bid is the original bid amount plus the EMV, which is:

Value = 500,000 + 47,500 = 547,500

Therefore, the correct answer is C. US$547,500.

References: (Professional in Business Analysis Reference Materials source and documents)

• PMBOK® Guide, 6th edition, Section 11.5.2.2, “Expected Monetary Value Analysis”

 According to the PMP Exam Content Outline, a project manager should select the appropriate project approach based on the project characteristics, such as the degree of uncertainty, complexity, and stakeholder involvement. A hybrid approach combines elements of predictive and adaptive (agile, iterative, incremental) approaches to suit the specific needs and context of the project. In this case, a hybrid approach would allow the project manager to accommodate the potential changes from the new CEO, while also ensuring the delivery of the correct sales results as the final product. A hybrid approach would also enable the project manager to collaborate with the customer and the development team to refine the requirements and validate the solution throughout the project life cycle. A predictive approach would not be suitable for this project, as it assumes a high level of certainty and stability in the requirements and the environment, which is not the case here. An incremental approach would deliver the product in smaller increments, which may not meet the customer’s expectation of no intermediate results. An iterative approach would repeat the same phases until the product meets the desired quality, which may not be efficient or effective for this project. References: = PMP Exam Content Outline, Domain I: People, Task 1: Manage conflict, page 6. PMP Exam Content Outline, Domain III: Business Environment, Task 2: Select project approach, page 14. PMBOK Guide, Chapter 1: Introduction, Section 1.2: Foundational Elements, page 9. PBA Guide, Chapter 2: Needs Assessment, Section 2.2: Assess Current State of the Organization, page 33.

 Schedule crashing is a technique to shorten the project schedule by adding more resources or working overtime, without changing the project scope1. This can help improve the Schedule Performance Index (SPI) and Cost Performance Index (CPI) by completing more work in less time and within budget. The other options are not relevant to the question. Fast tracking is a technique to overlap project phases or activities to reduce the project duration, but it may increase risks and costs2. Earned schedule and earned value are methods to measure project performance, not techniques to improve it3 . References: 1: PMBOK Guide, 6th edition, p. 215 2: PMBOK Guide, 6th edition, p. 216 3: PMBOK Guide, 6th edition, p. 267 : PMBOK Guide, 6th edition, p. 260

The project manager should use the PMIS to share information with the new stakeholders, as this is the most effective and efficient way to communicate project information and ensure that everyone has access to the same level of detail. The PMIS is a tool that supports the project manager in performing the processes of project integration management, project communications management, and project stakeholder management. The PMIS can include software applications, web-based systems, databases, and other technologies that facilitate the collection, integration, analysis, and dissemination of project information. The PMIS can also help the project manager to monitor and control the project performance and status, as well as to manage changes and issues. The PMIS can also provide a platform for collaboration and feedback among the project team and stakeholders. By using the PMIS, the project manager can ensure that the new stakeholders are informed and engaged in the project, and that their concerns are addressed in a timely manner. References: PMBOK Guide, 6th edition, pages 89, 377, 523, 540.

The best answer is D because it involves engaging the stakeholders in the decision-making process and respecting their preferences and expectations. The project manager should not impose a new approach on the stakeholders without their consent or input, as this could lead to resistance, confusion, or dissatisfaction. The project manager should also not delegate the decision to the team only, as this could exclude the stakeholders’ perspectives and needs. The project manager should explain the benefits and challenges of both the predictive and agile approaches, and facilitate a collaborative discussion with the stakeholders to reach a mutual agreement on the best approach for the new project. This would demonstrate the project manager’s leadership, communication, and stakeholder management skills, as well as the ability to adapt to changing organizational and environmental factors. References:

• PMBOK Guide, 7th edition, page 27, section 2.2.1, “Tailoring”
• PMBOK Guide, 7th edition, page 29, section 2.2.2, “Stakeholder Engagement”
• PMBOK Guide, 7th edition, page 31, section 2.2.3, “Leadership”
• PMBOK Guide, 7th edition, page 33, section 2.2.4, “Teamwork”
• PMBOK Guide, 7th edition, page 35, section 2.2.5, “Communication”
• Agile Practice Guide, page 8, section 1.2, “What is Agile?”
• Agile Practice Guide, page 9, section 1.3, “Why Use Agile Approaches?”
• Agile Practice Guide, page 10, section 1.4, “When to Use Agile Approaches?”
• Agile Practice Guide, page 11, section 1.5, “Tailoring to the Project Environment”
• Agile Practice Guide, page 12, section 1.6, “Implementing Agile: Creating an Agile Environment”
• Agile Practice Guide, page 13, section 1.7, “Implementing Agile: Delivering in an Agile Environment”
• Agile Practice Guide, page 14, section 1.8, “Organizational Considerations for Project Agility”

According to the PMP Exam Content Outline (2023), one of the tasks under the domain of Planning is to “Develop the procurement management plan based on the project scope, budget, and schedule, in order to ensure that the required project resources will be available” 1. This task involves identifying potential sellers, conducting market research, determining the contract type, and defining the procurement strategy and approach. One of the tools and techniques for this task is “Contract terms and conditions”, which are the legal provisions that govern the rights and obligations of the parties involved in the procurement 2. Penalty clauses are a type of contract terms and conditions that specify the amount of money or other compensation that a party will pay or forfeit in the event of a breach of contract, such as failing to meet the deliverable dates 3. Penalty clauses can be used to motivate the seller to perform according to the contract and to protect the buyer from losses or damages caused by the seller’s poor performance .

According to the PMI-PBA Exam Content Outline (2023), one of the tasks under the domain of Analysis is to “Assess risks that may impact the solution scope or requirements, and document them in the risk register” . This task involves identifying, analyzing, prioritizing, and documenting the risks that may affect the solution or its delivery, and planning the appropriate responses to mitigate or avoid them . One of the tools and techniques for this task is “Risk register”, which is a document that records the details of the identified risks, their causes, impacts, probabilities, priorities, responses, owners, and status . The risk register is a living document that is updated throughout the project as new risks are identified, existing risks are monitored, and risk responses are implemented .

Therefore, the best answer to this question is B. Add penalty clauses to the contract and update the risk register. This answer reflects the project manager’s responsibility to plan the procurement management and the risk management for the project, and to use appropriate tools and techniques to ensure that the project objectives are met. The other answers are not as good because they either do not address the issue of the provider’s poor performance (A and C), or they introduce a new risk by contracting another provider with less experience (D).

References: 1: PMP Exam Content Outline (2023), p. 10 2: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, p. 230 3: Business Law and the Legal Environment, v. 2.0, p. 15.2 : Project Procurement Management: A Guide to Structured Procurements, p. 153 : PMI-PBA Exam Content Outline (2023), p. 9 : Business Analysis for Practitioners: A Practice Guide, p. 97 : A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, p. 403 : Project Risk Management: A Practical Implementation Approach, p. 63

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

According to the Agile Methodology1, the product owner is responsible for defining the product vision, managing the backlog, and ensuring that the development team is working on the right priorities. The product owner is also the primary customer advocate and the link between the business and technology strategy. Therefore, the product owner’s engagement and interest are crucial for the success of the project. If the product owner changes during the project, the project manager should reevaluate the new product owner’s needs, expectations, and communication preferences, and adjust the collaboration accordingly. This can help to avoid delays, misunderstandings, and conflicts, and ensure that the product owner is aligned with the project goals and the development team. The project manager should also facilitate the transition of the product owner role and ensure that the new product owner is familiar with the product vision, the backlog, and the agile principles and practices. References:

• 3: Agile Methodology: Role of Product Owners & Development Teams

minimum viable product (MVP) is a version of a product that has enough features to satisfy early customers and provide feedback for future development1. The project manager should use an MVP to validate the customer requirements and test the assumptions and hypotheses about the product value and feasibility2. An MVP can help the project manager to learn from the customer feedback and make adjustments to the product scope and design3. Creating product documentation, a survey, or a prototype with all features are not as effective as an MVP in validating the customer requirements and obtaining feedback. References:

• 1: PMI, A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Project Management Institute Inc., 2021, p. 177.
• 2: PMI, The Standard for Project Management – Seventh Edition, Project Management Institute Inc., 2021, p. 63.
• 3: PMI, Agile Practice Guide, Project Management Institute Inc., 2017, p. 36.

The project manager should first perform an impact analysis with SMEs to assess the potential effects of the separate project on the network upgrade. This will help the project manager to determine the magnitude and probability of the risks, as well as the possible responses and contingency plans. The impact analysis is part of the Monitor Risks process, which involves tracking the identified risks, monitoring residual risks, identifying new risks, and evaluating risk process effectiveness1. Informing the government representative, implementing a change request, and updating the risk register are all possible actions that may follow the impact analysis, but they are not the first thing to do. References: 1 PMBOK® Guide, 6th edition, page 452.

An agile leader should ensure participation from all team members in the final phase of a complex project, as this will help to foster collaboration, communication, feedback, and alignment among the project stakeholders. Participation from all team members will also help to identify and resolve any integration issues, risks, or dependencies that may arise during the delivery stage. Participation from all team members will also promote a sense of ownership, accountability, and commitment to the project outcomes. Asking the client to attend all daily calls may not be feasible or necessary, as the client may have other priorities or constraints. Ensuring cross-departmental teams are colocated may not be possible or beneficial, as the project may involve remote or distributed teams, or different organizational cultures. Requesting additional project resources may not be the best option, as it may introduce new challenges such as coordination, training, or integration costs. References: PMBOK Guide, 7th edition, pages 99, 100, 101, 102.

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

 The project manager should conduct a kick-off meeting to ensure that all team members have a clear and common understanding of the project vision, goals, objectives, scope, deliverables, and roles and responsibilities. This is especially important for agile projects, where the team is expected to self-organize and collaborate effectively. A kick-off meeting can also help to establish trust, rapport, and alignment among team members who are working remotely or across different time zones and cultures. Scheduling team-building activities, coaching the team members, or continuing the meetings may be helpful, but they are not sufficient to address the gaps in understanding that exist at the beginning of the project. References:

• PMBOK® Guide, 6th edition, page 123: “The project kick-off meeting is usually the first time that the project team and key stakeholders meet together. The purpose of the kick-off meeting is to communicate the project vision, objectives, and scope; confirm initial roles and responsibilities; and provide an opportunity for team members to get to know each other.”
• PMI-PBA® Guide, 1st edition, page 39: “The business analyst should participate in the project kick-off meeting to ensure that the business needs, objectives, and benefits are clearly articulated and understood by the project team and stakeholders.

In agile projects, risks are assessed and managed continuously through regular feedback loops, such as daily standups, iteration demos, and retrospectives. These feedback loops allow the team to identify, analyze, prioritize, and respond to risks in a timely and collaborative manner. They also help the team to monitor and control the project performance and deliver value to the customer. Identifying and escalating risks to the facilitator is not an effective way of managing risks, as it does not involve the whole team or the customer. Updating the risk register during every iteration is a good practice, but it is not enough to assess and manage risks regularly. Focusing on developing a working deliverable instead of documenting risks is not a good option, as it ignores the potential impact of risks on the project outcome and quality. References: = PMBOK Guide, 7th edition, page 97; PMI, Project Management Professional (PMP) Examination Content Outline, 2021, page 8.

 The project manager should communicate individually with the affected team members to negotiate the decision and confirm their willingness to relocate, as this is the most respectful and ethical way to handle the situation. Relocating team members abroad for six months is a major change that will affect their personal and professional lives, and the project manager should consider their needs, preferences, and concerns before making any final decisions. The project manager should also explain the rationale and benefits of the relocation, and offer any support or incentives that may facilitate the transition. Communicating to the whole team, the HR department, or the team members’ manager may not be appropriate or sufficient, as the project manager should first consult with the team members directly and obtain their consent. These other communication options may also create unnecessary confusion, resentment, or resistance among the team members or other stakeholders. References: PMBOK Guide, 7th edition, pages 111, 112, 113, 114.

According to the PMBOK Guide, team-building activities are one of the tools and techniques for managing project teams. Team-building activities help enhance project performance by improving team morale, reducing conflicts, increasing trust, and fostering collaboration. Team-building activities can be formal or informal, and can be conducted throughout the project life cycle. Some examples of team-building activities are icebreakers, workshops, retreats, celebrations, and recognition programs. By planning to implement team-building strategies throughout the project, the project manager can avoid the challenges related to team motivation that were encountered in a similar, previous project. References: PMBOK Guide, 6th edition, pages 349-350.

According to the PMBOK Guide, a resource management plan is a component of the project management plan that describes how project resources are acquired, allocated, monitored, and controlled. It also includes the roles and responsibilities of project team members and other stakeholders, as well as the resource calendars and the process for managing changes to resource assignments. When a key subject matter expert (SME) leaves a multiyear project due to organizational downsizing, the project manager should refer to the resource management plan to determine how to replace the SME, how to transfer the SME’s knowledge and expertise to the remaining team members, and how to communicate the change to the relevant stakeholders. The other options are not the best actions to take in this situation. Updating the stakeholder register is a possible consequence of the change, but not the first thing to do. Consulting the project sponsor may be helpful, but not as effective as following the established plan. Modifying the statement of work (SOW) is not necessary unless the scope of the project is affected by the loss of the SME. References: PMBOK Guide, 6th edition, pages 313-314, 318-319.

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, issue management is the process of identifying and resolving issues that arise during the project life cycle1. Issues are problems that have already occurred and need to be addressed as soon as possible to avoid further negative impacts on the project objectives2. The project manager is responsible for managing issues and ensuring that they are resolved in a timely and effective manner3. One of the key steps in issue management is to identify the appropriate response and have it implemented4. This means that the project manager should analyze the issue, determine the best course of action, assign responsibilities, and monitor the progress of the resolution4. By doing so, the project manager can mitigate the impact of the issue on the project schedule and other aspects of the project performance4. The other options are not sufficient to manage the issue effectively. Identifying and reporting the issue (A) is necessary but not enough, as it does not involve taking any action to resolve the issue. Monitoring and controlling the issue (B) is also important but not sufficient, as it assumes that the issue has already been addressed and only needs to be tracked. Communicating any identified action to impacted stakeholders (D) is a good practice but not the primary responsibility of the project manager, as it does not ensure that the action is actually implemented and effective. References:

• 1: PMBOK Guide, 6th edition, p. 89
• 2: PMBOK Guide, 6th edition, p. 456
• 3: PMBOK Guide, 6th edition, p. 457
• 4: PMBOK Guide, 6th edition, p. 458

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 project manager should prepare a weekly status report and share it with executive management every week to keep them informed of the project’s progress and performance. This will help to address their concerns and expectations, as well as to provide them with relevant information for decision making. The status report should include key metrics such as schedule, cost, scope, quality, risks, and issues, as well as any changes or deviations from the baseline. The project manager should also communicate the benefits and value of the agile approach, and how it aligns with the project objectives and customer needs12. References:

• A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 10.4.3.1, page 387
• Agile Practice Guide, Chapter 3.3, page 37

A change request is a formal proposal to modify any document, deliverable, or baseline of a project. A change request should be submitted when a change is needed due to an external or internal factor, such as a new regulation, a stakeholder request, or an error correction. The Integrated change control process is the process of reviewing and approving all change requests, and managing the changes to the project management plan, project documents, and project baselines. The project manager should submit a change request through the Integrated change control process as the next step after receiving the announcement from the municipality, as this will ensure that the change is properly evaluated, approved, and communicated to the relevant stakeholders. Performing a qualitative risk analysis, updating the issue log, or estimating the associated costs are not the next steps that the project manager should take, as they do not address the need for a change request or the approval of the change. References: [PMBOK® Guide 6th Edition], page 115; Project Management Professional (PMP) Exam Questions for 2022, question 23.

A RAM is a tool that maps the project work packages or activities to the project team members or roles. It helps to define and assign the responsibilities, accountabilities, and authorities of each team member for each project task. It also helps to identify and resolve any gaps, overlaps, or conflicts in the resource allocation. A RAM can be presented in various formats, such as a RACI chart, a RASCI chart, or a linear responsibility chart12.

Developing an approved RAM can help the project manager to manage the team effectively, especially when some team members, such as the site engineers, may not be fully focused on the project due to other priorities or constraints. A RAM can help the project manager to communicate and clarify the expectations and deliverables of each team member, and to monitor and control their performance and progress. A RAM can also help the project manager to coordinate and collaborate with the other stakeholders, such as the production managers, to ensure that the project and the production imperatives are aligned and balanced34.

The other options are not as effective or relevant for managing the team:

• B. Commit each team member’s time and deliverables and aim for overall project completion: Committing each team member’s time and deliverables is important, but it may not be sufficient or realistic to manage the team, especially when some team members, such as the site engineers, may have competing or conflicting demands on their time and attention. Aiming for overall project completion is a desirable goal, but it may not be achievable or sustainable without proper planning, communication, and coordination among the team members and the other stakeholders.
• C. Continue the project implementation without the site engineers to ensure the schedule is maintained: Continuing the project implementation without the site engineers may not be feasible or advisable, as the site engineers may have critical skills, knowledge, or experience that are essential for the project success. Excluding the site engineers from the project may also create risks, issues, or gaps in the project quality, scope, or integration. Moreover, it may damage the relationship and trust between the project manager and the site engineers, and reduce their motivation and commitment to the project.
• D. Contract external resources to fulfill the role of the site engineers who cannot sup-port the project: Contracting external resources may be an option to supplement or replace the internal resources, such as the site engineers, who cannot support the project. However, this option may not be the best or the first choice, as it may involve additional costs, time, or risks for the project. Contracting external resources may also require approval, negotiation, or procurement processes that may delay or complicate the project. Furthermore, it may affect the morale, loyalty, or performance of the internal resources, who may feel threatened, replaced, or undervalued by the external resources.

References:

1: Responsibility Assignment Matrix - Project Management Knowledge 2: What is a Responsibility Assignment Matrix (RAM) in Project Management? 3: How to Create a Responsibility Assignment Matrix (RAM) for Your Project 4: How to Use a RACI Matrix to Manage Project Resources : [Project Team Management: How to Manage Your Team Effectively] : [How to Manage Project Team Conflicts] : [Project Procurement Management: The Ultimate Guide]

The question is about a project that faces a potential threat from a competitor’s product launch using the same innovation. The project manager needs to assess the impact of this threat on the project’s objectives and take appropriate actions to mitigate it. The best option for the project manager to do next is:

• Document the issue in the issue log and escalate to the project sponsor: This option is proactive and follows the best practice of issue management. The project manager should document the issue, its impact, and possible solutions in the issue log, which is a tool for tracking and resolving issues that affect the project. The project manager should also escalate the issue to the project sponsor, who is the person or group that provides the resources and support for the project. The project sponsor can help the project manager to evaluate the options and make decisions that align with the project’s goals and business strategy12

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

• Inform the project sponsor and suggest canceling the project: This option is premature and pessimistic. The project manager should not suggest canceling the project without analyzing the situation and exploring alternatives. Canceling the project might result in wasted resources, lost opportunities, and damaged reputation. The project manager should work with the project sponsor to find ways to overcome the threat and deliver value to the customer3
• Review the project goals and eat criteria m the project charter: This option is passive and incomplete. The project manager should review the project goals and acceptance criteria in the project charter, which is a document that authorizes the project and defines its scope, objectives, and stakeholders. However, this is not enough to address the issue. The project manager should also document the issue, communicate with the project sponsor, and take actions to resolve the issue4
• Ask the leader of research and development to decide on next steps: This option is irresponsible and risky. The project manager should not delegate the decision-making to the leader of research and development, who might not have the authority, responsibility, or knowledge to handle the issue. The project manager should consult with the leader of research and development, who is a subject matter expert, but the project manager should also involve the project sponsor, who is the project owner, and other relevant stakeholders, who might be affected by the issue. The project manager should lead the issue resolution process and ensure that the decisions are aligned with the project’s goals and business strategy.

References: 1: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 4, Section 4.4.3.1 2: Business Analysis for Practitioners: A Practice Guide, Chapter 8, Section 8.4.2 3: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 2, Section 2.4.3 4: A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 4, Section 4.1.3.1 : A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 13, Section 13.2.2.4

The project manager should update the risk register next. The risk register is a document that records the identified risks, their causes, impacts, probabilities, responses, owners, and other relevant information. Updating the risk register is part of the Monitor Risks process, which involves tracking the identified risks, monitoring residual risks, identifying new risks, executing risk responses, and evaluating their effectiveness. In this scenario, the low availability of the testing facility is a potential risk that could affect the project schedule. Therefore, the project manager should update the risk register with this information and plan appropriate risk responses. This option aligns with the PMBOK Guide, 6th edition, which states that “the risk register is updated as outputs from other risk management processes are completed” (p. 436). The other options are not the best choices because they do not address the risk of the testing facility’s low availability. Updating the issue log (option B) is not appropriate because the issue log is a document that records and monitors the resolution of issues that have occurred or are currently occurring on the project. In this case, the low availability of the testing facility is not an issue yet, but a potential risk that may or may not occur in the future. Updating the lessons learned register (option C) is not relevant because the lessons learned register is a document that captures the knowledge gained from the project, including the challenges, problems, risks, and opportunities encountered and how they were addressed. In this scenario, the project manager has not yet learned any lessons from the testing facility’s low availability, as it is still a potential risk. Updating the project schedule (option D) is premature because the project schedule is a document that presents the planned dates for performing activities and meeting milestones. In this case, the project manager has not yet determined the impact or probability of the testing facility’s low availability, or the risk responses to deal with it. Therefore, updating the project schedule without this information may result in inaccurate or unrealistic estimates. References:

• PMBOK Guide, 6th edition, p. 436 1
• PMBOK Guide, 6th edition, p. 123 2

 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 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, a project manager should plan to execute the procurement tasks in a virtual environment, when faced with the situation of local vendors being unavailable and having the option to hire the same services from companies in other countries. This is part of the plan procurement management process, which involves determining the project procurement strategy, the types of contracts, the procurement documents, the source selection criteria, and the procurement management plan. A virtual environment is one where the project team and the vendors communicate and collaborate using technology, such as online platforms, video conferencing, cloud computing, etc. A virtual environment can enable the project manager to access a wider pool of potential vendors, reduce travel costs and time, and increase flexibility and efficiency. However, a virtual environment also poses some challenges, such as cultural differences, legal issues, security risks, communication barriers, and quality control. Therefore, the project manager should plan the procurement tasks carefully, considering the project objectives, the stakeholder expectations, the project risks, and the best practices for managing virtual teams and vendors. References: PMBOK Guide, 6th edition, pages 459-460, 471-472.

According to the PMBOK Guide, planning poker is a technique used to estimate the size of user stories in agile projects. It involves each team member privately selecting a card with a number that represents the relative size or complexity of a user story, and then revealing their choices simultaneously. The team then discusses the reasons for the differences and repeats the process until they reach a consensus or an acceptable range. This technique helps the team to avoid anchoring, groupthink, and estimation bias, and to consider different perspectives and assumptions. By continuing multiple rounds of planning poker, the team can improve the accuracy and reliability of their estimates and plan their iterations more effectively. References: PMBOK Guide, 7th edition, page 309; Agile Estimation Techniques for the PMP Exam

According to the PMBOK Guide, an issue is “a point or matter in question or in dispute, or a point or matter that is not settled and is under discussion or over which there are opposing views or disagreements” (p. 720). Issues can arise from any aspect of the project, such as changes, risks, quality, stakeholders, etc. The issue log is a project document that records and tracks the issues that affect the project, along with their status, resolution, and ownership. The issue log is updated throughout the project as new issues are identified, analyzed, and resolved.

In this question, the change in environmental regulations is an external factor that could affect the project scope, schedule, cost, quality, or other aspects. Therefore, it is an issue that needs to be documented and tracked in the issue log. The project manager should update the issue log as an immediate action to ensure that the issue is properly addressed and communicated to the relevant stakeholders. Updating the issue log will also help the project manager to monitor and control the project performance and take corrective or preventive actions as needed.

Updating the project baseline, the risk management plan, or the change request log are not immediate actions that the project manager should take in this situation. The project baseline is the approved version of the project scope, schedule, and cost that serves as a reference for measuring and reporting the project performance. The project baseline can only be changed through the formal change control process, which requires a change request. The risk management plan is a subsidiary plan of the project management plan that describes how risk management activities will be planned, implemented, and monitored throughout the project. The risk management plan can also be changed through the change control process, if necessary. The change request log is a project document that records and tracks the change requests that are submitted, reviewed, approved, or rejected during the project. A change request is a formal proposal to modify any document, deliverable, or baseline of the project.

The project manager may need to update the project baseline, the risk management plan, or the change request log later, after analyzing the impact of the issue and determining the appropriate response. However, these are not immediate actions that the project manager should take before updating the issue log. References:

• PMBOK Guide, 6th edition, Project Management Institute, 2017, pp. 123, 129, 152, 456, 720.
• PMP Sample Test Questions, Project Management Institute, 2019, p. 15.

According to the PMBOK Guide, change requests are inevitable in any project and should be managed through an integrated change control process. This process involves analyzing the impact of the change on the project objectives, scope, schedule, cost, quality, risk, and other factors, and then deciding whether to approve or reject the change. If the change is approved, the project manager should update the project management plan and other relevant documents accordingly. The project manager should also communicate and negotiate with the stakeholders, especially the client, about the impact of the change and the possible trade-offs or alternatives. The project manager should not instruct the team to accommodate the changes without proper analysis and approval, as this would violate the project management plan and the agreed scope. The project manager should not review the project charter to identify the agreed scope, as this would not address the issue of the change requests and their impact on the project. The project charter is a high-level document that authorizes the project and defines its objectives, scope, and key stakeholders, but it does not provide the details of how the scope will be managed and controlled. The project manager should not escalate the issue to senior management, as this would imply that the project manager is unable to handle the change requests and their impact on the project. The project manager should only escalate the issue if the change requests are beyond the project manager’s authority or responsibility, or if the client is unreasonable or uncooperative. References: PMBOK Guide, 7th edition, pages 112-113, 118-119, 122-123; Project and Process Tailoring for the PMP® Exam

According to the PMBOK Guide, a workstream is a logical grouping of project activities that produces a specific deliverable or sub-deliverable within a project. A workstream leader is the person who is responsible for planning, executing, monitoring, and controlling the workstream activities and deliverables. A functional manager is the person who has management authority over an organizational unit, such as a department, within a functional organization1.

In this scenario, the project manager faces a situation where one of the workstreams has missed its deadline multiple times, affecting the project schedule and performance. The project manager should speak to the workstream leader and the functional manager about this situation to ensure it does not happen again. The project manager should communicate with the workstream leader to understand the root causes of the delays, identify the risks and issues, and agree on the corrective and preventive actions. The project manager should also communicate with the functional manager to obtain the necessary resources, support, and guidance for the workstream leader and the workstream team. The project manager should facilitate the collaboration and coordination between the workstream leader and the functional manager to ensure the alignment of expectations, objectives, and deliverables1.

The other options are not as suitable as option C. Option A involves speaking to the workstream leader and the project sponsor. The project sponsor is the person or group who provides resources and support for the project and is accountable for enabling success1. However, the project sponsor is not directly involved in the management or execution of the workstream activities and deliverables. The project sponsor may not have the detailed knowledge or authority to address the specific issues or challenges faced by the workstream leader and the workstream team. Option B involves speaking to the workstream leader alone. This option may not be sufficient to resolve the situation, as the workstream leader may need the support and assistance of other managers or stakeholders to overcome the delays and improve the workstream performance. Option D involves speaking to the workstream leader and the project management office (PMO). The PMO is an organizational structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques1. However, the PMO may not have the direct responsibility or authority over the workstream activities and deliverables. The PMO may not be able to provide the specific resources, support, or guidance needed by the workstream leader and the workstream team1.

References:

1: Project Management Institute. (2023). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Newtown Square, PA: Author.