for more information contact skot@penguinstorm.com or 206.629.8735
A project without documentation paints you into a corner –- losing a developer can set your timelines back by weeks or months while others struggle to catch up on work already done but not documented. Documentation takes many forms, but it should always exist. Documentation can take a number of forms.
All code should be documented, and standards exist to define this. You should make sure developers are doing this documentation as the work is done, but better late than never.
Developing custom software solutions can be costly – good user documentation is a critical component of software success.
User documentation can mean online help, printed manuals, and detailed training materials or a combination of all of these.
By the time a project is complete, the original project specification has often flexed and changed. The technical documentation process updates the project specification and creates a valuable detailed record of all technical aspects of the project.
Deliverables. Completed, edited documentation in digital format. (Format to be specified in project plan.) Printing can be arranged at additional cost.
Rates. Documentation can be prepared on an hourly basis, or can be included in a larger project at a fixed rate.
Documentation isn't an afterthough. Good documentation is as important as good code, if not more so.