task-decomposition

Task decomposition breaks complex projects into structured, actionable units with clear boundaries and dependencies. Identify your goal, divide it into major components, create tasks with estimates, organize them into execution waves, and document acceptance criteria so each step is verifiable and sequenced logically.

Wave planning organizes decomposed tasks into sequential execution phases that optimize dependencies and parallelism. Each wave groups related work that can run together, allowing you to verify completion and dependencies before moving to the next wave, reducing rework and improving team coordination.

Assign explicit dependencies to each task, define measurable acceptance criteria, and estimate scope. Document what must complete before each task starts, what successful completion looks like, and how you'll verify it. This makes tasks testable and prevents ambiguity during execution.

Use task decomposition when translating nebulous goals into concrete work items, planning large features, coordinating multi-team efforts, or managing projects with complex sequencing. It's essential when tasks depend on each other or must be verified at specific checkpoints before proceeding.

Yes. Wave planning explicitly optimizes for parallelism by grouping independent tasks into the same wave. Tasks without dependencies can execute concurrently, while dependent tasks move to subsequent waves, allowing you to parallelize work while respecting critical path constraints.

Task decomposition focuses on structural boundaries, dependencies, and verification criteria—what work must happen and in what order. Scheduling adds timing, resource allocation, and calendar estimates. Decomposition is the prerequisite; it clarifies *what* and *why* before scheduling determines *when* and *who*.