Hardware Project Scheduler

Problem

Hardware schedules usually fail in the details: task breakdown, effort estimates, date dependencies, and risk buffers. EVT/DVT/PVT work depends on tooling, PCBA, testing, and certification, while missing algorithm support or a shared PM can turn parallel work into a serial bottleneck. Generic project templates often miss hardware validation and rework/retest buffers.

How It Works

The skill follows a fixed flow: collect project name, product type, complexity, special modules, team setup, start/end dates, and constraints; load a WBS knowledge base; break work into Kickoff → ID → EVT → DVT → PVT → MP; apply product, complexity, and team coefficients; and mark serial/parallel tasks, critical path, risk levels, and review checkpoints. It can output Excel or Feishu Bitable. Excel uses WORKDAY formulas to keep start, finish, and duration linked, which suits offline single-user work; Feishu Bitable suits multi-user collaboration, Gantt views, and cross-table links. After output, it asks whether to adjust effort allocation for a stage.

Boundaries

Use it for product development involving mechanical parts, electronics, tooling, PCBA, and hardware validation. Avoid pure software, pure algorithm, pure procurement, post-production maintenance iterations, and overseas certification-heavy schedules. For mixed hardware/software projects, split the schedule: use it for hardware and plan software separately. Treat output as a baseline, not a promise; if defaults are used or the target date is infeasible, adjust scope, staffing, or milestones.