gsd-list-phase-assumptions

To validate phase assumptions, you analyze the technical approach, implementation order, scope boundaries, risks, and dependencies of a project phase. This surfaces hidden assumptions early, enabling course corrections and structured feedback before committing heavy execution resources.

Phase validation against a roadmap confirms that a targeted phase exists and aligns with the overall project trajectory. It articulates underlying technical assumptions, implementation order, and scope boundaries to ensure planning stays on track with defined objectives.

You surface technical assumptions by analyzing the phase across five areas: technical approach, implementation order, scope boundaries, risks, and dependencies. This cross-cutting analysis exposes hidden expectations and presents clear options for team feedback to guide subsequent planning steps.

You need to analyze phase dependencies and scope boundaries when preparing to plan a new project phase. Validating these elements against the roadmap early prevents misaligned execution and helps determine actionable next steps like discussing context or correcting flawed assumptions.

Yes, you can validate a specific phase number against the project roadmap to check its implementation order and risks. This process articulates assumptions across five cross-cutting areas, surfacing clear options for feedback to guide and adjust your planning.

Relying on phase assumptions without validation risks starting execution with hidden technical misunderstandings or incorrect scope boundaries. If assumptions are not surfaced and corrected against the roadmap early, teams may commit resources to a flawed implementation order.