Extreme Programming Pocket Guide

Ken Ford was a telecommunications engineer with BT for 29 years before taking early retirement in 1992 to take up writing and military book selling. He is an expert on the Second World War and the author of eight books on the NW Europe campaigns on 1944-45. He is the author of Battle Axe Division for Sutton (2003) and lives near Southampton.

• Foreword Preface Part I: Why XP? Who Cares About Process, Anyway? The XP Equation XP Values Communication Feedback Simplicity Courage Assuming Sufficiency Sufficient Time Sufficient Resources Constant Cost of Change Developer Effectiveness Freedom to Experiment Part II: Extreme Programming Practices 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 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 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 Part III: XP Events Iteration Planning Stories and Tasks Estimates and Schedules The First Iteration The Iteration Releasing Part IV: Extreme Programming Artifacts Story Cards Task Cards The Bullpen Part V: Roles in Extreme Programming The Customer Customer Rights Customer Responsibilities The Developer Developer Rights Developer Responsibilities Supplementary Roles The Tracker The Coach Part VI: Coding, XP Style Do the Simplest Thing That Could Possibly Work You Aren't Gonna Need It Once and Only Once Part VII: Adopting XP Before You Start Eliminating Fear and Working Together Starting Feedback Including Managers and Customers Now That You're Extreme Part VIII:Further Resources XP Resources Index

Select Guide Rating