Revision as of 13:34, 11 October 2014 edit Mmeijeri (talk \| contribs) Extended confirmed users 5,533 edits →Steering phase: not during planning ← Previous edit		Revision as of 13:37, 11 October 2014 edit undo Mmeijeri (talk \| contribs) Extended confirmed users 5,533 edits →Steering phase: move decription to TDD, which is a cycle, with each steps taking minutes at most, preferably much less Next edit →
Line 110: * Find a Partner: The programmer will implement this task along with another programmer. This is further discussed in the practice [[Pair Programming]]. * Design the task: If needed, the programmers will design the functionality of the task. * Implement the task using Test Driven Programming (see below) * Write [[unit test]]: Before the programmers start coding the functionality they first write automated tests. This is further discussed in the practice Unit Testing. * Fail test: The code must fail the test. * Write code: The programmers write the minimal amount of code to pass the test. * Run test: The unit tests are run to test the code. * [[Code refactoring\|Refactor]]: Remove any [[code smells]] from the code. * Run Functional test: Functional tests (based on the requirements in the associated user story and task card) are run.

Extreme programming practices: Difference between revisions