Generate Comprehensive Project Closeout Reports

This skill covers creating comprehensive project-closeout reports that ensure proper closure, knowledge transfer, and organizational learning, grounded in PMI/Agile/PRINCE2 methodologies and performance-measurement frameworks. Executive-summary structure covers project overview (name, objectives, timeline, budget, stakeholders), success metrics (quantified achievements versus original criteria), critical outcomes (major deliverables and business impact), resource utilization (budget variance, timeline performance, resource efficiency), and top 3-5 key lessons with actionable recommendations. A performance-analysis dashboard tracks planned versus actual versus variance across budget, timeline, scope, quality score, and stakeholder satisfaction.

Deliverables documentation uses a status matrix (deliverable, status, acceptance date, owner, location or repository) and a knowledge-transfer checklist (technical documentation to operations, user manuals to end users, admin-access transfer, maintenance procedures documented, vendor contracts and warranties transferred). Risk and issue analysis is captured via a risk-management summary documenting each top risk's original assessment, mitigation, actual impact, and the lesson learned - worked examples cover a vendor-delay risk (a 2-week schedule delay, $15K cost, with the lesson to establish vendor SLAs with penalties earlier) and a resource-availability risk (minimal actual impact due to effective cross-training mitigation).

Financial closeout uses a budget-reconciliation template comparing approved, committed, actual, and variance per category (personnel, technology, consulting, travel), plus tracking of uncommitted funds and outstanding invoices. The lessons-learned framework uses a structured format:

### Lesson #1: Early Stakeholder Alignment
**WHAT**: Requirements changed significantly in month 3, causing rework
**WHY**: Initial stakeholder workshops didn't include key end-users
**HOW**: Implement stakeholder mapping exercise at project start
**IMPACT**: 15-day schedule delay, $25K additional cost
**RECOMMENDATION**: Mandate inclusive stakeholder identification process
**APPLICABILITY**: All customer-facing projects >$100K

Team performance and recognition covers a resource-performance summary (team composition across internal, contractor, and vendor resources, productivity metrics like story points delivered and sprint completion rate, outstanding-contributor recognition, and identified development opportunities). Post-project activities cover a transition-and-support plan (a tiered go-live support schedule stepping down from full team coverage in weeks 1-2 to standard operational support by month 4+, plus named hypercare escalation contacts) and an archive and documentation section listing where each category of project artifact - charter, requirements, test plans, communications, vendor contracts - should be filed. Recommendations and next steps cover process improvements for PMO methodology, tool-configuration enhancements, identified training needs, and portfolio-level insights informing future investment decisions, closing with a call to document and celebrate team achievements.

Use it when formally closing out a project - documenting performance against plan, deliverable and knowledge-transfer status, risk and lessons-learned analysis, financial reconciliation, and post-project support transition. It is not a mid-project status-report or ongoing-PM tool - it is scoped specifically to the closeout and retrospective stage after delivery.

Given project performance data - budget, timeline, scope, deliverables, risks encountered - it produces an executive summary, a performance dashboard, deliverable/risk/financial tracking tables, structured lessons learned, and a post-project transition plan.

Project managers and PMOs formally closing out a project and capturing organizational learning.