Extreme Programming
Rules and Practices - Extreme Programming (XP) is an approach to software development that is successful because it stresses customer satisfaction
Extreme Programming Planning
- Write user stories
- The schedule is created from release planning
- Frequent small releases
- Measure project velocity
- Divide the project into iterations
- Iteration planning starts each iteration
- Move people around
- Stand-up meetings start every day
- Fix extreme programming when it breaks
Firelighter
Extreme Programming Designing
- Simple design
- A system metaphor is selected
- CRC cards are used for design sessions
- Create spike solutions to reduce risk
- No early functionality added
- Refactor wherever and whenever possible
Strategy Implementation
Extreme Programming Coding
- Ensure that the customer is always available
- Code is written to agreed standards
- The unit test is coded first
- All production code is programmed by pairs
- And only one pair integrates code at a time
- Often integrate
- Collective code ownership is used
- Optimization is left until last
- No overtime allowed
Web Design Agency
Extreme Programming Testing
- All code has unit tests
- All code must pass all unit tests before it is released
- When bugs are found tests are created
- Acceptance tests are run often and the scores are published
View Source
If customers need a new system on a specific date there is a high risk. If the system is a new challenge for the software group there is an even higher risk. Extreme Programming was established to deal with the problems of risk within projects.
ASD