Acceptance Criteria

Acceptance Criteria is a quality assurance technique. The Acceptance Criteria should describe the processes and checkpoints that need to take place before the solution is considered complete.

Does the system have to be perfect? You better hope not. But the Acceptance Criteria should define how the acceptance decision will be made.

For instance, the sponsor may accept a system with certain minor types of errors remaining, but there may be other levels of errors that will render the system unacceptable.

Part of the Acceptance Criteria may specify the types of testing that take place.

For instance, the client may want to thoroughly test security in a separate and focused test, something that may not have been in the original plans of the project team.

However, after defining the Acceptance Criteria, the project manager knows that this extra test should be planned and scheduled.

Examples of the types of events or activities that would be in the Acceptance Criteria are:

• Ensuring the requirements are formally approved
• Proving (through traceability or Requirements Testing) that all requirements are accounted for in the final solution
• Accounting of budget and expenses on the project
• Specifying the testing criteria and/or specific types of testing to perform
• Defining implementation options - for instance, first running a pilot test
• Ensuring that the solution is stable
• Validating that the training is completed
• Specifying how long the project team must support the solution before turning it over to the support organization
• Fixing all major bugs and errors, although minor bugs and nuisance errors could be unresolved
• Collecting certain metrics and validating against predefined targets

The Acceptance Criteria should be defined in writing and approved by the sponsor.

All things being equal, if the Acceptance Criteria are met, there should be no reason that the sponsor would not approve and accept the final solution.

Acceptance Testing

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.