| By Udayan Banerjee |
Article Rating: |
|
| September 27, 2012 05:00 AM EDT |
Reads: |
2,052 |
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?
Udayan Banerjee on Google+
Related Articles
Udayan Banerjee is CTO at NIIT Technologies Ltd, an IT industry veteran with more than 30 years' experience. He blogs at http://setandbma.wordpress.com.
The blog focuses on emerging technologies like cloud computing, mobile computing, social media aka web 2.0 etc. It also contains stuff about agile methodology and trends in architecture. It is a world view seen through the lens of a software service provider based out of Bangalore and serving clients across the world.
The focus is mostly on...
- Keep the hype out and project a realistic picture
- Uncover trends not very apparent
- Draw conclusion from real life experience
- Point out fallacy & discrepancy when I see them
- Talk about trends which I find interesting
Google
