Practices: Pair Programming, YAGNI, and OthersThis is a featured page

As you move to Agile software development, you quickly discover that you're not in Kansas any more. In the interest of the values of Agile you want to move away from massive documentation, and instead use practices such as pair programming; instead of heavyweight up-front design, you move into TDD. These are just two examples.
As you move into the XP practices such as pair programming and TDD, you find that they have important traps and pitfalls in the long term. Experience has shown that pair programming doesn't always work, and that you need some lightweight documentation and up-front design. Again, these are specific examples, part of a broader perspective we will cover here.


jcoplien
jcoplien
Latest page update: made by jcoplien , Jul 30 2007, 9:50 AM EDT (about this update About This Update jcoplien Edited by jcoplien

114 words added

view changes

- complete history)
Keyword tags: None
More Info: links to this page
There are no threads for this page.  Be the first to start a new thread.