Introduction to Agile

Anmerkungen:

• For (customer) Who (statement of the need) The (product) IS AN (product Category) THAT (key benefit) UNLIKE (key differentiator)

1. 4 Values
   1. Individuals & Interactions

      Anmerkungen:

      • over processes and tools
   2. Working Software

      Anmerkungen:

      • Over comprehensive documentation
   3. Customer collaboration

      Anmerkungen:

      • over contract negotaion
   4. Responding to change

      Anmerkungen:

      • Over following plan
2. 12 Principles
   1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software
   2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
   3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
   4. Business people and developers must work together daily throughout the project
   5. Build projects around motivated individuals. Given them the environment and support they need, and trust them to get the job done.
   6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation
   7. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
   8. Working software is the primary measure of progress
   9. Continuous attention to technical excellence and good design enhances agility
   10. Simplicity - the art of maximizing the amount of work not done - is essential
   11. The best architectures, requirements, and designs emerge from self-organizing teams
   12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly

1. Waterfal Development
   1. Linear process
   2. A lot of hand-offs between siloed teams
   3. Large amount of written documentation
   4. Fixes scope, cost, and duration up front
   5. Relies on detailed planning and design up front to reduce risk
   6. Change adverse or costly to change
   7. Relies on project manager to collect project status and report
   8. Value delivered at the end of the project
   9. Problems with traditional development process
      1. Artifact reviews can't prove the product is correct, or measure the project's true progress
      2. Overly precise plans are difficult to change
      3. Unnecessary dependencies cause blocked or delayed work
      4. Business must completely specify the product upfront
      5. Conformance to plan over change and adaptation
      6. Long feedback loops
      7. Impeded innovation
      8. Unnecessary overhead and bureaucracy
2. Agile Development
   1. An iterative process - delivery regularly
   2. Flexible duration, scope and cost
   3. Little dsign documentation
   4. Relies on frequesnt collaboration and short feedback loop to reduce risk
   5. Status is visible to everyone
   6. Deliver value quickly - within days or weeks
   7. Change is welcome
3. Drivers for Agile Adoption
   1. Buisiness Enviornment

      Anmerkungen:

      • 1.Our business is constantly Changing 2. New ideas emerges constantly 3. Opp. and Threats appear unepectedly
   2. Software Building Process

      Anmerkungen:

      • Solution doesn't always work
   3. Human Behaviour

      Anmerkungen:

      • We misunderstand requirements.  When we see something working, we also see improvements
   4. Deliver business value rather than just projects

1. Users are imvolved throughout the process
2. The team is empowered and allowed to make decisions
3. While requirements evolve, timelines and timescales are fixed

   Anmerkungen:

   • time duration of each iteration is fixed
4. All requirements are captured only at a high level, are lightweight, and are generally visually represented
5. Development proceeds in small incremental steps, each has a release at the end
6. General focus is always on the frequent delivery of products
7. At the end of each sprint (iteration), every feature included is complete.
8. The 80/20 rule is always applied; the focus is on the important 20% that willd rive the majority of the results
9. Testing is implemented throughtout the lifecycle. Testing is done early and often.
10. All interactions of the team and stakeholders are collaborative and cooperative.

1. Faster return on investment through shorter cycles; quicker to market and faster resolution of issues
2. Increased client confidence by improving productivity; quality and client satisfaction
3. Happier developers by giving them more autonomy; diversity; and lightweight loads
4. Better communication with more face-toface; feedback, and collaboration
5. Better change management
6. Improved project visibility