Team Collaboration & Accountability
Hardware-software teams fail when nobody owns the wiring, the flash procedure, or the demo. This subject is making work visible, asking for help before the sprint review, giving usable feedback on a merge request, and taking a deliverable to the team's Definition of Done — including a device someone else can power up.
Starting Points
- Google Engineering Practices. Code Review — introduction and reviewer guide.
- Agile project execution
- Version control & Git workflow
Key Points
- You make your work visible on the board and in the repo (status, blockers, next step).
- You ask for help in time when a lab or toolchain blocker appears, and you share what you already tried.
- You give and receive review comments that are specific and about the change, not the person.
- You finish a slice of work to the Definition of Done (builds, flashed, documented, demoable).
- You contribute to a shared lab or repo convention (branch names, issue labels, bench photos) and follow it.