• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/13

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

13 Cards in this Set

  • Front
  • Back
4 paired values
We are uncovering better ways of developing software by doing it and helping others do it. We value:
1. Individuals and interactions over processes and tools.
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan.
Agile Principals 1
highest priority
satisfy the customer through early and continuous delivery of valuable software
Agile principals 2
Welcome changing requirements
even late in development. Agile processes harness change for the customer's competitive advantage.
Agile principals 3
Deliver working software frequently
from a couple of weeks to a couple of months. with a preference to the shorter timescale
Agile principals 4
Business people and developers must work together...
daily through out the project.
Agile principals 5
Build projects around motivated individuals.
Give them the environment and support they need and trust them to get it done
Agile principals 6
The most efficient and effective method of conveying information to and within a development team is
face to face
Agile principals 7
Working software
is the primary measure of progress
Agile principals 8
Agile processes promote sustainable development
the sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Agile principals 9
Continuous attention to technical excellence and good design
enhances agility.
Agile principals 10
Simplicity
the art of maximizing the amount of work not done - is essential

(not doing unnecessary work)
Agile principals 11
The best architectures, requirements, and designs emerge from
self organizing teams
Agile principals 12
At regular intervals, the team
reflects on how to become more effective, then tunes, and adjusts its behavior accordingly.