Extreme Programming Pocket Guide: Team-Based Software Development

Extreme Programming Pocket Guide
Foreword
Preface
	Overview of This Book
	Typographic Conventions
	Comments and Questions
	Acknowledgments
I. Why XP?
	1. Who Cares About Process, Anyway?
	2. The XP Equation
	3. XP Values
		Communication
		Feedback
		Simplicity
		Courage
	4. Assuming Sufficiency
		Sufficient Time
		Sufficient Resources
		Constant Cost of Change
		Developer Effectiveness
		Freedom to Experiment
II. Extreme Programming Practices
	5. Coding Practices
		Coding Practice 1: Code and Design Simply
		Coding Practice 2: Refactor Mercilessly
		Coding Practice 3: Develop Coding Standards
		Coding Practice 4: Develop a Common Vocabulary
	6. Developer Practices
		Developer Practice 1: Adopt Test-Driven Development
		Developer Practice 2: Practice Pair Programming
		Developer Practice 3: Adopt Collective Code Ownership
		Developer Practice 4: Integrate Continually
	7. Business Practices
		Business Practice 1: Add a Customer to the Team
		Business Practice 2: Play the Planning Game
		Business Practice 3: Release Regularly
		Business Practice 4: Work at a Sustainable Pace
III. XP Events
	8. Iteration Planning
		Stories and Tasks
		Estimates and Schedules
		The First Iteration
	9. The Iteration
	10. Releasing
IV. Extreme Programming Artifacts
	11. Story Cards
	12. Task Cards
	13. The Bullpen
V. Roles in Extreme Programming
	14. The Customer
		Customer Rights
		Customer Responsibilities
	15. The Developer
		Developer Rights
		Developer Responsibilities
	16. Supplementary Roles
		The Tracker
		The Coach
VI. Coding, XP Style
	17. Do the Simplest Thing That Could Possibly Work
	18. You Aren’t Gonna Need It
	19. Once and Only Once
VII. Adopting XP
	20. Before You Start
	21. Eliminating Fear and Working Together
	22. Starting Feedback
	23. Including Managers and Customers
	24. Now That You’re Extreme
VIII. Further Resources
	25. XP Resources
Index
Copyright