3.1 Purpose of the Phase 0 Baseline

Go To Top

Return to Phase 0 Baseline

The Phase 0 Baseline gives the project its first executable implementation foundation. The team uses this Baseline to move from architecture and planning into repeatable development, execution, Observation, and review.

The Baseline identifies what the team will build, how the team will organise it, which tools the team will use, which Artifacts the team will generate, and how the team will decide whether Phase 0 has succeeded. It prevents implementation work from drifting into local experiments that only work on one developer’s machine or depend on undocumented assumptions.

The Baseline also protects Traceability. Each implementation Artifact should support a defined architectural purpose, implementation need, or developer Workflow. A source file, IDL file, generated Type, script, Configuration file, container definition, log, topic, or Node should not enter the Phase 0 Repository unless the team can explain why it belongs there.