
Hardware Sprint Planning & Dependency Mapper
Map hardware-software dependencies and manufacturing constraints for realistic sprint forecasts
What You Can Do
You can systematically map dependencies across electrical, mechanical, firmware, and software teams while accounting for manufacturing lead times, component procurement cycles, and physical testing phases. This skill helps you classify work by constraint type (CPU-bound, manufacturing-bound, test-bound, integration-bound) and build sprint forecasts that reflect hardware physics rather than software assumptions. You'll surface critical path items and integration risks early, preventing costly delays and rework cycles.
Features
visualize cross-team blockers between hardware and software work streams
identify PCB fab, component lead times, and assembly bottlenecks
determine which hardware iterations drive overall timeline
flag component shortages and logistics uncertainties affecting sprint capacity
structure firmware-hardware development to minimize idle time
identify where hardware and software teams depend on each other
track which constraints caused actual vs. planned delays
validate team capacity against realistic hardware iteration cycles
Example Output
Example 1: PCB Dependency Mapping
- Firmware team blocked: Waiting on PCB v2 from fab (lead time: 3 weeks)
- Software team can proceed: Building driver layer in parallel using v1 schematics
- Risk flagged: If PCB v2 fails thermal testing, firmware must iterate (adds 2-week cycle)
Example 2: Supply Chain Risk
- Component shortage identified: MCU procurement delayed 4 weeks
- Impact: Hardware assembly blocked until week 6
- Mitigation: Move firmware unit tests and software stack development to weeks 1-5
Example 3: Sprint Forecast
- Sprint capacity: 40 story points
- Manufacturing-bound work: 12 points (committed, no velocity risk)
- Integration-bound work: 8 points (blocked on PCB testing results)
- Parallel firmware work: 20 points (can proceed independently)
What's Included
- SKILL.md instruction file: complete framework for hardware sprint planning
- Dependency mapping template: cross-functional work stream matrix with lead time estimates
- Constraint classification worksheet: categorize work by CPU-bound, manufacturing-bound, test-bound, integration-bound
- Critical path analysis checklist: identify timeline-driving hardware iterations
- Supply chain risk register: track component lead times, shortage probabilities, mitigation actions
- Sprint commitment validator: realistic capacity planning accounting for hardware cycle times
Who It's For
- Scrum Masters / Agile coaches managing hardware-software teams
- Hardware project managers coordinating electrical, mechanical, and firmware work
- Product managers planning releases dependent on manufacturing timelines
- Engineering leads balancing firmware development against hardware iteration cycles
- Operations / supply chain teams forecasting component availability impact on sprints
Best For
- Sprint planning sessions for IoT, embedded systems, or hardware-software products
- Forecasting release timelines when manufacturing lead times exceed sprint length
- Identifying which teams can work in parallel vs. sequence during hardware development
- Risk assessment of supply chain constraints blocking software development
- Retrospective analysis of hardware delays and cross-team dependency failures
- Onboarding new hardware features with complex electrical-firmware integration







