Obsidian-MBPM4
1882c7ceb9
Affected files: .obsidian/workspace.json 0 Journal/Meetings/17.06.2025 - Pilot Kickoff Planning.md
46 lines
1.3 KiB
Markdown
46 lines
1.3 KiB
Markdown
---
|
||
title: 17.06.2025 - Pilot Kickoff Planning
|
||
created_date: 2025-06-12
|
||
updated_date: 2025-06-12
|
||
meeting_date:
|
||
aliases:
|
||
tags:
|
||
type: habit
|
||
status: not_started
|
||
---
|
||
# 17.06.2025 - Pilot Kickoff Planning
|
||
- **🏷️Tags** : #06-2025 #habit
|
||
---
|
||
## Meeting Summary
|
||
### Participants
|
||
-
|
||
### Summary
|
||
> [!important] 17.06.2025 - Pilot Kickoff Planning
|
||
> Please summarize the meeting here
|
||
|
||
## Preparation
|
||
### Points to Discuss
|
||
- last week showed many problems
|
||
#### Problems
|
||
- 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
|
||
|