|
|
This is only a preview of the paper
Click here to register and get the full text.
Existing members click here to login
|
|
|
This weekend, it finally clicked for me what XP really is, and why I believe in it so strongly, even though I've never used all the practices at once on any project. Years ago, back around 1988, a friend pointed out to me that it makes sense to develop a very simple, stripped-down version of a program first, and then add to it. That immediately resonated with me based on my experiences up to that time. From then on, I have consciously used "simplicity" as my focus and as a measure of quality. Most of the successful projects I've been involved with over the years have taken that basic approach: Get something simple working, and then add to it. Projects that have taken the BDUF (Big Design Up Front) approach have generally failed--sometimes taking the company down with them; other times just not living up to potential. Much of my success at my current (non-XP) company has been due to my focus on doing the simplest thing possbible, and avoiding designing for a future that might never arrive.
Approximate Word count = 597
Approximate Pages = 2.4
(250 words per page double spaced)
|
|
|
|
|
|