# Project Management Plan (PM Plan)

| Field           | Value                          |
|-----------------|--------------------------------|
| Project         | [Project name]                 |
| Date            | [YYYY-MM-DD]                   |
| Version         | [1.0]                          |
| Status          | [Draft / Released]             |

---

## 1. Project organisation

[Describe organisation, roles, escalation path. Distinct from the role section in the PID — here you go into more detail on day-to-day collaboration.]

## 2. Work packages

| WP-ID | Work package           | Owner          | Effort (PD) | Due       | Status |
|-------|------------------------|----------------|-------------|-----------|--------|
| WP-01 | [name]                 | [Name]         | [n]         | [Date]    | [open] |
| WP-02 | [name]                 | [Name]         | [n]         | [Date]    | [open] |

## 3. Schedule

| Phase                    | Start       | End         | Result                       |
|--------------------------|-------------|-------------|-------------------------------|
| Concept                  | [Date]      | [Date]      | PID released                  |
| Requirements             | [Date]      | [Date]      | SRS released                  |
| Architecture             | [Date]      | [Date]      | Architecture document         |
| Implementation           | [Date]      | [Date]      | Code complete                 |
| Verification             | [Date]      | [Date]      | Test report                   |
| Release                  | [Date]      | [Date]      | Release package               |

## 4. Change management

- Changes go through change requests (CR)
- CR ID: `CR-XXX`, tracked in Gitea Issues
- For ASIL-relevant changes: re-run impacted reviews (architecture, code, tests)
- Re-baselining via git tag (see CM Plan)

## 5. Communication

| Channel         | Use                                  | Frequency   |
|-----------------|--------------------------------------|-------------|
| Gitea Issues    | Tickets, bugs, change requests       | as needed   |
| Gitea PRs       | Reviews, approval, audit trail        | per change  |
| Status report   | Project status update                 | weekly       |
| Standup         | Quick alignment                       | daily       |
| Review meeting  | Architecture / design / code reviews | per CR      |

## 6. Risk management

See `RM Plan` (separate document). Top-level summary here:

| ID   | Risk                            | Status      |
|------|----------------------------------|-------------|
| R-01 | [Top risk]                       | [Mitigated] |
| R-02 | [Top risk]                       | [Open]      |

## 7. Reporting

- **Weekly status:** email to client with progress + open items
- **Audit report:** at project closure, PDF from Doorstop + Word plans
- **CI artefacts:** updated on every push (coverage, MISRA, traceability)

## 8. Closure

The project is considered closed when:
- All success criteria from the PID are met
- A `v1.0.0` git tag is set
- The release package has been delivered to the client and accepted

---

*Changes to this plan are versioned in the Gitea wiki.*
