An agile team strives for a product that is in a constant releasable state to minimize lead time and have rapid feedback. In other words, when a team member says that a story is Done and moves the story card into the Done column, a customer could run into the room at that moment and say "Great! Let's go live now!", and nobody in the team will say “no, but wait”.
Source control is not strictly speaking an agile practice. However, it is an enabler for a number of practices, from continuous integration to continuous delivery. It has to be able to support concurrent work on multiple features.
However, technology alone can not solve this problem. An agile team must agree upon version control policies that work seamlessly with their engineering practices.
As Henrik Kniberg eloquently says: in an agile environment, the version control model needs to achieve the following goals:
Code conflicts and integration problems should be discovered as soon as possible
Better to fix small problems often than to fix large problems seldom
Even after a really bad sprint there should be at least something that is releasable
All team members will be using this scheme every day, so the rules and routines must be clear and simple
In this one day workshop, we will be exploring and practicing several source code strategies and workflows that aim to achieve these goals, with their benefits and pitfalls. All the ideas we will see during this day are applicable to most modern version control systems. For the exercises we will be using git, so we will include a basic introduction and some time for installation.
This workshop is aimed at developers.
No experience is required with git. No limitation on technology (java, .net, ruby, php, …) or platform (windows, linux, mac).
|Date||Location||Trainer||Language||Price excl. VAT|
|There are no available registration dates for this training. Feel free to contact us for a in-house training|
SubscribeThere are no available registration dates for this training. Feel free to contact us for a in-house training
Short history of version control systems
Traditional techniques: No junk in the trunk
Branching workflows: From very simple to very comprehensive.
Distributed workflows: From centralized to distributed
This agenda is not written in stone. It will vary depending on the participant's’ needs.