Extreme Programming Applied: Playing to Win

Things To Pay Attention To......Page 1
Forward......Page 5
Preface......Page 6
The Sad Sponsor......Page 7
The Smelly Software......Page 8
Remembering the “Soft” in Software......Page 9
Building Software Like Bridges:  The Dreaded “Cost of Change” Curve......Page 10
XP Flattens the Curve......Page 11
Wagons Ho!......Page 12
Section One: Getting Started......Page 13
Dealing With Fear......Page 14
The Ledge......Page 16
Bring a Friend......Page 18
Just Do It......Page 19
Find a Target......Page 20
Assemble the Right Tools......Page 21
Driving Spikes......Page 22
It’s All Right To Feel Awkward......Page 25
Where Resistance Comes From......Page 26
Will It Help Us Win?......Page 27
What Not To Do......Page 28
The Manager Perspective on Winning......Page 29
XP Is Too New To Trust......Page 30
Pair Programming Is Too Expensive......Page 31
I Can’t Afford A Full-Time On-Site Customer......Page 32
XP Is Too Informal......Page 33
Be Wary of “XP-Lite”......Page 34
The Developer Perspective On Winning......Page 36
XP Is Too Simplistic......Page 37
I Won’t Like Pair Programming......Page 38
XP Is Weird......Page 39
XP Doesn’t Give Us Enough Information......Page 41
Honesty......Page 46
Humility......Page 47
Sweet Freedom......Page 48
Section Two: First Things First......Page 54
The Bare Essentials......Page 55
The XP Essentials......Page 57
Think Simply......Page 60
Get Feedback Early and Often......Page 61
Be Brave......Page 62
Handling XP Exceptions Like Code Exceptions......Page 63
The OddNumberOfDevelopers Exception......Page 64
The ManagementSetsUnrealisticSchedules Exception......Page 66
The MyManagementWontLetMePair Exception......Page 67
The CostOfTeaInChinaDoubles Exception......Page 68
Communication......Page 69
Pair Programming......Page 70
Stand-Up Meetings......Page 71
Planning......Page 73
Atmosphere And Environment......Page 74
If I Could Talk to The Customers/Developers......Page 77
Learning Roles......Page 78
An Introduction To Reality......Page 79
I'd Really Like to Help......Page 80
Welcome Back to Reality......Page 83
It's a Bigger Project Than I Thought, But We Can Get Something Out Quicker Than I Thought......Page 85
The Xtreme Hour......Page 87
Steering......Page 88
Embracing Change Fearlessly......Page 89
How To Plan......Page 91
What Plans Are......Page 95
How To Start Planning......Page 96
The Art of Estimation......Page 97
What’s Velocity?......Page 98
Estimation Rules?......Page 100
Thinking Short......Page 101
Staying Focused......Page 102
Staying Grounded In Reality......Page 103
How To Start Thinking Short......Page 104
What If Business & Development Have Different Ideas of "Short"......Page 105
Write the Tests, Run the Tests......Page 107
Confidence......Page 108
Tests As Documentation......Page 109
How To Write Tests First......Page 110
How To Start Writing Tests First......Page 112
Testing User Interfaces......Page 113
Functional Tests......Page 114
Code Quality......Page 116
The Need for Speed......Page 117
Reducing Risk......Page 118
How To Pair Program......Page 119
Taking It To The Next Level......Page 121
The Inevitable Objections......Page 122
When Not To Pair......Page 124
Personal Space......Page 125
How To Start Pair Programming......Page 126
Leftovers......Page 127
Being Ready for Change......Page 128
Making Change Possible......Page 129
How To Refactor......Page 130
When To Refactor......Page 131
When To Stop Refactoring......Page 132
How To Start Refactoring......Page 133
Why People Don’t Refactor......Page 134
Maintaining Speed......Page 135
Reducing Risk......Page 136
How To Integrate Continuously......Page 137
Techniques to Make It Easier......Page 138
Section Three: The Rest of the Story......Page 139
Defining Simplicity......Page 140
Why People Don’t Keep It Simple......Page 141
How To Start Doing Simple Design......Page 142
Why It’s Not Essential in the Beginning......Page 143
The Essential Design Tool......Page 144
What Collective Ownership Means......Page 145
Why Have Collective Code Ownership?......Page 146
How To Start Having Collective Code Ownership......Page 147
Why It’s Not Essential in the Beginning......Page 148
Why Have An On-Site Customer?......Page 149
How To Start Having An On-Site Customer......Page 150
Why An On-Site Customer Isn’t Essential......Page 151
Why Have Coding Standards?......Page 152
Why Coding Standards Aren’t Essential......Page 153
System Metaphor......Page 154
Why People Work Too Much......Page 157
What’s Wrong With Burning the Oil?......Page 158
How To Start Working “Normal” Hours......Page 159
Why A 40-Hour Week Isn’t Essential......Page 160
Other XP Roles......Page 161
Player/Coach......Page 162
AutoTracker......Page 165
Section Four: Uncharted Territory......Page 175
Why People Don’t Buy It......Page 176
The Results......Page 177
Proving It......Page 178
Developing A Track Record......Page 180
Easier Said Than Done......Page 181
When To Scale......Page 183
How To Scale......Page 184
Suggestions for Research......Page 186
Asdf......Page 187
Where To Next?......Page 188
Section Five: Reference......Page 190