Create a Knowledge Base for Project Management

# Knowledge Base for Project Management

Create a comprehensive internal knowledge base structure for the project management function at [ORGANIZATION_NAME], covering methodology, templates, tools, and best practices.

## Organization Context
- **Team size:** [SIZE]
- **Methodology:** [METHODOLOGY — e.g., Agile/Scrum, Waterfall, Hybrid, Prince2]
- **Primary PM tool:** [TOOL — e.g., Jira, Asana, Monday.com, Notion, MS Project]
- **Types of projects managed:** [PROJECT_TYPES]

## Knowledge Base Structure

### Section 1: Getting Started
- PM onboarding guide (what every new PM must know)
- Glossary of terms and acronyms
- Roles and responsibilities overview (RACI template)

### Section 2: Project Lifecycle
For each phase (Initiation, Planning, Execution, Monitoring, Closing):
- Phase overview and objectives
- Key activities and deliverables
- Entry/exit criteria
- Common pitfalls and how to avoid them

### Section 3: Templates Library
Provide the following templates in full:
- **Project Charter** — all standard fields
- **Project Plan / Gantt outline**
- **Risk Register** — ID, description, likelihood, impact, owner, mitigation
- **RACI Matrix** — roles vs. tasks
- **Lessons Learned Log**
- **Status Report template** (weekly/biweekly)
- **Meeting Minutes template**

### Section 4: Stakeholder Management
- Stakeholder mapping guide
- Communication plan template
- Difficult stakeholder scenarios and scripts

### Section 5: Tools & Integrations
- How to use [PM_TOOL] for this team
- Integration with [OTHER_TOOLS — e.g., Slack, Confluence, GitHub]

### Section 6: Lessons Learned Archive
Template for capturing and categorizing lessons learned after each project.

Write Section 2 and all templates in full. Provide outlines for all other sections.