PMI Updated PMP Exam Questions and Answers by saskia

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

The project manager should include knowledge transfer sessions between the project and operations teams at every stage of the migration project. Knowledge transfer is the process of sharing or disseminating knowledge from one party to another. It is essential for ensuring that the operations team is ready and capable of supporting the new system once the project is completed. By including knowledge transfer sessions at every stage, the project manager can ensure that the operations team is aware of the changes, benefits, and challenges of the new system, and can provide feedback and suggestions to the project team. This will also help to build trust and collaboration between the project and operations teams, and reduce the risk of resistance or rejection from the operations team. Creating a lessons learned register to include operations team training for future projects (option A) is a good practice, but it does not address the current situation or the needs of the operations team. Changing the project management plan to add a final stage for product handoff to the operations team (option C) may be necessary, but it does not ensure that the operations team is prepared and trained to support the new system. Preparing detailed documentation to be shared with the operations team during project closure (option D) is also important, but it may not be sufficient or timely to enable the operations team to understand and use the new system effectively. References:

PMBOK Guide, 6th edition, page 417-418, section 12.3.1.3 Knowledge Transfer

[Agile Practice Guide], page 77, section 5.2.2 Knowledge Transfer

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

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

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

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

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

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

According to the PMBOK® Guide, 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