This IS Agile Development
2 j'aime646 vues
Le document aborde le développement logiciel agile, mentionnant des ressources et des principes associés. Il cite notamment le travail de Dr. Winston W. Royce sur la gestion du développement de systèmes logiciels. Le contenu semble encourager la collaboration interfonctionnelle et le travail d'équipe.
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. • • • • •
Notes de l'éditeur
- #2: Working Software ASAP, Cross-Functional Teams, Emergence
- #9: Note this is NOT the same as SPEED
- #10: Note that the definition here aligns with the dictionary definition of Agile, and is NOT about SPEED
- #13: 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.
- #14: 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
- #16: 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.
- #17: You know, like what ‘Team’ is supposed to mean.
- #19: 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.
- #20: Where ACTIVITY formerly meant SEQUENTIAL STEP
- #27: 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