Stephan Lo
43cbd69c9c
- Move all existing docs content (concepts, project, solution) to /docs/v1/ - Add legacy banner component to warn users about archived documentation - Create v1 index page with legacy notice and redirect guidance - Implement automatic banner display for all v1 paths - Preserve all original content for reference during migration This enables incremental content migration while maintaining access to original documentation.
1.6 KiB
1.6 KiB
| title | weight |
|---|---|
| Workstreams | 2 |
This page is WiP (23.8.2024).
Continued discussion on 29th Aug 24
- idea: Top down mit SAFe, Value Streams
- paralell dazu bottom up (die zB aus den technisch/operativen Tätigkeietn entstehen)
- Scrum Master?
- Claim: Self Service im Onboarding (BTW, genau das Versprechen vom Developer Framework)
- Org-Struktur: Scrum of Scrum (?), max. 8,9 Menschen
Stefan and Stephan try to solve the mission 'wir wollen losmachen'.
Solution Idea:
- First we define a rough overall structure (see 'streams') and propose some initial activities (like user stories) within them.
- Next we work in iterative steps and produce iteratively progress and knowledge and outcomes in these activities.
- Next the whole team decides which are the next valuable steps
Overall Structure: Streams
We discovered three streams in the first project steps (see also blog):
- Research, Fundamentals, Architecture
- POCs (Applications, Platform-variants, ...)
- Deployment, production-lifecycle
#
## Stream 'Fundamentals'
### [Platform-Definition](./fundamentals/platform-definition/)
### [CI/CD Definition](./fundamentals/cicd-definition/)
## Stream 'POC'
### [CNOE](./pocs/cnoe/)
### [Kratix](./pocs/kratix/)
### [SIA Asset](./pocs/sia-asset/)
### Backstage
### Telemetry
## Stream 'Deployment'
### [Forgejo](./deployment/forgejo/)
DoR - Definition of Ready
Bevor eine Aufgabe umgesetzt wird, muss ein Design vorhanden sein.
Bezüglich der 'Bebauung' von Plaztform-Komponenten gilt für das Design:
- Die Zielstellung der Komponenet muss erfasst sein