Software Methodologies
-
I found this link while surfing around and thought it might be interesting to those of us who are always looking for better ways to perfect our craft: http://www.cio.com/archive/070101/secret_content.html The link talks about a software methodology called Agile Development. I'm interested to know if any of you have had any experience with using this methodology, and would like to share that experience. Also, do any of you guys follow any other particular methodology like RUP, XP (Extreme) Programming, the traditional Waterfall method, code by the seats of your pants :-D, etc.? Which one do you think is better for which situations? BTW, don't miss the second page of the article which goes over some case studies of failed projects, how much money they blown ($15 million over four years!) before killing the project, and whom the IT managers are blaming for their failures :-D http://www.cio.com/archive/070101/secret_sidebar_2.html
-
I found this link while surfing around and thought it might be interesting to those of us who are always looking for better ways to perfect our craft: http://www.cio.com/archive/070101/secret_content.html The link talks about a software methodology called Agile Development. I'm interested to know if any of you have had any experience with using this methodology, and would like to share that experience. Also, do any of you guys follow any other particular methodology like RUP, XP (Extreme) Programming, the traditional Waterfall method, code by the seats of your pants :-D, etc.? Which one do you think is better for which situations? BTW, don't miss the second page of the article which goes over some case studies of failed projects, how much money they blown ($15 million over four years!) before killing the project, and whom the IT managers are blaming for their failures :-D http://www.cio.com/archive/070101/secret_sidebar_2.html
We use XP to great success - for the first time in years we have shipped products on the date we were told to, within spec! We have now been running it for 6 months, with almost no problems. The biggest obstacle to XP is that is not only for the developers - QA and Product Management have to buy into it totally. The only setbacks have in fact been when people have reverted to the 'old way'. Otherwise it is the best methodology I have ever worked to.
-
We use XP to great success - for the first time in years we have shipped products on the date we were told to, within spec! We have now been running it for 6 months, with almost no problems. The biggest obstacle to XP is that is not only for the developers - QA and Product Management have to buy into it totally. The only setbacks have in fact been when people have reverted to the 'old way'. Otherwise it is the best methodology I have ever worked to.
Interesting, XP seems to have had a tremendously positive impact on your company's software development process! Congrats! I know of one shop that is also using XP and it is working great for them. Bugs have decreased, code is more readable and extensible, etc. I agree that with any change in methodology you have to get almost everyone else in addition to your own team to support the process change. Thanks for the feedback!
-
I found this link while surfing around and thought it might be interesting to those of us who are always looking for better ways to perfect our craft: http://www.cio.com/archive/070101/secret_content.html The link talks about a software methodology called Agile Development. I'm interested to know if any of you have had any experience with using this methodology, and would like to share that experience. Also, do any of you guys follow any other particular methodology like RUP, XP (Extreme) Programming, the traditional Waterfall method, code by the seats of your pants :-D, etc.? Which one do you think is better for which situations? BTW, don't miss the second page of the article which goes over some case studies of failed projects, how much money they blown ($15 million over four years!) before killing the project, and whom the IT managers are blaming for their failures :-D http://www.cio.com/archive/070101/secret_sidebar_2.html
We're an XP shop and have been very happy with this methodology. One important point - imho if you're a company of size > 1, you need to have a management team that understands and embraces XP. Disciplined engineering flows downhill, and it's a requirement that the cost of this discipline be understood by those who manage the development effort. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com