According to the PMBOK Guide, 6th edition, section 11.6, the project manager should monitor and control risks throughout the project life cycle, and update the risk register and other project documents as needed. The project manager should not assume that low-level risks are insignificant or that high-level risks are resolved permanently. The project manager should reevaluate the identified risks periodically and in response to triggering events, and reassess their probability, impact, priority, and response strategies. The project manager should also identify new risks, close risks that are no longer applicable, and communicate the risk status to stakeholders. References: PMBOK Guide, 6th edition, section 11.6; PMP Practice Exam, question 68.

 According to the PMBOK Guide, the project manager should update the resource management plan and resource allocation chart to reflect any changes in the availability and assignment of resources. The resource management plan describes how the project resources will be acquired, allocated, managed, and released. The resource allocation chart shows the planned and actual allocation of resources over time. By updating these documents, the project manager can communicate the impact of the resource unavailability to the project team and stakeholders, and plan for alternative solutions to mitigate the schedule risk. References: PMBOK Guide, 6th edition, page 318-319, section 9.1.3.1 Resource Management Plan; page 321, section 9.2.3.1 Resource Allocation Chart.

The benefits realization plan is a document that describes how the benefits of the project will be delivered, measured, and sustained. It includes the benefits identification, analysis, planning, realization, and transition activities. By monitoring and updating the benefits realization plan, the project manager can ensure that the work carried out and the product being created do not deviate from the prescribed business value. Monitoring and updating the benefits realization plan helps to track the progress and performance of the project and the benefits realization process, and to identify and address any gaps or issues that may arise. Monitoring and updating the benefits realization plan also helps to communicate and report the value of the project to the stakeholders and the senior management. References: (Professional in Business Analysis Reference Materials source and documents)

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

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

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

Agile project management is a flexible and iterative approach to delivering value to customers and stakeholders. Agile projects are built around motivated individuals who collaborate and communicate effectively, deliver working products frequently, and respond to changing requirements and feedback1. Motivation is a key factor that influences the performance, satisfaction, and retention of agile team members2. According to the agile manifesto, 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 " 3. Therefore, the project manager should implement a reward system that aligns with the agile values and principles, and that recognizes and reinforces the team’s achievements, contributions, and behaviors. A reward system can include both intrinsic and extrinsic rewards, such as feedback, recognition, appreciation, autonomy, mastery, purpose, growth, learning, fun, collaboration, innovation, and compensation45. A reward system should be tailored to the needs, preferences, and goals of each team member, and should be fair, transparent, and consistent. A reward system should also be flexible and adaptable, and should be reviewed and improved regularly based on the team’s feedback and performance. References:

What Is Agile Project Management? | A Comprehensive Guide

Motivation and Drive in Agile Teams - InfoQ

Manifesto for Agile Software Development

Motivation - the Agile Way! - Mind Tools

How can Agile leaders create and motivate effective teams?

[Rewarding Agile Teams, What are the options?]

 Daily standup meetings are an essential practice of Scrum, which aim to facilitate communication, collaboration, and coordination among the project team members1. Daily standup meetings are short, time-boxed, and focused sessions where each team member answers three questions: what they did yesterday, what they will do today, and what impediments they face2. Daily standup meetings help the team to:

Align their work with the sprint goal and the definition of done

Identify and resolve any issues or dependencies that may affect the sprint progress

Share information, feedback, and ideas with each other

Foster a sense of accountability, transparency, and trust If daily standup meetings are not held or enforced, the team may experience communication gaps, which can lead to misunderstandings, conflicts, delays, or poor quality of work3. Therefore, the project manager or the Scrum master should ensure that daily standup meetings are conducted regularly, effectively, and efficiently, and that all team members participate actively and respectfully4. References:

Daily Stand-up Meeting - Scrum Inc

Daily Scrum - Scrum Guide

Scrum & the challenge of effective communication - Medium

7 ways the Scrum Master can improve Scrum Team Communication

 The project manager should request the high-performing team member to mentor the other team members. This is because mentoring is a way of recognizing and rewarding the team member’s expertise and contributions, as well as enhancing the skills and performance of the other team members. Mentoring can also foster a positive team culture, increase collaboration and trust, and reduce turnover and attrition. The project manager should also provide feedback and appreciation to the high-performing team member, and ensure that the mentoring process is aligned with the project objectives and expectations. The other options are not as effective or appropriate as requesting the high-performing team member to mentor the other team members. Promoting the higher performing team member to a higher position may not be feasible or desirable, as it may create resentment among the other team members, disrupt the team dynamics, or reduce the team member’s motivation and satisfaction. Reminding the high-performing team member to focus on shared rewards rather than individual rewards may be perceived as unfair or discouraging, as it may imply that the team member’s efforts are not valued or appreciated. Rewarding the high-performing team member privately to avoid team disruption may also be seen as unfair or secretive, as it may create a sense of favoritism or inequality among the team members, and undermine the team morale and cohesion. References: PMBOK Guide, 6th edition, Chapter 9.4.2, 9.4.3, The Benefits of Mentoring in Project Management - PMI

The project manager should first try to address the issue of team members not following the ground rules by scheduling a meeting with the project team to reinforce the ground rules. This is the most proactive and collaborative approach to resolve the problem and ensure team adherence to the ground rules. The project manager should also use this opportunity to listen to the team members’ feedback and concerns, and make any necessary adjustments to the ground rules to suit the project context and team dynamics. This is consistent with the agile principles of self-organizing teams, frequent communication, and continuous improvement. The other options are not the best choices, as they involve escalating the issue to external parties, such as the project sponsor, human resources, or the functional manager, without first trying to resolve it within the team. These options may also create a negative impact on the team morale, trust, and performance, and undermine the project manager’s leadership and authority. References: (Professional in Business Analysis Reference Materials source and documents)

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 9: Project Team Management, Section 9.2.2: Team Charter

Business Analysis for Practitioners: A Practice Guide, Chapter 5: Elicitation and Collaboration, Section 5.3.1: Ground Rules

Agile Practice Guide, Chapter 2: An Introduction to Agile, Section 2.3: Agile Teams

 Feedback is the process of providing constructive and timely information to the project team members about their performance, behaviour, and contribution to the project. Feedback can help the project team to improve their skills, knowledge, and motivation, and to achieve the project goals and deliverables. According to the Project Management Professional (PMP) Reference Materials1, feedback can be given in various ways, such as:

Formal or informal: Formal feedback is planned and structured, and follows a specific format, criteria, and frequency. Informal feedback is spontaneous and flexible, and does not follow a predefined format or schedule.

Positive or negative: Positive feedback is praise or recognition for doing something well, and aims to reinforce and encourage the desired performance or behaviour. Negative feedback is criticism or correction for doing something poorly, and aims to address and improve the undesired performance or behaviour.

Individual or group: Individual feedback is given to one person at a time, and focuses on their specific performance or behaviour. Group feedback is given to a team or a group of people at the same time, and focuses on their collective performance or behaviour.

In this scenario, the team is working on a critical project deliverable and the project manager is concerned about meeting the deadline. There have been complaints from some stakeholders about some of the team members’ performance. The project manager wants to understand the situation and provide feedback to the team as soon as possible. Therefore, the best three actions that the project manager should take to address this situation are:

Define team ground rules: Team ground rules are the agreed-upon norms and expectations that guide the team’s work and interactions. They can help the team to establish a common vision, purpose, and values, and to define their roles, responsibilities, and accountabilities. They can also help the team to communicate effectively, collaborate efficiently, and resolve conflicts constructively. By defining team ground rules, the project manager can ensure that the team members are aware of and aligned with the project goals and deliverables, and that they respect and support each other’s performance and behaviour.

Perform a retrospective session: A retrospective session is a meeting that allows the team to reflect on their past performance and behaviour, and to identify what went well, what went wrong, and what can be improved. It can help the team to learn from their experiences, celebrate their achievements, and address their challenges. It can also help the team to generate ideas and action plans for future improvement and innovation. By performing a retrospective session, the project manager can provide formal and group feedback to the team, and involve them in the feedback process.

Implement daily team meetings: Daily team meetings are short and frequent meetings that allow the team to share their progress, issues, and plans for the day. They can help the team to stay on track, coordinate their tasks, and solve their problems. They can also help the team to communicate regularly, transparently, and collaboratively. By implementing daily team meetings, the project manager can provide informal and individual feedback to the team members, and monitor and support their performance and behaviour.

The other options are not the best choices, because:

Request a manager performance review: A manager performance review is a formal and individual feedback that is given by the team member’s direct manager, and focuses on their overall performance, behaviour, and career development. It is usually done annually or semi-annually, and follows a specific format and criteria. While a manager performance review can be useful and beneficial for the team member, it is not the responsibility of the project manager, unless they are also the team member’s direct manager. Moreover, it is not the most appropriate or timely feedback for the situation, as it does not address the specific project deliverable, deadline, or stakeholder complaints.

Conduct an annual review: An annual review is a formal and group feedback that is given by the project manager, and focuses on the team’s overall performance, behaviour, and achievements for the year. It is usually done at the end of the year or the project, and follows a specific format and criteria. While an annual review can be useful and beneficial for the team, it is not the most appropriate or timely feedback for the situation, as it does not address the specific project deliverable, deadline, or stakeholder complaints.

 According to the PMBOK Guide, the communications management plan is a component of the project management plan that describes how project communications will be planned, structured, implemented, and monitored for effectiveness. It includes information such as the communication requirements, methods, formats, frequency, roles, and responsibilities of the project stakeholders. When a company’s new communication system introduces online dashboard reporting, this is a change that affects the communication methods and formats of the project. Therefore, the project manager should update the communications management plan to reflect this change and ensure that the project communications are aligned with the new system and the stakeholder expectations. Updating the communications management plan will also help the project manager to identify and address any potential risks, issues, or challenges that may arise from the change, such as compatibility, security, or training needs. References: PMBOK Guide, Tools for managing projects : digital dashboards to report performance

When a quality issue that requires a change to the quality standard is encountered in a project, and there is currently no budget available for the required changes, the project manager should check the change management plan. The change management plan is a part of the project management plan and it documents how changes will be monitored and controlled throughout the lifecycle of the project. It provides a process for managing changes and their impact on the project’s objectives. In this case, the change management plan would provide guidance on how to handle a situation where a change to the quality standard is required but there is no budget available for the changes. References: Project Management

In this scenario, the organization is exploiting a risk management strategy. Exploitation is a strategy used in positive risk management or opportunity management. It seeks to make sure the opportunity is realized. By assigning the most talented resource to the project, the organization is trying to exploit the opportunity to finish the project earlier than planned.

PMBOK Guide, 6th Edition, Section 11.5.2.1, Strategies for Opportunities. The PMBOK Guide is a foundational standard from the Project Management Institute (PMI) that provides guidelines for managing individual projects and defines project management related concepts. It also describes the project management life cycle and its related processes, as well as the project life cycle. The PMBOK Guide is process-based, meaning it describes work as being accomplished by processes. This approach is consistent with other management standards such as ISO 9000 and the Software Engineering Institute’s CMMI. Processes overlap and interact throughout a project or its various phases. Processes are described in terms of:

Inputs (documents, plans, designs, etc.)

Tools and Techniques (mechanisms applied to inputs)

Outputs (documents, products, etc.)

The Laissez-faire management style is characterized by a hands-off approach where leaders provide teams with resources and advice, if needed, but otherwise don’t interfere. This style is most effective with experienced, highly competent, and self-directed teams who are capable of performing their tasks without much supervision. In the context of the question, the project manager trusts the team and their work, indicating that they are likely using a Laissez-faire approach. References: 

https://www.g2.com/articles/project-management-approach

 The project manager’s role is to ensure that the project meets its objectives while balancing the project constraints. In this scenario, the project team has identified a low-cost software product that could drastically reduce the scope of development. The development manager has confirmed that this tool would fulfill the business need. Therefore, the project manager should recommend this option to the product owner for consideration. The product owner is responsible for maximizing the value of the product resulting from the work of the development team. They are the ones who manage the product backlog and make the final decision on what should be included in it. References: Project Management Professional (PMP) Reference Materials, Professional in Business Analysis Reference Materials study guide.

 In this situation, the project manager should communicate with the client about the third-party supplier’s situation and request payment. This is because the agreement was that payment would be made after the organization receives payment from the client. By explaining the situation to the client, the project manager can potentially expedite the payment process and prevent the withdrawal of team members from the project, thereby minimizing project disruption. References: PMBOK® Guide, 6th Edition, Section 12.1: Plan Procurement Management, and Section 12.3: Control Procurements.

 The project manager should explain that more features can be planned in upcoming iterations and begin building the product12. This approach aligns with the principles of Agile project management, which emphasizes iterative development and the delivery of incremental value12. By starting the build phase, the team can start delivering value and receiving feedback, which can inform the planning and development of additional features in future iterations12. This approach also helps to prevent scope creep, which can delay the project and increase costs3. References: 

https://www.projectpractical.com/12-steps-to-initiate-and-plan-a-successful-project/ https://asana.com/resources/project-initiation

 The project manager should have monitored the progress in achieving the business value throughout the project. This involves tracking the project’s impact on the company’s image and reputation, which are the expected business values in this case. If the project manager had been monitoring these aspects, they could have identified the negative perception about the company’s brand earlier and taken steps to address it12. This could involve changes to the project’s design, communication strategies, or implementation processes3. References: Asana Resources | Project planning | 7 common project risks and how to prevent them, Why Projects Fail: 7 Reasons (and Their Solutions) [2023] • Asana, Stakeholder Perception Management in Project Management - Edbrick

The project manager should conduct project reviews to monitor compliance with user data protection regulations. Project reviews are a critical part of the project management process, as they allow the project manager to assess the project’s progress, identify any issues or risks, and make necessary adjustments1. In the context of data protection, project reviews can help ensure that the project is adhering to relevant regulations and standards2. This could involve reviewing the project’s data handling practices, assessing the effectiveness of data protection measures, and identifying any areas where improvements could be made3. References: 

https://docket.acc.com/node/202

https://www.cipd.org/uk/knowledge/guides/managing-data-protection-requirements-guidance-for-managers/

 In a project with team members located in different countries and time zones, common understanding about task distribution is crucial for team performance. Here are the recommended actions:

Perform team-building activities (B): Team-building activities can help improve communication and understanding among team members1. These activities can be designed to focus on task distribution and roles within the team, helping to ensure everyone understands their responsibilities1.

Revisit the communications management plan (D): The communications management plan outlines the methods and technologies used for communication among team members2. If the team doesn’t have a common understanding about task distribution, it may indicate that the current communications management plan is not effective. The project manager should revisit this plan, making necessary adjustments to improve clarity and understanding2.

https://www.pmi.org/learning/library/managing-distributed-project-teams-6035

When a project manager communicates the project management plan to the team, it’s crucial to ensure that the communication is understood and to solicit feedback from the team12. This involves checking in regularly, listening actively, and inviting communication through multiple channels3. By confirming understanding and soliciting feedback, the project manager can identify and address any confusion or misunderstandings early on, ensuring that all team members are clear about their roles and the project schedule12. This approach helps to foster effective communication, enhance team collaboration, and contribute to the success of the project12. References: How to Create a Project Communication Plan (Template Included), How To Create A Project Communication Plan [+ Template], 9 Key Project Communication Strategies & How To Best Use Them, 10 Key Project Management Communication Strategies - ClearPoint Strategy

The project manager should request the project sponsor prioritize and if necessary, allocate additional budget so the team can work on a single project. This is because working on multiple projects at the same time can reduce the team’s focus, productivity, quality, and morale. It can also increase the risk of delays, errors, conflicts, and rework. Agile approaches require dedicated and cross-functional teams that can deliver value in short iterations. Therefore, the project manager should seek the support of the project sponsor to ensure that the team has the necessary resources and time to work on one project at a time. Providing an incentive plan so the team members will work more unaccounted hours on multiple projects (option B) is not a good solution, as it may lead to burnout, stress, and dissatisfaction among the team members. It may also violate the labor laws and ethical standards. Brainstorming with the team members on how they can deliver on multiple projects within the given budget (option C) is a possible option, but it may not be realistic or feasible, as it may compromise the quality and scope of the projects. Instructing the team members to spread evenly across projects so mistakes will not occur within the current budget (option D) is not a good option, as it may create confusion, duplication, and inconsistency among the team members. It may also prevent the team from forming, storming, norming, and performing as a cohesive unit. References:

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

[Agile Practice Guide], page 26-27, section 3.1.1 Team Composition

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

The project manager should provide clear and objective feedback to the team member based on the key performance indicators (KPIs) that were established for the project. The KPIs are measurable values that demonstrate how effectively the project is achieving its objectives and delivering value to the stakeholders. The project manager should review the KPIs for this team member and remind them how they are determined, such as by using data from the project management information system (PMIS), the earned value management (EVM) technique, or the agile metrics. The project manager should also explain how the KPIs are linked to the performance review and the rewards or recognition system. This way, the team member can understand the criteria for their evaluation and improve their performance accordingly. 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, 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 PMI, a hybrid approach is a combination of two or more project methodologies, such as waterfall and agile, to suit the needs of the project. A hybrid approach can offer flexibility, adaptability, and customer focus, while also maintaining some level of predictability, structure, and control. However, a hybrid approach can also pose some challenges, such as stakeholder resistance, misalignment, or confusion. Therefore, the project manager needs to address and remove any obstacles and blockers that may prevent the team from achieving their goals. Obstacles and blockers are issues or impediments that hinder or stop the team’s progress, such as lack of resources, unclear requirements, technical debt, conflicts, communication gaps, etc. The project manager should follow these steps to address and remove obstacles and blockers for the team:

Identify the obstacles and blockers by using various techniques, such as daily stand-up meetings, retrospectives, feedback sessions, surveys, etc.

Analyze the impact, root cause, and priority of the obstacles and blockers by using tools, such as issue logs, risk registers, impact analysis, root cause analysis, prioritization matrix, etc.

Develop and implement solutions to remove the obstacles and blockers by using methods, such as problem-solving, negotiation, escalation, delegation, collaboration, etc.

Monitor and evaluate the effectiveness of the solutions by using measures, such as team velocity, customer satisfaction, quality metrics, etc.

Communicate and report the status and results of the solutions to the relevant stakeholders, such as the team, the sponsor, the customer, etc.

By addressing and removing obstacles and blockers for the team, the project manager can improve the project performance, as well as the team’s productivity, quality, morale, and collaboration.

The other options are not the best choices, because:

Asking stakeholders to communicate with the project manager and not directly with the team would create a communication bottleneck, reduce transparency, and increase the risk of misunderstanding or miscommunication.

Empowering the team members to remove obstacles and blockers would be a good practice, but it would not be sufficient without the project manager’s support, guidance, and intervention, especially if the obstacles and blockers are beyond the team’s authority or capability.

Adding blockers to the issue log and risk management plan would be a necessary step, but it would not be enough without taking action to resolve them. Simply documenting the blockers would not help the team to overcome them or improve their performance. References:

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

Agile, Traditional, and Hybrid Approaches to Project Success

Impediments, Obstacles, and Blockers: How to Address and Remove Them

1.7. Address and remove impediments, obstacles, and blockers for the team - KnowledgeMap

1.7 Address and Remove Impediments, Obstacles, and Blockers … - BrainBOK

According to the PMBOK® Guide, 7th edition, one of the principles of project management is to tailor the delivery approach based on context1. This principle suggests that project managers should select and adapt the delivery approach that best suits the project characteristics, stakeholder needs, and organizational goals. It also implies that project managers should recognize and respond to changes in the project environment and facilitate the transition between different delivery approaches1.

In a hybrid project, the delivery approach combines elements of predictive, adaptive, and iterative methods2. A hybrid project may start with a predictive phase to define the scope, schedule, and budget, and then switch to an adaptive or iterative phase to deliver the product or service incrementally2. A hybrid project may also use different delivery approaches for different components or work packages within the same project2.

In this scenario, the project manager observes that the team performance was excellent during the predictive stages, but declined when the iterations began. This could indicate that the team members are not comfortable or familiar with the change in the delivery approach, and that they are lacking the skills, mindset, or tools to work effectively in an adaptive or iterative environment. Therefore, the best course of action for the project manager is to perform team-building activities and enhance collaboration. This will help the team to build trust, rapport, and cohesion among themselves and with other stakeholders, and to align their expectations, roles, and responsibilities with the new delivery approach. It will also help the team to learn and apply the agile values and principles, such as customer collaboration over contract negotiation and working software over comprehensive documentation3.

The other options are not as effective as option B. Option A, giving team members more authority to make decisions, may be appropriate for an agile team, but it does not address the root cause of the problem, which is the change in the delivery approach. It may also create more confusion and conflicts if the team members are not clear about the decision-making process or criteria. Option C, identifying the team members who are impacting low morale, may be helpful, but it does not solve the problem of the team’s performance. It may also create a blame culture or a sense of isolation among the team members. Option D, coaching the team members on agile processes and knowledge, is also a good practice, but it is not sufficient to improve the team’s morale. Coaching should be complemented by team-building and collaboration activities to foster a positive and supportive team culture.

 1: PMBOK® Guide, 7th edition, page 10 2: PMBOK® Guide, 7th edition, page 19 3: Agile Manifesto,

According to the PMBOK Guide, 6th edition, page 341, cross-training and mentoring are two of the techniques for developing the project team. Cross-training allows team members to acquire new skills and knowledge from other team members, while mentoring provides guidance and support from experienced team members. These techniques can help the new team member to integrate into the project team, learn the project processes and procedures, and improve their performance and productivity. They can also reduce the impact of the loss of the highly skilled team resource and maintain the project performance. References: PMBOK Guide, 6th edition, page 341; Free PMP Practice Exam Questions - 120 Sample Test Questions

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.

According to the PMBOK® Guide Seventh Edition, one of the project management principles is to engage stakeholders actively and frequently. This means that the project manager should identify and analyze the needs, expectations, and interests of all stakeholders, and involve them appropriately throughout the project life cycle. The stakeholder register is a document that lists the key stakeholders, their roles, responsibilities, and level of influence on the project. The stakeholder engagement plan is a document that describes the strategies and actions to communicate with, manage, and influence the stakeholders.

In this scenario, the project manager has discovered that the local community was not included in the stakeholder register, which has caused them to oppose the project. This is a serious issue that can affect the project’s performance, reputation, and acceptance. Therefore, the project manager should not disregard these stakeholders, as this would violate the principle of stakeholder engagement and potentially escalate the conflict. The project manager should also not just explain to the community members why they were not included as stakeholders, as this would not address their concerns or expectations. The best option is to update the stakeholder register and revise the stakeholder engagement plan, as this would allow the project manager to acknowledge the community as a stakeholder, assess their impact and interest, and develop appropriate strategies and actions to engage them effectively and proactively. References:

PMBOK® Guide Seventh Edition, page 9

Project Management Principles 9-12, Episode 479: Project Management Principles 9-12 (Free)

According to the PMBOK Guide, 6th edition, section 13.1.3.1, the stakeholder register is a project document that identifies the stakeholders who have an interest in the project or may be affected by the project. The stakeholder register should be updated whenever there is a change in the stakeholder community, such as when a new stakeholder is identified or an existing stakeholder leaves the project. The new business unit manager is a new stakeholder who has authority and influence over the project, and therefore should be added to the stakeholder register. The stakeholder engagement plan, which is a subsidiary plan of the project management plan, describes the strategies and actions to engage the stakeholders and manage their expectations throughout the project life cycle. The stakeholder engagement plan should also be updated to reflect the new stakeholder’s current and desired level of engagement, as well as the communication and engagement activities planned for the new stakeholder. The other options are not the best next steps for the project manager, because they do not address the need to formally identify and document the new stakeholder and plan for their engagement. Contacting the previous business unit manager may be helpful, but it is not a formal project document. Sending the new manager a copy of the project charter may be informative, but it does not capture the new stakeholder’s needs and expectations. Scheduling a meeting with the new manager may be beneficial, but it should be done after updating the stakeholder register and the stakeholder engagement plan. References:

PMBOK Guide, 6th edition, section 13.1.3.1, page 513

PMI-PBA Exam Practice Test and Study Guide, 2nd edition, chapter 2, page 30

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.

According to the PMBOK Guide, an issue log is a project document that records and tracks any issues that arise during the project and how they are resolved. It is part of the project communications management knowledge area and the monitor communications process. A project manager should update the issue log whenever a new issue is identified, analyzed, or resolved. Updating the issue log and defining the mitigation strategy is the immediate action that the project manager should take to improve the situation of a new team member impacting the project performance. This will help to document the issue, communicate it to the relevant stakeholders, and plan how to address it effectively. Communicating the issue to the human resources department (A) may be a subsequent action, but not the immediate one. Providing additional training to the new hire (B) may be a possible mitigation strategy, but not an action to take before updating the issue log. Increasing team cohesiveness by sharing information and experiences openly © may be a good practice for team development, but not a direct response to the issue at hand. References: PMBOK Guide, 6th edition, pages 377-378, 529-530.

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 Agile Practice 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 complete. The DoD helps to ensure that the quality standards and customer expectations are met, and that there is a consistent understanding of what done means among the team and the customer. Therefore, the project manager should have included all relevant criteria in the agreed upon DoD, and crafted a shared product vision that aligns with the customer’s needs and goals. This would have helped to prevent the customer from rejecting the deliverables at the end of the iteration. Involved the customer more in the planning process for the project, and ensured agreement on the proceedings may be a good practice, but it is not the best answer. The customer may still reject the deliverables if the planning process does not result in a clear and agreed upon DoD and product vision. Provided the customer with the backlog and the specified user stories at the beginning of the iteration may be helpful, but it is not sufficient to prevent the customer from rejecting the deliverables. The backlog and the user stories may change during the iteration, and they may not reflect the quality criteria and the customer expectations. Developed the DoD in close cooperation with all stakeholders to ensure their expectations were included may be a good practice, but it is not the best answer. The DoD should be developed with the customer, not with all stakeholders. Some stakeholders may have different or conflicting expectations than the customer, and they may not be the ones who accept or reject the deliverables. References: Agile Practice Guide, Chapter 3, Section 3.2.2 (Definition of Done) and Section 3.2.3 (Product Vision)

 According to the Agile Practice Guide, one of the benefits of agile approaches is that they enable early and frequent delivery of value to the customer and stakeholders1. This can help to build trust and collaboration among the project team and the stakeholders, and also to validate and adapt the project requirements and solutions2. Therefore, the project manager should propose a phased project approach with multiple small interactions and build trust with the stakeholder through frequent value delivery. This will help the stakeholder to see the benefits of agile and overcome their reluctance. The other options are incorrect because:

B. Documenting the request and escalating to upper management to consider a modification of the project charter is not a persuasive strategy, but a confrontational one. It may create resistance and conflict with the stakeholder, and also undermine the project manager’s authority and credibility3.

C. Agreeing on a predictive approach, but applying agile concepts under the project management umbrella is not a transparent or ethical strategy. It may confuse and mislead the stakeholder, and also create inconsistency and ambiguity in the project management processes and practices4.

D. Ensuring the stakeholder that an agile approach will deliver all of the expected results in a shorter period of time is not a realistic or honest strategy. It may create unrealistic expectations and pressure on the project team, and also ignore the uncertainty and complexity of the project environment5. References:

1: Agile Practice Guide, Chapter 2, Section 2.1, page 13

2: Agile Practice Guide, Chapter 2, Section 2.2, page 14

3: PMBOK Guide, 6th edition, Chapter 13, Section 13.3.2.3, page 524

4: PMBOK Guide, 6th edition, Chapter 1, Section 1.2.3, page 7

5: Agile Practice Guide, Chapter 2, Section 2.3, page 15

 According to the PMP Exam Content Outline, one of the tasks of a project manager in the execution domain is to “Implement approved changes and corrective actions by following the change management plan in order to meet project requirements.” This implies that the project manager should update the assumptions log and change log, and implement the change control process when the assumptions change during the execution phase. The assumptions log is a tool that documents the assumptions and constraints of the project scope, and the change log is a tool that records the changes that occur during the project life cycle. The change control process is a set of procedures that defines how changes are proposed, reviewed, approved, implemented, and communicated. By following these steps, the project manager can ensure that the changes are aligned with the project objectives and stakeholders’ expectations, and that the impact of the changes on the project scope, schedule, cost, quality, risk, and benefits are assessed and managed. References:

PMP Exam Content Outline

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 4.1.3.2 and 4.6.3.2

A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter 4.6

Business Analysis for Practitioners: A Practice Guide, Chapter 5.5.2 and 5.5.3

According to the PMBOK Guide, the project manager should communicate the organizational culture and project goal to the external stakeholders in a formal and written manner. This will help the stakeholders understand the context, scope, objectives, and deliverables of the project, as well as the roles and responsibilities of the project team and other stakeholders. A report is an appropriate communication tool for this purpose, as it can provide a comprehensive and structured overview of the project information. The other options are either too informal, indirect, or ineffective for communicating the organizational culture and project goal to the external stakeholders. References: PMBOK Guide, 6th edition, page 376-377, section 10.1.2.1.

 The project manager should validate if the training request is within the scope and budget of the project before approving or rejecting it. The training request may be a valid requirement that was not identified during the planning process, or it may be a nice-to-have that is not necessary for the project success. The project manager should evaluate the benefits and costs of the training request and compare them with the project baseline. If the training request is within the scope and budget, the project manager can approve it. If the training request is outside the scope and budget, the project manager should send it to the change control board (CCB) for approval. The CCB is responsible for reviewing and approving change requests that affect the project baseline. Rejecting the request without validation may result in missing a critical requirement or losing a valuable team member. Approving the request without validation may result in scope creep or budget overrun. References:

PMBOK® Guide, 6th Edition, Chapter 4, Section 4.5.6, “Change Requests”

PMBOK® Guide, 6th Edition, Chapter 5, Section 5.6.3.1, “Requirements Documentation Updates”

PMBOK® Guide, 6th Edition, Chapter 7, Section 7.4.3.1, “Cost Forecasts”

PMBOK® Guide, 6th Edition, Chapter 9, Section 9.3.3.1, “Resource Requirements Updates”

The project manager should review the operations manager’s concerns and ensure these concerns are addressed, as this is part of managing stakeholder engagement. Stakeholder engagement involves communicating and working with stakeholders to meet their needs and expectations, address issues, and foster appropriate stakeholder involvement. By reviewing and addressing the concerns, the project manager can increase the stakeholder satisfaction and support for the project, as well as avoid potential conflicts and delays. The other options are not the best ways to handle this situation, as they either ignore, escalate, or document the concerns without resolving them. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 13, Section 13.3

PMP Exam Content Outline, June 2019, Domain II, Task 9

PMP Sample Test Questions, Question 163

According to the PMBOK Guide, one of the key project management processes is stakeholder engagement1, which involves identifying, analyzing, planning, managing, and monitoring the stakeholders’ expectations and involvement throughout the project life cycle2. The project manager should use effective communication and collaboration techniques to ensure that the stakeholders are aligned with the project vision, objectives, scope, and deliverables3. This will help to build trust, resolve conflicts, and enhance stakeholder satisfaction. Meeting with the stakeholders regularly is an example of such a technique, as it allows the project manager to share project information, solicit feedback, address issues, and agree on common goals and plans. This is especially important for a project that involves multiple partners and has to comply with various standards and policies.

The other options are not the best ways to ensure project success, because they do not involve stakeholder engagement or collaboration. Option A is too authoritarian and may create resistance or resentment from the contracting partner. Option B is too passive and may result in loss of control or accountability for the project. Option C is too unilateral and may ignore or conflict with the partners’ needs and expectations. References:

1: PMBOK Guide, 6th Edition, page 513

2: PMBOK Guide, 6th Edition, page 515

3: PMBOK Guide, 6th Edition, page 518

PMBOK Guide, 6th Edition, page 520

PMBOK Guide, 6th Edition, page 524

According to the PMBOK Guide, one of the tools and techniques for collecting requirements is prototypes1. This involves developing a preliminary version or model of the product, service, or result that is expected from the project, and using it to elicit feedback from the stakeholders. By discussing the project scope statement with the key stakeholder and building prototypes, the project manager can improve the stakeholder’s engagement, as well as clarify and validate the requirements, reduce changes, and enhance satisfaction1. The other options are not appropriate, as they do not address the issue of the stakeholder’s frequent requests for changes to the project scope. Discussing the WBS, updating the project backlog, or updating the project charter are all possible actions that could be taken after collecting the requirements, depending on the project methodology and life cycle. References:

1: PMBOK Guide, 6th edition, page 149

 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 PMBOK Guide, risk management is an iterative process that should be performed throughout the project life cycle1. Agile projects also follow this principle, as they use frequent iterations to deliver value and respond to changes2. Therefore, the project manager should follow the risk management process while ensuring that risks are identified, analyzed, and managed during each iteration. This will help the project manager to monitor and control the project risks effectively and proactively. The other options are incorrect because:

A. There is no such thing as an agile risk manifesto. The Agile Manifesto is a set of values and principles that guide agile software development, but it does not specifically address risk management3.

B. Asking the product owner to act as a risk manager is not a good practice, as it may create role confusion and conflict of interest. The product owner is responsible for defining and prioritizing the product requirements, not for managing the project risks4. The project manager should collaborate with the product owner and other stakeholders to identify and manage the project risks, but not delegate this responsibility to them.

C. Implementing the role of an agile risk manager is not necessary, as the project manager already has the responsibility and authority to manage the project risks. Creating a separate role for risk management may create duplication of work and communication barriers. The project manager should leverage the skills and knowledge of the project team and other stakeholders to perform risk management activities, but not create a new role for this purpose. References:

1: PMBOK Guide, 6th edition, Chapter 11, Section 11.1, page 397

2: PMBOK Guide, 6th edition, Chapter 3, Section 3.8, page 52

3: Agile Manifesto

4: PMBOK Guide, 6th edition, Chapter 9, Section 9.3.2.2, page 286

PMBOK Guide, 6th edition, Chapter 9, Section 9.1.2.1, page 273

Answer steps

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

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

PMI-PBA Sample Questions, question 10, answer A

Creating prototypes is a technique to elicit, analyze, and validate requirements by providing a working model of the expected product or service. Prototypes can help reduce ambiguity, resolve conflicts, and obtain feedback from the stakeholders and the development team. Prototypes can also facilitate communication and collaboration across different locations and cultures, and improve the quality and efficiency of the development process. By creating prototypes with the development team, the project manager can ensure that the client’s needs are understood and met, and that the rework and delays are minimized. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 5.2.2.4, p. 154

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

Business Analysis for Practitioners: A Practice Guide, Section 4.3.3, p. 93

According to the PBA Guide, one of the techniques for managing stakeholder engagement is recognition and rewards, which can be used to motivate and appreciate the team members for their contributions and achievements1. The PMP Exam Content Outline also lists recognition and rewards as one of the tools and techniques for leading a team2. Awarding certificates of appreciation is an example of recognition and rewards that can boost the team’s morale and performance. Informing the team about the delivery pressure from the project sponsor may increase their stress and anxiety, which can negatively affect their performance. Sending a formal notice to team members instructing them to maintain performance may be perceived as a threat or a punishment, which can also demotivate the team. Hiring a few temporary team members to help with the additional work may introduce new risks and challenges, such as communication issues, learning curves, and integration problems, which can delay the project further. References:

1: PBA Guide, Chapter 6, Section 6.4.3.5 Recognition and Rewards

2: PMP Exam Content Outline, Domain II: People, Task 8: Lead a team

 According to the PMBOK Guide, iterative tools are techniques that enable project managers to plan and execute projects in an iterative and flexible way. Iterative tools are part of an adaptive or agile approach, where the project scope, schedule, and cost are responsive to changes and uncertainties. Iterative tools allow project managers to deliver value incrementally, rather than in one go, by breaking down the project into smaller cycles or iterations. Each iteration produces a deliverable or output that can be tested, reviewed, and improved. By using iterative tools, project managers can reduce risks, increase quality, and enhance customer satisfaction. To determine the benefits of using iterative tools in a project, the project manager should conduct reviews with stakeholders to discuss the potential benefits the approach may have to the project. Stakeholders are individuals or groups who can affect or be affected by the project outcomes. By conducting reviews with stakeholders, the project manager can solicit their feedback, address their concerns, and align their expectations. The reviews can also help the project manager to communicate the value and benefits of using iterative tools, such as faster delivery, higher quality, lower costs, and better customer satisfaction. The reviews can also help the project manager to identify the challenges and lessons learned from using iterative tools, such as managing changes, ensuring collaboration, and maintaining documentation. By conducting reviews with stakeholders, the project manager can evaluate the effectiveness and efficiency of using iterative tools, and report the results to the PMO and the steering committee. 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 9: Stakeholders, Section 9.3: Engage Stakeholders, pp. 144-1451

Iterative Process in Development & Design | project-management.com2