\(
\def\WIPO{World Intellectual Property Organisation}
\)
Extreme programming eXplained : embrace change / Kent Beck.
1999
D 73 BEC.E
Available at WIPO Library
Formats
| Format | |
|---|---|
| BibTeX | |
| MARCXML | |
| TextMARC | |
| MARC | |
| DataCite | |
| DublinCore | |
| EndNote | |
| NLM | |
| RefWorks | |
| RIS |
Items
Details
Title
Extreme programming eXplained : embrace change / Kent Beck.
Description
xxi, 190 pages ; [28] cm.
ISBN
0201616416
9780201616415 alk. paper
9780201616415 alk. paper
Alternate Call Number
D 73 BEC.E
Summary
"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 cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned." "You may love XP or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software."--Jacket.
Bibliography, etc. Note
Includes bibliographical references and index.
Formatted Contents Note
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.
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.
Series
Series
Xp Series.
Published
Reading, MA : Addison-Wesley, 1999.
Language
English
Record Appears in
Added Corporate Author
Review
"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 cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned." "You may love XP or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software."--Jacket.