Please enable JavaScript.
Coggle requires JavaScript to display documents.
Extreme programming (XP) (values (simplicity, communication, feeeback,…
Extreme programming (XP)
values
simplicity
communication
feeeback
courage
respect
Practices
Fine-scale feedback
test driven development
planning game
Release/iteration planning
phases
exploration
commitment
steering
pair programming
Whole team
continuous process
refactoring
continuous integration
small releases
Shared understanding
Collective code ownership
Coding standards
metaphors
simple design
Programmer welphare
sustainable phase
Rules
planning
user stories are written
Release planning
Make frequent small releases
Project divided into iterations
iteration planning starts each iteration
managing
Give the team an open workspace
Set a sustainable pase
A Stand-up meeting starts each day
The project velocity is measured
Move people around
Fix XP when it breaks
designing
simplicity
choose a system metaphor
use CRC cards for design sessions
create spike solutions to reduce risk
no functionality is added early
coding
customer is always available
code written to agreed to standards
code the unit test first
production code is pair programmed
only one pair integrates code at a time
integration often
use a dedicated integration machine
use collective ownership
testing
All code must have unit tests
All code must pass all unit tests
when a bug is found tests are created
acceptance tests are run often and the score is published