our team is "code complete" today.
What senior management takes this as meaning is that we're "done", and
should be starting on integration, which will just take a matter of
What this actually means is that every module in the system has been
written and compiles.
What it doesn't mean is that the modules actually function.
Apparently the program managers have accepted this terminology across
the board because it makes them look better. Now as we continue the
development and testing of the code, we as developers look like cretins
because we have to keep "fixing" the code that we've "completed".
However, our team is refusing one thing that the other teams have
adopted. We are continuing to perform unit tests on our modules to test
the functionality. Some of the other teams have decided that unit
testing will take too much time, and are moving directly from "code
complete" into integration. And hey, if it doesn't work, they'll catch
it in PV&V (beta testing).
Oh, and the team leads now have to edit our status reports, because
senior management doesn't want to be exposed to anything that might be
construed as negative.
It's weird. My tie is curling up at the bottom.