Explanation The project manager should ask the Scrum team members to share retrospectives because they can provide valuable insights and feedback on the project performance,processes, and practices. Retrospectives are an agile technique that helps teams to identify what went well, what can be improved, and what actions can be taken to enhance future performance. By asking the Scrum team members to share retrospectives, the project manager can facilitate a collaborative and constructive learning environment, and capture the lessons learned from both the agile and traditional aspects of the hybrid project. This can also help to increase the stakeholder's appreciation and understanding of the Scrum team's contribution and value to the project. References: A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition, Chapter 3.2.4, page 57 Agile Practice Guide, Chapter 3.3.2, page 48 PMP Exam Content Outline, Domain III: Executing, Task 9
Explanation The project manager should meet with the stakeholders involved to clearly define their roles and responsibilities with regard to the benefit. This will help to clarify the expectations, avoid confusion, and ensure alignment of the project objectives with the business needs. Option A is not the best answer because documenting the risk in the risk register and generating the risk responses and their respective associated plans is a reactive approach that does not address the root cause of the problem. Option B is not the best answer because meeting with the customer to obtain consensus with the recipient of the benefit and determine a means to deliver the benefit may not resolve the issue of who is responsible for delivering the benefit. Option C is not the best answer because understanding the context of the situation and escalating the problem to the steering committee may not be necessary or appropriate if the project manager can resolve the issue by meeting with the stakeholders involved. References: Top 60+ PMP Exam Questions and Answers for 2023 - KnowledgeHut However, I cannot guarantee that this answer is 100% verified or accurate, as it is based on a third-party source and not the official PMI reference materials. Therefore, I suggest you to consult the official PMI website2 or other reliable sources for more information and confirmation. I hope this helps.
Explanation According to the PMBOK Guide, the project manager is responsible for selecting the appropriate project delivery approach based on the project characteristics, stakeholder needs, and environmental factors. One of the project delivery approaches is agile, which is a flexible and iterative method that embraces change and delivers value incrementally. Within agile, there are different frameworks or methods, such as Scrum, Kanban, Spiral, and Rapid Application Development (RAD). Each of these methods has its own advantages and disadvantages, depending on the project context and requirements. In this scenario, a customer support team has planned short, iterative cycles for working on customer-reported issues, which indicates an agile approach. However, recently, there was a surge of high-priority issues that disrupted the original plan, and the team's manager is finding it difficult to manage the progress. The question asks which approach the project manager should suggest using in this situation. The best approach for this scenario is agile Kanban, which is a method that uses a visual board to manage the flow of work and limit the work in progress. Kanban can help the project manager and the team prioritize the most important issues, monitor the status and progress of each issue, and optimize the delivery of value to the customers. Kanban is suitable for projects that have frequent and unpredictable changes, as well as high variability and uncertainty. Agile Scrum, Spiral, and RAD are not the best approaches for this scenario, as they have different characteristics and assumptions that may not fit the project context and requirements. Scrum is a method that uses fixed-length iterations called sprints to deliver potentially shippable increments of the product. Scrum is suitable for projects that have stable and committed teams, clear and prioritized requirements, and minimal changes within each sprint. Spiral is a method that combines elements of waterfall and prototyping, using a cyclical process of planning, risk analysis, engineering, and evaluation. Spiral is suitable for projects that have complex and high-risk requirements, as well as the need for extensive testing and validation. RAD is a method that uses rapid prototyping and user feedback to deliver functional components of the product in a short time frame. RAD is suitable for projects that have well-defined and modularized requirements, as well as the availability of user involvement and collaboration. References: PMBOK Guide, 7th edition, pages 27-28, 1.4 Tailoring; pages 29-30, 1.5 Project Delivery Approaches; pages 31-32, 1.6 Project Delivery Methods.
