Patrick.Sy/website-and-documentation
1
0
Fork 0
forked from DevFW-CICD/website-and-documentation
Code Pull requests Activity

feat(poc-structure): added high level design of poc output

Browse source
This commit is contained in:
Stephan Lo 2024-11-26 16:50:01 +01:00
parent 9ec0ae1ca9
commit 6b37c0b08a
5 changed files with 16 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

BIN
content/en/docs/project/image-1.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 264 KiB

BIN
content/en/docs/project/image.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 295 KiB

15
content/en/docs/project/poc-structure.md Normal file
View file

@ -0,0 +1,15 @@
---
title: PoC Structure
weight: 5
description: Building plan of the PoC milestone (end 2024) output
---
Presented and approved on tuesday, 26.11.2024 within the team:
![alt text](image.png)
The use cases/application lifecycle and deployment flow is drawn here: https://confluence.telekom-mms.com/display/IPCEICIS/Proof+of+Concept+2024
![alt text](image-1.png)

2
content/en/docs/project/team-process/_index.md
View file

@ -11,7 +11,7 @@ This document describes a proposal to set up a team work structure to primarily
### Rationale
We current face the following [challenges in our process](https://confluence.telekom-mms.com/display/IPCEICIS/Proof+of+Concept+2024):
We currently face the following [challenges in our process](https://confluence.telekom-mms.com/display/IPCEICIS/Proof+of+Concept+2024):
1. missing team alignment on PoC-Output over all components
1. Action: team is committed to **clearly defined PoC capabilities**