This post is part of a series, Debugging Extreme Programming - Agile not Fragile looking at all of the XP practices. Simple Design Goal: Build what’s needed now, business needs something to deploy or to sell as soon as possible; don’t try to predict the future, it’s unknown; tomorrow you’ll know better what’s needed; don’t complicate preemptively;
Debugging Extreme Programming - Simple Design
Related with "Debugging Extreme Programming - Simple Design"
Debugging Extreme Programming - Refactoring
This post is part of a series, Debugging Extreme Programming - Agile not Fragile looking at all of the XP practices. Refactoring Goal: Continuous improvement and re-design of source code via safe Debugging Extreme Programming - Refactoring[...]
Debugging Extreme Programming - Pair Programming
This post is part of a series, Debugging Extreme Programming - Agile not Fragile looking at all of the XP practices. Pair Programming Goal: Share knowledge and review code continuously. Supported Debugging Extreme Programming - Pair Programming[...]
Debugging Extreme Programming - Testing
This post is part of a series, Debugging Extreme Programming - Agile not Fragile looking at all of … provide concrete realistic use cases for API design. Testing in agile means developer-authored Debugging Extreme Programming - Testing[...]
Debugging Extreme Programming - Metaphor
This post is part of a series, Debugging Extreme Programming - Agile not Fragile looking at all of … and riskiest part of XP, and one which few other agile metho Debugging Extreme Programming - Metaphor[...]
Debugging Extreme Programming - Planning Game
This post is part of a series, Debugging Extreme Programming - Agile not Fragile looking at all of the XP practices. Planning Game Goal: Enable the customer to describe and prioritise the desired Debugging Extreme Programming - Planning Game[...]
