According to the PMBOK Guide, a retrospective is a meeting held by a project team at the end of a project or process (often after an iteration) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements into future iterations or projects. In an agile project, retrospectives are usually held at the end of each iteration or sprint, regardless of the size or duration of the increment, milestone, or progress. The purpose of retrospectives is to enable continuous improvement and learning throughout the project life cycle, not just at the end of a major phase or deliverable. Therefore, the project manager should organize the first team retrospective when the work is progressing well through the team, which implies that the team has completed at least one iteration or sprint and has some feedback to share and act upon. References: (Professional in Business Analysis Reference Materials source and documents) PMBOK Guide, 6th edition, Chapter 4, Section 4.6.1.2, page 123 PMBOK Guide, 6th edition, Appendix X3, Section X3.2.2, page 718 PMI PMP-Project Management Professional Practice Exam Q. 781 to 790

Retrospective results are the outputs of the retrospective meeting, which is a ceremony that is performed at the end of every sprint or iteration in an agile project. The retrospective meeting is an opportunity for the team to reflect on what went well, what could be improved, and how to implement the improvement actions in the next sprint or iteration. The retrospective results can help the project manager to identify the risks and opportunities for the event planning, and to update the risk register accordingly. 12345 References:
* 1: ProjectManagement.com - Retrospectives
* 2: A Guide To Effective Retrospectives By Project Managers
* 3: Retrospective - BrainBOK
* 4: Retrospective - Lovepmp
* 5: Retrospective - InLoox

When a concern is escalated by a key stakeholder, the project manager should first clarify the concern directly with the stakeholder. This ensures accurate understanding before taking corrective actions with the team.
The PMBOK Guide - Seventh Edition stresses effective stakeholder engagement, communication, and managing concerns early.
Option A involves the team too early without context.
Option B skips clarification and jumps into defense.
Option C assumes team fault without stakeholder input.
References:
PMBOK Guide - Seventh Edition, Stakeholder Performance Domain
PMI Communication Management Guidelines

The project manager should have established ground rules for the team at the beginning of the project, which would include guidelines for communication, decision making, conflict resolution, and stakeholder engagement. Ground rules help the team to work effectively and collaboratively, and to avoid misunderstandings and disagreements. Providing copies of the stakeholder engagement plan (A) is not enough, as it does not specify how the team should interact with the stakeholders. Defining the roles and responsibilities of the team members (B) is also important, but it does not address the issue of who should attend the meeting with the local council authority. Updating the communications management plan is not relevant, as it does not prevent the conflict from occurring in the first place. References: PMBOK Guide, 7th edition, page 91; Agile Practice Guide, page 14.