Role-Based Requirements

One way to classify requirements is based on the role of the person that would typically provide the requirements.

For instance, the user of a deliverable would likely provide a different set of requirements than a manager that only needs to get reports on a monthly basis. It's not a matter of right and wrong.

It is a matter of perspective. Different people in different roles have differing perspectives on features and functions and what the relative importance of requirements is. Examples of role-based classification of requirements are as follows:

  • Client requirements

  • User requirements

  • Sponsor requirements

  • IT requirements

  • Security requirements

  • Auditing requirements

  • Etc.

It is important to understand the role of the people who are providing requirements so that you can validate whether they are appropriate.

For instance, you would not expect a high-level manager to provide detailed requirements on features and functions. If he or she does, you may need to validate whether the manager really has the right perspective to provide these types of requirements.

Likewise, if a typical user provides technology requirements, you would need to validate what his or her perspective is and determine whether these are real requirements or not.

A common mistake in people gathering requirements is that they accept requirements from people who are not really in a position to provide those role-based requirements.

If they are accepted at face-value and not challenged, they can end up confusing the requirements rationalization and prioritization that takes place during the Specification Step.
Roles

Roles


Libro El Director de Proyectos Práctico -

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

EL DIRECTOR DE PROYECTOS PRACTICO -

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.