Iteration 0 Plan
Background & Use Cases
When a new project starts, concept-level requirements exist but there's still a big gap to an executable development plan. You don't know what to do first, how many people are needed, what risks exist, or what features the MVP should include. This skill helps you, from a PM perspective, drive BA and SA to work in parallel and produce a complete execution plan for the project initiation iteration (Iteration 0).
Input & Output
You need to provide: Concept-level requirements specification (including project profile, core scenarios, technical constraints) + high-level technical constraints (tech stack preferences, deployment environment requirements). BA and SA detailed outputs can be absent initially — the PM Agent will plan based on concept-level inputs.
You will receive: A 9-chapter "Iteration 0 Plan" document including: iteration overview & target scope, team investment & person-day estimates, four-phase task breakdown (concept input → three-dimensional parallel definition → scope confirmation → MVP execution), milestones & checkpoints, risk list & mitigation strategies, cost estimates, communication plan, execution flowchart.
Process Overview
The PM Agent drives a four-phase process: Phase 1 collects materials, distills concept-level requirements, performs knowledge retrieval, and decides whether to enter Iteration 0. Phase 2 runs BA and SA in three-dimensional parallel — BA produces an initial PRD and MVP story set, SA produces a technical risk assessment and development task list, PM integrates and produces an execution plan and master schedule. Phase 3 conducts business-technical cross-review to finalize scope boundaries. Phase 4 enters execution — development team codes the MVP, while BA and SA synchronously deepen full documentation.