Presented by:-

Ashish Agrawal

M.Tech.(2nd year)

(Software Engineering)

Outline● Introduction to Agile●Water fall Vs Agile●Agile lifecycle●Graphical representation●Agile manifesto●Characteristics of Agile●Techniques of Agile●Limitations●Conclusion

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

Definition● 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

Waterfall Vs Agile Approach

Agile Lifecycle

Graphical Representation

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

AGILE MANIFESTO PRINCIPLES

●P1:Customer is the highest priority

●P2:Welcome changing requirements , even late in

development

●P3:Deliver working software frequently

●P4:Bussiness people and developers must work

together daily throughout the project

●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.

CHARACTERISTICS

● 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

Techniques of Agile

1. Pair programming-

2. Continuous Customer Feedback-

3. Whole team involvement-

4. Daily stand-up meetings-

Techniques of AgileAgile Techniques Pros Cons

Whole team involvement

• Improve quality planning• Gain commitment from

everyone

• require high level of communication from the entire team

Pair programming • Reduce bottleneck• Increases flexibility of making

changes

• Lack of compatibility• Mismatched skills

Continuous integration

• Identifies build issues early• Risk reduction

• More work for developers

Continuous customer feedback

• Customer interest & priorities• Lead to more useful products

• Communication gaps• Customer may become

designer of system

Daily standup meetings

• Team work together to improve quality

• Purpose of meeting may lost

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.

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.

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

John Wiley and Sons, 2002●A. Cockburn, Agile Software Development.

Reading, Massachusetts: Addison Wesley Longman, 2001.

● 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).

Thank you