I was recently asked: “How do you use Agile for business processes?” Here’s my response:
Many people confuse Agile with Scrum and when they say “Agile”, they really mean “Scrum”. Scrum is not a solution to every problem but you can apply general Agile principles and Agile thinking to almost anything. It’s mostly just a shift in thinking rather than attempting to follow a well-defined Agile methodology like Scrum. For example, I have written several books on Agile Project Management and I used a somewhat Agile process to publish the books:
- I started out with a vision of what I wanted to do with the book and further elaborated it as I went along rather than having a highly detailed outline of exactly what the book would look like to start with
- I engaged a group of people over the Internet to provide feedback and inputs. These people represented potential customers of the book as well as subject matter experts
- I took an adaptive approach to adapt the design of the book based on the feedback I received
- I used an incremental development approach. As I wrote each chapter or section of the book, I put it out for feedback and inputs and made adjustments as necessary based on that feedback and inputs
You can use that kind of thinking process on almost anything without necessarily following all the rituals of Scrum.
A lot of people also want to try to use Agile for business process improvement and that’s not necessary. There are lots of ways to improve business processes that are totally independent of Agile. For example, Agile is based on the ideas of continuous improvement that have their roots in Total Quality Management (TQM), Lean, Six Sigma, and other approaches that go back long before Agile. It isn’t essential to fully adopt Agile if what you really want is business process improvement.
Many people seem to want to jump on the Agile bandwagon because it is the latest and hottest buzzword to adopt but it isn’t necessarily a solution to any problem you might have.