Version 5
Created by Francisco Vives on Apr 16, 2008 10:02 AM. Last modified by federico on Jul 1, 2009 9:46 AM.

    Factores que se evalúan antes para definir la prioridad de un error:

    • Efecto en el cliente

    • Cantidad de consecuencias / funcionalidades que se dejan de usar

    • Importancia de las funcionalidades que se dejan de usar

    • Si el error genera daños muy dificiles de recuperar

    • Si existe una forma de tener la funcionalidad aunque sea de una forma diferente (workaround)

     

    Niveles de Prioridad

    • Blocker: es un problema de seguridad o un issue que afecta un requerimiento central al cual no hay un workaround. Esto previene el uso y pruebas del sistema.

    • High: es un problema que afecta un requerimiento central del sistema en el cual hay un workaround. La funcionalidad del sistema puede ser usada aunque algo limitada.

    • Medium: es un problema que afecta un requerimiento no central del sistema en el cual no hay workaround. La funcionalidad no puede ser usada.

    • Medium-low: es un problema que afecta un requerimiento no central del sistema en el cual hay workaround.

    • Trivial: la información es mostrada correctamente pero la apariencia es incorrecta, como problemas de identación, fuentes erróneas, etc.

    • Low: es un problema que afecta un requerimiento no central del sistema en el cual hay workaround.

     

     

     

    Severity:

    Severity level of the issue with respect to the application. Not necessarily the importance of getting the issue fixed, but rather, how bad is it with respect to broken functionality.

    • S0: Total Blocker, development or QA is at a standstill.  Drop everything and fix it.
    • S1: Very Critical, these issues must be fixed before a version is release.
    • S2: Major, these issues are problematic but have a documented workaround.
    • S3: Minor, these issues would be nice to have fixed.
    • S4: Trivial, these issues would also be nice to have fixed, but if they are never fixed, it's not a huge deal

     

    Priority:

    Priority should be defined with respect to who reported it, who it affects, how large is group of customers this will or would affect. Even if the severity of a bug is low, it might affect every single customer in a painful way, or it affects one really large customer, that would raise the priority.

    • P0: Total Blocker, user is dead in the water
    • P1: Very Critical, broad scope in terms of who and how it will affect the user
    • P2: Major, these issues are problematic but can wait an extra release cycle to be fixed
    • P3: Minor, these issues would be nice to have but are not causing any major customer pain.
    • P4: Trivial, these issues would also be nice to have fixed, but if they are never fixed, it's not a huge deal to anyone.