vault backup: 2025-06-16 13:25:41

Affected files:
.obsidian/workspace.json
0 Journal/Meetings/17.06.2025 - Pilot Kickoff Planning.md

.obsidian/workspace.json

@@ -43,12 +43,12 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/Kalman Filter.md",
+                "file": "0 Journal/Meetings/17.06.2025 - Pilot Kickoff Planning.md",
                 "mode": "source",
                 "source": false
               },
               "icon": "lucide-file",
-              "title": "Kalman Filter"
+              "title": "17.06.2025 - Pilot Kickoff Planning"
             }
           }
         ],
@@ -299,8 +299,9 @@
       "periodic-notes:Open today": false
     }
   },
-  "active": "1d5570e10a658ca5",
+  "active": "84f0fd68d3885e08",
   "lastOpenFiles": [
+    "99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/Kalman Filter.md",
     "0 Journal/0 Daily/2025-06-15.md",
     "Attachments/Pasted image 20250612230414.png",
     "Attachments/Pasted image 20250612230104 1.png",
@@ -309,7 +310,6 @@
     "Attachments/Pasted image 20250612225625.png",
     "Attachments/Pasted image 20250612221908.png",
     "99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/kalman_filter.excalidraw.md",
-    "99 Work/0 OneSec/OneSecNotes/30 Engineering Skills/Robotics/Kalman Filter.md",
     "OneNote/PhD/Things to know very well when applying for a robotics PhD.md",
     "0 Journal/Meetings/17.06.2025 - Pilot Kickoff Planning.md",
     "2 Personal/1 Skills/IT/React Learnings.md",

0 Journal/Meetings/17.06.2025 - Pilot Kickoff Planning.md

@@ -25,5 +25,21 @@ status: not_started
 - we have so many pcbs that are not well tested --> we don't even know what is happening. Every Pcb we make should be onboarded --> user manual, way of logging its sensors continuously (ideally fully integrated, less ideal with a teensy, instructions and a serial port)
 - we build everything from scratch --> takes a lot of time, a lot of tooling is missing. visualization tools, etc.
 - 
+
+### Timeline
+
+
+December:
+Pilot Project Start
+- 
+
+
+### Agenda
+1. Quick Overview of Scope, Timeline and goals
+2. Detailed definition of scope
+3. Detailed requirements definition based on scope
+4. Review rough planning and then go into detailed planning based on requirements
+	1. Areas: drone development (hardware, software), ground station development, business software development, regulatory, testing and QA
+	2. For each area: final requirements, intermediary milestones, 
 ## Meeting Minutes