Agile software processes are characterized by unpredictable requirements that change over time. Agile methods promote iterative development in short cycles with customer involvement and frequent review. The Agile Manifesto from 2001 defines key agile principles including valuing individuals, collaboration, response to change, and working software over documentation. Popular agile methods include scrum, extreme programming, feature-driven development, and lean software development.

1. AGILE SOFTWARE PROCESSES SOFTWARE ENGINEERING 1 SIDRA MATLOOB SHEIKH BSCS 4 B

3. For software: design and construction are interleaved. Both activities are used in tandem.

5. team work

6. collaboration

7. process adaptability through out the lifeAGILE METHODS: Break tasks into small increments with minimal planning

9. worked on full software development cycle including:

10. Planning

11. Requirement

12. Analysis

13. Design

14. Coding

15. Unit Testing

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

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

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“

33. Working software over comprehensive documentation

34. Customer Collaboration over contract Negotiation

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

45. Senior developers

46. Requirements changes very often

47. Small number of developers

49. Junior developers

50. Requirement do not change

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

62. Behavior driven development (BDD)

63. Continuous Integration

64. Pair Programming

66. www.stell_greene.com

67. www.sci.cmu.edu