agile approach(sad)

8/8/2019 Agile Approach(SAD)

1/15


2/15


3/15

The Agile Approach


4/15

AGILE PRINCIPLES


5/15

Agile Manifesto

Individuals and interactions over

processes and tools

Working software over comprehensivedocumentation

Customer collaboration over contract

negotiation Responding to change over following a

plan


6/15

Agile Methods

Agile methods are approaches to manage thedevelopment of Internet products and servicesbased on principles of early customer involvement,iterative development, self organizing teams, andflexibility.

Agile is a principles-based developmentapproach that speeds delivery and controls costs by

minimizing overhead

Ensures closer fit to business needs throughstronger collaboration

Reduces risk through rapid releases of valuableand usable business functionality.


7/15

Agile Attributes

Agile processes include three major attributes,theyare:

Incremental and Evolutionary allowingadaptation to both internal and external events.

Modular and Lean allowing components of theprocess to come and go depending on specificneeds if the participants and stake-holders.

Time Based built on iterative and concurrentwork cycles, which contain feedback loops andprogress checkpoints.


8/15

Agile Attributes

Continuous integration-The process of creating workingversions of code quickly and on a regular basis (daily or morefrequently depending on the methodology) for testing anduser review.

Iterations-An agile development cycle involving design, codeand test of a preselected series of features or requirements.Depending on the methodology used, a typical iteration maybe as short as two weeks or as long as three months.

Pair programming-A technique that uses two developers

working side by side on the same assignment. It encouragescontinuous interaction and review of each others work.


9/15

Agile Attributes

Refactoring-An agile technique for restructuring aunit of code to simplify its design and operationwithout changing its functionality.

Stories-Short descriptions of a desired feature orfunction written in a narrative manner. Stories describehow a user imagines a feature being used rather thanan approach for implementing that feature.

Use cases-A more formal description of functionalitythat describes the expected behavior of the desired

functionality. Use cases guide development of thefunctionality and are also the basis for test cases thatverify if the implementation is correct.


10/15

What is


11/15

WHAT IS SCRUM?

SCRUM is the default process for Agile ProjectManagement and has the followingassumptions in its pure form:

Senior Team Members

Dedicated Team

100% Product Owner Involvement

Product Backlog

Sprint Backlog

Daily Meeting

Burndown Chart

Sprint Planning Meeting

Pigs - Committed

Chickens - Not Committed


12/15

Scrum is an interactive, incremental

process for developing any product or

managing any work.

It produces a potentially shippable set of

functionality at the end of everyiterations.

WHAT IS SCRUM?


13/15

Attributes of Scrum

An Agile process to manage andcontrol development work.

Is a wrapper for existingengineering practice.

Is a team-based approach toiterative, incremental

development of systems andproducts when requirements arerapidly changing.


14/15

Attributes of Scrum

A Process that controls the chaos of conflicting

interest and needs.

Is a way to improve communications andmaximize co-operations.

To detect and cause the removal of anything

that gets in the way of developing and

delivering products.

A way to maximize productivity.


15/15

Scrum process flow isiterative andincremental in nature.

It results in better

performance.

agile approach(sad)

Documents