Is there a development project scenario you would not recommend using the Agile development model ? I am currently taking a design course, my first, and we are discussing the benefits of Agile development vs traditional development. I am really looking forward to your answer.
The short answer is that trying to go agile can lead to some pretty bad results if the mindset of the team or the culture of the company are incompatible with the values and principles of agile and the methodology being put in place. We actually talk a lot about this in Learning Agile, because recognizing where your team and company values clash with agile can go a long way towards helping you get better results in the real world.
The truth is that some teams and companies punish mistakes harshly, assume that people get everything right the first time, and generally freak out when projects don't go perfectly. If you're at a company where making mistakes can get you fired, for example, you should not try agile. At least, not unless you have another job already lined up.
Author of Head First Agile, Learning Agile, Beautiful Teams, Head First C#, Head First PMP, and Applied Software Project Management (O'Reilly)
posted 5 years ago
Thank you for answering my question. I hadn't thought of the company mindset being against Agile development. That will be something for me to keep in mind when I finally get a job in IT. I find the Agile development model to be very interesting and have a lot of benefits. I also believe that with the complex software being developed today, the traditional model is incompatible with OO languages and the entire iterative process. Thank you again for replying to my post.
Been there. Done that. Went back for more. But this time, I took this tiny ad with me:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop