slohmaier/dev-process
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor(i18n): rename vorlagen/ -> templates/, *-vorlage -> *-template

Browse Source 
Final German naming cleanup in dev-process:
- vorlagen/                            -> templates/
- vorlagen-word/                       -> templates-word/
- tools/generate_word_vorlagen.sh      -> tools/generate_word_templates.sh
- *-vorlage.md / *-vorlage.docx        -> *-template.md / *-template.docx
- Review-Protokoll-vorlage.*           -> Review-Minutes-template.*
- angebot-vorlage.*                    -> quote-template.*
- angebot-beispiel.html                -> quote-example.html

All references in README.md, toolstack/toolstack.md, build_word_template.py,
and generate_word_templates.sh updated. The master Word style template
(slohmaier-doc-template.docx) was already English-named.

The dev-process repo is now fully English in both content and structure.
This commit is contained in:
Stefan Lohmaier
2026-05-12 12:09:06 -07:00
parent cc1a2b8129
commit 247b8311f3
29 changed files with 25 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
templates/PM-Plan-template.md
+75
View File
@@ -0,0 +1,75 @@
# 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.*