import type { SystemInfoConfig } from './types' export const backlogConfig: SystemInfoConfig = { title: 'Backlog System-Info', description: 'Produkt-Backlog und Feature-Tracking.', version: '1.0', architecture: { layers: [ { title: 'Backlog UI', components: ['Board View', 'List View', 'Roadmap'], color: '#3b82f6' }, { title: 'Planning', components: ['Sprint Planning', 'Estimation', 'Prioritization'], color: '#8b5cf6' }, { title: 'Tracking', components: ['Progress', 'Velocity', 'Burndown'], color: '#10b981' }, { title: 'Integration', components: ['GitHub', 'Jira', 'Notion'], color: '#f59e0b' }, ], }, features: [ { name: 'Feature Tracking', status: 'active', description: 'Anforderungsverwaltung' }, { name: 'Prioritization', status: 'active', description: 'MoSCoW/RICE Methoden' }, { name: 'Sprint Planning', status: 'active', description: 'Agile Planung' }, { name: 'Dependency Tracking', status: 'planned', description: 'Feature-Abhaengigkeiten' }, ], roadmap: [ { phase: 'Phase 1: Core (Q1)', priority: 'high', items: ['Kanban Board', 'Story Points', 'Labels/Tags', 'Assignees'] }, { phase: 'Phase 2: Planning (Q2)', priority: 'medium', items: ['Sprint Backlog', 'Velocity Charts', 'Capacity Planning', 'Release Planning'] }, { phase: 'Phase 3: Intelligence (Q3)', priority: 'low', items: ['Auto-Prioritization', 'Effort Prediction', 'Risk Identification', 'Stakeholder Reports'] }, ], technicalDetails: [ { component: 'UI', technology: 'React DnD', description: 'Drag & Drop' }, { component: 'Storage', technology: 'PostgreSQL', description: 'Relational Data' }, { component: 'Sync', technology: 'GitHub API', description: 'Issue Sync' }, { component: 'Export', technology: 'CSV/JSON', description: 'Data Export' }, ], auditInfo: [ { category: 'Backlog Status', items: [ { label: 'Offene Items', value: 'Tracking', status: 'ok' }, { label: 'In Progress', value: 'Tracking', status: 'ok' }, { label: 'Completed (Sprint)', value: 'Tracking', status: 'ok' }, { label: 'Backlog Grooming', value: 'Woechentlich', status: 'ok' }, ], }, { category: 'Priorisierung', items: [ { label: 'Must Have', value: 'Tracking', status: 'ok' }, { label: 'Should Have', value: 'Tracking', status: 'ok' }, { label: 'Could Have', value: 'Tracking', status: 'ok' }, { label: 'Wont Have', value: 'Tracking', status: 'ok' }, ], }, { category: 'Integration', items: [ { label: 'GitHub Sync', value: 'Aktiv', status: 'ok' }, { label: 'Jira Sync', value: 'Optional', status: 'ok' }, { label: 'Slack Notifications', value: 'Konfigurierbar', status: 'ok' }, { label: 'Webhooks', value: 'Aktiv', status: 'ok' }, ], }, ], fullDocumentation: `

Backlog Management System

1. Uebersicht

Das Backlog-Modul verwaltet alle Feature-Anfragen, Bugs und Verbesserungen. Es unterstuetzt agile Methoden wie Scrum und Kanban.

2. Item-Typen

TypIconBeschreibung
EpicGrosses Feature, mehrere Stories
Story📖User Story mit Akzeptanzkriterien
TaskTechnische Aufgabe
Bug🐛Fehlerbericht
Improvement💡Verbesserungsvorschlag

3. Workflow

┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐
│ Backlog  │ → │ Selected │ → │ In Dev   │ → │ Review   │ → │ Done     │
└──────────┘   └──────────┘   └──────────┘   └──────────┘   └──────────┘
     │              │              │              │              │
     │              │              │              │              │
  Priorisiert   Sprint       Entwicklung      Code Review    Abgeschlossen
               Planning      & Testing        & QA

4. Item-Struktur

{
  "id": "BP-123",
  "type": "story",
  "title": "Als Nutzer moechte ich...",
  "description": "...",
  "acceptance_criteria": [
    "Gegeben..., Wenn..., Dann..."
  ],
  "priority": "must_have",
  "story_points": 5,
  "labels": ["frontend", "ux"],
  "assignee": "user_id",
  "sprint": "Sprint 12",
  "epic": "BP-100",
  "created_at": "2025-01-14T10:00:00Z",
  "updated_at": "2025-01-14T12:00:00Z"
}

5. Priorisierung (MoSCoW)

PrioritaetBeschreibungBehandlung
Must HaveUnverzichtbarIm naechsten Sprint
Should HaveWichtigBaldmoeglichst
Could HaveWuenschenswertWenn Zeit
Wont HaveNicht jetztSpaeter evaluieren

6. API Endpoints

EndpointMethodeBeschreibung
/api/backlog/itemsGETItems listen
/api/backlog/itemsPOSTNeues Item
/api/backlog/items/{id}PATCHItem aktualisieren
/api/backlog/sprintsGETSprints listen
/api/backlog/kanbanGETBoard-Ansicht

7. Sprint Planning

Sprint Planning Flow:

1. Velocity berechnen
   └── Durchschnitt der letzten 3 Sprints

2. Kapazitaet ermitteln
   └── Teamgroesse × Verfuegbarkeit

3. Items auswaehlen
   ├── Priorisierte Items
   ├── Story Points summieren
   └── Kapazitaet nicht ueberschreiten

4. Sprint Goal definieren
   └── Uebergreifendes Ziel

5. Sprint starten
   └── 2 Wochen Timeebox

8. Metriken

MetrikBeschreibungZiel
VelocityStory Points/SprintStabil
Cycle TimeZeit bis DoneSinkend
Lead TimeBacklog bis DoneSinkend
BurndownRemaining WorkLinear

9. GitHub Integration

Sync-Konfiguration:

GitHub Issues → Backlog Items
├── Labels → Typ-Mapping
├── Milestones → Sprints
├── Assignees → Team-Members
└── Comments → Bidirektional

Automatisierung:
├── PR merged → Item nach Done
├── Branch erstellt → Item nach In Dev
└── Review requested → Item nach Review

10. Reporting

`, }