Manifesto Flashcards
What do we value over processes and tools?
Individuals and interactions
What do we value over comprehensive documentation?
Working software
What do we value over contract negotiation?
Customer Collaboration
What do we value over following a plan?
Responding to change
A principle talks about “our highest priority”, explain it
Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software
A principle talk about changing requirements, explain it
Welcome changing requirements, even late in development. Agile processes
harness change for the customer’s competitive advantage.
A principle talks about software, explain it
Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.
A principle talks about working together, explain it
Business people and developers must work together daily throughout the project
A principle talks about motivated individuals, explain it
Build projects around motivated individuals. Give them the environment and
support they need, and trust them to get the job done
A principle talks about communication, explain it
The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
A principle talks about measure of progress, explain it
Working software is the primary measure of progress
A principle talks about “Agile processes promote..”, explain it
Agile processes promote sustainable development. The sponsors, developers, and
users should be able to maintain a constant pace indefinitely.
A principle talks about agility, explain it
Continuous attention to technical excellence and good design enhances agility
A principle talks about simplicity, explain it
Simplicity–the art of maximizing the amount of work not done–is essential (emphasizes the importance of focusing on the most valuable work and avoiding unnecessary or low-priority tasks. )
A principle talks about self organizing teams, explain it
The best architectures, requirements, and designs emerge from self-organizing
teams.
