An Examination and Evaluation of ‘Agile Methodologies’ for Systems Development with Recommendations for Future Developments of These Methods.
Strategic Planning and Systems Development
An examination and evaluation of ‘agile methodologies’ for systems development with recommendations for future developments of these methods.
Andre Giovani (TP029118)
Denny Tan (TP029117)
Submission Date: 21st January 2013
Agile Methodology in System Development
1. Introduction
This paper focusing on concept of how agile methodology support system development. The use of agile methodology appear because alot of critics in traditional methodology. According to Nandhakumar & Avison (1999) traditional methods are too mechanistic to be used in detail. Baskerville et al. (2003) claim that “to compete in the digital economy, companies must be able to develop high-quality software systems at “Internet speed”—that is, deliver new systems to customers with more value and at a faster pace than ever before”.
The understanding of traditional methods are this methods are required so much planning and also there are a lot of work in documentation. Because that heavy aspects, this traditional methodology also called as heavyweight.
Because of that, the agile methodology came up and built on existing traditional method that throw away the ‘bad’ parts of traditional method and remain the ‘good’ parts of it. This methodology also called lightweight because it is light and sufficient.
Recently, most of the information system development choose agile methodology. The motivation of choosing agile methodology are to make sure time to market system development to achieve substantial product, improvement in process and the used of one terminology in each project.
Highsmith and Cockburn (2001) reports that the change of environment in software business will bring an effect to system development processes. According to this author, to satisfy the customer in time delivering the system is not about how to stop changing the project in the early stage, but how to handle when unexpectable changing is required in the middle
An examination and evaluation of ‘agile methodologies’ for systems development with recommendations for future developments of these methods.
Andre Giovani (TP029118)
Denny Tan (TP029117)
Submission Date: 21st January 2013
Agile Methodology in System Development
1. Introduction
This paper focusing on concept of how agile methodology support system development. The use of agile methodology appear because alot of critics in traditional methodology. According to Nandhakumar & Avison (1999) traditional methods are too mechanistic to be used in detail. Baskerville et al. (2003) claim that “to compete in the digital economy, companies must be able to develop high-quality software systems at “Internet speed”—that is, deliver new systems to customers with more value and at a faster pace than ever before”.
The understanding of traditional methods are this methods are required so much planning and also there are a lot of work in documentation. Because that heavy aspects, this traditional methodology also called as heavyweight.
Because of that, the agile methodology came up and built on existing traditional method that throw away the ‘bad’ parts of traditional method and remain the ‘good’ parts of it. This methodology also called lightweight because it is light and sufficient.
Recently, most of the information system development choose agile methodology. The motivation of choosing agile methodology are to make sure time to market system development to achieve substantial product, improvement in process and the used of one terminology in each project.
Highsmith and Cockburn (2001) reports that the change of environment in software business will bring an effect to system development processes. According to this author, to satisfy the customer in time delivering the system is not about how to stop changing the project in the early stage, but how to handle when unexpectable changing is required in the middle
References: * Mehmet Na. (2004). An Agile Information Systems Development Method in Use. Available: http://journals.tubitak.gov.tr/elektrik/issues/elk-04-12-2/elk-12-2-5-0404-6.pdf. Last accessed 3 january 2013. * Stefan Cronholm. (2008). Using Agile Methods? – expected effects .Available: http://www.vits.org/publikationer/dokument/651.pdf. Last accessed 3 january 2013. * Natheer K. Garaibeh,. (2012). DSS Development and Agile Methods: Towards a new Framework for Software Development Methodology.Available: http://www.ijmlc.org/papers/162-C01203-002.pdf. Last accessed 4 january 2013. * David Moran. (2010). Top 10 Reasons to Use Agile Development.Available: http://www.devx.com/enterprise/Article/44619. Last accessed 4 january 2013. * BM. (2012). Five benefits of agile practices in software-intensive systems development. Available: https://www.ibm.com/developerworks/mydeveloperworks/blogs/invisiblethread/entry/five_benefits_of_agile_practices?lang=en. Last accessed 13 january 2013. * AFEI. (2011). The Business Case for Agile Methods. Available: http://www.afei.org/WorkingGroups/ADAPT/Documents/Business%20Case%20for%20Agile.pdf. Last accessed 14 janury 2013. * K. Vlaanderen S. Brinkkemper T. Cheng S. Jansen. (2009). Case Study Report: Agile Product Management at Planon. Available: http://webdoc.sub.gwdg.de/ebook/serien/ah/UU-CS/2009-005.pdf. Last accessed 18 january 2013. * Kelly Waters. (2007). Disadvantages of Agile Development. Available: http://www.allaboutagile.com/disadvantages-of-agile-development/. Last accessed 20 january 2013.