Operational Objective: Improve Quality

Relationships
Main Description

Description

By IEEE definition [IEEE, 1991], quality is

  1. The degree to which a system, component, or process meets specified requirements
  2. The degree to which a system, component, or process meets stakeholders needs or expectations.

To monitor Quality status for a project, see the Quality Dashboard.

Strategies

The following strategies help improve quality:

  • Increase Defect Detection
    • Increase ability to detect or remove defects during development, when they are less costly to fix
    • Indicators:
      • High post-shipment or customer-reported defects
      • High rate of fixes which have to be reworked
  • Increase Defect Prevention
    • Reduce the number of defects injected during development
    • Indicators:
      • High pre-shipment and post-shipment defect reports
      • Growing defect backlog
  • Improve Nonfunctional Requirements
    • Focus on performance, reliability or security requirements early in the development lifecycle for mission-critical or high-availability systems. Focus on usability requirements for highly-interactive systems.
    • Indicators:
      • High occurrence of non-functional requirement issues
      • High number of help desk calls
      • Resolution time is high for reported incidents
  • Deliver on Customer Requirements
    • Increase value by delivering high value, high priority features that are needed
    • Indicators:
      • High number of features that have not been used
      • Large and aging enhancement request backlog
      • Large amounts of post-delivery support
      • Low customer satisfaction levels