agile (s.e)

19
Presented by:- Deep kumar M.Tech.(1 st year) (Software Engineering) AGILE METHODOLOGY

Upload: deep-sharma

Post on 02-Jul-2015

69 views

Category:

Engineering


0 download

DESCRIPTION

agile methodology

TRANSCRIPT

Page 1: Agile (s.e)

Presented by:-

Deep kumar

M.Tech.(1st

year)

(Software Engineering)

AGILE METHODOLOGY

Page 2: Agile (s.e)

Outline

1. Introduction to Agile

2. Water fall Vs Agile

3.Agile lifecycle

4.Agile manifesto

5.Characteristics of Agile

6.Techniques of Agile

7.Methods of Agile

8.Limitations

9.Conclusion

10. References

06-02-20141Vipul Rastogi

Page 3: Agile (s.e)

1. INTRODUCTION TO AGILE

● “Everything Should Be Made As Simple As Possible

But Not Simpler” -Albert Einstein

● “Core to agile software development is the use of light

but sufficient rules of project behavior and the use of

human and communication oriented rules.”

• -C . Burn

06-02-20142Vipul Rastogi

Page 4: Agile (s.e)

● The term agile can be defined as-

1) ability to move with quick easy grace, or

2) having a quick resourceful and adaptable character

(Merriam-Webster 2002)

● An iterative and incremental (evolutionary) approach

performed in a highly collaborative manner with just the

right amount of ceremony to produce high quality software

in a cost effective and timely manner which meets the

changing needs of it’s stakeholders.

06-02-20143Vipul Rastogi

Page 5: Agile (s.e)

2. Waterfall Vs Agile Approach

06-02-20144Vipul Rastogi

Page 6: Agile (s.e)

3. Agile Lifecycle

06-02-20145

Vipul Rastogi

Page 7: Agile (s.e)

4. AGILE MANIFESTO VALUES

● V1: Individual and interaction are valued over process and

tools.

● V2: Working software is valued over comprehensive

documentation.

● V3: Customer collaboration is valued over contract

negotiation.

● V4: Responding to change is valued over following a plan.

06-02-20146Vipul Rastogi

Page 8: Agile (s.e)

5. AGILE MANIFESTO PRINCIPLES

● P1: Customer is the highest priority

● P2: Welcome changing requirements , even late in

development

● P3: Deliver working software frequently

● P4: Business people and developers must work together daily

throughout the project

06-02-20147Vipul Rastogi

Page 9: Agile (s.e)

● P5: Face-to-face conservation is the best communication

method

● P6: Working software is the primary measure of progress.

● P7: Agile process promote sustainable development.

● P8: Continuous attention to technical excellence and good

design enhance agility.

● P9: The best architecture , requirement , and design emerge

from self-organizing teams.

06-02-20148Vipul Rastogi

Page 10: Agile (s.e)

5. CHARACTERISTICS OF AGILE

● Agile method break the task into small increments with

minimal planning.

● Iteration is a short time frame.

● Each iteration involves a cross-functional team working in all

function.

● Each agile team must have customer representative.

● Most of the agile methodology use daily face-to-face

communication.06-02-20149Vipul Rastogi

Page 11: Agile (s.e)

6. Techniques of Agile

6.1. Pair programming-

06-02-201410Vipul Rastogi

Page 12: Agile (s.e)

6.2. Continuous Customer Feedback-

.

06-02-201411Vipul Rastogi

Page 13: Agile (s.e)

6.3. Whole team involvement-

.

06-02-201412Vipul Rastogi

Page 14: Agile (s.e)

6.4. Daily stand-up meetings-

.

06-02-201413Vipul Rastogi

Page 15: Agile (s.e)

7. Methods of Agile

• XP eXtreme Programming

• ASD Adaptive Software Development

• DSDM Dynamic Systems Development Method

• Scrum (the name of an activity in a rugby match)

• FDD Feature Driven Development

• AUP Agile Unified Process

06-02-201414Vipul Rastogi

Page 16: Agile (s.e)

8. Limitations

● The agilest have not clearly defined the context for their

statements.

● Agile Manifesto and literature concerning agile software

development have not thoroughly discussed the use of

software tools and their role in agility.

● When software development is performed by several parties,

more pressure to communication and coordination emerges.

06-02-201415Vipul Rastogi

Page 17: Agile (s.e)

9. Conclusion

Most frequently changing thing in software development field

is customer requirements which keep on changing with in fraction

of second. Hence it become very difficult for developer to cope up

with continuously changing requirement. In today’s cut throat

competition it is very important to satisfy your customer , if you

are not than you are out of the race.

So in this environment Agile methodology is panacea to all. It

provide flexibility to customers that they can change their

requirement at any point of time according to their ease and this

change is not a matter of worry to developers. In nutshell , Agile

methodology rejuvenate conventional process of software

development.

06-02-201416Vipul Rastogi

Page 18: Agile (s.e)

10. References

● S. W. Ambler, Agile Modeling. New York, NY:

John Wiley and Sons, 2002

● agilemethodology.org

● James Mark Jamieson, agile Quality

Management Techniques,2012.

● A. Ahmed, S. Ahmad, Dr. N Ehsan, E. Mirza, S.Z.

Sarwar, “Agile Software Development: Impact on

Productivity and Quality” in the Proceedings of

IEEE ICMIT.(2010).

06-02-201417Vipul Rastogi

Page 19: Agile (s.e)

Thank you

06-02-201418Vipul Rastogi

…SHOOT YOUR QUERIES…