Principles of Agile Version Control: From Object-oriented Design to Project-oriented Branching


The Change Transaction Principle (CHTP)

The CHTP is suggestive of patterns like task-level atomic commits. And last but not least, we have the ISP translating into the ever important, and almost too fundamental to mention, principle of incremental development, even for tasks.

The Incremental/Evolutionary Development Principle:

Develop changes in fine-grained increments that are client-valued. In order to be client-valued, the increments need only to add some portion of requested functionality that can be successfully built and tested. The presumption here is that the increments may be within a task. This principle doesn’t make that very clear, though, nor does it make it clear if change-increments should be separately integrated or not. For this reason, we feel that while the above is certainly important, it's not quite specific enough to claim it is a version-control principle, much less a TBD-specific one.

Principles of Baseline Management

Principles of Baseline Management

The Baseline Integrity Principle (BLIP)

A baseline's historical integrity must be preserved - it must always accurately correspond to what its content was at the time was baselined.



The Promotion Leveling Principle (PLP)

Define fine-grained promotion-levels that are consumer/role-specific.



The Integration/Promotion Principle (IPP)

The scope of promotion is the unit of integration & baselining



About the author

About the author

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.