In my previous post Introducing Lean thinking to DevOps I showed how Lean thinking, particularly establishing a pull system through work in progress (WIP) limits, can fully align the delivery capability of your DevOps team(s) with the ability of business to accept change.
DevOps seems to be on everyone’s lips right now. It has surpassed Agile and become the newest and blackest of blacks.
The definition I’ll give it for the purposes of this blog is “…a lot of technical stuff done using strangely named products with the intent of creating a frictionless and smooth flow of value to end users”. I mean, Chef, Puppet, Git. Who names these products? Nevertheless, the important part of that definition rests in the last ten words; a frictionless and smooth flow of value to end users.
Over the last couple of months we've had numerous learning opportunities outside of our training courses:
I kicked off our third 'Projects and Agile Community of Practice' event in early December with two teams of six participating in a 'work in progress' exercise. Each team had a timer, four project team members and a project manager. The four project team members were assigned a Greek character - Alpha, Beta, Gamma, and Delta. They had a backlog of 30 cards, where card by card each team member would put their specific colour sticky dots on spots on the card that referenced their character, before handing it onto the next team member. The project manager collected the completed cards (work) at the end of the line. Two rounds of work were completed.
As the only New Zealand owned company to be a Microsoft Gold Partner for the DevOps competency we were delighted to yesterday work with Microsoft to deliver a half-day Azure DevOps event in Wellington. The event started with breakfast and we had a full room attending the presentations. The same event is taking place today in Auckland at Microsoft's offices.