This IS Agile Development
•
2 gostaram•644 visualizações
As presented at Chicago Code Camp 2013.
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (20)
This IS Agile Development
- 2. • • • • • •
- 3. • • • • • •
- 4. • • • • • •
- 5. • • • •
- 6. • • • •
- 11. • • • • • • • •
- 12. • • • •
- 13. © 1993 - 2013 Scrum.org, All Rights Reserved
- 14. • •
- 15. • •
- 16. • • • • •
- 17. • • • • • • •
- 18. • • •
- 19. • • • •
- 21. • • • Requirements Design Code Test © 1993 - 2013 Scrum.org, All Rights Reserved
- 22. • • • •
- 25. • • • • • •
- 26. • • • • •
- 27. •
- 30. Managing the Development of Large Software Systems – Dr. Winston W. Royce
- 31. Managing the Development of Large Software Systems – Dr. Winston W. Royce
- 32. Managing the Development of Large Software Systems – Dr. Winston W. Royce
- 35. • • •
- 36. • • • •
- 37. • • • •
- 38. Complete Cross-Functionality All Generalists Pure Teamwork Condescending Jerks
- 39. • •
- 40. • •
- 41. • • • • •
Notas do Editor
- Working Software ASAP, Cross-Functional Teams, Emergence
- Note this is NOT the same as SPEED
- Note that the definition here aligns with the dictionary definition of Agile, and is NOT about SPEED
- We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planThat is, while there is value in the items on the right, we value the items on the left more.
- Point out that the vertical lines on the right-hand (slices) diagram are never straightFor example, Sprint 2 may require the team to go back and refactor code/decisions made in Sprint 1Also, it takes a cross-functional team to do this effectivelyDoes it take smart people to do emergent architecture? No, it takes smart people to develop software
- We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planThat is, while there is value in the items on the right, we value the items on the left more.
- You know, like what ‘Team’ is supposed to mean.
- We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planThat is, while there is value in the items on the right, we value the items on the left more.
- Where ACTIVITY formerly meant SEQUENTIAL STEP
- Emergent Design/Architecture: Following conventions of the original application, which does have some basic layering and use of good, known patterns (MVC, Repositories), negotiating for a “harvest, don’t grow” approach with CC ServiceTesting Pyramid – what’s interesting about the testing pyramid is that it’s not just about testing – yes, it shows that automation has a lot more ROI as you move towards the base, but it also talks about the amount or focus of tests, in a way that CANNOT be achieved without good application design