I can always read source code. Any programmer worth a damn can. Docs are out of sync with the code the second the code changes in any non-trivial way.
However, code always documents how it works (sometimes poorly, of course).
However, code always documents how it works (sometimes poorly, of course).
If code is temporary then it might not be worth the effort to document, but my documentation is what everybody except one person 20 years from now sees along with the user interface, so for my application the code doesn’t matter and the documentation matters quite a bit!
So I wonder how you feel about:
Individuals and interactions VS processes and tools
Customer collaboration VS contract negotiation
Responding to change VS following a plan
If you have a design iteration plan, how do you respond to a showstopper that makes the plan infeasible if you are on a strictly waterfall design plan?
Each has it's trade offs so you can't always pick one or the other willy-nilly or else you don't have a design strategy at all