Extreme programming explained embrace change
"Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Boston :
Addison-Wesley
c2000.
|
| Edición: | 1st edition |
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627427406719 |
Tabla de Contenidos:
- Foreword
- Preface
- Chap. 1. Risk : the basic problem
- Chap. 2. A development episode
- Chap. 3. Economics of software development
- Chap. 4. Four variables
- Chap. 5. Cost of change
- Chap. 6. Learning the drive
- Chap. 7. Four values
- Chap. 8. Basic principles
- Chap. 9. Back to basics
- Chap. 10. Quick overview
- Chap. 11. How could this work?
- Chap. 12. Management strategy
- Chap. 13. Facilities strategy
- Chap. 14. Splitting business and technical responsibility
- Chap. 15. Planning strategy
- Chap. 16. Development strategy
- Chap. 17. Design strategy
- Chap. 18. Testing strategy
- Chap. 19. Adopting XP
- Chap. 20. Retrofitting XP
- Chap. 21. Lifecycle of an ideal XP project
- Chap. 22. Roles for people
- Chap. 23. 20-80 rule
- Chap. 24. What makes XP hard
- Chap. 25. When you shouldn't try XP
- Chap. 26. XP at work
- Chap. 27. Conclusion.
