3.1 Purpose of the Phase 0 Baseline [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 3.1 Purpose of the Phase 0 Baseline ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:03-phase-0-baseline:start | Return to Phase 0 Baseline ]]

The Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] gives the project its first executable implementation foundation. The team uses this Baseline to move from architecture and planning into repeatable development, execution, [[dido:99_annexes:annex-b-terms-and-definitions:o:observation|Observation]], and review.

The Baseline identifies what the team will build, how the team will organise it, which tools the team will use, which [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]. Each implementation Artifact should support a defined architectural purpose, implementation need, or developer [[dido:99_annexes:annex-b-terms-and-definitions:w:workflow|Workflow]]. A source file, [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] file, generated [[dido:99_annexes:annex-b-terms-and-definitions:t:type|Type]], script, [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] file, container definition, log, topic, or [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] should not enter the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] unless the team can explain why it belongs there.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>