Too often we adopt agile practices to solve our problems. Agile is the answer to life, the universe, and everything (not 42!). Ok, so if Agile is the answer, what is the problem being solved? Over lunch a group of us discussed why and how we adopt (or help our clients adopt) agile practices. The notes below are disjointed because we had many different understandings of the question.
Here is a list of questions raised that may be the root(s) of Agile adoption:
- Why does software cost so much?!
- What is a more humane way of building software?
- How can we get functionality to the customer faster?
- How do I improve productivity?
- How do you measure productivity?
- How do you minimize waste?
- How do you make software useful?
- We've tried 3 times to build this project!
- Last project was PAINFUL.
- How do I feel in control of this project?
- whole team
- Silver bullet for what?
- Visibility and customer feedback?
- Who is asking the question?
It DEPENDS! But, in trying to get past it depends!
we ask the question "who is asking?" So, before we adopt agile practices, we must understand the problem(s) being solved. The problems that need solving are different from person to person. We must understand who is asking that their problems be solved to correctly identify them. We then can attempt to solve them by appropriate adoption of agile practices.