DevOps is widely recognised for improving IT's ability to deliver more business value faster. But we often see DevOps applied incorrectly or inconsistently and there is confusion around the competencies and skills required for successful DevOps.
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 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.