PMI Updated PMP Exam Questions and Answers by nolan

 According to the PMBOK Guide, 7th edition, section 12.2.3, “The issue log is a project document used to capture and track issues until they are resolved. It typically contains a description of the issue, the owner, the priority, the status, the resolution, and any other relevant information.” Therefore, the project manager should schedule a meeting with the concerned team member to review and update the issue log together, as this will help to document the issue, assign responsibility, monitor progress, and implement resolution. Asking the team member to follow the approved communications management plan to communicate their issue (option A) may not be sufficient or timely, as the issue may require immediate attention and action. Reviewing the risk register with the team member to find the proper response action for this issue (option C) may not be applicable or effective, as the issue may not be a risk that was identified and planned for in advance. Asking the team member to raise a change request to assess the issue in detail (option D) may not be necessary or appropriate, as the issue may not affect the project scope, schedule, cost, or quality, and may be resolved within the project team. References:

PMBOK Guide, 7th edition, section 12.2.3

PMI-PBA Exam Practice Test and Study Guide, 2nd edition, page 184, question 22

The project manager should alert the new project sponsor about the issues that are affecting the project delivery as soon as possible, and seek their support and guidance. The best way to do this is to send an email that summarizes the project status and key concerns, and request an immediate face-to-face meeting to discuss them. This way, the project manager can communicate the urgency and importance of the situation, and establish a direct and personal connection with the project sponsor. The project manager should also prepare a clear and concise agenda for the meeting, and provide relevant information and data to support their claims and recommendations.

Option A is not a good choice, because it is passive and hopeful, rather than proactive and assertive. The project manager should not rely on the project sponsor to find time to attend the project team’s weekly meetings, which may not be relevant or convenient for them. The project manager should initiate a dedicated meeting with the project sponsor to address the specific issues and concerns.

Option C is also not a good choice, because it is ineffective and inefficient. The project manager should not continue emailing updated project status reports, which may not capture the attention or interest of the project sponsor, and may not convey the severity and impact of the issues. The project manager should not wait for the project sponsor to request a meeting, which may not happen in time or at all. The project manager should take the initiative and responsibility to escalate the issues and seek the project sponsor’s involvement and support.

Option D is not a good choice, because it is incomplete and insufficient. The project manager should not just complete a risk analysis and email a copy of the risk register, which may not be enough to persuade or inform the project sponsor. The project manager should also explain the context and background of the issues, and propose possible solutions and actions. The project manager should also follow up with a meeting request, rather than just urging the project sponsor to respond.

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

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

According to the Professional in Business Analysis (PMI-PBA)® Guide, a minimum viable product (MVP) is a version of a product that has enough features to satisfy early customers and provide feedback for future development. A MVP is a way of delivering value to customers quickly and iteratively, while minimizing waste and risk. In this scenario, the project manager is faced with a drastic reduction in the project timeline, from 18 months to six months. This means that the original scope and schedule are no longer feasible, and the project manager needs to find a way to deliver a product that meets the customer’s needs and expectations within the new constraints. Reviewing the project backlog and prioritizing the high-value items that can be delivered in six months is a sensible approach to achieve this goal. The project manager can then work with the stakeholders to define and agree on the MVP that will provide the most value to the customer and the business. This option also allows for flexibility and feedback, as the MVP can be refined and improved based on customer feedback and changing requirements. Planning for overtime, applying crashing and fast tracking, and sharing the risk of failure are options that try to compress the schedule without reducing the scope. These options may increase the cost, quality, and resource risks, and may not be acceptable to the stakeholders or the customer. Seeking approval to triple the project budget and hiring more people is an option that tries to increase the resources without reducing the scope. This option may not be feasible or realistic, as it assumes that the sponsor is willing and able to provide the additional funds, and that the project can benefit from adding more people in a short time. This option may also introduce communication, coordination, and integration challenges, and may not guarantee the delivery of the product in six months. Going over the critical path with stakeholders and explaining why it is not possible to deliver all the scope in the expected timeline is an option that tries to justify the original plan without considering alternatives. This option may not be satisfactory to the stakeholders or the customer, as it does not offer any solution or value proposition. This option may also damage the relationship and trust between the project manager and the stakeholders, and may result in the cancellation or termination of the project. Conclusion: Given the options, Option B stands out as the most viable and effective action. Reviewing the project backlog and coming up with a MVP that fits the expected timeline addresses the customer’s needs and expectations, delivers value quickly and iteratively, and minimizes waste and risk. Among the presented choices, Option B emerges as the optimal solution. PMP Exam Content Outline Mapping Domain Task Process Task 2: Execute the project Topics Covered Minimum Viable Product (MVP) Project Backlog Prioritization Value Delivery References: (Professional in Business Analysis Reference Materials source and documents)

Professional in Business Analysis (PMI-PBA)® Guide, Chapter 5, Section 5.3.1.2

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition, Chapter 5, Section 5.2.2.2

The Standard for Project Management – Seventh Edition, Chapter 3, Section 3.2.2.2