#xp
12 pages tagged.
Concepts
Continuous Integration
Everyone pushes to the mainline at least daily, and every push is verified by an automated build. Running a CI server is not the same thing.
Energized Work
Work only as many hours as you can be productive, and only as many as you can sustain. The renamed 40-Hour Week, improved by the rename.
Extreme Programming
A discipline of software development organized as values, principles, and practices. The second edition rebuilt the practice list so a team can adopt one piece at a time.
Incremental Design
Invest in design every day, in the light of what the system now does. Viable only because three other practices flatten the cost of changing your mind.
Pair Programming
Two people, one running system. The XP practice with the most empirical study behind it, and the results are more qualified than either camp quotes.
Refactoring
Changing a program's structure without changing its observable behavior. Not a named practice in XP's second edition, and load-bearing for two that are.
Slack
Put work in every plan that can be dropped without breaking the promise. The cheapest way to make a schedule believable.
Stories
Units of customer-visible functionality, planned as a promise to talk rather than a written specification. Card, Conversation, Confirmation.
Ten-Minute Build
Build the whole system and run all the tests in ten minutes. A budget, deliberately arbitrary, that makes two other practices affordable.
Test-First Programming
Write the failing test before the code that satisfies it. A design technique that happens to leave a regression suite behind.
Weekly and Quarterly Cycle
Two nested planning rhythms. The week plans the work, the quarter plans the theme, and the point of both is the length of the feedback loop.
XP Values
Communication, Simplicity, Feedback, Courage, Respect. The criteria that decide which practice to reach for when no practice fits.