first release

server/data/slot.yaml

@@ -0,0 +1,116 @@
+# yaml-language-server: $schema=slot-config-scheme.json
+apiVersion: v1
+kind: SlotConfig
+metadata:
+  name: engagement3y
+  labels:
+    company: softway
+spec:
+  category:
+    - feature # roadmap
+    - enabler # 0-BV prereq for feature
+    - archi30 # transversal program
+    - nfr # support, maintenance, improvements, experimentations, onboarding, discovery
+  domains:
+    - forms
+    - automation
+    - office
+    - ito
+    - cvh
+  # mettre un % d'intention (il ne faut pas traiter les initiatives en séquence)
+  initiatives:
+    - name: Public France
+      kind: feature
+    - name: International Belgique
+      kind: feature
+    - name: Modernisation
+      kind: enabler
+  engagements:
+    - name: CHU Besançon
+      initiative: Public France
+      priority: 1
+      notBefore: Q4-25
+      notAfter: Q4-26
+    - name: Move
+      initiative: International Belgique
+      priority: 2
+      notBefore: Q4-25
+      notAfter: Q4-27
+  features:
+    - name: feature1
+      engagement: CHU Besançon
+      maturity: 50
+      domain:
+        - name: forms
+          load: 200
+          split: # uniform on all engagement duration if not defined
+            uniform:
+              quarters: 4
+            relative:
+              quarters: [ 10, 30, 40, 20 ] # total must be 100 and size <= engagement max duration
+            fixed:
+              quarters: [ 50, 100, 25 ] # size <= engagement max duration
+  teams:
+    - name: forms
+      capacity:
+        base:
+          quarter: 100
+        expanding:
+          start: Q3-25
+          end: Q1-26
+          ratio: "+10%"
+        shrinking:
+          start: Q2-26
+          end: Q3-26
+          ratio: "-10%"
+      domains:
+        - name: forms
+          efficiency: 100
+          start: Q4-25
+        - name: office
+          efficiency: 50
+          start: Q2-27
+      bandwidths: # nfr, transversal programs, learning to acquire cross-tribe knowledge, internal/nearshore onboarding, ...
+        - name: learning-office
+          category: nfr
+          start: Q1-27
+          end: Q1-27
+          quantity: 20%
+        - name: archi30
+          category: archi30
+          start: Q4-25
+          end: Q4-27
+          quantity: 10%
+      workpackages: [] # field only present in status (as this is the result of slotting exercice)
+---
+# yaml-language-server: $schema=slot-config-scheme.json
+apiVersion: v1
+kind: SlotRequest
+metadata:
+  name: engagement3y
+  labels:
+    company: softway
+spec:
+  config: engagement3y
+  constraints:
+    # express constraints as described in UI tentative
+    velocity:
+      teams:
+        - name: forms
+          ratio: "+20%"
+    timeline:
+      engagements:
+        - name: CHU Besançon
+          start: Q4-25
+          end: Q1-27
+    scope:
+      engagements:
+        - name: CHU Besançon
+          priority: "-1"
+          ratio: "80%"
+        - name: Move
+          priority: "+1"
+          ratio: "80%"
+    capacity:
+status:
+# should be more or less same fields with load provided for each engagement, initiative & global