Explanation The project manager should work with the team to understand their views and add the appropriate dependencies and risks before sending the information to the client because this is consistent with the agile principles and values. The agile approach emphasizes collaboration, communication, and feedback among the project team and stakeholders. The project manager should involve the team in the estimation and planning process, as they have the best knowledge and experience of the work to be done. The project manager should also identify and analyze the dependencies and risks that may affect the project scope, schedule, cost, and quality, and communicate them to the client. This will help to establish trust, transparency, and alignment between the project team and the client, and enable them to respond to changes and uncertainties effectively. References: A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition, Chapter 2.2.2, page 28 Agile Practice Guide, Chapter 2.1.1, page 14 PMP Exam Content Outline, Domain II: Planning, Task 2
Explanation According to the PMBOK Guide, 7th edition, one of the key practices for stakeholder engagement is to "engage stakeholders to understand their needs, expectations, and interests, and to obtain their support and commitment for the project" (p. 121). This practice involves identifying and analyzing stakeholders, developing and implementing stakeholder engagement plans, and monitoring and adjusting stakeholder engagement activities. The project manager should allocate time to gain buy-in from the stakeholder prior to key decision meetings, as this will help to reduce resistance, increase collaboration, and enhance the quality of decisions. Updating the project schedule, asking that only key decision makers attend the meetings, or updating the risk register are not effective ways to handle the situation, as they do not address the root cause of the problem, which is the stakeholder's lack of alignment with the project objectives and approach. References: PMBOK Guide, 7th edition, p. 121-122; PMP Exam Content Outline, Domain II: Process, Task 4.
Explanation According to the PMBOK Guide, 7th edition, one of the key principles for project delivery is to "focus on value" (p. 10). This principle implies that the project manager should measure the project performance based on the value delivered to the customer and the stakeholders, rather than the output produced or the effort expended. The team that completes the most stories selected from the sprint backlog is performing better, as this indicates that they are delivering the highest priority and most valuable features to the customer. Story points are a relative measure of complexity or size of a user story, and they are not comparable across different teams or projects. The team with the least amount of defects or the team with fewer story points are not necessarily performing better, as they may be delivering low-value or low-quality features, or working on easier or smaller stories. References: PMBOK Guide, 7th edition, p. 10; PMP Exam Content Outline, Domain I: People, Task 2.
