This is the third post in a series exploring Lean thinking and DevOps. In this post I cover one of the reasons work takes longer than it should.
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.
Over the last couple of months we've had numerous learning opportunities outside of our training courses:
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.
On Monday night I presented on multi-factor authentication at the OWASP (Open Web Application Security Project) New Zealand Chapter meetup in Wellington.