Development Workload Estimation

Problem

Small teams often mix frontend, backend, integration, testing, and third-party services into one rough guess. Workload Estimation targets Spring Boot, Vue 2 / Vue 3, UniApp, WeChat Mini Programs, and MySQL, turning product requirements into a module-level effort table in person-days for budgeting and scheduling.

How It Works

The skill first checks technology boundaries. If a requirement depends on unfamiliar tech, it pauses and asks whether that tech is mandatory or whether acceptable learning cost is planned. It then identifies purchased third-party services, such as SMS, maps, payments, or AI APIs, and separates them into a procurement list, estimating only integration work like SDK setup, API wiring, and callbacks. Next, it breaks requirements into business modules, gives minimum, maximum, and recommended effort, adds roughly 20% self-testing time, and applies a default ×1.35 medium-risk factor. Stable requirements can use ×1.2; heavy third-party dependence or unstable scope can use ×1.5.

Boundaries

It is useful for early module-level estimates and internal resourcing. It does not replace detailed design, performance assessment, or contractual SLA estimation. Ambiguous modules should state assumptions, and final numbers should be reviewed against the team's real baselines.