The document discusses labeling phrases from a set of core values with categories of "Bad", "Unknown", "Neutral", and "Good". It then labels each phrase from the Agile Manifesto with these categories. Most phrases are labeled as "Good". It then discusses hunting for "unspoken words" related to software development issues and principles of agile development. In the end it questions how applicable the 12 principles are for solving specific software development problems.

1. AgilityReboot:II
Andrew Chum

2. Label CoreValue Phrases with …
Categories descriptions

3. Label CoreValue Phrases with B
Categories descriptions
Bad Negative, undesirable, not working…

4. Label CoreValue Phrases with BU
Categories descriptions
Bad Negative, undesirable, not working…
Unknown Just unknown, undecidable, hard to says…

5. Label CoreValue Phrases with BUN
Categories descriptions
Bad Negative, undesirable, not working…
Unknown Just unknown, undecidable, hard to says…
Neutral Sometimes good, sometimes bad, 50/50, it depends…

6. Label CoreValue Phrases with BUNG
Categories descriptions
Bad Negative, undesirable, not working…
Unknown Just unknown, undecidable, hard to says…
Neutral Sometimes good, sometimes bad, 50/50, it depends…
Good Positive, desirable, working…

7. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred
over processes and tools Not preferred
Working software preferred
over comprehensive documentation Not preferred
Customer collaboration preferred
over contract negotiation Not preferred
Responding to change preferred
over following a plan Not preferred

8. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred Unknown
over processes and tools Not preferred
Working software preferred
over comprehensive documentation Not preferred
Customer collaboration preferred
over contract negotiation Not preferred
Responding to change preferred
over following a plan Not preferred

9. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred Unknown
over processes and tools Not preferred Neutral
Working software preferred
over comprehensive documentation Not preferred
Customer collaboration preferred
over contract negotiation Not preferred
Responding to change preferred
over following a plan Not preferred

10. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred Unknown
over processes and tools Not preferred Neutral
Working software preferred Good
over comprehensive documentation Not preferred
Customer collaboration preferred
over contract negotiation Not preferred
Responding to change preferred
over following a plan Not preferred

11. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred Unknown
over processes and tools Not preferred Neutral
Working software preferred Good
over comprehensive documentation Not preferred Good
Customer collaboration preferred
over contract negotiation Not preferred
Responding to change preferred
over following a plan Not preferred

12. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred Unknown
over processes and tools Not preferred Neutral
Working software preferred Good
over comprehensive documentation Not preferred Good
Customer collaboration preferred Good
over contract negotiation Not preferred
Responding to change preferred
over following a plan Not preferred

13. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred Unknown
over processes and tools Not preferred Neutral
Working software preferred Good
over comprehensive documentation Not preferred Good
Customer collaboration preferred Good
over contract negotiation Not preferred Neutral
Responding to change preferred
over following a plan Not preferred

14. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred Unknown
over processes and tools Not preferred Neutral
Working software preferred Good
over comprehensive documentation Not preferred Good
Customer collaboration preferred Good
over contract negotiation Not preferred Neutral
Responding to change preferred Good
over following a plan Not preferred

15. BUNG it
Phrases in the core values Preference BUNG
Individuals and interactions preferred Unknown
over processes and tools Not preferred Neutral
Working software preferred Good
over comprehensive documentation Not preferred Good
Customer collaboration preferred Good
over contract negotiation Not preferred Neutral
Responding to change preferred Good
over following a plan Not preferred Good

16. Observations So Far
• 5 out of 8 are Good
• 2 out of 8 are Neutral
• 1 is Unknown
• NO Bad!
• It depends on how the phrases get used in what context.

17. Hunting for the Unspoken Words
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
Unspoken Words:
• Not treating customer with highest priority
• Software release delayed
• Few deliveries
• Buggy software

18. Hunting the Unspoken Words
2. Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive
advantage.
Unspoken Words:
• Reject or can’t handle requirement changes, especially late in
development

19. Hunting the Unspoken Words
3. Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
Unspoken Words:
• Delivering non-working or partially working software

20. Hunting the Unspoken Words
4. Business people and developers must work together daily
throughout the project.
Unspoken Words:
• Business people and developers are disconnected most of the
time

21. Hunting the Unspoken Words
5. Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the
job done.
Unspoken Words:
• Projects are built or led by unmotivated individuals
• Needed resources (environment, support…) are not provided
• Not trusting the developers to get the job done

22. Hunting the Unspoken Words
6. The most efficient and effective method of conveying
information to and within a development team is face-to-face
conversation.
Unspoken Words:
• Using inefficient and ineffective ways in conveying information,
like email, IM, wiki, paper documents… but not face-to-face.

23. Hunting the Unspoken Words
7. Working software is the primary measure of progress
Unspoken Words:
• Software progress is measured by many different ways.
Working software is only one of them for measuring progress
and not the primary one.

24. Hunting the Unspoken Words
8. Agile processes promote sustainable development.The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
Unspoken Words:
• Current development processes are not sustainable.
• The sponsors, developers and users cannot maintain a constant
pace of development.

25. Hunting the Unspoken Words
9. Continuous attention to technical excellence and good design
enhances agility.
Unspoken Words:
• technical excellence and good design do not always have
attentions.

26. Hunting the Unspoken Words
10. The best architectures, requirements, and designs emerge from
self-organizing teams.
Unspoken Words:
• Architectures, requirements and designs come from outside of
the team usually are not the best.

27. Hunting the Unspoken Words
11. Simplicity -- the art of maximizing the amount of work not done -
- is essential.
Unspoken Words:
• Complexity is favored, intentionally or unintentionally.

28. Hunting the Unspoken Words
12. At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
Unspoken Words:
• Teams seldom reflect on how to become more effective, then
tunes and adjusts for the best.

29. 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. 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.
Principles
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.
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.

30. Unspoken Words on
Software Development Issues
• Very often, software releases are late.
• Very often, software releases are few.
• Very often, software releases are very buggy (low quality)
• Very often, customers changed requirements along the development
cycle, especially in late stage. Development teams are not prepared
to handle the changes in any efficient and effective way.
• Very often, software development is unpredictable and
unsustainable

31. Are the 12 Principles specific for
Software Development?
• Only 3 of them mention “Software”
• Replacing “Software” with “Product”, the 3 principles can still make
sense.
• The other 9 principles are very generic.

32. Questions
• How can 12 principles lead to solutions for
the software development issues?
• Can they?

33. Q & A