12. Por que stand ups? Por que Programação em pares? Por que iterações?
13. Por que stand ups? Por que Programação em pares? Por que iterações? Por que Testes/TDD?
14. Por quê? Stand ups Iterações TDD Pares Testes Integração contínua Retrospectivas Card Wall Planning Poker Show cases Por quê? Por quê? Por quê? Por quê? Por quê? Por quê?
16. Lição #1 “ Boards don't hit back.” “ Life itself is your teacher, and you are in a state of constant learning.”
17. Lição #1 “ Boards don't hit back.” “ Life itself is your teacher, and you are in a state of constant learning.” Pessoas
18. Pessoas: Individuals and interactions over processes and tools Lição #1 “ Boards don't hit back.” “ Life itself is your teacher, and you are in a state of constant learning.”
19. Lição #2 “ What IS is more important than WHAT SHOULD BE.”
20. Lição #2 “ What IS is more important than WHAT SHOULD BE.” Qualidade interna
21. Lição #2 “ What IS is more important than WHAT SHOULD BE.” Qualidade externa
22. Qualidade do produto: Working software over comprehensive documentation Lição #2 “ What IS is more important than WHAT SHOULD BE.”
23. Lição #3 “ A goal is not always meant to be reached, it often serves simply as something to aim at.”
24. Lição #3 “ A goal is not always meant to be reached, it often serves simply as something to aim at.” Feedback
25. Ciclo de feedback menor : Responding to change over following a plan Lição #3 “ A goal is not always meant to be reached, it often serves simply as something to aim at.”
26. Lição #4 “ Forget about winning and losing; forget about pride and pain”
27. Lição #4 “ Forget about winning and losing; forget about pride and pain” Colaboração
28. Colaboração [com o cliente]: Customer collaboration over contract negotiation Lição #4 “ Forget about winning and losing; forget about pride and pain”