Presenter: 王秉森 Progression towards Agility: A comprehensive survey.

Presenter:王秉森

Progression towards Agility:A comprehensive survey

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

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

But in practice, customers cannot tell everything they want in

advance

Iterative model

Iterative model

• Iterative Development aims to develop the project is divided into small parts

• allows the development team to demonstrate results earlier on in the process

and obtain valuable feedback from system users

• Often, each iteration is actually a mini-Waterfall process with the feedback

from one phase providing vital information for the design of the 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 IntelliJ IDEA plugins development services

• C. Agile explosion at Yahoo! Products have to be released as quickly as possible

CHALLENGES DURING TRANSITION

• People used to resist the abrupt change in the development structure from the one they are following from the scratch

• Management feels uncomfortable with not having a final commitment date of delivery with a bottom line cost

• Customers would rather know the total cost of the project and overall project schedule beforehand

CONCLUSION

• Agile alone will not be efficient

• Agile is able to produce the products in shorter time creating a goodwill among the customers. But security and other quality related aspects should not be compromised

• Every successful agile project is actually a combination of several methodologies

Thank you