Extreme Programming
Selected quotes from
Ron Jeffries et al.
Extreme Programming Installed.
Addison-Wesley, 2001
12 Key Practices in Extreme Programming
- On-Site Customer
- Small Releases
- Planning (via stories; customer defines releases ...)
- Metaphor (code expresses intention first, then the algorithm)
- Simple(st) design
(only solve problems for today's release, no duplicate code)
- Pair programming
- Collective Code Ownership
- Continuous Integration (multiple times per day)
- Coding Standard
- Testing (unit tests must always score 100%)
- Refactoring (only when needed)
- Forty-Hour Week (no prolonged overwork)
XP Tracking and Reporting
XP prescribes tracking and reporting approaches that are easy and public.
- Resources
- Keep track of key resources: planned versus actual;
- number of developers
- number of customers assigned to the project
- number of testers
- number of computers in development, test, production
- Scope
- Keep track of the number of stories over time:
- how many exist
- how many are done
- how many more are expected
- Quality
- Use a standard acceptance testing graph showing
- number of [acceptance] tests
- number of succeeding over time
- Time
- Track the results of each release plan.
- Graph schedule versus time.
- Discuss dropped or added functionality and its impact on time.
Feedback about this page is welcome