Notes & Brainstorms
- Assumptions: rugged embedded device for wildfire response; glove-friendly screen+buttons; internet-optional comms (ESP-NOW/LoRa); outdoor sun/dust.
- Key metrics: ≤1 s alert latency; 99% message delivery (n≥100 in lab); >95% detection accuracy for chosen condition; ≤3 actions for core task.
- Constraints: course timeline, limited budget, safe lab surrogates (no open flame), simple enclosure & power budget.
- Why this scope: maximizes embedded-systems learning while remaining demo-feasible; clear pass/fail tests.
Team Organization Steps
- Expectations Charter: response time ≤24h on chat; meetings start on time; escalate blockers after 2 days.
- Conflict Path: 1:1 → team discussion (15 min timebox) → instructor input if unresolved.
- Peer Reviews: every PR needs one review; use a 3-item checklist (builds clean, tests noted, docs touched).
Team Roles
| Name | Role | Primary Deliverables |
|---|---|---|
| Vinny | Project Manager / Team Lead | Project timeline & coordination; task assignments & follow-ups; meeting agendas/notes; risk & scope management; instructor/stakeholder communication. |
| Emonie | Documentation Lead | Report drafting & editing; citation management; submission packaging; Google Drive organization & version control; compliance with course formatting. |
| Amanda | Design & Branding Lead | Slide templates and graphics; diagrams/figures; logo and visual assets; UI mockups as needed; visual consistency across deliverables. |
| Danitza | Research Lead | Literature & standards review; sensor/comms trade studies; evidence-backed recommendations; source summaries; data collection planning. |
| Erjan | Electronics Lead | Circuit design & prototyping; PCB layout and BOM; component selection; firmware integration support; bench bring-up and debugging. |
| James | Test & Validation Lead | Test plans & procedures; unit/system testing; data logging & analysis; acceptance criteria; demo readiness checks and issue tracking. |
Note: team members may support multiple roles as project needs evolve.
Decision Log (Template)
Date:
Topic:
Options Considered:
Criteria & Tradeoffs:
Decision:
Owner:
Revisit If:
Communication Channels
Preferred modes for each team member.
| Name | First Choice Communication | Second Choice Communication | Third Choice Communication |
|---|---|---|---|
| Vinny Panchal | Group Text | Phone Call | Email / Canvas |
| Emonie France | Group Text | Phone Call | Email / Canvas |
| Amanda Pizarro | Group Text | Phone Call | Email / Canvas |
| Danitza Jimenez | Group Text | Phone Call | Email / Canvas |
| James Austin | Group Text | Phone Call | Email / Canvas |
| Erjan Baigenzhin | Group Text | Phone Call | Email / Canvas |
Notes: “Group Text” refers to the team chat chosen by the group (iMessage/Text Message/WhatsApp/Discord). Call = direct phone/audio. Email/Canvas for formal or instructor-facing items.
Communication Procedures
- Async (default): Group text for day-to-day updates, quick questions, and coordination. Response expectation: within 24 hours; reactions are OK for simple acks.
- Sync (when needed): Phone call for blocking issues, time-sensitive decisions, or pair-debugging. Set a 15-30 min timebox; post a short summary in the group chat afterward.
- Formal / Records: Email (cc the team) or Canvas for deliverables, instructor questions, and decisions that need a paper trail.
- Instructor correspondence: Primary point of contact: Vinny (sends/receives), with all members cc’d. Vinny posts a 2–3 line recap + links in the group chat within 12 hours of any instructor reply.
-
Shared files: Google Drive is the source of truth for docs
and assets:
Team Drive Folder.
Naming:
EGR314 - Deliverable - vYYMMDD - Owner(e.g.,EGR314 - P1 Slides - v250915 - Vinny). - Escalation path: 1) ping in group chat → 2) quick call within 24h → 3) escalate to instructor if blocked & deadline risk.
Availability Matrix
Summary of the teams overall availability based on the survey form.
| Member | Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|---|
| Vinny | ✓ | ✓ | x | ✓ | x | x | x |
| Emonie | ✓ | ✓ | x | ✓ | x | x | x |
| Amanda | ✓ | ✓ | x | ✓ | x | x | x |
| Danitza | ✓ | ✓ | x | ✓ | x | x | x |
| Erjan | ✓ | ✓ | x | ✓ | x | x | x |
| James | x | ✓ | x | ✓ | x | x | x |
Meeting Template
Agenda:
1) Check-in & blockers (5m)
2) Progress since last review (10m)
3) Decisions needed (10m)
4) Next steps & owners (5m)
Notes:
- …