In the second part of this series on configuration and change management in the TfL hybrid Agile, DevOps & ITIL world, I’ll take a look at infrastructure as code and the CMDB.
We have successfully adopted and transitioned into DevOps, Agile and continuous integration with weekly deployments of code, new features and functionality to the TfL website. This is the first in a series of posts looking at how we manage these processes behind the scenes.
How we deliver
In this post I’m going to outline the way in which we, as a team, have delivered this project to date as well as highlight some of the processes and tools we’ve utilised and hopefully give a bit more perspective on the scale of some of the tasks this project is trying to overcome.
Building solid foundations
First came the brief: Design a new look and feel for tfl.gov.uk: a site used by 75% of Londoners that already has a satisfaction score of 90% and working in an ‘agile’ project with the TfL team and two other agencies.
No problem, we’ll just go and fetch our thinking caps and get started.
However, what we hadn’t quite appreciated was the fact that when you’re in the pub in London and you mention you are working on the new TfL site – absolutely EVERYBODY has an opinion.
So no pressure then…
Where on earth to begin?