>I've been there
>
>>It's not my boss that's the problem - it's the environment as a whole.
>
>How exactly will outdated docs keep you safe in an audit?

My exact point. Management has a warm fuzzy feeling when they had auditors a document. If it is pointed out as outdated, it MUST be the developer's fault, even if the developer has no knowledge whatsoever of the document.

>>We might get audited, so we need to have documentation available", but the documentation is not kept up to date and is quickly outdated.
>
>It's a common misconception that Agile = no documentation. What it really means is that you create little documentation. Just enough to do the job.

Agreed. I read the article on wikipedia, and they illustrated the differences between agile development and cowboy coding. They went from cowboy coding to a heavily regulated waterfall method here and I was brought in as part of that change, and I'm paying the price by trying to provide advanced analysis on subpar code.

It makes for a frustrating Friday, but hey, is 4:59, and the Hawks are going to kick the crap out of Wann-stache and his kitties this weekend.

>>Agile development is a dirty word around here.