previous |
start |
next
Extreme Programming
Development methodology that strives for simplicity by removing
formal structure and focusing on best practices
- Realistic planning
- Customers make business decisions
- Programmers make technical decisions
- Small releases
-
- Release a useful system quickly
- Release updates on a short cycle
- Metaphor
-
- a shared story to explain the system
- Simplicity
-
- Design as simply as possible instead of preparing for future
complexities
- Testing
-
- Programmers and customers write test cases
- Test continuously
- Refactoring
-
- Restructure the system continuously to improve code and
eliminate duplication
- Pair programming
-
- Two programmers write code on the same computer
- Collective ownership
-
- All programmers change all code as needed
- Continuous integration
-
- Build the entire system and test it whenever a task is
complete
- 40-hour week
-
- Don't cover up unrealistic schedules with heroic effort
- On-site customer
-
- A customer is accessible to the programming team at all
times
- Coding standards
-
- Follow standards that emphasize self-documenting code
previous |
start |
next