When a stakeholder requests changes that could impact the project scope, the project manager should first review and validate the scope management plan. This plan outlines how scope changes are managed and controlled. If the new ideas are not covered within the existing project scope, they may require a formal change request and impact analysis before proceeding. This ensures that any changes align with project objectives and do not adversely affect project constraints such as time, cost, and quality.
References:
* Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOKGuide) - Sixth Edition.
* Project Scope Management according to the PMBOK1.
* The PMBOK's Project Scope Management Knowledge Area2.
* Project scope management: Plan, template, and guide3.

nager should also help the stakeholders understand how the agile principles and practices affect the project's reporting and metrics2. The project manager should explain that agile reporting focuses on delivering value, responding to change, and satisfying customer needs3. The project manager should also collaborate with the stakeholders to identify the most relevant and meaningful reports and KPIs for the agile project, such as velocity, burn-up or burn-down charts, sprint or product backlog, and customer feedback. References:
* 1: PMBOKGuide, 6th edition, section 10.1.3.1
* 2: PMBOKGuide, 6th edition, section 1.2.3
* 3: PMBOKGuide, 6th edition, section 1.2.2
* : PMBOKGuide, 6th edition, section 1.2.4

According to the PMBOK Guide, 7th edition, one of the principles of project management is to engage stakeholders1. This means that the project manager should communicate effectively with all stakeholders, provide them with relevant information, and address their needs and expectations. In a hybrid project, where some aspects of the project follow a predictive approach and others follow an adaptive approach, the project manager should use a combination of tools and techniques to manage the project artifacts2. One of these tools is a repository or a system that stores and organizes the project artifacts, such as the project schedule, for easy access and retrieval3. The project manager should ensure that all stakeholders have access to the repository and know how to use it to find the project artifacts they need. This will help to avoid confusion, duplication, and inconsistency of information, and to foster collaboration and transparency among the project team and other stakeholders. Therefore, the best answer is C.
References:
1: PMBOK Guide, 7th edition, page 9
2: PMBOK Guide, 7th edition, page 19
3: PMBOK Guide, 7th edition, page 97
4: PMBOK Guide, 7th edition, page 98

First, calculate total required effort:
16 tasks × 8 hours each = 128 hours
Now, calculate the team's effective capacity per day:
3 full-time members: 3 × 8 = 24 hours/day
2 half-time members: 2 × 4 = 8 hours/day
Total per day = 32 hours/day
Now calculate how many days are required:
128 hours ÷ 32 hours/day = 4 days
However, the question asks whether this can be completed within one week (5 days), so why is the correct answer B (6 days)?
Actually, if the total effort is 128 hours and you have 32 hours/day of effective team capacity:
128 ÷ 32 = 4 days exactly. Therefore, the correct answer is: A
Explanation Updated:
The team has enough capacity to complete all 16 tasks in 4 working days.
References:
Agile Practice Guide, Ch. 5.6: Measuring Work in Progress and Cycle Time Kanban flow and capacity planning principles
-