Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Inspired by this question - can an agile shop really score 12 on the Joel Test: Can you come up with explanations or examples where a software development organization satisfies technically all 12 points of the Joel Test, but fails to live up to the agile or lean principles?

share|improve this question
up vote 4 down vote accepted

Having an up to date spec is possible with a big design upfront process, one with lots of text and diagrams that are written as a contract. That's hardly agile.

I am tempted to say a quiet team room is also not agile, agile is all about communication, team work, pair programming, collaborating, shared goals. A quiet room might actually mean it's not really a team just a group of peeps in the same room.

A bug database can be considered unnecessary inventory in lean terms.. either fix them or don't.. Piling them up is waste. Having this many bugs that one needs to track them may be indication of a broken process, it's fighting symptoms not the root problem.

share|improve this answer
Automated tests are a spec, the very best kind of spec. – kevin cline Mar 17 '11 at 4:01
A set of bug cards on the wall is a "bug database" – Ian Jul 18 '11 at 11:06
"A quiet room might actually mean it's not really a team just a group of peeps in the same room.": Not necessarily. A well-functioning team will reduce communication to the essential and concentrate on getting work done. – Giorgio Dec 22 '14 at 19:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.