• About me

    JensI have been working as a software consultant for more than 11 years. Because of that I am an eager supporter of lean principles and agile methods.

  • Recent Posts

  • Recent Comments

    • ankara evden eve nakliyat: i have one of this quaker oats from taiwan but i dont know how to cook it. Mary...
    • Engineering CV: You did make a brave move..in this downtime economic crisis. Best wishes for your new job!
    • lazer epilasyon: A blog post was really useful, you can not find the information sought in a lot of places I’ve...
    • one minute left: not be published) (required) Website. Subscribe to comments feed. What do the extreme left and...
    • joseph pelrine: I will have to watch that as I’m a big fan of his because of the unique perspectives he brings....
  • Archives

  • Blogroll

  • Meta

Normally we don’t associate configuration management with agile processes, but nevertheless it is needed even in an agile project. The keywords with agile configuration management are “frequent changes and integration” and the CM process needs to support it. It’s about having the correct amount of process. Not too little, then the codeline will degrade, and not too much, then the workflow is disrupted instead of supported.

However the difference to traditional projects is that in agile projects there is no dedicated CM role. Instead the CM activities are carried out by the team, where everybody needs to have a certain amount of CM knowledge.

Lucas will shortly arrange a meeting at LTH around the subject: “Software Configuration Management in Agile Development”.

Read more:
Lucas meeting
SNESCM coffe meetings
Forum post on topic

Something to say?

Bloggtoppen.se