ReconcilingTheJoelTestWithXp

As far as I can see:

• Do you use source control? yes
• Can you make a build in one step? yes
• Do you make daily builds? yes and more
• Do you have a bug database? no
• Do you fix bugs before writing new code? yes
• Do you have an up-to-date schedule? yes
• Do you have a spec? yes (but card-sized)
• Do programmers have quiet working conditions? no
• Do you use the best tools money can buy? no
• Do you have testers? no dedicated human ones
• Do new candidates write code during their interview? yes
• Do you do hallway usability testing? no (Does this matter so much if you're not doing shrinkwrap?)

I always thought that was because the aim is to have [Wiki.ZeroDefects] or at least zero known defects? If you're working test first (or at least doing unit testing of the riskiest code) and integrating continuously with regular releases to actual users then you'll be finding your bugs a lot quicker. Then the addition of even more unit tests for those bugs means you don't need a fancy bug tracking system because your unit tests are doing the same job.

Of course on a large project what would be nice would be something that can track your bugs, link them to user stories and the associated unit test that automatically triggers the bug. Does anyone know if Jira from Atlassian Software can do this? --AdewaleOshineye

Do you use the best tools money can buy? Why no? We use the best tools we can find - even if they are free :-) I think the answer to this question is team specific rather than the same for all XP teams. IvanM and TungMac.

BTW, he says "you're wasting money by having $100/hour programmers do work that can be done by $30/hour testers" - how many programmers earn $100/hour in the UK? (that's far too little ;-)