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?

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.

During our Certified Scrum Meetup yesterday I explained that I find it valuable to cover the Scrum approach with my team at the start of every new Scrum project. Even when people say they have a good understanding of Scrum there is always value in taking people back to the basic principles of Scrum, knowing they may have moved away from and lost sight of some aspects in day to day project life.

More and more organisations across the world are following the lead of IT and adopting Agile practices. It’s worth taking a moment to look at some key concepts and considering whether Agile change is right for your business. In this post I’ll be examining what the following means for your business: