### 7.3.3 Project Reports The development aspect of the project should contribute with domain-specific **development status and progress information** to the Project’s reports. The goal is to translate the domain-specific information and metrics used to monitor the development progress and **incorporate it at the project level status and project reports**. The Project Status Report introduces the feedback of the development aspect of the project to the Managing Layer in the **section related to the Development Status Report**. For projects that follow PM2-Agile, the [[Project Progress Report]] is a frequent reporting tool (e.g. bi-monthly or quarterly as opposed to yearly for multi-annual projects) that allows the Project Core Team (PCT) and the overall project to better capture and manage significant scope changes. As in PM2, the Project Progress Report provides a high-level overview of the entire project and its actual status. The report includes a Project Overview (Project stakeholders, Milestones and Deliverables, Project Plan, Budget and Costs) and further Project Details (Scope Changes, Major Risks/Issues and Actions Taken, Achievements). Providing this high-level overview of the entire project, including domain-specific considerations, together with updates to the initial Project Charter (PC) allows communicating to all the stakeholders how the project is progressing, what has evolved since the initial charter and the reasons that lead to those changes. **Ad hoc Project Status reporting (including an updated version of the Project Charter) may be needed**, depending on the complexity of the project and the impact of scope changes during the development of the solution.