1. How Strong is Your Agile Foundation
How Strong is Your Agile Foundation? Steve Toalson November 7, 2017 LeanAgileKC 2017

3. Why are these items important?

4. Instructions

5. 1 The Customer is always right.
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 1

6. 2
1, ,
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

7. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

8. Business people and developers must work TWOgether daily throughout the project.
Business people and developers must work together daily throughout the project. 4
2+2=

9. Build projects around motivated individuals
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 5

10. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

11. Progress 
Working software is the primary measure of progress.

12. Agile processes promote sustainable development
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

13. Continuous attention to technical excellence and good design enhances agility.K

14. 1
Simplicity--the art of maximizing the amount of work not done--is essential.
Simplicity

15. The best architectures, requirements, and designs emerge from self-organizing teams.

16. 12
12 | 21
Reflection
Come on People!
It’s the thing we do at the end….
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

17. Test #1

18. Business people and developers must work together daily throughout the project.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Simplicity--the art of maximizing the amount of work not done--is essential.

19. Build projects around motivated individuals
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Working software is the primary measure of progress.
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
The best architectures, requirements, and designs emerge from self-organizing teams.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

20. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Continuous attention to technical excellence and good design enhances agility.
The End.

21. Test #2

22. The Customer is always right.1
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

23. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

24. 2
1, ,
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

25. Continuous attention to technical excellence and good design enhances agility.

26. Build projects around motivated individuals
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 5

27. Progress 
Working software is the primary measure of progress.

28. 1
Simplicity--the art of maximizing the amount of work not done--is essential.
Simplicity

29. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

30. Come on People!
It’s the thing we do at the end….

31. Business people and developers must work TWOgether daily throughout the project.4
2+2=

32. The best architectures, requirements, and designs emerge from self-organizing teams.

33. Agile processes promote sustainable development
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

34. So….???? How’d we do?

36. Hey Alistair! Being a firm believer in the Agile Manifesto along with the 12 Principles, I made a commitment to memorize them so as to share them back with team mates at the drop of a hat. In fact, I have several mnemonics to assist with recalling them. My question or request from you: I’d like to understand a bit more about HOW you all came up with the 12 principles. Were there 16 at first? 22? or maybe only 8? What was the process involved in getting to the 12 principles? Thank you so much for what you have contributed to Agile. -by Steve Toalson on 8/14/2017 at 11:39 AM That I don’t recall. I know we said, “a strong name and 4 values is pretty good, but what could lie underneath that?” and someone proposed principles. We were running out of time and energy and agreement, so it wasn’t a tight process. I don’t recall a discussion of how many there should be, but clearly is an upper limit. Someone just proposed one and we wandered around having discussions. There was not complete agreement, people started leaving, and we tried unsuccessfully to close it out by , but that didn’t work, so we just published the closest approximation to what we had at the time. Ergo, not a tightly revised set of words, but best-3nd-round writing. Cheers

37. Alistair Cockburn - That I don’t recall
Alistair Cockburn - That I don’t recall. I know we said, “a strong name and 4 values is pretty good, but what could lie underneath that?” and someone proposed principles. We were running out of time and energy and agreement, so it wasn’t a tight process. I don’t recall a discussion of how many there should be, but clearly is an upper limit. Someone just proposed one and we wandered around having discussions. There was not complete agreement, people started leaving, and we tried unsuccessfully to close it out by , but that didn’t work, so we just published the closest approximation to what we had at the time. Ergo, not a tightly revised set of words, but best-3nd-round writing. Cheers
Robert Martin (Uncle Bob) - I don’t remember a lot about the process.  There was a lot of exchange going back and forth.  It seems to me that Ron was the most energetic and prolific writer when it came to the principles. I don’t remember how we got to consensus on the principles; but I _do_ remember that a quorum (by some definition of that word) did.
Ron Jefferies – I have no specific recall either, it was definitely done via . I probably made a lot of noise but have no reason to believe that I actually contributed anything of value. :)