Re: The last minute crunch
Are your developers under the (all-too-common) illusion that becuaseA few rounds of, "I just noticed this screen where the capitalization of the field labels doesn't match our style guide; could you just take a few minutes to fix it before the product ships?" will drive home the point. <g>
it's "just" the docs, that their requests should be easy?
Once you get toward the end of a product cycle, what are you procedures forExactly. Just like the capitalization errors on the screen labels.
product changes? Many places I've worked require that any such requests get
tracked, often in the bug database. "Bugs" that are actual feature requests
have to be scoped out and approved before they are implemented. And true
bugs have to be prioritized; not all bugs can always be fixed within the
scope of the project.
Is there such a process there (I can hardly beleiveIBM and process used to be synonyms. The new, more agile IBM is full of creative people who do what they can however they can get away with it. That's not necessarily a bad thing.
that there's not; "IBM" and "process" are synonyms), and if so, are the
developers going around that process, either because they think the issue is
so small or they believe that docs aren't part of the development process?
Search our Technical Writing Archives & Magazine