Tier 4

project_closure

Complete projects properly with handoff and learning capture

Usage in Claude Code: /project_closure your question here

Project Closure

Overview

Complete projects properly with handoff and learning capture

Steps

Step 1: Verify completion

Confirm all project work is truly complete:

  1. Review deliverable status:
    • List all committed deliverables
    • Verify each is complete and accepted
    • Get formal sign-off from stakeholders
    • Document any deferred items and their disposition
  2. Confirm success criteria met:
    • Review original success criteria
    • Measure actual outcomes against criteria
    • Document which criteria were met, partially met, or not met
    • Get sponsor agreement on outcome assessment
  3. Close out remaining work:
    • Complete any outstanding tasks
    • Resolve or transfer remaining issues
    • Close or transition open risks
    • Ensure all testing is complete
  4. Address any final changes:
    • Decline new change requests (project is closing)
    • Complete approved changes in progress
    • Document any approved but unimplemented changes

Step 2: Prepare handoff documentation

Create complete package for receiving team/operations:

  1. Technical documentation: System/solution documentation:
    • Architecture and design documents
    • Configuration and setup guides
    • API documentation
    • Data models and schemas
    • Integration specifications Operational documentation:
    • User manuals and guides
    • Administrator guides
    • Standard operating procedures
    • Troubleshooting guides
    • FAQs and common issues Support documentation:
    • Known issues and workarounds
    • Escalation procedures
    • Contact information
    • SLAs and support commitments
  2. Knowledge transfer:
    • Schedule knowledge transfer sessions
    • Walk through key systems and processes
    • Demonstrate operational procedures
    • Answer questions from receiving team
    • Document answers to questions raised
  3. Access and credentials:
    • Transfer system access appropriately
    • Update ownership of accounts/services
    • Rotate or transfer credentials
    • Update distribution lists and contacts
  4. Outstanding items:
    • Known issues and their status
    • Technical debt inventory
    • Future enhancement recommendations
    • Deferred requirements

Step 3: Close contracts and vendors

Properly conclude external relationships:

  1. Review all contracts:
    • List active contracts related to project
    • Identify closure requirements per contract
    • Note any ongoing obligations
  2. Close vendor contracts:
    • Verify all deliverables received
    • Complete final acceptance testing
    • Process final invoices
    • Obtain warranty information
    • Document ongoing support terms
  3. Close contractor engagements:
    • Confirm all work complete
    • Process final payments
    • Collect any project materials
    • Return any company equipment
    • Complete off-boarding procedures
  4. Document transition:
    • Ongoing maintenance contracts
    • Support contact information
    • Warranty terms and expiration
    • License renewals needed

Step 4: Release resources

Transition team members back to their organizations:

  1. Plan resource release:
    • Create resource release schedule
    • Align with knowledge transfer needs
    • Coordinate with functional managers
    • Allow for closure activities
  2. Complete HR activities:
    • Update assignments in HR systems
    • Process any performance feedback
    • Ensure time is properly charged
    • Complete any required evaluations
  3. Communicate transitions:
    • Thank team members individually
    • Notify stakeholders of team changes
    • Provide references for contractors
    • Recommend team members as appropriate
  4. Return assets:
    • Collect project-specific equipment
    • Revoke project-specific access
    • Return licenses to pool
    • Close project-specific accounts

Step 5: Conduct lessons learned

Capture insights for organizational improvement:

  1. Prepare for lessons learned session:
    • Schedule session with key team members
    • Allow adequate time (1-3 hours depending on project)
    • Gather project data (metrics, issues, changes)
    • Create prompt questions
  2. Capture lessons in key areas: Planning:
    • Was the scope well-defined?
    • Were estimates accurate?
    • Was the schedule realistic?
    • Were risks identified properly? Execution:
    • What went well?
    • What didn’t go well?
    • What would we do differently?
    • What should the organization learn? Team and stakeholders:
    • How was team performance?
    • Was communication effective?
    • How well did we manage stakeholders?
    • What relationship lessons emerged? Process and tools:
    • What processes helped?
    • What processes hindered?
    • What tools should we use again?
    • What should we avoid?
  3. Focus on actionable insights:
    • What should future projects do differently?
    • What should the organization change?
    • What training or resources would have helped?
    • What can be reused or templated?
  4. Document and share:
    • Write up lessons learned document
    • Share with relevant stakeholders
    • Submit to organizational knowledge base
    • Identify specific recommendations

Step 6: Create project archive

Preserve complete project records:

  1. Gather all project documents: Governance:
    • Project charter
    • Scope statements
    • Change requests and approvals
    • Meeting minutes
    • Decision logs Planning:
    • Project plans
    • Schedules (baseline and final)
    • Resource plans
    • Risk registers
    • Communication plans Execution:
    • Status reports
    • Issue logs
    • Deliverable acceptance records
    • Test results Technical:
    • Design documents
    • Specifications
    • Code/configuration (as appropriate)
    • User documentation Closure:
    • Handoff documentation
    • Lessons learned
    • Final report
  2. Organize archive:
    • Create logical folder structure
    • Include index/table of contents
    • Note location of large files (videos, images)
    • Include README with archive overview
  3. Store appropriately:
    • Move to long-term storage location
    • Set appropriate access permissions
    • Apply retention policy
    • Notify stakeholders of archive location
  4. Close project systems:
    • Archive or close project workspace
    • Close project tracking (Jira, etc.)
    • Archive communication channels
    • Update project portfolio

Step 7: Prepare closure report

Create final project summary:

  1. Executive summary:
    • Project name and description
    • Dates (start, end, duration)
    • Final status (success, partial success, failure)
    • Key achievements
  2. Objectives and outcomes:
    • Original objectives
    • Actual outcomes vs. objectives
    • Benefits realized (or expected)
    • Success criteria assessment
  3. Performance summary: Schedule:
    • Planned vs. actual duration
    • Milestone achievement
    • Schedule variance explanation Budget:
    • Planned vs. actual cost
    • Cost variance explanation
    • Final budget reconciliation Scope:
    • Planned vs. actual deliverables
    • Scope changes summary Quality:
    • Quality metrics achieved
    • Defects/issues summary
  4. Key learnings:
    • Top 3-5 lessons learned
    • Recommendations for future
  5. Acknowledgments:
    • Key contributors
    • Special recognition
  6. Sign-off:
    • Sponsor signature
    • PM signature
    • Date of closure

Step 8: Communicate closure

Notify stakeholders of project completion:

  1. Stakeholder communication:
    • Send closure announcement
    • Share closure report (or summary)
    • Thank stakeholders for support
    • Provide contact for ongoing questions
  2. Organizational communication:
    • Announce project completion
    • Share key accomplishments
    • Acknowledge team contributions
    • Highlight benefits delivered
  3. Update organizational records:
    • Update project portfolio status
    • Record in project registry
    • Update resource allocations
    • Close project codes/cost centers

Step 9: Celebrate and recognize

Acknowledge accomplishments and team contributions:

  1. Plan celebration:
    • Appropriate to project size and culture
    • Could be: team lunch, recognition event, awards, party
    • Budget within guidelines
    • Include key contributors and stakeholders
  2. Recognition activities: Team recognition:
    • Thank team members publicly
    • Highlight specific contributions
    • Provide formal recognition if appropriate
    • Write recommendations for team members Individual recognition:
    • Call out exceptional contributions
    • Nominate for awards if applicable
    • Note in performance records
    • Express personal appreciation
  3. Create celebration record:
    • Photos from celebration
    • List of accomplishments
    • Thank you messages
    • Awards or recognition given
  4. Personal touches:
    • Individual thank you notes
    • Team memento if appropriate
    • Reference letters for contractors
    • Future collaboration invitations

Step 10: Final sign-off

Formally close the project:

  1. Obtain formal sign-off:
    • Sponsor signs closure report
    • Confirms deliverables accepted
    • Agrees project is complete
    • Authorizes resource release
  2. Conduct closure meeting:
    • Brief review of outcomes
    • Confirm all closure activities complete
    • Any final questions or concerns
    • Formal declaration of closure
  3. Complete administrative closure:
    • Update project status to “Closed”
    • Close financial tracking
    • Archive project materials
    • Update portfolio dashboard
  4. Personal closure:
    • Reflect on the experience
    • Note personal lessons learned
    • Update personal portfolio
    • Prepare for next assignment

When to Use

  • When project deliverables are complete
  • When project objectives have been met
  • When project is cancelled or terminated
  • At the end of each project phase (phased closure)
  • When transitioning to operations or support team
  • Before team members move to other assignments

Verification

  • All deliverables are accepted and signed off
  • Handoff documentation is complete and transferred
  • Lessons learned are captured and shared
  • All contracts and vendors are properly closed
  • Team resources are released appropriately
  • Project archive is complete and accessible
  • Closure report is signed by sponsor
  • Team is recognized and celebrated

Input: $ARGUMENTS

Apply this procedure to the input provided.