To say that Agile development doesnt' include documentation, or that you can't do documentation in an agile development process is simply incorrect.
While Agile programmers certain like to avoid documentation (http://www.martinfowler.com/distributedComputing/ thud.html), if such documentation is a user requirement, than deliver it.
The key is helping the user understand what they are paying for. When the user begins to understand the cost of documentation, and 'documentation maintenance' when the code base is changing frequently, than a compromise can be reached. In cases, test cases are acceptable documentation. At other times a disciplined team can write javadocs/docbook/ every nth iteration that will satisfy the user.
Documentation is important to non-technical people. And to support people that have to diagnose production problems with cryptic error messages and no familiarity with the code base. Just keep in mind which documentation is valuable, who the audience is, and when the process is solidified enough that the documentation can be written.
I, too, sleep MORE when I'm on an exercise regime. Without exercise, I usually get 4 or 5 hours of sleep a night. I lay in bed for at least 6, but I spend an hour trying to "shut my mind off".
When I go to the gym in the morning, I'm dead tired at night. I don't have to worry that I'm too interested in something to go to bed. I rarely have trouble falling to sleep.
Frankly, I hate wasting away my time exercising and not having any time for hobbies.
The group of folks leading XP have changed the name - "Agile Software Development".
A good reference for the methodologies can be found at http://agileAlliance.org
Slashdot Mirror
Forget the lemon/ade jokes -
Wasted away again in Margaritaville...
To say that Agile development doesnt' include documentation, or that you can't do documentation in an agile development process is simply incorrect.
/ thud.html), if such documentation is a user requirement, than deliver it.
While Agile programmers certain like to avoid documentation (http://www.martinfowler.com/distributedComputing
The key is helping the user understand what they are paying for. When the user begins to understand the cost of documentation, and 'documentation maintenance' when the code base is changing frequently, than a compromise can be reached. In cases, test cases are acceptable documentation. At other times a disciplined team can write javadocs/docbook/ every nth iteration that will satisfy the user.
Documentation is important to non-technical people. And to support people that have to diagnose production problems with cryptic error messages and no familiarity with the code base. Just keep in mind which documentation is valuable, who the audience is, and when the process is solidified enough that the documentation can be written.
I, too, sleep MORE when I'm on an exercise regime. Without exercise, I usually get 4 or 5 hours of sleep a night. I lay in bed for at least 6, but I spend an hour trying to "shut my mind off".
When I go to the gym in the morning, I'm dead tired at night. I don't have to worry that I'm too interested in something to go to bed. I rarely have trouble falling to sleep.
Frankly, I hate wasting away my time exercising and not having any time for hobbies.
Oh - and I'm fat.
It's a sad reflection of American society when Buffy the Vampire Slayer is declared the best show on TV today...
The group of folks leading XP have changed the name - "Agile Software Development". A good reference for the methodologies can be found at http://agileAlliance.org
Sun has their own take on the settlement... http://www.sun.com/smi/Press/sunflash/2001-01/sunf lash.20010123.1.html