Scrum is the most popular Agile method in use in the world, and so more than likely your organisation uses Scrum or aspects of it in the work that you do. You may even have people with the title or Scrum Master or you may be one yourself.

Are you looking to adopt new practices, potentially Agile or DevOps practices, in your team?

Are you getting stuck trying to make Agile and DevOps work in your organisation?

In this short two and half minute long video I share ideas on why organisations get stuck with Agile and DevOps, plus tips for successfully making these approaches work.

This is the fourth post in a series exploring Lean thinking and DevOps.

In my previous post Increasing the speed of your DevOps teams I covered multi-tasking and large amounts of work in progress as two significant issues impacting the speed of work flowing through teams to customers. In this post we are going to cover another key reason work takes longer than it should; time lost due to work sitting in non-productive states.

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.