Software development from a technical documentation standpoint

Posted 15 January 2011 by

Not every frame is found in every project. But, hang around long enough and you will see every frame at least once.

What the project sponsor described at the kick-off meeting
What the project sponsor described at the kick-off meeting
What the system analysts understood
What the system analysts understood
How the technical writer described it in the system help
How the technical writer described it in the system help
How much targeted end-user input there was
How much targeted end-user input there was
What the developers programmed
What the developers programmed
What went to beta testing (the fix will be the release version)
What went to beta testing (the fix will be the release version)
What the product manager sees
What the product manager sees
What the instructional designer was told to do with the training
What the instructional designer was told to do with the training
What was released after the budget cuts and cost overruns
What was released after the budget cuts and cost overruns
What marketing advertised
What marketing advertised
When the software was released
When the software was released
What resulted when real customers used the software
What resulted when real customers used the software
What support is given
What support is given
How upgrades are made with later releases to fix the problems
How upgrades are made with later releases to fix the problems
What the customer wanted
What the customer wanted

I created the initial version of this at Project Cartoon. (I made minor text changes made later for each picture, as well as improving accessibility to this web page.)

Some of the work is licensed under a Creative Commons Attribution 3.0 Unported License. View the details.

Post Details

Leave a Reply

Page optimized by WP Minify WordPress Plugin