140 likes | 249 Views
p rogression towards a gility: a comprehensive survey. Presenter: 王秉森. Outline. INTRODUCTION TRADITIONAL METHODOLOGIES AGILE METHODOLOGIES SUCCESS STORIES OF AGILE CHALLENGES DURING TRANSITION CONCLUSION. INTRODUCTION.
E N D
progression towards agility:a comprehensive survey Presenter:王秉森
Outline • INTRODUCTION • TRADITIONAL METHODOLOGIES • AGILE METHODOLOGIES • SUCCESS STORIES OF AGILE • CHALLENGES DURING TRANSITION • CONCLUSION
INTRODUCTION • Nowadays, Businesses are being forced to respond at a more rapid tempo to keep up with today’s changing requirements • The requirement for rapid development and change cannot be addressed by a traditional development process • There may be cases where the product may completely be rejected by the stakeholder and the entire effort may go waste • In the nineties, a new system of methods was introduced to meet the changing needs of customers. Known as “Agile system”
TRADITIONAL METHODOLOGIES • A: Waterfall model • delivers the product at the end • B: Iterative model • delivers the product in iterations • C. Pitfalls of the models
Waterfall model • emphasizes a structured progression between defined phases. Each phase consists on a definite set of activities and deliverables that must be accomplished before the following phase can begin • It assumes that all requirements can be accurately gathered at the beginning of the project • Butin practice, customers cannot tell everything they want in advance
Iterative model • Iterative Development aims to develop the project is divided into small parts • allows the development team to demonstrate resultsearlier on in the process and obtain valuable feedbackfrom system users • Often, each iteration is actually amini-Waterfall process with the feedback from onephase providing vital information for the design ofthe next phase
Pitfalls of the models • Unpredictability of Requirements • Continuously changing environment • Unable to produce the product in time and budget due to changing requirements • Unable to achieve customer satisfaction
Agile methodologies • XP Programming • Scrum
SUCCESS STORIES OF AGILE • A. Rail application to ensure safety • Customer requested a compressed schedule • B. Agile at Spartez:http://www.spartez.com/ • Eclipse and IntelliJIDEA plugins development services • C. Agile explosion at Yahoo! • Products have to be released as quickly as possible
CHALLENGES DURING TRANSITION • Peopleused to resist the abrupt change in the developmentstructure from the one they are following from thescratch • Management feels uncomfortable withnot having a final commitment date ofdelivery with a bottom line cost • Customers would rather know the total cost of theproject and overall project schedule beforehand
CONCLUSION • Agile alone will not be efficient • Agile is able to produce the products in shorter timecreating a goodwill among the customers. Butsecurity and other quality related aspects should notbe compromised • Every successful agile project isactually a combination of several methodologies