Consistent Agile has one guarantee: Consistent failure, or mediocrity at best.

Agile is no more a universal set of practices any more than Java (or Ruby or Fortran in my day) is a universal language, or Spring a universal framework, or Angular.js a universal UI tool.

This session explores the behavioral purpose behind the practices, and asserts that once the behavior is achieved, the practices serve as a barrier to success, or at a minimum, a barrier to further process innovation. Understand that these practices, radical in their time, were meant to break the chains of waterfall thinking. Unfortunately, these practices have too often become new, gilded chains.

We make two arguments for flexibility in team-to-team, project-to-project Agile practices. First, the type of problems we are solving today vary greatly. We will expound on that with Dave Snowden’s Cynefin framework.

Second, we will dissect several key Agile processes, making claims about the intended behavior for the practice. Once that behavior is achieved, the value of the process is largely gone, and sometimes even an inhibitor to further progress. As an Agile practitioner for nearly two decades, I will talk about my use and removal of these processes.

We briefly present several signs that your current Agile process is staid (ie, not Agile anymore!)

We wrap up by looking at a UK retailer, and how they have adopted different practices for different purposes.

About the Speaker(s)

Fred George is an industry consultant, and has been writing code for over 50 years in (by his count) over 70 languages. He has delivered projects and products across his career, and in the last decade alone, has worked in the US, India, China, and the UK. He started ThoughtWorks University in Bangalore, India, based on a commercial programming training program he developed in the 90s. An early adopter of OO and Agile, Fred continues to impact the industry with his leading edge ideas, most recently advocating Micro Service Architectures, flat team structures (under the moniker of Programmer Anarchy), and advanced development practices called Chaos Development. Oh, and he still writes code!