Your SlideShare is downloading. ×
  • Like
Sidra Agile Software Process
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Sidra Agile Software Process

  • 2,242 views
Published

Agile Software Process

Agile Software Process

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • :)
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
2,242
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
87
Comments
1
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. AGILE SOFTWARE PROCESSES
    SOFTWARE ENGINEERING 1
    SIDRA MATLOOB SHEIKH
    BSCS 4 B
  • 2. INTRODUCTION
    WHAT IS AN AGILE PROCESS?
    CHARACTERIZED:
    • Difficult to predict which software requirements will persists or which change
    • 3. For software: design and construction are interleaved. Both activities are used in tandem.
    • 4. Analysis design, construction are not predictable.
  • INTRODUCTION
    There are many specific agile development
    methods most promote:
    • development iterations
    • 5. team work
    • 6. collaboration
    • 7. process adaptability through out the life
    AGILE METHODS:
    Break tasks into small increments with minimal planning
  • 8. ITERATION
  • ITERATION
    • At the end of each iteration customer representative review progress and re-evaluate priorities with a view to optimizing the return on investment and ensuring alignment with customer needs and company goals
  • HISTORY
    • The modern definition of agile software evolved in mid of 1990s , perceived to be typified by a
    • 17. Heavily regulating
    • 18. Regimented
    • 19. Micro managed use of the waterfall model were seen as:
    • 20. Bureaucratic
    • 21. Slow
    • 22. Demeaning
    • 23. Inconsistent
    With a ways that software developers actually perform effective work
  • 24. HISTORY
    • “Light weight methods “
    • 25. In 2001 ,prominent member of community of met at Snowbird ,Utah and Adopted the name “Agile Methods”
    • 26. An adaptive software development process was introduced in a paper by Edmonds 1974
    • 27. Early Agile methods include scrum 1995
    • 28. The crystal year , Extreme Programming 1996
    • 29. ASD, FDD,DSDM 1995
    These typically are referred to as Agile methodologies since Agile Manifesto was published in 2001
  • 30. Principles Behind Agile Process
    • Agile methods are a family of development processes, not a single approach to software development
    • 31. In 2001, 17 prominent figures in the field of agile development came together “ to discuss ways of creating software in a lighter , faster ,more people-centric way“
    • 32. They coined the term Agile Software Development and created the Agile Manifesto, widely regarded as canonical definition of agile development & accompanying agile principles
  • Agile States Are
    • Individual & Interaction over processes and Tools .
    • 33. Working software over comprehensive documentation
    • 34. Customer Collaboration over contract Negotiation
    • 35. Responding to change over a plan
  • Principle Behind Agile Manifesto are:
    • Delivery of useful software
    • 36. Working Software is delivered frequently
    • 37. Working is principle measure of progress
    • 38. Close, daily cooperation between business people and developer
    • 39. Face-to-face conversation is the best form of communication
    • 40. Project are built around motivated individuals , who should be trusted .
    • 41. Continuous attention to technical excellence and good design
    • 42. Simplicity
    • 43. Self organization team
    • 44. Regular adaptation to changing circumstance
  • AGILE HOME GROUND
    • Low criticality
    • 45. Senior developers
    • 46. Requirements changes very often
    • 47. Small number of developers
    • 48. Culture that thrives on chaos
  • PLAN-DRIVEN HOME GROUND
    • High criticality
    • 49. Junior developers
    • 50. Requirement do not change
    • 51. Large number of developers
  • AGILE METHODS
    Some of the well known agile software development
    method:
    • Agile modeling
    • 52. Agile unified process (AUP)
    • 53. Agile data methods
    • 54. DSDM
    • 55. Essential unified process (EssUP)
    • 56. Extreme programming (XP)
    • 57. Feature driven development (FDD)
    • 58. Getting real
    • 59. open unified process (OpenUPP)
    • 60. Scrum
    • 61. Lean software development
  • Agile Practices
    • Test driven development (TDD)
    • 62. Behavior driven development (BDD)
    • 63. Continuous Integration
    • 64. Pair Programming
    • 65. Planning Poker
  • References
    • www.wikipedia.com
    • 66. www.stell_greene.com
    • 67. www.sci.cmu.edu
    • 68. www.spc.ca
  • Thanks