agile method.pptx

8/13/2019 Agile Method.pptx

1/25

Agile Methodology

Prepared by:

:

AZMI BIN MOHAMED | M20131000289MAZLAN BIN MUHAMAD YUSOF | M20131000281

MUHAMAD FIRDAUS BIN MOHAMAD | M20131000280


2/25

Contents Introduction

History of Agile Methodology

What is Agile Methodology? The Agile Manifesto, Principles & Development

Characteristics of Agile Methodology

Advantages & Disadvantages

Some Agile Methodologies

Summary

References


3/25

Introduction

Classical methods of software development havemany disadvantages:

huge effort during the planning phase

poor requirements conversion in a rapid changing environment

treatment of staff as a factor of production

New methods:Agile Software Development Methodology


4/25

Traditional Waterfall Approach

Months to working deliverable software

Requirements Requirement Fixing

Impossible to accuratelydefine

Design Waste of defining before

codingdesign willalways change

Code and UnitTest

No priorityall aspects batchedand built at same time -horizontally

SystemsIntegration

Issues found long afterdesign & implementation

Testing Unpredictable

testing cycle

Delivery Late detection

of missingcustomer value


5/25


6/25

History of Agile?


7/25


Metod pembangunan perisian ini telah dikesan pada

tahun 1957. Lightweightadalah metod yang diperkenalkan pada

tahun 1990 sebagai pengganti heavyweight, yang

dikenali sebagai Waterfall Model.

Kemudian sekitar 1990-an juga metod Agile muladiperkenalkan, iaitu bermaksud pantas, ringan, bebas

bergerak, dan peka.


8/25


Konsep Pembangunan Perisian Agile ini dicipta oleh

Kent Beck dan 16 orang rakan beliau, merakamenyatakan Agile ini adalah satu cara membangun

perisian sendiri dan sekaligus juga membantu orang lain

membangunkannya.

Early implementations of agile methods include Rational UnifiedProcess(1994), Scrum(1995), Crystal Clear, Extreme Programming

(1996),Adaptive Software Development, Feature Driven

Development(1997), and Dynamic Systems Development Method

(DSDM) (1995). These are now collectively referred to as agile

methodologies, after the Agile Manifesto was published in 2001.[5]
http://en.wikipedia.org/wiki/Unified_Processhttp://en.wikipedia.org/wiki/Unified_Processhttp://en.wikipedia.org/wiki/Scrum_(development)http://en.wikipedia.org/wiki/Crystal_Clear_(software_development)http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Adaptive_Software_Developmenthttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Dynamic_Systems_Development_Methodhttp://c/Users/user/Desktop/agile%20model/Agile%20software%20development%20-%20Wikipedia,%20the%20free%20encyclopedia.htmhttp://c/Users/user/Desktop/agile%20model/Agile%20software%20development%20-%20Wikipedia,%20the%20free%20encyclopedia.htmhttp://c/Users/user/Desktop/agile%20model/Agile%20software%20development%20-%20Wikipedia,%20the%20free%20encyclopedia.htmhttp://c/Users/user/Desktop/agile%20model/Agile%20software%20development%20-%20Wikipedia,%20the%20free%20encyclopedia.htmhttp://en.wikipedia.org/wiki/Dynamic_Systems_Development_Methodhttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Adaptive_Software_Developmenthttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Crystal_Clear_(software_development)http://en.wikipedia.org/wiki/Scrum_(development)http://en.wikipedia.org/wiki/Unified_Processhttp://en.wikipedia.org/wiki/Unified_Process


9/25

What is Agile?


10/25

AGILEIterative

AdaptableRapid

Cooperative

Quality-driven

Not a process, it's a philosophy or set of values


11/25

What is Agile ?

Agile proponents believe Current software development processes are too

heavyweight or cumbersome

Too many things are done that are not directly related to

software product being produced

Current software development is too rigid

Difficulty with incomplete or changing requirements

Short development cycles (Internet applications)

More active customer involvement needed

CMM focuses on process


12/25

Contd

Agile methods are considered Lightweight

People-based rather than Plan-based

Several agile methods

No single agile method XP most popular

No single definition

Agile Manifesto closest to a definition

Set of principles Developed by Agile Alliance


13/25

What is Agile Development?

Self Organizing*

Empowering

Collaborative

Active Customer Involvement

Frequent Delivery

Incremental

Time-Based*

Disciplined

Continuous Integration*

Feature Driven

Adaptive

GoalDriven

IterativeLean

EmergentApproach


14/25

What Is Agile Agile --readiness for motion, nimbleness, activity, dexterity inmotion

AgilityThe ability to both create and respond to change in order to profit in

a turbulent business environment Companies need to determine the amount of agility they need to be

competitive

Chaordic

Exhibiting properties of bothcha

os andord

er The blend of chaos and order inherent in the external environmentand in people themselves, argues against the prevailing wisdom aboutpredictability and planning

Things get done because people adapt, not because they slavishlyfollow processes


15/25

Individuals and interactions over

processes and tools

Working software overcomprehensivedocumentation

Customer collaboration overcontract negotiation

Responding to change over

following a plan

Agile Manifesto


16/25

Agile Principles

Customer satisfaction by rapid, continuous delivery of usefulsoftware

Working software is the principle measure of success

Changes in requirements are anticipated and welcomed

Close, daily cooperation between business and developers

Face-to-face conversation is the best form ofcommunication

Self-organizing teams

Regular adaptation to changing circumstances


17/25

Agile Development Includes

Continuous Innovation and Integration

Deliver current customer requirements

Decreased communication latency

Stakeholders actively involved in development

Testing integrated into the development process

Doesnt need or include a separate QA cycle

Continuous integration, multiple builds

Product adaptability Doesnt preclude future requirements

Adapts to changing requirements


18/25

Agile Software Development Agile software developmentis a conceptual framework

for software engineering that promotes development

iterations throughout the life-cycle of the project.

Software developed during one unit of time is referred to

as an iteration, which may last from one to four weeks.

Agile methods also emphasize working software as the

primary measure of progress


19/25

Agile Software Development: Intro Characteristics of Agile Software Development

-- Light Weighted methodology

-- Small to medium sized teams-- vague and/or changing requirements

-- vague and/or changing techniques

-- Simple design-- Minimal system into production


20/25

Characteristics Modularity

Iterative

Time-bound Incremental

Convergent

People-oriented

Collaborative


21/25

:: Advantages :: No Detail requirement needed: You dontneed to have the entire requirements finalised

to start the development work. Build and Test can start as soon as initial high level

requirements are available.

Early benefit to the user/business: Following Agile methodology gives an early view tothe user about how the final product might look and behave. This helps them into

finalising the user requirements. It might also happen that the prototype delivers some of

the requirements which use may want to use and evaluate till the final product is delivered

with all the functionalities.

Face to face communication: Agile method give more emphasis on having the face toface communication between the user/customer and project team to make sure there is

no room left for any kind of confusion in understanding requirement and inputs.

Less time to market: Using Agile method, final product is delivered to the customer inleast possible time.

Less cost to customer: It saves cost for both customer and supplier as resources areused for less time.

High Quality: Since customer is involved in all the stages of software development,means the quality of final quality if high resulting in highly satisfied customer.


22/25

:: Disadvantages ::

Smaller Planning Horizon: Since Agile projects have smaller planning horizonmeaning that project is started with out detailed planning, there is always a chance that

initial project effort and cost estimation may not be correct. This might result in multiple

changes to estimation in subsequent estimation.

Lesser design and documentation:Since build and test starts early, there is always achance that proper designing and documentation may take a back seat.

Need clear customer vision: As customer input is required in all iterations, it is verynecessary that customer should have clear vision of end product. Project can easily

loose its direction if client have only vague idea of the product they want.

Necessity of experienced and senior resources:Since Agile method is more aboutless planning and more decision making, it is absolutely necessary to have experienced

and senior resources in the team or experienced resources mentoring new resources.


23/25

Agile Methods

1. Extreme Programmning (XP)

2. Adaptive Software Development (ASD)

3. Dynamic Systems Development Method (DSDM)

4. Scrum Methodology

5. Crystal

6. Feature Driven Development (FDD)

7. Agile Modeling (AM)

8. Rational Unified Process


24/25

Existing Agile Methods

Agile

Crystal

XPScrum

DSDMFDD

KanbanRUP

and few more

* Check wikipedia for list of all Agile methods


25/25

Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J.(2002). Agile software development methods: review and

analysis. Espoo [Finland]: VTT. Retrieved from

http://www.pss-europe.com/P478.pdf

http://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overview

http://dwijaantara.wordpress.com/2010/10/25/agile-method/

REFERENCES
http://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://dwijaantara.wordpress.com/2010/10/25/agile-method/http://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overviewhttp://navneetjha.hubpages.com/hub/Agile-Methodology-A-Brief-Overview

agile method.pptx

Documents