Agile Methods vs Process Oriented Software Development Method

3018 WordsFeb 7, 201113 Pages
Agile Methods Vs Process-Oriented Software Development Subject - CMT 624: Software And Data Management Lecturer – Dr. Wendy K. Ivins & Dr. Tom W. Carnduff Student – Rahul Dutta Roy Student ID - 1014860 “On February 11.13, 2001, at The Lodge at Snowbird ski resort in the Wasatch mountains of Utah, 17 people met to talk, ski, relax and try to find common ground. What emerged was the Agile Software Development Alliance.” (Martin Fowler and Jim Highsmith, 2001 ) This new approach redefined our vision of software development- giving rise to a work culture focussed on human resources, mutual trust, interaction and productivity - radically going against the long established approach based on detailed structuring and modelling,…show more content…
While concept of iteration was already available, Agile Manifesto has taken it one step further by reducing the time span for each cycle (timeboxing) and further specifying requirements scope. Also there can be many internal releases for learning from previous release and developing further before final delivery to customer (Petersen et al., 2010 ). The Agile Manifesto also encourages simple solutions to complex problems that incorporate dependencies, are easy to understand and minimise risks. "Simple, clear purpose and principles give rise to complex, intelligent behavior," (Dee Hock, former CEO of Visa International as cited in Martin Fowler and Jim Highsmith, 2001). On the downside, the above scenario may be specific to only smaller projects as in larger, more complex systems, absence of critical architecture and documentation reflecting core functions makes it difficult to map coding with exact requirements introducing risks of costly changes ( Turk et al., 2002), as it is troublesome for novice programmers in understanding the enterprise operations and necessitates all team-members with immense experience, dedication and skillset. Difficulty in identifying organisation structure becomes paramount when development is distributed hindering smooth communication and opinion exchange. Designs, models and documenting each phase’s result remain only options to bridge the gap; clarify
Open Document