Save £12 Million every year > Save £3 Million every quarter   
The Big Agile Toolkit: no Dogma, no Bias, no Accreditation, no Exams & no Fees   
 RAID Log Review  RAID Log Review   Branching   Branching

Lifecycle   »   Development   »   Version Control


Work on a project with poor version control, agile or waterfall, and the frustrations, anxiety and explosion of grey hairs appear with uncontrolled ferocious rapidity. The same warning applies to Configuration management.

Working quickly also means working smartly and if your team hack away at code then launch it indiscriminately at your stylishly waiting servers your project is building looming catastrophes. Poorly applied or missing version control causes a solution to become unstable and the outcomes of operating the solution are unexpected, often random and incorrect. Furthermore if code branching has been performed and code branches are lost or erroneously overwritten then functionality developed within that branch is very likely lost or missing.

The lack of version control or poor version control introduces a damaging uncertainty and ambiguity to the project as well as extra work to repair it. Code and versioning mistakes need backing out and revisions to code development need applying in careful steps. This is laborious error-prone work itself.

The experience of conflicting unexpected results on top of demands for extra endeavour to overcome wasted work disheartens team members and destroys any confidence a team had in its capability to deliver. This threatens your project success and the extra work it develops causes undue pressure on the original estimates, the time left to deliver and the cost of the overall project. So it is important we get version control installed, and installed correctly. Furthermore, it is vital that you define clear team usage guidelines including the naming standards for release names or revision tags, minor and major number of release versions and so on.



Version control is a challenge for all projects but on an agile project it is a greater challenge. You are building faster and releasing more frequently, so the versioning events occur more often and the space between them is diminished. Mistakes occur but in the agile development scenarios the mistakes have a snowball effect on the current release and the next release and so on.

A policy to allow you to version efficiently and cover the rapidity of agile releasing as well as allowing you to deploy your releases at any time is an important added guideline. Whilst we advocate no specific version control solutions we recommend that the due diligence in selecting a source control tool is strongly influenced by selecting very widely used and stable mature products especially those in Open Source software communities. The web is covered with open source and much more costly software solutions. For now, Let us have a look at code development using branching.

Buffer



 RAID Log Review     RAID Log Review   Branching    Branching



Glossary:     a  »   b  »   c  »   d  »   e  »   f  »   g  »   h  »   i  »   j  »   k  »   l  »   m  »   n  »   o  »   p  »   q  »   r  »   s  »   t  »   u  »   v  »   w  »   x  »   y  »   z


#personas  »   #artefacts  »   #archetypes  »   #patterns  »   #change  »   #personas  »   #increasingoutput  »   #reducingvariation  »   #improveefficiency  »   #abstraction  »   #predictionandcontrol  »   #management  »   #organisations  »   #socialnetworktheory  »   #failfast  »   #quality  »   #waste  »   #complexity  »   #learning  »   #adapt  »   #inspect  »   #improvement  »   #models  »   #complexadaptivesystems  »   #informationflow  »   #sytemsthinking  »   #butterflyeffect  »   #unpredictability  »   #chaos  »   #emergence  »   #emergentbehaviour  »   #distributedcontrol  »   #continuousimprovement  »   #complexityscience  »   #gametheory  »  
 Agile In 6 Steps    |    Projectivity    |    Instant Agile    |    Risks    |    Auditing Agile Projects 
Big Agile Toolkit Book (Amazon Japan)   |   Big Agile Toolkit Book (Barnes and Noble)
Buy the Big Agile Toolkit Book   |   Buy the Big Agile Toolkit Kindle eBook
Version Control






   


The Big Agile Toolkit

 SPADE: Successful Pragmatic Agile Delivery Everytime™ 
   
Topic: 312  Page: 264/444  Progress: 59.5%
 About    |    Author 
Follow @BigAgileToolkit


This content can be copied to third parties for personal use if you acknowledge the source of the material with website URL (http://www.bigagiletoolkit.com/) and Twitter hashtag (#BigAgileToolkit).
In all other cases, no part of bigagiletoolkit or associated text or website may be copied reproduced or redistributed in any form or by any means without prior permission in writing from the author.
Agile Project Governance for Cost Conscious Companies™

All rights reserved.