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?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
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.