3.6 Baseline Change Control [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.6 Baseline Change Control ======

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

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

The team should treat the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] as controlled, not frozen. The Baseline may change as the team learns, but changes should occur deliberately and visibly.

A Baseline change may affect [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] structure, required tools, generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]], [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] patterns, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]]/[[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] definitions, topic names, scripts, containers, logging conventions, [[dido:99_annexes:annex-b-terms-and-definitions:e:exception_handling|Exception Handling]], [[dido:99_annexes:annex-b-terms-and-definitions:a:acceptance_criteria|Acceptance Criteria]], or demonstration scope. When a change affects shared implementation practice, the team should update the handbook or the relevant Repository documentation.

Developers should not make Baseline changes as incidental side effects of local coding work. A change that alters shared conventions should receive review before the team treats it as part of the Baseline. The review should consider [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_compatibility|Compatibility]], documentation, and impact on other team members.

The team should record open decisions and unresolved risks in the Risks and Open Decisions section. Once the team resolves an issue, it should update the relevant handbook section and, where appropriate, tag or otherwise identify the updated Baseline in [[dido:99_annexes:annex-b-terms-and-definitions:g:git|Git]].

Baseline control gives the Phase 0 work its credibility. The team can improve the implementation as it learns. Still, it should always know which [[dido:99_annexes:annex-b-terms-and-definitions:v:version|Version]] of the Repository, tools, scripts, generated Artifacts, Nodes, and Acceptance Criteria defines the current Phase 0 Baseline.

----

<WRAP centeralign>

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

</WRAP>