« microformats | About microformats SOA Governance: When, Where, and How »

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


Related with "Debugging Extreme Programming - Testing"

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 - 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 - 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[...]


Debugging Extreme Programming - Collective Ownership

This post is part of a series, Debugging Extreme Programming - Agile not Fragile looking at all of the XP practices. Collective Ownership Goal: Everyone owns all the code, so everyone knows Debugging Extreme Programming - Collective Ownership[...]