docs(roadmaps): add sprint execution order and detailed role-specific roadmaps
Build and Publish Docker Images / build-and-push (., backend/infrastructure/gateway/Dockerfile, api-gateway, api-gateway) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., backend/services/ping/Dockerfile, ping-service, ping-service) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., config/docker/caddy/web-app/Dockerfile, web-app, web-app) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., config/docker/keycloak/Dockerfile, keycloak, keycloak) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., backend/infrastructure/gateway/Dockerfile, api-gateway, api-gateway) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., backend/services/ping/Dockerfile, ping-service, ping-service) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., config/docker/caddy/web-app/Dockerfile, web-app, web-app) (push) Has been cancelled
Build and Publish Docker Images / build-and-push (., config/docker/keycloak/Dockerfile, keycloak, keycloak) (push) Has been cancelled
- Added `SPRINT_EXECUTION_ORDER.md` to define the cross-role sprint step sequence. - Created individual roadmaps for Architect, Backend, Frontend, DevOps, Rulebook, QA, UI/UX, and Curator. - Captured developer responsibilities, dependencies, and timelines for Sprints A–C. - Aligned sprint planning documentation with session log agreements. - Provided structured documentation in `docs/04_Agents/Roadmaps/`. Signed-off-by: Stefan Mogeritsch <stefan.mo.co@gmail.com>
This commit is contained in:
@@ -0,0 +1,57 @@
|
||||
# 🏗️ [Lead Architect] — Schritt-für-Schritt Roadmap
|
||||
|
||||
> **Stand:** 2. April 2026
|
||||
> **Rolle:** Strategie, Architektur-Entscheidungen (ADRs), Domänen-Modell, Master-Roadmap
|
||||
|
||||
---
|
||||
|
||||
## 🔴 Sprint A — Sofort (diese Woche)
|
||||
|
||||
- [ ] **A-1** | ADR-0021 schreiben: Tenant-Resolution-Strategie
|
||||
- [ ] Optionen analysieren: Schema-per-Tenant vs. Tenant-ID in allen Tabellen
|
||||
- [ ] Entscheidung treffen und begründen
|
||||
- [ ] ADR-0021 in `docs/01_Architecture/ADRs/` ablegen
|
||||
- [ ] Backend Developer informieren (A-3 ist Blocker)
|
||||
|
||||
- [ ] **A-2** | Domänen-Modell formal präzisieren
|
||||
- [ ] Hierarchie `Veranstaltung → Turnier → Bewerb → Abteilung` als offizielles Modell festschreiben
|
||||
- [ ] `TeilnehmerKonto` auf Veranstaltungsebene (Multi-Turnier) ins Modell aufnehmen
|
||||
- [ ] Veranstaltungs-Kassa mit Turnier-übergreifendem Saldo modellieren
|
||||
- [ ] Abteilungs-Typen `SEPARATE_SIEGEREHRUNG` und `ORGANISATORISCH` ins Modell aufnehmen
|
||||
- [ ] Curator beauftragen: `Ubiquitous_Language.md` aktualisieren
|
||||
|
||||
---
|
||||
|
||||
## 🟠 Sprint B — Kurzfristig (nächste Woche)
|
||||
|
||||
- [ ] **B-1** | ADR für LAN-Sync-Protokoll schreiben
|
||||
- [ ] Optionen analysieren: Event-Sourcing vs. CRDT vs. Timestamp-Sync
|
||||
- [ ] Entscheidung für Meldestelle ↔ Richter-Turm Sync treffen
|
||||
- [ ] ADR in `docs/01_Architecture/ADRs/` ablegen
|
||||
|
||||
> ⏸️ **USB-Stick Fallback** — Separate Besprechung zu einem späteren Zeitpunkt
|
||||
|
||||
---
|
||||
|
||||
## 🟡 Sprint C — Mittelfristig (in 2 Wochen)
|
||||
|
||||
- [ ] **C-1** | Synchronisations-Protokoll-Konzeption starten
|
||||
- [ ] Offline-First-Konzept für Desktop ↔ Backend ausarbeiten
|
||||
- [ ] Conflict-Resolution-Strategie definieren (was passiert bei gleichzeitigen Änderungen?)
|
||||
- [ ] Ergebnis als Konzept-Dokument in `docs/01_Architecture/` ablegen
|
||||
|
||||
- [ ] **C-2** | MASTER_ROADMAP aktualisieren
|
||||
- [ ] Desktop-App-Fokus eintragen
|
||||
- [ ] Tenant-Isolation-Meilensteine eintragen
|
||||
- [ ] Offline-Sync-Meilensteine eintragen
|
||||
- [ ] Sprint A/B/C Ergebnisse als "erledigt" markieren
|
||||
|
||||
---
|
||||
|
||||
## 📌 Abhängigkeiten
|
||||
|
||||
| Meine Aufgabe | Blockiert wen |
|
||||
|----------------------|----------------------------------------------------------|
|
||||
| ADR-0021 (A-1) | 👷 Backend: Tenant-Isolation (Backend Sprint A) |
|
||||
| Domänen-Modell (A-2) | 👷 Backend: Schema-Design; 🎨 Frontend: ViewModel-Design |
|
||||
| LAN-Sync ADR (B-1) | 🎨 Frontend: Sync-UI; 👷 Backend: Sync-Endpunkte |
|
||||
Reference in New Issue
Block a user