Lars Bendix
Lars is an associate professor at Lund University. His main research interest is software configuration management and how it can be used to support various software development processes and different contexts – and he teaches an academic course on software configuration management.
Sessions
Most DevOps/Agile people have never heard about Software Configuration Management (SCM). Those who have consider SCM to be either a bureaucratic obstacle or a superfluous task. After all isn't DevOps/Agile a complete development method and it doesn't (explicitly) mention SCM.
That couldn't be more mistaken. All projects need to apply SCM concepts and principles to avoid that a certain amount of chaos reigns. Outside the software world it has long since been common practise to use configuration management. For many aspects software projects are no different from non-software projects.
In this presentation, I would like to take things to the extreme and put forward my view on what, when and how to introduce SCM in a young, agile start-up. Just about the most informal, light-weight and fast-paced setup one could imagine.
Even if your company is not a young, agile start-up maybe your needs (the what) and your priorities (the when) could/should be the same, though the implementation (the how) will probably differ.