Agile - Introduction

Software Engineering
1.0x

Agile - Introduction

Created 2 years ago

Duration 0:04:26
lesson view count 143
Select the file type you wish to download
Slide Content
  1. Agile Introduction

    Slide 1 - Agile Introduction

    • Emerson Murphy-Hill
  2. Agile Manifesto/Alliance

    Slide 2 - Agile Manifesto/Alliance

    • XP, SCRUM, DSDM, Adaptive Software Development, Crystal, FDD
    • February 2001 (Snowbird, UT)
    • Agile Alliance
    • Started as 17 methodology authors and practitioners
  3. http://agilemanifesto.org/

    Slide 3 - http://agilemanifesto.org/

  4. Agile Principles (1 of 3)

    Slide 4 - Agile Principles (1 of 3)

    • 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.
    • from http://agilemanifesto.org/principles.html
  5. Agile Principles (2 of 3)

    Slide 5 - Agile Principles (2 of 3)

    • 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.
    • Continuous attention to technical excellence and good design enhances agility.
    • from http://agilemanifesto.org/principles.html
  6. Agile Principles (3 of 3)

    Slide 6 - Agile Principles (3 of 3)

    • 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.
    • from http://agilemanifesto.org/principles.html