-The first statement is false. It is not true - -2
-that because of pair programming, we need twice as many - -3
-developers. In fact that there is some evidence that even - -4
-though in pair programming we have two developers working together, - -5
-that the overall efficiency of the programmers is not really - -6
-affected by use of this practice. In XP, code is - -7
-rarely changed after being written. This is also definitely false. - -8
-In fact in XP there is a lot of emphasis - -9
-on change on the fact that the code can be changed, - -10
-it can be resigned, because of the fact when we do - -11
-that, we have a set of these cases that we can - -12
-use to check right away that the code still works as - -13
-expected. So again in XP, it's all about steering rather than - -14
-just driving down one fixed direction. And therefore, the code can - -15
-be changed. So this statement is false. It is definitely true - -16
-that XP follows the test driven development paradigm. In XP we first - -17
-write tests, and then we write the code, which is - -18
-exactly what TDD is about. It is not true that - -19
-the customer does not need to provide requirements in XP. - -20
-The customer does provide requirements in the form of user - -21
-stories, and the user stories are the starting point of - -22
-the development process. Finally, XP is definitely an iterative software - -23
-development process. In fact, we saw that XP is based - -24
-on subsequent iterations of the same cycle, in which we - -25
-select from a set of story cards, or user - -26
-stories, the stories that we want to implement in the - -27
-next iteration. Based on that we develop task cards, - -28
-and then we use the task cards to write this - -29
-case and then to write code. And we continue - -30
-this cycle in an iterative way until we are done - -31
-with all the story cards, and all the user - -32
-stories, so definitely XP is an iterative software development process. -- cgit 1.4.1