Extreme Programming in Perl

by Thamarai Selvi

Contents

1The Problem
11.1Some Statistics . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2Risk Averse Methodologies. . . . . . . . . . . . . . . . . . .
21.3Fostering Failure . . . . . . . . . . . . . . . . . . . . . . . . .
31.4Get Me a Rock . . . . . . . . . . . . . . . . . . . . . . . . . .
41.5Requirements Risk . . . . . . . . . . . . . . . . . . . . . . . .
51.6Let’s Rock And Roll . . . . . . . . . . . . . . . . . . . . . . .
6
2Extreme Programming
72.1
Core Values . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
2.2
Communication . . . . . . . . . . . . . . . . . . . . . . . . . .
9
2.3
Simplicity . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
2.4
Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11
2.5
Courage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
2.6
The Practices . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
2.7
Adopting XP . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
3Perl
17
3.1
Core Values . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
3.2
Customer-Orientation . . . . . . . . . . . . . . . . . . . . . .
18
3.3
Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
3.4
CPAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
3.5
Organizing Your Workshop . . . . . . . . . . . . . . . . . . .
19

4Release Planning21
Planning Game22
Roles22
Stories23
iiiOn-site Customer23
Story Cards24
Dead Wood26
Estimation28
Easing Estimation28
Spike Solutions29
Prioritization30
All the Facts31
Small Releases31
5Iteration Planning33
Tasks33
The Meeting34
Get Me a Bucket35
Velocity35
Watch Your Speed36
Customer Priorities36
Taking Care of Business37
The Beat Goes on37
6Pair Programming39
Quality39
How It Works40
Ease on down the Road41
Rest & Relaxation41
People Problems41
Different Strokes43
Yea, Whatever44
Gumption Traps44
Reducing Risk Through Knowledge Transfer45
7Tracking47
Iteration Tracking48
Don’t Slip the Date48
Adding Tasks49
The Tracker49
Release Tracking50
What Goes Wrong?51
Fixing Troubled Projects54
Meetings55
Show Your Stuff55
Sign Off56
Here and Now56
8Acceptance Testing57
Acceptance Tests57
Automation58
58section.8.3
Group Multiple Paths60
Without Deviation, Testing Is Incomplete61
Subject Matter Oriented Programming63
Data-Driven Testing64
Empower The Customer to Test66
9Coding Style67
There’s More Than One Way To Do It68
Give Me Consistency or Give Me Death68
Team Colors69
An Example70
You Say, “if else”, And I Say, “?:”72
Once And Only Once73
Refactored Example73
Change Log75
Refactoring78
Input Validation78
You’d Rather Die79
10Logistics81
11Test-Driven Design83
Unit Tests84
Test First, By Intention84
Exponential Moving Average86
Test Things That Might Break86
Satisfy The Test, Don’t Trick It87
Test Base Cases First88
Choose Self-Evident Data89
Use The Algorithm, Luke!90
Fail Fast91
Deviance Testing92
Only Test The New API93
Solid Foundation94
12Continuous Design95
Refactoring96
Simple Moving Average97
SMA Unit Test97
SMA Implementation98
Move Common Features to a Base Class100
Refactor the Unit Tests102
Fixing a Defect103
Global Refactoring105
Continuous Rennovation in the Real World108
Simplify Accessors109
Change Happens110
13Unit Testing111
Testing Isn’t Hard111

Make Assumptions112
Test Data Dependent Algorithms113
Validate Basic Assumptions First114
Validate
Perturb One Parameter per Deviance Case118
Relate Results When You Need To119
Order Dependencies to Minimize Test Length120
Consistent APIs Ease Testing121
Inject Failures122
Mock Objects123
Does It Work?125
14Refactor

343 pages, Kindle Edition

Published December 29, 2020