PMI PMP - Project Management Professional (PMBOK 7th Version)

 When a new law is enacted that affects project parameters, the project manager should first assess and prioritize the impact of the new law on the project plan. This involves analyzing how the changes will affect the project scope, schedule, cost, and quality, and determining the necessary adjustments to the project plan. The assessment should consider the severity of the impact and the urgency of the response required. This approach aligns with the PMBOK® Guide’s principles of conducting a risk analysis to evaluate the potential effects of an uncertain event or condition on the objectives of the project. It also reflects the PMP’s emphasis on adaptive project management, where project managers must be able to respond to changes and dynamic project environments effectively. References: PMBOK® Guide and Standards1.

When a delay in equipment delivery is communicated, it directly impacts the project schedule and potentially other aspects of the project. The project manager should update the risk register to document this new risk, including its potential impact on the project, and then discuss the issue with the project stakeholders. This is in line with the best practices of risk management, which involve continuous identification, analysis, and communication of project risks. The risk register serves as a central repository for all identified project risks and is a critical tool for tracking and managing risks throughout the project lifecycle123.

The best approach when dealing with stakeholders who have a preference for traditional communication methods is to align and agree on a communication approach that suits their preferences. This is supported by the PMBOK® Guide, which emphasizes the importance of tailoring communication to stakeholder needs and preferences. It is essential to respect the stakeholder’s working style and adapt the communication strategy accordingly to ensure effective engagement and project success23. References:

“8 Techniques to Communicate Effectively with Project Stakeholders” from PMI2.

"STAKEHOLDERS COMMUNICATION APPROACH: A NEW ERA

The PMBOK Guide suggests that conflicts should be addressed early and directly among the affected parties using a collaborative approach. This involves open communication and problem-solving techniques to find a mutually acceptable solution. It is recommended to resolve disputes privately and collaboratively, ensuring that the project manager and team members work together to reach a satisfactory resolution1. References: = PMBOK Guide 7th edition; Conflict Resolution Strategies In Project Management (PMP)1.

When a significant regulatory feature is missing in the project backlog, it is essential to engage stakeholders to discuss the impact of adding this feature. This aligns with the PMBOK® Guide’s emphasis on stakeholder engagement and the importance of communication with stakeholders when project changes occur. The PMBOK® Guide suggests that project managers should continuously engage stakeholders to understand their needs and expectations, address issues as they occur, and foster appropriate stakeholder engagement in project decisions and activities.

 When a consultant requests changes to a software component during an iteration, claiming it does not meet market requirements, the project manager should continue the iteration and review the change with the customer. This action ensures that the iteration’s progress is not halted while also addressing the consultant’s concerns. It is essential to involve the customer in the decision-making process since they have a vested interest in the product’s success and alignment with market needs. This approach is consistent with the principles of stakeholder engagement and communication found in both PMP and business analysis best practices.

 Three-point estimating is a technique that can be particularly useful when there is uncertainty about the individual task estimates. It involves the development team providing optimistic, pessimistic, and most likely estimates for each task, which can then be used to calculate an expected duration for the entire project. This method is beneficial when the team lacks experience with similar projects, as it allows for a range of possible outcomes to be considered, which can lead to a more realistic and reliable estimate123.

Transitioning a project to an operational state involves ensuring that all deliverables have been completed and meet the required standards. Reviewing the WBS with the project team is a good practice to confirm that all planned deliverables have been produced and validated. This step is crucial as it helps to ensure that the project has met its objectives and that all components are in place for the operational phase. It also allows for the identification of any remaining work that needs to be completed before the project can be closed out. References: (Professional in Business Analysis Reference Materials source and documents)

Executive Notebook - Transition Plans | PMI1

Exam PMP topic 1 question 749 discussion - ExamTopics2

Business Analysis 2018: The BA Role in Transitioning a Project’s Outcome/Capability to Operations3

When a company is undergoing structural changes, it is crucial for the project manager to maintain open communication with the team. Organizing a team meeting to discuss the changes and their importance for the company is aligned with the best practices in change management and project management. This approach allows for transparency, provides a platform for addressing concerns, and helps in aligning the team with the company’s vision and strategy. It is essential to ensure that the team understands the reasons behind the changes and how these changes can potentially benefit the company and their own work in the long run.

The answer is verified based on the principles of change management and team communication as outlined in the Project Management Professional (PMP) and Professional in Business Analysis (PMI-PBA) reference materials. These materials emphasize the importance of stakeholder engagement and effective communication during times of change to ensure project success and team alignment.

The best course of action when receiving a request for a more detailed project status is to engage in a dialogue with the senior manager to understand their specific needs. This approach aligns with the PMBOK® Guide’s emphasis on effective communication and stakeholder engagement as key aspects of project management. By discussing the requirements directly, the project manager can tailor the communication to provide relevant and precise information that satisfies the senior manager’s request without overwhelming them with unnecessary details. This method ensures that the project manager is responsive to stakeholder needs and maintains clear and open lines of communication.

The answer is supported by the principles outlined in the PMBOK® Guide, which advocate for proactive stakeholder engagement and effective communication strategies1. Additionally, the PMI’s standards on project communication emphasize the importance of understanding and addressing stakeholder information needs23.

The lessons learned database is a valuable resource for reviewing past projects, which can provide insights into the performance and reliability of potential vendors. It contains historical information that can help in making informed decisions about vendor selection by analyzing previous experiences, challenges, and successes related to similar procurements1234.

When a delay occurs, it is essential for the project manager to engage with the team to understand the reasons behind the delay. This approach aligns with the principles of both Project Management and Business Analysis, where communication and problem-solving are key to addressing project challenges. By discussing the issue with the team, the project manager can gather insights into the root causes of the delay and work collaboratively to find a solution that minimizes the impact on the project milestone. This method is preferred over immediately seeking assistance from senior management or reallocating resources, which may be more disruptive and less informed actions at this stage.

= The approach of discussing delays with the team is supported by the PMI’s guidance on dealing with project delays, which emphasizes the importance of understanding the causes of delays and working with the team to resolve them1. Additionally, the Professional in Business Analysis materials highlight the significance of stakeholder engagement and communication in managing project challenges2.

The first step in addressing the contractor’s failure to comply with the contractual commitments is to remind them of their obligations. This aligns with the best practices in project management, which emphasize communication and problem-solving as initial steps before escalating the issue or seeking legal recourse. It’s important to address the issue directly with the contractor to understand their perspective and to work towards a mutually beneficial resolution. This approach is supported by the principles outlined in the PMBOK® Guide, which advocate for proactive stakeholder engagement and communication management as essential components of project management.

Engaging a disengaged team often involves understanding individual team members’ perspectives and addressing any concerns they may have. One-to-one meetings can provide a safe space for team members to express their thoughts and feelings without the pressure of a group setting. Additionally, team-building meetings can help in building rapport, trust, and a sense of community within the team, which are essential for engagement and collaboration. This approach aligns with the PMBOK® Guide’s emphasis on the importance of effective team management and stakeholder engagement.

The answer is verified and explained using the principles found in the PMBOK® Guide and the Professional in Business Analysis Reference Materials provided by PMI12.

 Engaging the main stakeholders in the sprint review sessions is a key agile practice to ensure continuous collaboration and feedback. It allows stakeholders to provide input and clarifications, ensuring that the product evolves to meet their needs and expectations. This approach aligns with the agile principle of customer collaboration over contract negotiation and promotes transparency and adaptability.

= The PMI Guide to Business Analysis1, which includes The Standard for Business Analysis, and the PMBOK® Guide2 both emphasize the importance of stakeholder engagement and collaboration throughout the project lifecycle.

To avoid such setbacks, the project manager should have conducted a thorough stakeholder analysis as part of the initial project planning. This involves identifying all stakeholders, understanding their interests and influence, and anticipating their reactions to the project. By doing so, the project manager can engage with key stakeholders early on, address their concerns, and gain their support, which is crucial for the smooth approval of the project charter123.

 When a project involves integration of existing systems, especially when there are known issues in production, it is crucial for the project manager to identify and remove impediments and mitigate the risks. This approach is aligned with the principles of project management which emphasize the importance of addressing and managing risks proactively. The project manager should work on identifying the root causes of the issues and take corrective actions to ensure that the project objectives are met without significant delays or quality problems.

The answer is verified and explained using the principles found in the PMBOK® Guide and the standards for project management by PMI, which include risk identification and mitigation as key responsibilities of a project manager12. Additionally, the Professional in Business Analysis Reference Materials also support the importance of addressing risks and impediments in project management practices3.

 The project manager should review the list of team members’ skills and understand how they will work together to deliver the project outcomes to build a cohesive, high-performing team. According to the PMBOK® Guide, a high-performing team is a team that exhibits a high level of collaboration, trust, commitment, and performance1. To build a high-performing team, the project manager should apply team development techniques that enhance the team’s ability to work effectively and efficiently1. One of the team development techniques is skill assessment, which involves identifying and evaluating the skills and competencies of the team members, and aligning them with the project objectives and requirements1. By reviewing the list of team members’ skills, the project manager can understand the strengths and weaknesses of the team, and determine the best way to assign roles and responsibilities. The project manager can also identify any skill gaps or overlaps that may affect the team performance, and plan for training or coaching to address them. Additionally, by understanding how the team members will work together, the project manager can facilitate communication and collaboration among the team members and other stakeholders, and foster a positive team culture that supports the project goals. This way, the project manager can build a cohesive, high-performing team that can deliver the project outcomes. The other options are not the best ways to build a cohesive, high-performing team, as they do not address the need to assess and align the team skills and competencies.

Organizing the team members into several kick-off sessions based on technology type is a possible action that the project manager can take, but it is not the main activity that the project manager should do to build a cohesive, high-performing team. Kick-off sessions are meetings that introduce the project and the team to the team members and other stakeholders, and establish the project vision, scope, and expectations1. While kick-off sessions can help the team members to get to know each other and the project, they do not necessarily help the project manager to review and evaluate the team skills and competencies, and align them with the project objectives and requirements. Moreover, organizing the team members into several kick-off sessions based on technology type may create silos and barriers among the team members, and reduce the team cohesion and collaboration.

Asking the human resources (HR) department to arrange interview meetings to select the team is a wrong way to build a cohesive, high-performing team, as it delegates the responsibility of the project manager to the HR department, and ignores the input and involvement of the team members and other stakeholders. The project manager is the person who is accountable for the team performance and satisfaction, and who has the best knowledge and understanding of the project objectives and requirements1. Therefore, the project manager should take the lead in selecting and developing the team, and consult and collaborate with the team members and other stakeholders to ensure the team is aligned and engaged with the project goals.

Asking prospective team members to write a short biography explaining how they can contribute to the team’s success is an unnecessary and ineffective activity that does not help the project manager to build a cohesive, high-performing team. Writing a short biography is a one-way and subjective way of presenting the team members’ skills and competencies, and it does not provide the project manager with a comprehensive and objective assessment of the team skills and competencies. Furthermore, writing a short biography does not help the project manager to understand how the team members will work together, and facilitate communication and collaboration among the team members and other stakeholders.

 1: PMBOK® Guide, 7th edition, pages 96-97.

 The Project Management Professional (PMP)® certification emphasizes the importance of human resource management and the development of the project team. According to the PMBOK® Guide, project managers should develop the team through training, team-building activities, and creating an environment that promotes high performance. In the scenario provided, where the team lacks experience, the project manager should utilize coaching and mentoring to bridge the experience gap, enhance skills, and improve team performance. This aligns with the PMP’s focus on leadership and the development of human resources within the project team.

The references for this answer are drawn from the PMBOK® Guide and the PMP Examination Content Outline, which detail the project manager’s role in team development and the competencies required for effective project management. Additionally, the Professional in Business Analysis (PMI-PBA)® reference materials support the approach of enhancing competencies through coaching and mentoring to ensure project success.

When faced with a situation where a vice president from a different product line brings a valid concern during the release of an important product, the project manager should have proactively identified the vice president as a stakeholder. Here’s why:

1.Stakeholder Identification:

oIdentifying stakeholders is a critical step in project management.

oStakeholders include anyone who has an interest in or can be affected by the project.

oThe vice president’s involvement in the project, even if not previously engaged, makes them a relevant stakeholder.

2.Benefits of Identifying Stakeholders:

oRecognizing the vice president as a stakeholder allows the project manager to consider their concerns and priorities.

oIt facilitates effective communication and collaboration throughout the project lifecycle.

oStakeholder engagement ensures that all relevant perspectives are considered.

3.Risk Mitigation:

oBy identifying the vice president as a stakeholder early on, the project manager could have addressed their concerns proactively.

oRecording the concerns in the risk register (Option B) is also valuable, but stakeholder identification comes first.

4.Project Boundaries and Scope:

oSharing project boundaries and scope (Option D) is essential, but it doesn’t directly address the vice president’s concerns.

oEscalating dissent to top management (Option C) should be a last resort after attempting to resolve issues at lower levels.

In summary, identifying the vice president as a stakeholder would have allowed the project manager to engage them effectively, address their concerns, and prevent delays in the product release.

 Earned Value Analysis (EVA) is a project management technique used for monitoring and controlling project performance by integrating scope, schedule, and cost parameters. It is a critical tool for project managers to report the project’s value and is particularly useful for large projects where tracking progress against the budget is essential. EVA provides a set of mathematical metrics that reflect the health of the project and is used to report information for the current reporting period and on a cumulative basis. This method allows project managers to identify variances from the plan and forecast future performance, which is crucial for seeking further funding and demonstrating the project’s value to sponsors.

(Earned Value Analysis & Management (EVA/EVM) - Project-Management.info1, Professional in Business Analysis Reference Materials | PMI2)

 When faced with a situation where a vendor is unable to deliver as promised, it is essential for the project manager to engage in communication with both the vendor and the project team to explore all possible solutions. This approach aligns with the PMBOK® Guide’s emphasis on communication as a key aspect of project management. The project manager should work collaboratively to address the issue, which may involve negotiating a new delivery schedule, modifying the project scope, or finding alternative ways to meet project objectives.

Exam PMP topic 1 question 128 discussion - ExamTopics1.

The project manager should first revisit the project charter and assess if the project goals and objectives can be met with other alternatives. This could include re-evaluating the project requirements, researching other suppliers and/or re-designing the project in order to reduce the cost. If all other alternatives are exhausted, then the project manager should seek approval from the project sponsor or the CEO to proceed with the purchase order.

The purpose of identifying, evaluating, and categorizing stakeholder relationships in an ERP initiative is to ensure that the needs and expectations of all stakeholders are understood and addressed within the communications management plan. This process is crucial for the success of the project as it helps in developing a structured approach to stakeholder engagement, which is essential for gaining support and buy-in from various business lines involved in the program. By incorporating the needs of all stakeholders, the project manager can tailor communication strategies to manage expectations effectively and facilitate smoother project execution.

The importance of stakeholder engagement in an ERP project is highlighted in resources that discuss the roles and responsibilities of an ERP Project Manager1. The PMBOK Guide also emphasizes the need for effective communication management plans that consider all stakeholders2. Additionally, the Professional in Business Analysis materials advocate for the inclusion of stakeholder needs in communication plans to ensure project success3.

When a project schedule risk becomes an issue, it is crucial for the project manager to actively engage with relevant stakeholders to explore and implement potential solutions. This collaborative approach ensures that the issue is understood from multiple perspectives and that the solutions are comprehensive and effective. It aligns with the PMI’s principles of stakeholder engagement and proactive issue resolution12.

The approach is supported by the PMI’s guidelines on project risk and issue management, which recommend involving stakeholders in the resolution process to ensure that the project remains aligned with its objectives and can adapt to changes effectively12.

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

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

According to the PMBOK Guide, one of the tools and techniques for the Plan Risk Management process is the review of lessons learned from previous projects. This helps the project manager to identify potential risks, causes, and responses for the current project. By studying and applying the lessons learned from the failed project, the project manager can avoid repeating the same mistakes and improve the project performance. This is also consistent with the principle of continuous improvement and organizational learning. References: PMBOK Guide, 6th edition, page 397-398. PMP Sample Test Questions, question 3. Free PMP Exam Practice Questions, question 3. PMP Questions page 485, question 485.

 According to the PMBOK Guide, daily standup meetings are a common tool used in agile and hybrid project management approaches. They are short, time-boxed meetings that allow the project team to communicate their progress, issues, and plans for the day. Daily standup meetings can enhance collaboration, transparency, and alignment among the project team members. However, some team members may resist or challenge the use of daily standup meetings, especially if they are not familiar with them or perceive them as a waste of time. In this situation, the project manager should define the ground rules, responsibilities, and conflict management strategies for the project team. The project manager should explain the purpose and benefits of daily standup meetings, and establish clear expectations and guidelines for their conduct. The project manager should also assign roles and responsibilities to the team members, such as facilitator, timekeeper, recorder, etc. The project manager should also address any conflicts or issues that may arise from the use of daily standup meetings, and resolve them in a constructive and respectful manner. The project manager should not engage an external vendor, request new team members, or update the project schedule, as these actions may not address the root cause of the team’s resistance or challenge to the daily standup meetings. References:

PMBOK Guide, 6th edition, pages 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, …

According to the PMBOK® Guide, the project manager should document the technical reviews with the new change and obtain formal acceptance from the customer before delivering the project. This is part of the Validate Scope process, which ensures that the project deliverables meet the agreed requirements and specifications. By documenting the technical reviews, the project manager can demonstrate the rationale and benefits of the change, as well as the impact on the project scope, schedule, cost, quality, and risk. By obtaining formal acceptance, the project manager can ensure that the customer is satisfied with the project outcome and avoid any disputes or rework later. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Chapter 5, Section 5.5, Validate Scope

PMP Exam Prep, 10th edition, Rita Mulcahy, Page 157, Validate Scope

The project manager should try to resolve the conflict between the supervisor and the workers by communicating the company culture and values, and how they affect the project objectives and stakeholder satisfaction. The project manager should also seek to understand the supervisor’s perspective and goals, and find a way to align them with the project team’s needs and expectations. This approach is consistent with the PMBOK Guide’s recommendations on managing stakeholder engagement, conflict management, and leadership skills12. References: 1: PMBOK Guide, 6th Edition, Chapter 13: Stakeholder Management 2: PMBOK Guide, 6th Edition, Appendix X3: Interpersonal and Team Skills

This answer is based on the agile principle of responding to change over following a plan1. By reviewing the backlog and prioritizing the tasks, the project manager can deliver value to the customer faster and reduce the risk of rework. The other options are not aligned with agile principles, as they either delay the project, ignore the customer feedback, or cancel the project altogether. References: 1: Agile Manifesto

The agile project leader should explain the new team velocity to the customer and negotiate the scope and schedule of the project accordingly. Team velocity is a measure of the amount of work a team can handle during a single iteration1. It is affected by factors such as team size, skills, experience, and availability2. Since the team has lost two members, the team velocity will likely decrease, which means the team will not be able to deliver the same amount of work as before. The agile project leader should communicate this change to the customer and collaborate with them to prioritize the most valuable features and adjust the release plan3. Updating the restriction log with the new team capacity (A) is not a sufficient action since it does not address the impact on the project scope and schedule. Explaining the new project requirements to the team (B) is also not a good option since it may overload the team and compromise the quality and value of the product. Updating the project budget with the released team members © is not relevant since the budget has already been reduced by the customer. References:

1: Agile Practice Guide, Glossary, page 91

2: Agile Practice Guide, Chapter 2, Section 2.4.2.2

3: Agile Practice Guide, Chapter 2, Section 2.4.2.3

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

In a fixed time and budget project, the project manager needs to balance the customer’s expectations and the project’s profitability. If the customer wants the development of a core component to be based on agile practices, the project manager should use a hybrid contract that combines both fixed and agile elements. This way, the project manager can accommodate the customer’s changing requirements while maintaining control over the project scope, schedule, and cost. A tiered contract for fixed and agile components allows the project manager to define the fixed deliverables and the agile deliverables separately, and assign different payment terms and conditions for each. For example, the fixed deliverables can be paid based on milestones, while the agile deliverables can be paid based on iterations or value delivered. This also helps the project manager to manage the risks and uncertainties associated with the agile component. Providing alternatives to scope change at specific project phases within the contract is another way to control the development costs and ensure the profitability of the project. The project manager can specify the criteria and process for requesting and approving scope changes, and offer different options for the customer to choose from, such as adding or removing features, adjusting the quality standards, or modifying the schedule or budget. This way, the project manager can negotiate with the customer and reach a mutually beneficial agreement that satisfies both parties’ needs and expectations. Limiting the number of iterations for development in the contract is not a good control, as it may compromise the quality and value of the agile component. Establishing a governance committee to review the contract delivery is not a specific control for the development of the core component, but a general practice for any project. Requiring that only internal resources be utilized for this project is not a relevant control, as it does not address the customer’s requirement or the project’s profitability. References: PMBOK Guide, 6th edition, pages 704-705, 718-719.

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

In an agile project, the project manager does not assign tasks to the team members, but rather facilitates the team’s self-organization and empowerment. The team decides how to plan, execute, monitor, and control the work within the sprint, based on the agreed-upon requirements and priorities. The project manager supports the team by removing impediments, providing feedback, and ensuring alignment with the project vision and goals. The daily standup is a short meeting where the team members share their progress, challenges, and plans for the next 24 hours, not a place where the project manager instructs the team what to do. References:

Agile Practice Guide, page 37

PMBOK Guide 7th Edition, page 97

 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

The first thing the project manager should do is to evaluate the impact that the inclusion of this new requirement will have on project performance. This is because the project manager needs to assess how the new requirement will affect the project scope, schedule, cost, quality, risk, and stakeholder satisfaction. The project manager should also consider the feasibility, desirability, and viability of the new requirement, and whether it aligns with the project objectives and business case. Based on the impact analysis, the project manager can then decide whether to accept or reject the change request, or to escalate it to the appropriate authority for approval. The project manager should also communicate the results of the impact analysis to the stakeholder and explain the rationale behind the decision. References:

Change Management | What is Change Management | Prosci

What Is Project Scope? Scope Management Steps, Tips & Tools

Definition of Change Management - Prosci

According to the PMBOK Guide, 6th edition, one of the key skills of a project manager is to negotiate with stakeholders to achieve project objectives and balance the competing project constraints. Negotiation is also a tool and technique for the process of Manage Stakeholder Engagement, which aims to ensure that stakeholders’ needs and expectations are met or exceeded. By engaging in creative and iterative negotiations with the leaders of each entity, the project manager can foster collaboration, trust, and commitment among the parties involved in the project, and ensure that the launch date is acceptable and feasible for all. This will increase the likelihood of timely and successful adoption of the new solution by the entire organization. References: PMBOK Guide, 6th edition, pages 53, 513-514, 518.

 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 project manager should review the communications management plan and submit a change request if required. The communications management plan is a document that describes how the project information will be communicated to the stakeholders. It defines the communication requirements, methods, formats, frequency, and responsibilities for each stakeholder group. The project manager should review the communications management plan to understand the current communication expectations and agreements, and to identify any gaps or conflicts between the sponsor’s request and the key team members’ preferences. If the communications management plan needs to be updated to accommodate the sponsor’s request, the project manager should submit a change request and follow the change control process. Negotiating with the key team members to send a daily report and letting the sponsor know that the project cost will increase (option A) may be a possible solution, but it should be done after reviewing the communications management plan and submitting a change request if required. Recommending to the sponsor that performance of the project be reviewed once per week (option B) may not satisfy the sponsor’s needs and expectations, and may also contradict the communications management plan. Evaluating the capacity of each team member to attend daily meetings in person or virtually and reducing the time of each meeting (option D) may be a good practice, but it should also be done after reviewing the communications management plan and submitting a change request if required. References:

PMBOK Guide, 6th edition, page 377-378, section 10.1 Plan Communications Management

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

QU According to the PMBOK Guide, 6th edition, page 18, a project manager should use a combination of leadership styles depending on the situation and the needs of the team. In this case, the project manager should have used a collaborative or facilitative style to engage the team members in the agile development approach, empower them to make decisions, and set clear and measurable goals. This would have helped to create a shared vision, foster trust and commitment, and improve team performance and satisfaction. By contrast, the other options (A, B, and D) are more indicative of a directive or controlling style, which could have increased the resistance and confusion of the team members, reduced their motivation and creativity, and created a blame culture. References: = PMBOK Guide, 6th edition, page 18; Agile Practice Guide, page 13.ESTION NO: 140

A company has an existing contract to maintain and enhance a client's customer database The company's legal department informs the project manager that a new piece of legislature requiring stricter protection of customer information might soon be signed into law. The law will require additional security features to be implemented into the database the project manager is maintaining These features are not included in the scope of the current contract

What should the project manager do?

A. Ask the legal department to raise the issue in the next contract negotiation with the customer

B. Seek the project sponsor's support to influence the client to amend the contract immediately

C. Update the risk register to include this issue and discuss the appropriate risk response plans with the project sponsor and client

D. Wait until the legal requirements are finalized so the change in scope can be concretely defined

Answer: C

According to the PMBOK Guide, a risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives. A risk register is a document that records the identified risks, their analysis, and their response plans. A project manager should update the risk register whenever new risks are identified, analyzed, or resolved. In this case, the potential change in the legal requirements is a risk that could affect the project scope, cost, schedule, and quality. Therefore, the project manager should update the risk register to include this risk and its impact, probability, and priority. The project manager should also discuss the appropriate risk response plans with the project sponsor and the client, such as avoiding, transferring, mitigating, or accepting the risk. This way, the project manager can proactively manage the risk and prepare for any changes that might occur. References:

PMBOK Guide, Seventh Edition, Chapter 4: Project Integration Management, Section 4.6: Monitor and Control Project Work, Page 123

PMBOK Guide, Seventh Edition, Chapter 11: Project Risk Management, Section 11.2: Identify Risks, Page 409

PMBOK Guide, Seventh Edition, Chapter 11: Project Risk Management, Section 11.3: Perform Qualitative Risk Analysis, Page 415

PMBOK Guide, Seventh Edition, Chapter 11: Project Risk Management, Section 11.4: Perform Quantitative Risk Analysis, Page 423

PMBOK Guide, Seventh Edition, Chapter 11: Project Risk Management, Section 11.5: Plan Risk Responses, Page 431

PMBOK Guide, Seventh Edition, Chapter 11: Project Risk Management, Section 11.6: Implement Risk Responses, Page 439

PMBOK Guide, Seventh Edition, Chapter 11: Project Risk Management, Section 11.7: Monitor Risks, Page 445

According to the PMBOK Guide, 6th edition, section 9.4.2.3, the project manager should use conflict management techniques to resolve conflicts among team members and stakeholders.3

Some of the conflict management techniques are: problem solving, compromising, smoothing, forcing, and withdrawing.3

In this scenario, the project manager has tried problem solving (holding a meeting to work out a permanent solution) and compromising (asking them to find a way to resolve the issues), but these techniques were unsuccessful.4

The project manager should not use smoothing (emphasizing areas of agreement and avoiding areas of disagreement), forcing (imposing a solution), or withdrawing (avoiding or postponing the conflict), as these techniques may not address the root cause of the conflict or may worsen the situation.4

Therefore, the project manager should escalate the issue to a higher authority, such as the functional manager, the sponsor, or the steering committee, who have more power and influence in a weak matrix environment.4

Escalating the issue to a higher authority may help to resolve the conflict, protect the project objectives, and maintain the team performance and morale.4

The references for this answer are:

1: PMP Exam Questions | 100% Free PMP Example Questions 2: PMP Practice Exam 1 | Free PMP Exam Questions 3: PMBOK Guide, 6th edition, Project Management Institute, 2017, pp. 349-350. 4: [Conflict Management Techniques for the PMP Exam - PM Study Circle] : [PMP Exam Prep: Project Human Resource Management - Simplilearn]

The project manager should address the issue between the two team members by scheduling a meeting with them and using conflict resolution techniques to find a mutually acceptable solution. This way, the project manager can prevent the issue from escalating and affecting the project performance and team morale. This approach is consistent with the agile principle of fostering collaboration and trust among the team members12. References: 1: PMBOK Guide, 6th Edition, Chapter 9: Project Resource Management 2: Agile Practice Guide, Chapter 2: An Agile Mindset

The project manager should follow the risk management plan that was developed during the planning phase of the project. The risk management plan should include a risk register that identifies the potential risks, their probability and impact, and the planned responses for each risk. Since the labor union contract negotiation was documented as a risk, the project manager should log the issue and execute the risk response plan that was prepared for this situation. This may involve implementing contingency plans, fallback plans, or workarounds to minimize the negative effects of the risk on the project objectives. The other options are not appropriate because they do not follow the risk management plan or they introduce new risks or changes to the project scope, schedule, or budget. References:

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Chapter 11: Project Risk Management, pp. 397-441.

PMP® Examination Practice Questions: 400 Practice Questions and Answers to help you Pass, Question 400, p. 401.

A burndown chart is a graphical tool that shows the amount of work remaining versus the time available for a release or iteration. It helps the agile project manager and the team to monitor the progress and velocity of the work, identify any deviations or impediments, and adjust the plan accordingly. A burndown chart can provide a deeper look into the team’s progress than a release plan, a product roadmap, or a Kanban board, which are more high-level and strategic tools that show the scope, vision, and priorities of the project. 123 References:

https://www.pmi.org/learning/library/agile-metrics-progress-tracking-status-6564

https://www.forbes.com/advisor/business/what-is-agile-project-management/

QUE : A self-organizing team is a team that has the autonomy and authority to manage its own work and make its own decisions. A self-organizing team is also expected to adapt to changing situations and learn new skills as needed. Therefore, the best management decision for this situation is to provide opportunity for team members to learn and adjust to the new technology, rather than moving them, adding new members, or re-assigning the project. This will help the team overcome the learning curve and improve their velocity in the future. It will also foster trust, collaboration, and innovation within the team. Providing opportunity for team members to learn and adjust to the technology is consistent with the agile principles and values, which emphasize continuous improvement, customer satisfaction, and team empowerment. It is also covered in the PMBOK Guide under the Develop Team process, and in the PMI-PBA Exam Content Outline under Domain III: Analysis. References:

PMBOK Guide, 7th edition, page 247

PMI-PBA Exam Content Outline, 2018, page 11

Agile Manifesto

STION NO: 184 DRAG DROP

Drag the interpersonal skill on the left to the correct scenario on the right.

Answer: