1 / 14

Agile Methodologies

Agile Methodologies. Agile Methodologies - history. Traditional Methodologies: Waterfall approaches Iterative approaches Etc. Characterized by: Documentation – (repositories) Detailed planning. Assumptions about sw-projects:. It is hard to predict in advance:

amergin
Download Presentation

Agile Methodologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile Methodologies

  2. Agile Methodologies - history • Traditional Methodologies: • Waterfall approaches • Iterative approaches • Etc. • Characterized by: • Documentation – (repositories) • Detailed planning

  3. Assumptions about sw-projects: • It is hard to predict in advance: • The number of changes and priority changes in software requirements • How much design is needed before construction is used to prove it • The time to analysis, design, construction and testing • Solution? • Incremental development

  4. Agile Methodologies - history • During 1990’ies: • Extreme Programming (Kent Beck) • SCRUM (Ken Schwaber) • DSDM (DSDM-consortium) • Adaptive Software Development (Jim High smith) • Crystal (Alistair Cockburn) • Feature Driven Development • Pragmatic Programming

  5. Agile Methodologies - history • 11th of February 2001: • Snowbird ski resort in Utah mountains • 17 ’methodology’ people • “Agile” in stead of “light” • “The Agile Alliance” • Not anti-methodology

  6. Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick Robert C. MartinSteve Mellor Ken Schwaber Jeff Sutherland Dave Thomas Agile Methodologies 2001

  7. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.

  8. Principles behind the Agile Manifesto • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project.

  9. Principles behind the Agile Manifesto • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. • Working software is the primary measure of progress. • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

  10. Principles behind the Agile Manifesto • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

  11. Agile Methodologies • An agile team recognizes that software is developed by individuals working in teams and that the skills of these people, their ability to collaborate is at the core for success og the project.

  12. Human Factors • Competence • Common focus • Collaboration • Decision-making ability • Fuzzy problem-solving ability • Mutual trust and respect • Self-organization

  13. Agile Methodologies • XP eXtreme Programming • ASD Adaptive Software Development • DSDM Dynamic Systems Development Method • Scrum (the name of an activity in a rugby match) • (Crystal) a family of agile methodologies (Alistair & Cockburn) • FDD Feature Driven Development • AUP Agile Unified Process

  14. Agile Modeling • Model with a purpose • Use multiple models • Travel light • Content is more important than representation • Know the models and the tools you use to create them • Adapt locally

More Related