According to the PMBOK Guide, 7th edition, one of the key activities in the monitoring and controlling phase of a project is to control quality by verifying that the project deliverables conform to the quality standards and requirements. This involves inspecting and testing the deliverables, reviewing the quality documentation, and requesting corrective actions if needed. The other options are either inefficient, ineffective, or not aligned with the quality management principles. References: PMBOK Guide, 7th edition, page 123-124, section 3.5.2.1.

In Agile project management, when there is a lack of clarity on the requirements, it’s beneficial to start with the product prototype development1. This approach allows the team to create a tangible representation of the product that can be reviewed with the customer1. The feedback gathered from this review can then be used to refine the requirements and reduce ambiguity1. This iterative process of development, review, and feedback is a key aspect of Agile methodologies and helps ensure that the final product aligns with the customer’s needs and expectations234. References: 2314

https://www.scrum.org/resources/blog/five-essential-things-needed-agile-transformation

https://project-management.com/agile-project-management/

In a virtual team, especially one that is globally distributed, it is crucial for the project manager to establish clear communication protocols and expectations. This includes defining roles and responsibilities, setting up a workable schedule considering different time zones, and respecting cultural observances. This approach ensures that all team members are on the same page and can collaborate effectively, thereby fostering team building. References: PMBOK® Guide – Sixth Edition, Section 10.3.2.1: Plan Communications Management

For a project in a remote rural area, especially one nearing completion, the most effective communication method with the local community would likely be through newspapers. This approach is suitable for reaching a broad audience in a locality where digital communication channels like social media or email may not be as accessible or frequently used. Newspapers are a traditional and reliable means of communication that can effectively convey important updates to all segments of the local population, including those who may not have access to or prefer not to use digital media.

The PMBOK® Guide emphasizes the need to tailor communication methods to the stakeholders’ needs and the context of the project1. It suggests that the format of communication should depend on the type of stakeholder, and various ways should be tailored to each group1. This is supported by the Professional in Business Analysis (PBA) reference materials, which advocate for the analysis of stakeholder needs and the selection of an engagement approach that best suits stakeholders’ needs for effective communication and collaboration2.

To implement Agile practices effectively, the project lead should:

A: Introduce sprints and sprint reviews to support iterative planning and frequent inspection.

B: Establish team working agreements (ground rules) to improve self-management.

E: Foster full participation in daily stand-ups to promote collaboration and team accountability.

Option C is too restrictive; valuable issues can be parked and discussed after.

Option D goes against Agile principles, where the team self-manages and Scrum Master facilitates rather than delegates meeting leadership.

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

PMBOK Guide, 7th edition, page 215

PMI-PBA Exam Content Outline, 2018, page 12

The issue log is a project document where the project manager records and tracks issues that can impact the project. In this case, the inability of the supplier to deliver the materials due to a large-scale labor problem is an issue that can impact the project. Therefore, the project manager should update the details of this issue in the issue log and communicate it to the relevant stakeholders. This will ensure that everyone is aware of the issue and can work together to find a solution. References: Project Management Professional (PMP)® Examination Content Outline, June 2015, PMI; A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Project Management Institute, Inc., 2017.

In project management, it’s important to maintain open and transparent communication with all stakeholders, including unsuccessful bidders. Meeting with the unsuccessful bidder not only provides them with feedback but also maintains a good relationship with them, which could be beneficial for future projects. This approach aligns with the principles of stakeholder management and communication management in project management practices. References: 

https://bordio.com/blog/how-to-become-a-project-manager/

https://www.indeed.com/career-advice/career-development/how-to-become-a-project-manager

 According to the Project Management Professional (PMP) guidelines, effective communication is crucial for the success of a project. In this scenario, the project manager is facing challenges with the current communication channels. The best course of action is to collaborate with the project team and agree on a suitable communication method that ensures information is shared promptly and effectively. This proactive approach can help avoid delays and negative consequences for project delivery. References: PMBOK Guide, Communication Management. Please refer to the specific sections in the PMBOK Guide and PMP study materials for more detailed information.

According to the Project Management Professional (PMP) principles, a project manager should actively engage with team members to identify and resolve issues. In this scenario, the project manager should meet with the designer to understand the challenges and work collaboratively to find a solution. This approach promotes open communication, problem-solving, and maintains the momentum of the project. References: PMBOK® Guide – Sixth Edition, Section 9.5.2.1: Manage Team

According to the PMBOK Guide, 7th edition, one of the challenges of agile project management is to align the expectations and understanding of the stakeholders with the agile values and principles. This is especially important when the organization is transitioning from a predictive to an agile approach, as there may be resistance or confusion from the executives who are used to a different way of working. Therefore, the best way to resolve the conflicts between the project team and the executives is to train the executives on agile practices, such as iterative development, adaptive planning, customer collaboration, and continuous improvement. This will help the executives to appreciate the benefits of agile, support the project team, and provide constructive feedback. Training the executives on agile practices will also foster a culture of trust, respect, and empowerment, which are essential for agile project success. References: PMBOK Guide, 7th edition, page 14, Section 1.3.2, Agile Project Management; page 17, Section 1.4.2, Agile Mindset; page 19, Section 1.5, Agile Principles.

In a global project team, when requests outside the defined scope for a local team are received, it is important for the project manager to evaluate and understand the cause of the conflict. This involves analyzing why the requests are being directed to the local team instead of the global team and determining if there is a misunderstanding or miscommunication regarding the division of scope. By doing so, the project manager can address the root cause of the issue and work towards a resolution that aligns with the project’s defined scope and responsibilities12.

Transitioning to an agile approach requires a shift in mindset and practices, especially when the team is inexperienced and working remotely. As a servant leader, the project manager should focus on coaching the team members to enhance their engagement and collaboration. This involves empowering the team, facilitating a supportive environment for learning, and encouraging open communication. Coaching helps in building a strong team dynamic that is essential for agile teams, particularly in a remote setting where team members may feel disconnected. By coaching, the project manager can help the team members to understand the agile values and principles, thereby increasing their commitment to the project goals.

The answer is supported by the principles of agile project management, which emphasize the importance of servant leadership and coaching for team development and engagement123. Additionally, the guidance on working with remote agile teams suggests that coaching and fostering collaboration are key to maintaining team commitment and performance4567.

In project management, it’s crucial to address stakeholders’ concerns and align the project with their requirements. This is especially true when there are uncertainties, such as in this case where there are no proper records for the original design and execution of the product. By acknowledging the stakeholders’ concerns through open dialogues, the project manager can understand their perspectives and adjust the project plan accordingly. This approach also allows the project manager to apply lessons learned from past projects, which can be invaluable in managing risks and uncertainties. References: Project Management Professional (PMP) Reference Materials source and documents, Professional in Business Analysis Reference Materials study guide.

Agile methodology offers several benefits from a project evaluation perspective. One of the key benefits is that it allows for early and incremental delivery of functionality, which in turn delivers more value1. This is because Agile projects offer incremental delivery, customers can see constant progress in their projects1. You can demonstrate working functionalities to customers with every Sprint, allowing them to see continual progression1. Since working functionalities are delivered faster, this means your customer will get a product to market faster, as well1. This early delivery of functionality not only provides value to the customer sooner but also allows for early feedback and the ability to make changes as needed, thereby increasing the overall value of the project2. References: 

https://projectmanagementacademy.net/resources/blog/benefits-of-the-agile-methodology/

When a project manager realizes that some stakeholders are working against the success targets of the project, it’s important to engage all stakeholders, including the unsupportive ones. This is because every stakeholder has a role to play in the project, and their concerns need to be addressed for the project to succeed.

The project manager should also update the project stakeholder analysis and methods to satisfy the stakeholders’ requirements. This involves identifying the needs and expectations of the stakeholders and developing strategies to meet them. By doing so, the project manager can ensure that the stakeholders are satisfied and that their concerns are addressed, which can lead to their support for the project.

While escalating the issue to the functional manager (option B), involving all stakeholders by distributing status reports (option C), and focusing on the supportive stakeholders (option D) might be part of the subsequent actions, the immediate steps should be to engage all stakeholders and update the stakeholder analysis and methods.

Project Management Body of Knowledge (PMBOK) Guide, 6th Edition, Section 13: Stakeholder Management.

When a new stakeholder is assigned to a project and expresses concerns about the benefits of the deliverables, it is important to address these concerns directly and proactively. The benefits realization plan is designed to outline the activities necessary for achieving the planned benefits, including a timeline, tools, resources, and metrics for measuring progress. Reviewing this plan with the stakeholder can help clarify how the deliverables will contribute to the project’s benefits and align with the stakeholder’s expectations. This approach is supported by the Benefits Realization Management Framework, which emphasizes the importance of engaging stakeholders in understanding and supporting the benefits realization process. References: (Benefits Realization Management Framework, PMI1; Benefits Realization Management Practice Guide, PMI2; BrainBOK3; Project Management Templates4)

This question fits the People domain because it focuses on team empowerment, leadership, and decision-making behavior. PMI’s PMP Examination Content Outline emphasizes that the project manager should determine and bestow appropriate levels of decision-making authority and address and remove impediments, obstacles, and blockers for the team. In this scenario, the issue is not simply that the team is failing to decide; the deeper problem is that the team is uncomfortable, hesitant, or constrained in some way. The project manager should first understand the root cause of that hesitation before trying to force new behavior.

Option A moves too quickly into behavior change without diagnosing why the team avoids decisions. Option B is overly formal and not the best first action; KPIs do not solve psychological safety or confidence issues. Option C ignores a clear team-development problem. The best PMP-aligned response is to understand the obstacles and then work with the team on improvement, which reflects servant leadership and sustainable team development rather than command-and-control management.

According to the PMBOK Guide, project closure is the process of finalizing all activities across all of the project management process groups to formally complete the project or phase1. Project closure involves verifying that all the project deliverables have been completed and accepted by the customer or sponsor, confirming that all the contractual obligations have been met, documenting the project performance and lessons learned, releasing the project resources, and archiving the project records2.

In this question, the project manager is faced with a problem that the client will not agree to closure, claiming that the project team has not performed the code inspections mandated in the development contract. The project team has performed the code inspections, however the records are not complete. This indicates that there is a discrepancy between the contractual requirements and the project documentation, which can lead to disputes, claims, or litigation. The project manager should approach this problem by holding a meeting with the project team, project sponsor, and the client to agree to the further work required to close the project and add to lessons learned. This way, the project manager can facilitate a constructive dialogue among the key stakeholders, clarify the expectations and obligations of each party, negotiate a mutually acceptable solution, and document the agreed actions and outcomes. This will also help to maintain the relationship with the client, ensure customer satisfaction, and capture the lessons learned for future projects.

The other options are not the best actions to take to solve this problem. Seeking expert legal advice on the interpretation of the clauses in the contract is a possible option, but it should be done after trying to resolve the issue amicably with the client and the sponsor. Seeking legal advice may also escalate the conflict and damage the trust and goodwill with the client. Closing the project and handing over the deliverables to the client is not advisable, as it may violate the contract terms and expose the project to legal risks. Holding a lessons learned workshop with the project team and project sponsor to avoid contractual compliance issues arising in future projects is a good practice, but it does not address the current issue with the client and the project closure.

 1: PMBOK Guide, 6th edition, p. 123 2: PMBOK Guide, 6th edition, p. 125

When multiple stakeholders and organizational layers are involved, it ' s essential to have a well-defined Communications Management Plan. This plan outlines what information will be shared, how, when, and with whom. It integrates both agile practices (e.g., information radiators, daily standups) and organizational needs (e.g., formal reports, PMO templates).

PMBOK® Guide – Seventh Edition emphasizes tailoring communication strategies based on stakeholder needs and context. Agile teams are encouraged to remain transparent and adapt communication forms to suit stakeholders (Agile Practice Guide, Chapter 6).

Option A ignores the need for comprehensive documentation.

Option B is incomplete and doesn’t cover all communication formats.

Option C prioritizes PMO policy over project-specific needs.

 The first step for a project manager in this scenario is to inform the neighbor that all project documentation, including the initial project plans, has been approved. This action is in line with the best practices of project management, which emphasize transparency and communication with stakeholders. It is important to provide assurance that the project is proceeding according to the approved plans and specifications. If the neighbor’s concerns persist, the project manager can then consider escalating the issue or requesting a formal complaint, but the initial response should be informative and aim to clarify any misunderstandings.

This response is based on the principles of stakeholder engagement and communication found in the PMBOK® Guide and the Professional in Business Analysis (PBA) reference materials, which highlight the importance of addressing stakeholder concerns promptly and transparently123.

In a hybrid project, it is common to use both predictive and agile approaches. If a key stakeholder is only familiar with predictive approaches, it could be challenging for them to understand and contribute effectively to the project. Therefore, it would be beneficial for the project manager to allocate time to mentor the stakeholder in the selected project approach. This would help the stakeholder understand the hybrid approach better and enable them to contribute more effectively to the project. References: Project Management Professional (PMP) Reference Materials, Professional in Business Analysis Reference Materials study guide. Please note that the exact documents and page numbers are not provided as the information is based on general project management principles. For more detailed information, please refer to the specific guides and documents mentioned.

Before taking any action, the project manager should gather more context and engage the team to assess feasibility. This includes evaluating schedule impacts, resource constraints, regulatory implications, and whether scope trade-offs are required. This approach aligns with the PMBOK® Guide’s recommendation to evaluate change impacts before making decisions.

Option A is misaligned; root cause analysis is more appropriate for problem resolution, not for scope acceleration.

Option B assumes approval and feasibility without review.

Option C applies to Agile backlog reprioritization but this is a regulatory milestone, likely not in a product backlog.

When a change (such as a new regulatory requirement) is introduced, the first step is always to assess the potential impact. This allows the project manager to understand how scope, schedule, cost, or quality may be affected. Only after assessing the impact should changes be formally documented and implemented.

The PMBOK® Guide – Seventh Edition emphasizes adaptive planning and impact assessment in response to external change (e.g., legal or regulatory). The guide states: " Assess changes to determine impact before recommending a course of action. "

Option A (Increase slack) is reactive and premature without assessment.

Option B implies implementation before assessing consequences.

Option C (Consult the plan) might follow, but impact assessment is the most immediate and necessary action.

In Scrum, the product owner is the sole person responsible for managing the product backlog. When a customer requests new features mid-sprint, it is inappropriate to add them directly to the sprint. The correct procedure is to have the Scrum Master direct the customer to the product owner, who will evaluate the request and decide whether to include it in the product backlog for future prioritization.

According to the Agile Practice Guide and the Scrum Guide, only the product owner has the authority to accept or reject items in the product backlog. The Scrum Master facilitates communication and protects the team from scope creep during the sprint.

Option A (Definition of Done) is useful for clarifying quality, not for managing scope changes.

Option C (Acceptance criteria) applies to existing backlog items, not new feature requests.

Option D (Backlog prioritization) is the product owner’s job and only happens after the sprint, not mid-sprint.

????

In Agile (particularly Scrum), the Product Owner is solely responsible for backlog prioritization. The Scrum Master facilitates the process but does not have authority over content decisions. When a conflict arises about prioritization, the resolution lies in re-establishing role clarity—not in the project manager stepping in to override roles.

The correct action is to reinforce Agile roles and responsibilities, particularly that the Product Owner owns prioritization. This aligns with the Agile Practice Guide and the Scrum Guide.

Option B may be helpful but delays resolution and misses the fundamental answer.

Option C incorrectly shifts authority to the Scrum Master.

Option D bypasses the Agile team structure and disrespects team autonomy.

In an agile project with a fixed budget and aggressive timeline, it is crucial to prioritize the backlog effectively. The project manager should review the backlog items and decide which ones are essential to meet the project goals and deliver value. This involves evaluating each item’s impact on the project’s success and its alignment with the project’s objectives. By focusing on the most valuable activities, the project manager can ensure that the team’s efforts are directed towards tasks that will contribute most significantly to the project’s outcomes, even with limited time and resources234.

When a key stakeholder introduces a new requirement, it is essential for the project manager to request further clarification. This ensures that the requirement is fully understood and its impact on the project schedule can be accurately assessed. The PMBOK Guide emphasizes the importance of clear communication and understanding stakeholders’ needs for successful project management1. Additionally, the PMI-PBA highlights the need for detailed requirement analysis to manage changes effectively and align them with business objectives2. References:

Stakeholder Analysis: Pivotal Practice to Project Success | PMI1

PMI Professional in Business Analysis (PMI-PBA)® Handbook2

Test-Driven Development (TDD) is a widely used Agile engineering practice that ensures quality is embedded early in the development cycle. By writing tests before code, developers maintain focus on producing working, high-quality software that meets functional requirements and reduces rework and bugs.

According to the Agile Practice Guide and XP (Extreme Programming) principles, TDD is a proactive method to maintain high quality under fast delivery constraints. It helps reduce technical debt, enables continuous integration, and supports long-term maintainability.

Option A suggests reducing quality, which contradicts the Agile value of delivering working, high-quality software.

Option B focuses on reducing complexity but doesn’t specifically improve quality.

Option D postpones addressing quality and technical debt, risking product instability.

 The project manager should have conducted periodic reviews with the manager on resource availability. This proactive approach would have allowed the project manager to identify the capacity issue earlier and take measures to mitigate the risk of a delayed equipment installation. Regular reviews can reveal potential conflicts or shortages in resources, allowing for timely interventions such as securing additional resources or adjusting the project schedule accordingly21. References: = Project Management Professional (PMP) Certification, Professional in Business Analysis (PMI-PBA) Handbook.

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

The project manager should discuss the issue with the functional manager to understand the reason for the complaint. This is the best option because it shows the project manager’s respect and communication skills, as well as the willingness to resolve the conflict in a constructive way. By discussing the issue with the functional manager, the project manager can also clarify the expectations, roles, and responsibilities of the team member, as well as identify the root cause and possible solutions for the problem. This option also aligns with the PMBOK® Guide’s guidance on managing stakeholder engagement, which includes addressing and resolving issues, and fostering collaboration among stakeholders1.

The other options are not as effective as option B. Option A is not fair and may demotivate the team member and the rest of the team. Option C is not collaborative and may escalate the conflict. Option D is not realistic and may create more interruptions and resistance from the functional manager. References: 1: PMBOK® Guide, 6th edition, page 518

According to the PMBOK Guide, the project manager should assess the situation to understand how the organization’s culture impacts the decision-making process, and coach the team toward a new model. This is because the project manager is responsible for facilitating the team’s decision-making process and ensuring that it aligns with the agile principles and values1. The project manager should also consider the following factors that may affect the team’s decision-making process2:

The level of empowerment and autonomy given to the team by the organization and the stakeholders

The degree of collaboration and communication among the team members and with other parties

The availability and quality of information and data to support the decision-making process

The complexity and uncertainty of the project environment and the product requirements

The time and resource constraints and the impact of delays on the project outcomes

The potential risks and opportunities associated with the decisions and the alternatives

The feedback and learning mechanisms to evaluate and improve the decision-making process

The project manager should coach the team toward a new model of decision-making that is more agile and adaptive, such as the following3:

Decentralized decision-making: The team members are empowered to make decisions within their scope of work and authority, without waiting for approval from higher levels of management. This can increase the team’s speed, efficiency, and ownership of the decisions.

Collaborative decision-making: The team members work together to make decisions that benefit the project and the stakeholders, rather than competing or conflicting with each other. This can enhance the team’s creativity, innovation, and quality of the decisions.

Data-driven decision-making: The team members use empirical evidence and data to support their decisions, rather than relying on assumptions or opinions. This can improve the team’s accuracy, reliability, and transparency of the decisions.

Iterative decision-making: The team members make decisions in small increments and cycles, rather than in large batches and phases. This can allow the team to adapt to changing conditions and feedback, and to deliver value early and frequently.

Value-based decision-making: The team members make decisions that maximize the value delivered to the customer and the stakeholders, rather than focusing on the cost or the schedule. This can ensure the team’s alignment with the project vision and goals.

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

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

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

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

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

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

 According to the Project Management Body of Knowledge (PMBOK), one of the key responsibilities of a project manager is to ensure that lessons learned from previous projects are applied to current projects. This helps to avoid repeating the same mistakes and to leverage successful strategies. In this scenario, the project manager should share the lessons learned from the previous project with the team member. This will not only help to resolve the current issue more efficiently but also contribute to the team member’s learning and development. References: PMBOK Guide, 6th Edition, Section 4.4.3.1 - Lessons Learned Register

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

Adaptive leadership is a practical leadership framework that helps individuals and organizations adapt and thrive in challenging environments. It is being able, both individually and collectively, to take on the gradual but meaningful process of adaptation. It is about diagnosing the essential from the expendable and bringing about a real challenge to the status quo1. A team lead who is highly engaged and involved in a project and is operating without a chain of command or authority levels is demonstrating adaptive leadership by anticipating future needs, articulating those needs to build collective support and understanding, adapting their responses based on continuous learning, and demonstrating accountability through transparency in their decision-making process1.

The other options are not correct because they do not match the description of the team lead. Directive leadership is a style of leadership that involves giving clear and specific instructions to the followers and expecting them to follow them without question2. Commanding leadership is a style of leadership that involves exerting control and authority over the followers and demanding compliance and obedience3. Servant leadership is a style of leadership that involves putting the needs and interests of the followers first and empowering them to grow and develop4. None of these styles reflect the team lead’s behavior of being highly engaged and involved in the project and operating without a chain of command or authority levels. References: 1 5 Principles to Guide Adaptive Leadership, Harvard Business Review2 Directive Leadership Style: Definition, Examples, Pros & Cons, Indeed3 Commanding Leadership Style: Definition, Examples, Pros & Cons, Indeed4 Transformational versus Servant Leadership: A Difference in Leader Focus, Regent University.

 The project manager should raise a new issue in the issue log and convene SMEs and relevant stakeholders to identify alternatives to address the problem. This is because the inability of the subcontractor to supply a key component is an issue that has already occurred and needs to be resolved as soon as possible. The issue log is a tool for documenting and monitoring the resolution of issues that arise during a project1. The project manager should also involve the SMEs and relevant stakeholders who have the expertise and authority to provide input and guidance on how to deal with the issue. The project manager should not discuss the issue with the project sponsor and request extra time and budget to obtain the component from a different supplier, as this would be premature and may not be the best option. The project manager should not raise a new risk in the risk register, perform a risk assessment, and convene SMEs and relevant stakeholders to plan a risk response, as this would be appropriate for a potential problem that has not yet occurred, not an actual issue that has already happened. The project manager should not submit a change request to the CCB for changes to the performance measurement baseline to obtain the component from a different supplier, as this would be a formal process that requires approval and may not be necessary if the issue can be resolved in other ways. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK® Guide, 6th edition, Section 4.6.1.1, “Issue Log”

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

1: PMBOK Guide, 6th edition, p. 89

2: PMBOK Guide, 6th edition, p. 456

3: PMBOK Guide, 6th edition, p. 457

4: PMBOK Guide, 6th edition, p. 458

A minimum viable product (MVP) is a product with the minimum features that can deliver value to the customer and validate the product concept1. To estimate the cost of an MVP, the project manager can use agile methods such as user story points and forecasting. User story points are a relative measure of the size and complexity of a user story, which is a description of a feature from the user’s perspective2. Forecasting is a technique that uses historical data and trends to project future outcomes3. By estimating the user story points for each feature of the MVP and using forecasting to calculate the time and resources needed, the project manager can report a realistic and accurate budget for the MVP. This approach is more suitable than the other options because:

B. Determining the control accounts and using a top bottom estimate is a traditional method that is more applicable to large and complex projects with well-defined scope and requirements. It involves breaking down the project into smaller units and estimating the cost of each unit from the top level to the bottom level. This method may not be flexible enough to accommodate the changes and uncertainties that are common in MVP development.

C. Considering the cost performance index (CPI) based on earned value (EV) divided by costs is a method that is used to measure the efficiency of the project performance. It compares the value of the work completed with the actual cost incurred. This method is not relevant for estimating the cost of an MVP, as it requires the project to be already in progress and have a baseline plan to compare with.

D. Calculating the budget at completion (BAC) based on the completed and planned features is a method that is used to estimate the total cost of the project at the end of its life cycle. It involves adding up the actual cost of the work done and the estimated cost of the remaining work. This method is not appropriate for estimating the cost of an MVP, as it assumes that the scope and features of the project are fixed and known in advance, which is not the case for MVP development.

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

PMBOK Guide 7th Edition, page 67, section 3.2.2

PMI Agile Practice Guide, page 33, section 3.2.1

PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 14, section 3.3.1.1

According to the PMBOK Guide, the project manager is responsible for managing the project work and ensuring that the project objectives are met. One of the processes in the project management process group is Monitor and Control Project Work, which involves tracking, reviewing, and reporting the progress and performance of the project, as well as identifying and resolving issues. The project manager should use the issue log, a project document that records and tracks the issues that arise during the project, to document the issue of the missing notification and assign it to the appropriate project team member(s) for resolution. The project manager should also communicate the issue to the relevant stakeholders and update the project management plan and other project documents as needed. The project manager should not close out the project until the issue is resolved and the system migration is completed for all departments, as this would compromise the quality and scope of the project deliverables. The project manager should also not escalate the issue to the project sponsor and upper management, as this would indicate a lack of control and responsibility for the project. The project manager should also not report the issue during the next status meeting at the end of the week, as this would delay the resolution and potentially cause more problems for the project. The project manager should act promptly and proactively to address the issue and ensure the project is closed successfully. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 6th edition, Chapter 4: Project Integration Management, Section 4.6: Monitor and Control Project Work, p. 123-127

PMBOK Guide, 6th edition, Appendix X1: Agile, Iterative, Adaptive, and Hybrid Project Environments, Section X1.5.2: Issue Log, p. 715

Business Analysis for Practitioners: A Practice Guide, Chapter 5: Traceability and Monitoring, Section 5.3: Monitoring the Performance of Business Analysis Work, p. 143-144

The PMI Guide to Business Analysis, Chapter 7: Solution Evaluation, Section 7.3: Assess Solution Limitations, p. 373-374

The project manager should not ignore the new regulation, as it may affect the quality, scope, and compliance of the software. Nor should the project manager bypass the sponsor’s authority and include the new requirement without approval. The project manager should also not release the software as is and start a new project, as this may create unnecessary rework, waste, and risk. The best option is to collect the requirements of the regulation and follow the change control process, which involves analyzing the impact of the change, obtaining approval from the sponsor and other stakeholders, and updating the project management plan and baselines accordingly. This way, the project manager can ensure that the software meets the customer’s needs and expectations, as well as the legal and regulatory requirements. References: (Professional in Business Analysis Reference Materials source and documents)

PMBOK Guide, 7th edition, section 4.6.1, page 113

PMI Professional in Business Analysis (PMI-PBA) Guide, 2nd edition, section 5.3, page 87

 A hybrid approach is a combination of agile and predictive methods that can be applied to different phases or modules of a project. A hybrid approach can be suitable for a project that has both uncertain and certain aspects, such as a long research process followed by incremental delivery of complex equipment. A hybrid approach can allow the project manager to adapt to changing requirements and customer feedback in the agile part, while ensuring quality and control in the predictive part. A hybrid approach can also balance the benefits and challenges of both agile and predictive methods, such as flexibility, speed, risk, scope, and stakeholder satisfaction. References: PMBOK Guide 7th Edition, Chapter 2.2.2; Agile Practice Guide, Section 2.1.2.