Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
AGILE METHODOLOGY
 PRESENTED TO:
 MR. MANESSH KUMAR
 MRS. DEEPTI GUPTA
 PRESENTED BY:
 MOHIT KUMAR
 1313310092
 CSE...
Contents of the table
 Definition
 Manifesto
 Principles
 Characteristics
 Overview
 Philosophy
 Agile methods
 Ag...
What is Agile software development?
Agile software development is a set
of principles for software
development in which re...
Agile Manifesto
 Individuals and interactions: self-organization and
motivation are important, as are interactions like c...
Principles
The Agile Manifesto is based on twelve
principles:
 Customer satisfaction by early and continuous delivery of
...
Principle continued..
 Face-to-face conversation is the best form of communication
(co-location)
 Working software is th...
Characteristics of Agile Software
Development
-- Light Weighted methodology
-- Small to medium sized teams
-- vague and/or...
Overview
There are many specific agile
development methods. Most
promote development, teamwork,
collaboration, and proces...
Philosophy
 Compared to traditional software engineering,
agile software development mainly targets
complex systems and p...
Adaptive vs. predictive
 Agile methods lie on the adaptive side of this
continuum. One key of adaptive development
method...
Predictive
 Predictive methods, focus on analysing and planning
the future in detail and cater for known risks.
 In the ...
Iterative vs Waterfall
 In the waterfall model there is always a separate
testing phase after a build phase.
 However, i...
3/2/2016 23
3/2/2016 24
3/2/2016 25
3/2/2016 26
3/2/2016 27
Agile Method
 Adaptive software development (ASD)
 Agile modeling
 Agile Unified Process (AUP)
 Business analyst desig...
3/2/2016 29
Agile Practices
 Acceptance test-driven development (ATDD)
 Agile modeling
 Backlogs (Product and Sprint)
 Behavior-dr...
Experience and Adoption
 Agile methods were first used by technology early
adopters such as Tektronix.
 Agile can be use...
Common Pitfalls
 Lack of overall project design
 Adding stories to a sprint in progress
 Lack of sponsor support
 Insu...
Criticism
 The agile movement is in some ways a bit like a
teenager: very self-conscious, checking constantly
its appeara...
Aplications outside s/w development
 Integrated customer engagement - to embed
customers within any delivery process to s...
THANKS
3/2/2016 35
Agile Methodology PPT
Agile Methodology PPT
Agile Methodology PPT
Agile Methodology PPT
Agile Methodology PPT
Agile Methodology PPT
Agile Methodology PPT
Agile Methodology PPT
Agile Methodology PPT
Agile Methodology PPT
Upcoming SlideShare
Loading in …5
×

22

Share

Download to read offline

Agile Methodology PPT

Download to read offline

This Presentation shows That what is Agile methodology, its principles and key points and how it is different from other software development life cycle.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Agile Methodology PPT

  1. 1. AGILE METHODOLOGY  PRESENTED TO:  MR. MANESSH KUMAR  MRS. DEEPTI GUPTA  PRESENTED BY:  MOHIT KUMAR  1313310092  CSE 3/2/2016 1
  2. 2. Contents of the table  Definition  Manifesto  Principles  Characteristics  Overview  Philosophy  Agile methods  Agile practices  Experience and Adoption  Pitfalls  Criticism  Application outside software development 3/2/2016 2
  3. 3. What is Agile software development? Agile software development is a set of principles for software development in which requirements and solutions evolve through collaboration between self- organizing,cross-functional teams. 3/2/2016 3
  4. 4. Agile Manifesto  Individuals and interactions: self-organization and motivation are important, as are interactions like co- location and pair programming.  Working software: working software is more useful and welcome than just presenting documents to clients in meetings.  Customer collaboration: requirements cannot be fully collected at the beginning of the software development cycle, therefore continuous customer or stakeholder involvement is very important.  Responding to change: agile methods are focused on quick responses to change and continuous development. 3/2/2016 4
  5. 5. Principles The Agile Manifesto is based on twelve principles:  Customer satisfaction by early and continuous delivery of valuable software  Welcome changing requirements, even in late development  Working software is delivered frequently (weeks rather than months)  Close, daily cooperation between business people and developers  Projects are built around motivated individuals, who should be trusted. 3/2/2016 5
  6. 6. Principle continued..  Face-to-face conversation is the best form of communication (co-location)  Working software is the principal measure of progress  Sustainable development, able to maintain a constant pace  Continuous attention to technical excellence and good design  Simplicity—the art of maximizing the amount of work not done—is essential  Best architectures, requirements, and designs emerge from self- organizing teams  Regularly, the team reflects on how to become more effective, and adjusts accordingly 3/2/2016 6
  7. 7. 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 3/2/2016 7
  8. 8. Overview There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life- cycle of the project. 3/2/2016 8
  9. 9. Philosophy  Compared to traditional software engineering, agile software development mainly targets complex systems and projects with dynamic, non- deterministic and non-linear characteristics, where accurate estimates, stable plans, and predictions are often hard to get in early stages— and big up-front designs and arrangements would probably cause a lot of waste, i.e., are not economically sound. 3/2/2016 9
  10. 10. Adaptive vs. predictive  Agile methods lie on the adaptive side of this continuum. One key of adaptive development methods is a "Rolling Wave" approach to schedule planning, which identifies milestones but leaves flexibility in the path to reach them, and also allows for the milestones themselves to change.  Adaptive methods focus on adapting quickly to changing realities. When the needs of a project change, an adaptive team changes as well. 3/2/2016 10
  11. 11. Predictive  Predictive methods, focus on analysing and planning the future in detail and cater for known risks.  In the extremes, a predictive team can report exactly what features and tasks are planned for the entire length of the development process.  Predictive methods rely on effective early phase analysis and if this goes very wrong, the project may have difficulty changing direction.  Predictive teams often institute a change control board to ensure they consider only the most valuable changes. 3/2/2016 11
  12. 12. Iterative vs Waterfall  In the waterfall model there is always a separate testing phase after a build phase.  However, in agile development testing is usually done concurrently with, or at least in the same iteration as, programming.  Because testing is done in every iteration—which develops a small piece of the software—users can frequently use those new pieces of software and validate the value. 3/2/2016 12
  13. 13. 3/2/2016 23
  14. 14. 3/2/2016 24
  15. 15. 3/2/2016 25
  16. 16. 3/2/2016 26
  17. 17. 3/2/2016 27
  18. 18. Agile Method  Adaptive software development (ASD)  Agile modeling  Agile Unified Process (AUP)  Business analyst designer method (BADM)  Crystal Clear Methods  Disciplined agile delivery  Dynamic systems development method (DSDM)  Extreme programming (XP)  Feature-driven development (FDD)  Lean software development 3/2/2016 28
  19. 19. 3/2/2016 29
  20. 20. Agile Practices  Acceptance test-driven development (ATDD)  Agile modeling  Backlogs (Product and Sprint)  Behavior-driven development (BDD)  Cross-functional team  Continuous integration (CI)  Domain-driven design (DDD)  Pair programming  Planning poker  Refactoring 3/2/2016 30
  21. 21. Experience and Adoption  Agile methods were first used by technology early adopters such as Tektronix.  Agile can be used with any programming paradigm or language in practice Agile has usually been closely associated with object-oriented environments such as Smalltalk and Lisp and later Java.  The initial adopters of Agile methods were usually small to medium-sized teams working on unprecedented systems with requirements that were difficult to finalize and likely to change as the system was being developed. 3/2/2016 31
  22. 22. Common Pitfalls  Lack of overall project design  Adding stories to a sprint in progress  Lack of sponsor support  Insufficient training  Product owner role is not properly filled  Excessive preparation/planning  Lacking test automation 3/2/2016 32
  23. 23. Criticism  The agile movement is in some ways a bit like a teenager: very self-conscious, checking constantly its appearance in a mirror, accepting few criticisms, only interested in being with its peers, rejecting en bloc all wisdom from the past, just because it is from the past, adopting fads and new jargon, at times cocky and arrogant. But I have no doubts that it will mature further, become more open to the outside world, more reflective, and also therefore more effective. 3/2/2016 33
  24. 24. Aplications outside s/w development  Integrated customer engagement - to embed customers within any delivery process to share accountability for product/service delivery.  Facilitation-based management - adopting agile management models, like the role of Scrum Master to facilitate the day-to-day operation of teams.  An enabling organisational structure - with a focus on staff engagement,personal autonomy and outcomes based governance. 3/2/2016 34
  25. 25. THANKS 3/2/2016 35
  • HaoChen13

    Oct. 15, 2020
  • AkashPhoenix1

    Oct. 11, 2020
  • SunitaRai1

    Jul. 28, 2020
  • ZeinPomecha

    Jul. 1, 2020
  • DeepikaGosavi

    May. 15, 2020
  • zaidalmarhabi

    Feb. 25, 2020
  • meghayp

    Jan. 22, 2020
  • BhushanGawande10

    Dec. 9, 2019
  • AsHiHuGz

    Dec. 9, 2019
  • RadhikaChandok

    Nov. 29, 2019
  • slaubaer

    Jun. 10, 2019
  • kkranthiReddy

    Apr. 22, 2019
  • iimaanhabeeb

    Apr. 14, 2019
  • SatishReddy212

    Mar. 6, 2019
  • ravipandey7284

    Feb. 8, 2019
  • ShubhangiBarmase

    Feb. 7, 2019
  • VikramSathishAsokan2

    Feb. 6, 2019
  • GDvenugopal

    Apr. 18, 2018
  • EdelmiraBaldonado

    Apr. 12, 2018
  • AaimaBhatti

    Mar. 15, 2018

This Presentation shows That what is Agile methodology, its principles and key points and how it is different from other software development life cycle.

Views

Total views

40,758

On Slideshare

0

From embeds

0

Number of embeds

9

Actions

Downloads

2,153

Shares

0

Comments

0

Likes

22

×