Final answer:
The statement that is not true about pair programming in Agile is 'Pair programming slows down the development process.' In fact, it often results in better code quality and fewer errors through collaboration and knowledge sharing.
Step-by-step explanation:
The student asked which statement is not true about pair programming in Agile. To determine the correct answer, it's important to understand what pair programming involves and how it fits within the Agile methodology. Pair programming is a programming technique where two developers work together at one workstation. One, the driver, writes code while the other, the observer or navigator, reviews each line of code as it's typed in. The two programmers switch roles frequently.
The correct answer to the question is option C: Pair programming slows down the development process. This statement is not true about pair programming in Agile. While it might seem like having two developers working on the same task could slow down the process, the opposite is often true. Pair programming encourages collaboration and knowledge sharing (option B), which often leads to better code quality and fewer errors (option D). It's a practice that enhances learning amongst team members and can actually speed up the development process because of the reduced number of bugs and less time spent on code reviews.
Option A is correct, as it accurately describes the setup of pair programming. Option B is also correct because pair programming involves two individuals collaborating closely, which naturally promotes knowledge sharing. Option D is correct because having two sets of eyes on the code tends to reduce errors and improve its overall quality.