NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
The Spirit of XP (Score:2)
You should test constantly and integrate continuously, whether you are using JUnit and Ant, prove and Make, Aegis, or scratch paper and a fleet of hamsters.
You should be in constant contact with your customer, whether he is on site with the developers, teleconferences twice daily, video chats on demand, or retains a psychic to transfer thoughts through subspace telepathy.
If you read between the lines in the XP literature, it's not about us
Re:The Spirit of XP (Score:2)
Microsoft Project style tools are precisely what I am trying to avoid. However, there are still benefits to a good XP project management tool.
The primary benefit of XP is how it lowers the cost of information. A good tool can lower those costs even further. A bad tool, however, can raise those costs significantly and hurt XP style practices, hence my desire for find a good tool.
Reply to This
Parent
Re:The Spirit of XP (Score:2)
But moving away from 3x5 cards for these use cases seems rather, um, heavyweight. Reading what problems you want to solve, the one word that comes to mind is photocopier.
If you've got a good 3x5 card process at the moment, making photocopies of what you're doing this week takes about a minute, and has very little impact on your workflow. Added cost to the team, maybe $5/year. Added cost to adopt some software automation? Well, depends on how long it takes you to retool your workflow.
If,