Explanation According to the PMBOK Guide, an assumption log is a project document that records the assumptions and constraints that affect the project planning and execution. The assumption log helps to identify, validate, and monitor the assumptions and constraints throughout the project life cycle, and to address any deviations or changes that may occur. The assumption log also helps to communicate the assumptions and constraints to the project stakeholders, and to manage their expectations and feedback. In this scenario, the project manager faces a fixed-cost contract that defines the scope and final delivery date of the project, but also several internal constraints and conditions that may prevent the project from being completed as planned. The best course of action is to create an assumption log and map the assumptions to the impediments based on the impact to the project value. This can help the project manager to assess the validity and reliability of the assumptions, to identify and prioritize the impediments that may affect the project performance and delivery, and to develop appropriate strategies and actions to mitigate or resolve them. Creating an assumption log and mapping assumptions to impediments based on the impact to the project value (option B) is the best solution to the issue, as it demonstrates proactive and effective project integration and risk management. Creating a contingency plan in case the project deviates from the initial plan (option A) may also be helpful, but it is not the first step that the project manager should take. A contingency plan is a predefined action plan that specifies the steps to be taken if an identified risk event occurs. Before creating a contingency plan, the project manager should first identify and analyze the assumptions and impediments that may cause the project deviation, and determine the probability and impact of the risk events. Creating an issue log template that will be used to identify and track impediments (option C) may also be useful, but it is not the most comprehensive or effective approach. An issue log is a project document that records and monitors the issues that arise during the project and require resolution. However, an issue log does not capture the assumptions and constraints that underlie the issues, nor does it provide a clear mapping of the assumptions to the impediments based on the impact to the project value. Creating a schedule management plan to ensure the project meets the delivery date (option D) may also be necessary, but it is not the most urgent or relevant action. A schedule management plan is a component of the project management plan that establishes the policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule. However, a schedule management plan does not address the assumptions andimpediments that may affect the project scope and value, nor does it account for the fixed-cost contract that limits the flexibility and adaptability of the project schedule. References: : Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK Guide) (6th ed.). Newtown Square, PA: Author1 : Project Management Institute. (2017). Agile Practice Guide. Newtown Square, PA: Author2 : The special challenges of project management under fixed-price contracts. (2015)3 : Fixed price agile projects. (2011)2 : Managing Fixed Price Contracts. (2009)3
Explanation According to the PMBOK Guide - Seventh Edition1, a hybrid approach in project management is a combination of two or more methodologies or systems that aims tocreate a new and better model. A hybrid approach can blend elements from predictive and adaptive methods, such as waterfall and agile, to suit the needs and context of the project. A hybrid approach can provide flexibility, responsiveness, and customer satisfaction, as well as clarity, structure, and control. In this scenario, the project manager is using a hybrid approach to deliver the project, which means that the team should be able to adapt to changes and uncertainties, as well as follow the agreed-on plan and scope. The team has identified a risk of not delivering on time, which is a serious threat to the project success. The project manager should act quickly and effectively to mitigate this risk and ensure the timely completion of the project. The best option for the project manager to do in this situation is to empower the team to self-organize and make decisions to overcome the delay (option B). This is consistent with the agile principle of trusting the team to deliver the best value to the customer2. By empowering the team, the project manager can foster a sense of ownership, accountability, and motivation among the team members, and enable them to collaborate, communicate, and solve problems more efficiently and creatively. The team can also leverage their skills, knowledge, and experience to prioritize, plan, and execute the tasks that are most critical and valuable for the project. The other options are not the best actions to take in this situation, as they may not address the root cause of the delay, and may have negative consequences for the project and the team. Hiring additional resources to increase capacity using the contingency budget (option A) may not be feasible or effective in a hybrid environment, where the team is expected to be cross-functional, self-organizing, and collaborative. Adding new resources may introduce communication and coordination challenges, increase the complexity and cost of the project, and disrupt the team dynamics and performance. Reassigning the remaining tasks to the most experienced team members (option C) may not be fair or realistic, as it may overload and demoralize the experienced team members, and undermine the trust and collaboration among the team. It may also create a dependency and a single point of failure for the project. Informing the sponsor about the degraded performance of the team members (option D) may not be helpful or constructive, as it may damage the relationship and reputation of the team, and may not provide any solution or action plan for the delay. It may also violate the principle of transparency and feedback, which requires the project manager to communicate openly and honestly with the team and the stakeholders, and to provide constructive and timely feedback to improve the team performance3. References: 1: PMBOK Guide - Seventh Edition | Project Management Institute 2: Principles behind the Agile Manifesto 3: Agile Practice Guide | Project Management Institute
