Agile software development process

30
AGILE SOFTWARE DEVELOPMENT METHODS Presenters Names: Mobeen Xyz..

Transcript of Agile software development process

Page 1: Agile software development process

AGILE SOFTWARE DEVELOPMENT METHODS

Presenters Names:Mobeen

Xyz..

Page 2: Agile software development process

We are going to explain...

• Abstraction• Introduction• Background• The Agile Manifesto• Terminology• Some Agile Methodologies• Comparison

Page 3: Agile software development process

• What’s Agility?

Being agile

Page 4: Agile software development process

• What’s Agile?

“marked by ready ability to move with quick easy grace”

“having a quick resourceful and adaptable character”

Page 5: Agile software development process

• What does that mean?

– Process has to be lightweight and sufficient

Page 6: Agile software development process

– Lightweight helps us adapt and move

– Sufficient recognizes our ineffectiveness to be complete and relies on strong communication

Page 7: Agile software development process

Background• European wide research initiative on agile methods• Agile-ITEA project conducted between 2004 and 2006• methods in embedded software development in EuropeSurvey study design.the industrial participantorganizations of Agile-ITEA provided a sample of organizations that were known to be interested in agile methods,and known to have access and involvement in the ongoingresearch on agile software development methods inEurope.

Goal; adoption of XP and scrum methods

Page 8: Agile software development process

• „Late 1990 several methodologies began to get increasing public attention. Each had a different combination of old ideas, new ideas, and transmuted old ideas. But they all emphasized close collaboration between the programmer team and business experts;

• face-to-face communication (as more efficient than written documentation);

• frequent delivery of new deployable business value; tight, self-organizing teams; and ways to craft the code and the team such that the inevitable requirements churn was not a crisis.”

Page 9: Agile software development process

The image below shows how these activities align with the project schedule in traditional software

Page 10: Agile software development process

With Agile development methodology –

Page 11: Agile software development process

BRIEF OVERVIEW OF AGILE METHODOLOGY

Page 12: Agile software development process

Who’s Who

Page 13: Agile software development process

Methodology

• Agile software development methodology is an process for developing software (like other software development methodologies

Page 14: Agile software development process
Page 15: Agile software development process
Page 16: Agile software development process

Working Toward Mastery

Page 17: Agile software development process
Page 18: Agile software development process

Doing Your Best Work

Page 19: Agile software development process
Page 20: Agile software development process
Page 21: Agile software development process
Page 22: Agile software development process
Page 23: Agile software development process
Page 24: Agile software development process
Page 25: Agile software development process

COMPARISON OF AGILE AND NON-AGILE

Page 26: Agile software development process

Parameters

Approach of this methodology

Measurement of Success

Size of the Project

Style of Management

Ability to adapt to changeDocumentation required

Agile Model Non-Agile Models

Flexible and adjustable and can project needs.

Not as flexible

The success of the project is measured by the Business value delivered.

The success is measured by the Conformation to plan.

The Project size is small . The project size is Large in non- Agile models.

Not centralized, distributed among the team members.

Only one person is the decision maker and rest of the people follows him.

Changes are accepted and adapted needs.

Changes are not accepted easily in the later stages of the development.

Less documentation is required in Agile.

More documentation is required in non-Agile models.

Page 27: Agile software development process

Parameters Agile Model Non-Agile Models

Importance of

Cycles or iterations

Planning in Advance

Revenue

Size of the team

More emphasis is given to the People- Oriented.

More importance is given to the process .

Has many cycles or iterations. But, in Non-Agile methodology the cycles are limited.

There is minimal upfront planning in Agile methodology.

Planning should be complete before the development starts.

The return on investment is early in the project cycle.

The return on investment is at the end of the project.

The size of the team in Agile methodology is usually small and creative.

But in Non-Agile models the team size is large.

Page 28: Agile software development process

Resources

• <Intranet site text here>http://www.slideshare.net/hareshkarkar/overview-of-agile-methodology

• <Additional reading material text here><hyperlink here>

• This slide deck and related resources:<hyperlink here>

Page 29: Agile software development process

ANY QUESTIONS?

QUESTION SESSION

QUESTIONS HANDLER: MOBEEN KHAN

Page 30: Agile software development process

THANKS FOR APPRECIATING