Do we need to define what agile is?
Assume that you are trying agile for the first time. If the project succeeds then everybody is happy. But…
What happens if the project fails?
Did the project fail because your agile implementation was wrong?
…or…
Did it fail it because agile was not the right methodology for your project?
How would you know without a definition or a objective unambiguous description of what agile is and what agile is not?
It is easy to say if you are following Scrum or XP or TDD. But what happens if you are not following one of them?
Head I win – Tails you lose
Alternately, you can assume like some proponents seem to advocate that if you have failed then…
- You have not adopted agile correctly, or
- You have done a checklist based adoption without understanding the principles
This way there is no question of failure of agile!
Don’t you think we should be able to do better than that?
Comments
One Response to “Do we need to define what agile is?”Trackbacks
Check out what others are saying...[...] Do we need to define what agile is? [...]