Documentation Testing

Documentation Testing - Many people have experienced frustration after they buy something that needs assembly, only to find that the instructions are vague or wrong.

Given that common experience, the project team needs to be sensitive to making sure that the documentation provided is understandable and complete.

In some cases, the documentation of the solution is done by the project team, and in some instances it is done by the client organization.

However, all of the available documentation can be "tested" regardless of where it was produced.

The purpose of Documentation Testing is to thoroughly review all written material that will be a part of the final solution. In other words, you want to review the User’s Manual, the Application Maintenance Manual, the Disaster Recovery Manual, etc.

However, you do not need to review project documents like the Business Requirements Report or Status Reports. The testing can be done a couple different ways.

  • Ask people who are unfamiliar with the application to follow all documented procedures. These should be written in a way that provides step-by-step guidance on how to accomplish the given task. If the testers cannot successfully complete the procedures, the procedures need to be improved.
  • Get people who have strong English, punctuation, and grammar skills to review all the material for professionalism and readability. It would be great to utilize experienced proofreaders. Otherwise, use employees with strong written communication skills.
  • Try out all alternative ways that are documented to accomplish a task. In many cases, the primary way works, but the alternatives do not.
  • If you are describing policies or standards, make sure that the appropriate authorities in your organization review and approve your wording. You do not want to misquote or misapply an important company policy.
  • Evaluate any manual forms, checklists, and templates to ensure they are accurate and that the appropriate information is being collected.

If you have the right people identified for this test, and you go over all the manual documentation thoroughly, you will reduce or eliminate a source of frustration and resistance after the application is implemented.

Domain Modeling

Libro El Director de Proyectos Práctico -

Un Método probado de 28 Pasos para completar tu Proyecto Exitosamente


Por fin ─ un libro sencillo con un método paso a paso para completar tu proyecto.

¡Y sin tener conocimiento previo sobre administración de proyectos!

Toda la "paja" de la metodología de dirección de proyectos fue eliminada, dejando solo lo que es absolutamente útil para completar la tarea.

El Director de Proyectos Práctico, Project Management for Small Projects. 

Un libro pensado en el líder de proyectos empírico que salió ganador de la rifa del tigre. Pues ya tiene la responsabilidad de un proyecto, pero que no sabe ni por donde empezar. Necesita una receta ABC para seguir.

Contiene 260 páginas perfectamente detalladas con ejemplos e ilustraciones, que te llevan de la mano hasta completar tu proyecto.

Pruébalo, síguelo, ten éxito. O sigue haciendo lo mismo... :(

Disponible en Amazon

Compra aquí El Director de Proyectos Práctico en su versión electrónica─

Entrega inmediata.

BONO ADICIONAL:  El libro incluye todos los templates─plantillas─que necesitas, listos para ser usadas. No necesitas comprar nada mas.

COPYRIGHT © 2007-2012 por Hector Olvera Padilla 1853071. Reproduction in whole or in part, or translation without written permission is prohibited. "PMP®", "PMBOK®", and "PMI®" are registered marks of the Project Management Institute, Inc.