Projects Hub
Projects Hub
Section titled “Projects Hub”Client Project Documentation
Section titled “Client Project Documentation”Last Updated: November 8, 2025 Version: 1.0 Owner: Project Management Lead
🎯 Purpose
Section titled “🎯 Purpose”This hub contains documentation for all client projects - active, completed, and archived. Each project follows standardized documentation templates ensuring consistent quality and knowledge capture.
📂 Directory Structure
Section titled “📂 Directory Structure”/projects/├── README.md (this file)├── templates/ # Project documentation templates│ ├── project-charter-template.md│ ├── requirements-document-template.md│ ├── project-report-template.md│ └── handover-document-template.md├── active/ # Current ongoing projects│ ├── mgslg-analytics-platform/│ ├── sace-provider-intelligence/│ └── [client-name-project]/├── completed/ # Successfully delivered projects│ └── [archived successful projects]└── archived/ # Historical reference └── [old projects for reference]📚 Quick Links
Section titled “📚 Quick Links”| I Need To… | Go To… |
|---|---|
| Start a new project | Use /templates/project-charter-template.md |
| Document project requirements | Use /templates/requirements-document-template.md |
| Create project report | Use /templates/project-report-template.md |
| Hand over completed project | Use /templates/handover-document-template.md |
| Review active projects | Browse /active/ folders |
| Learn from past projects | Review /completed/ and /knowledge-base/lessons-learned/ |
🎯 Project Lifecycle
Section titled “🎯 Project Lifecycle”Stage 1: Initiation
Section titled “Stage 1: Initiation”- Create project folder in
/active/[client-name-project]/ - Draft project charter from template
- Identify stakeholders and project team
- Get approval to proceed
Stage 2: Planning
Section titled “Stage 2: Planning”- Requirements gathering (use requirements template)
- Technical architecture design
- Project plan and timeline
- Resource allocation
Stage 3: Execution
Section titled “Stage 3: Execution”- Regular status updates
- Risk management
- Stakeholder communication
- Deliverable tracking
Stage 4: Delivery
Section titled “Stage 4: Delivery”- User acceptance testing
- Training delivery
- Go-live support
- Handover documentation
Stage 5: Closure
Section titled “Stage 5: Closure”- Project retrospective (lessons learned)
- Final report
- Move to
/completed/ - Create case study (for
/knowledge-base/case-studies/)
📋 Standard Project Folder Structure
Section titled “📋 Standard Project Folder Structure”Each project should follow this structure:
/active/[client-name-project]/├── README.md # Project overview├── 01-charter/│ └── project-charter.md├── 02-requirements/│ ├── requirements-document.md│ └── technical-specs.md├── 03-planning/│ ├── project-plan.md│ └── risk-register.md├── 04-deliverables/│ ├── [deliverable-1]/│ └── [deliverable-2]/├── 05-reports/│ ├── status-reports/│ └── final-report.md├── 06-handover/│ ├── handover-document.md│ ├── user-guides/│ └── training-materials/└── 07-retrospective/ └── lessons-learned.md📊 Project Documentation Requirements
Section titled “📊 Project Documentation Requirements”Required Documents (All Projects)
Section titled “Required Documents (All Projects)”| Document | Template | When Created | Owner |
|---|---|---|---|
| Project Charter | /templates/project-charter-template.md | Project initiation | PM |
| Requirements | /templates/requirements-document-template.md | Planning phase | BA/PM |
| Final Report | /templates/project-report-template.md | Project closure | PM |
| Handover | /templates/handover-document-template.md | Delivery phase | PM |
| Lessons Learned | See Knowledge Base templates | Post-project | Team |
Optional Documents (As Needed)
Section titled “Optional Documents (As Needed)”- Technical specifications
- Architecture diagrams
- Test plans
- Training materials
- User guides
- API documentation
✅ Project Quality Standards
Section titled “✅ Project Quality Standards”Project Documentation Checklist
Section titled “Project Documentation Checklist”Initiation:
- Project charter approved
- Stakeholders identified
- Project folder created
- Team assigned
Planning:
- Requirements documented and approved
- Technical approach defined
- Project plan created
- Risks identified and mitigation planned
Execution:
- Regular status updates
- Risks actively managed
- Changes controlled
- Stakeholders engaged
Delivery:
- UAT completed successfully
- Training delivered
- Documentation complete
- Handover executed
Closure:
- Final report created
- Lessons learned documented
- Project moved to completed/
- Case study created (if applicable)
📈 Active Projects
Section titled “📈 Active Projects”MGSLG Analytics Platform
Section titled “MGSLG Analytics Platform”- Client: Mathew Goniwe School of Leadership and Governance
- Status: Implementation Phase
- Go-Live: TBD
- PM: [PM_NAME]
- Folder:
/active/mgslg-analytics-platform/
SACE Provider Intelligence
Section titled “SACE Provider Intelligence”- Client: South African Council for Educators
- Status: Requirements Phase
- Go-Live: TBD
- PM: [PM_NAME]
- Folder:
/active/sace-provider-intelligence/
🎓 Learning from Projects
Section titled “🎓 Learning from Projects”After each project, ensure:
- Lessons learned documented in
/knowledge-base/lessons-learned/ - Case study created (if successful) in
/knowledge-base/case-studies/ - Best practices extracted in
/knowledge-base/best-practices/ - Templates updated based on learnings
📞 Project Support
Section titled “📞 Project Support”Project Management Lead: [NAME] Contact: [EMAIL/PHONE]
For help with:
- Project planning and execution
- Documentation templates
- Risk management
- Stakeholder management
Projects Hub maintained by iSu Technologies Project Management Team Last Updated: November 8, 2025