2. Back to Basics
• Reboot from the beginning
• The History of Manifesto for Agile Software Development
• Agile Manifesto is consist of 4 CoreValues & 12 Principles
3. The History
• http://agilemanifesto.org/history.html
• Happened in 2001
• “Representatives from Extreme Programming, SCRUM, DSDM,
Adaptive Software Development, Crystal, Feature-Driven
Development, Pragmatic Programming, and others sympathetic to
the need for an alternative to documentation driven, heavyweight
software development processes convened.”
• Formed “The Agile Alliance”
4. Who are the authors?
• http://agilemanifesto.org/authors.html
• 19 authors
• 14 out of 19 listed
• Very high level professionals: company founders, CEO, chief
scientist, authors and consultants
5. Observations on the 4 CoreValues
• Try to find out the relationships between the Preferred and Not-
Preferred value.
6. Manifesto for Agile Software
Development
• 4 core values, http://agilemanifesto.org/
Preferred over Not Preferred
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
8. Categorize each principle withTIME
Categories descriptions
Technical
practices
architecture, design, coding, testing…
Internal Process
development process involved internally to a group or
company.
Mindset no explicit, formal actions required
External Process
development process involved external to a group or
company.
• Categorize each principle with, at most, 2 of theTIME categories
9. 12 Principles behind the Agile
Manifesto
Principles Categories
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.
10. 12 Principles behind the Agile
Manifesto
Principles Categories
5. Build projects around motivated individuals. Give 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. Working software is the primary measure of progress.
8. Agile processes promote sustainable development.The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
11. 12 Principles behind the Agile
Manifesto
Principles Categories
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.
12. Principles Categorie
s
1. Our highest priority is to satisfy the customer
through early and continuous delivery of valuable
software.
M
2.Welcome changing requirements, even late
in development. Agile processes harness change
for the customer's competitive advantage.
M
3. Deliver working software frequently, from
a couple of weeks to a couple of months, with
a preference to the shorter timescale.
IE
4. Business people and developers must
work together daily throughout the project. IE
5. Build projects around motivated individuals.
Give them the environment and support they
need, and trust them to get the job done.
I
6.The most efficient and effective method
of conveying information to and within a
development team is face-to-face conversation.
IM
Principles Categories
7.Working software is the primary measure of
progress. M
8. Agile processes promote sustainable
development. The sponsors, developers, and
users should be able to maintain a constant
pace indefinitely.
IM
9. Continuous attention to technical
excellence and good design enhances agility. MT
10. Simplicity--the art of maximizing the
amount of work not done--is essential. M
11.The best architectures, requirements, and
designs emerge from self-organizing teams MT
12. At regular intervals, the team reflects on
how to become more effective, then tunes
and adjusts its behavior accordingly.
IM
13. Observations on 12 Principles
• Some of the principles are very loaded statement.
• Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
• Some are general principles.
• Most of them (9/12) involve Mindsets, 5 for IP, 2 for EP andTP each.
• No one will dispute some of the principles in general
• Business people and developers must work together daily throughout the
project.
• Continuous attention to technical excellence and good design enhances
agility.
14. Questions
1. How much help can these Agile Principles
provide to Software Development?
2. What issues do they try to address?
3. How would the 12 principles address those
issues?
