---
# System prepended metadata

title: PMR

---

# PMR


Project Management Report (what is the)
Project Management Report
The  Project Management Report is an overview of the final status of the project. It is a formal document of the state of a project at the closure phase. Should be provided to all project stakeholders (clients, supervisors and team members) to help keep them up to date on the project results and any valuable lessons learned during the project.
The PMR should be developed by the startup with active contribution from all members and reference complementary artefacts (e.g. project charter, weekly briefs, MVP, etc.). 

The following topics need to be addressed in the report:

- Company description and organisation (and changes needed during the build-measure-learn phase)
- Communication and coordination mechanisms
- Team coordination and work planning
- Major risks and lessons learned (analysis of the risk register; overview of risks faced (Were there any high risks that needed to be managed?) 
- Project description and client
- Project management practices and activities (highlighting changes implemented based on inputs from the PST)
- Schedule progress against plan and degree of completion (Were all the project objectives achieved?)
- Final scope compared to plan (Has the scope changed since the project began? If so, how?)
- Planned versus actual resourcing (Are any resources missing or over-allocated? Weekly progress)
- Current quality findings (Has quality testing been done? Were there any issues?)
- Lessons learned (Strengths, weaknesses and what has been improved)
- Plan for the hand-over


Some tips to write the project management report:

Be concise and share results and outcomes. Don’t focus on details your stakeholders don’t need to know. Try to use bullet points, not paragraphs. If you create a 100-page document, no one is likely to read it.
Provide context. Don’t just say a deliverable was late or low quality. How will this impact the rest of the project and what actions are being taken to resolve it? Stakeholders need to know how significant the problem is.
Make it visual. This allows stakeholders to quickly identify which projects are struggling and what areas they are struggling with, before reading further into the report. 