The Ambiguity Review

This is nothing but a ‘requirements testing’. A process put forward by Richard Bender.

An Ambiguity Review improves the quality of requirements by making them deterministic, unambiguous, correct and complete.  An Ambiguity Review is a testing technique that helps eliminate defects in the requirements phase of the software development lifecycle, thereby preventing those defects from propagating to the remaining phases of the software development lifecycle.

Find the process concept document here.


Six Sigma at a glance

  • Six Sigma – A systematic methodology for quality management
  • TQM & ISO 9000 are other similar quality management methodologies
  • It uses various theories and tools for process improvement
  • Improves process and tries to reduce time, cost, resource etc.
  • Denoted by , where σ is a Greek symbol
  • Six-Sigma represents the statistical term standard-deviation
  • Standard Deviation is the deviations from average
  • Standard Deviation = unit of measurement of deviation 
  • More deviation from average/mean means more defects
  • A business/product which follows 6σ will have only 3.4 DPMO
  • DPMO = Defects Per Million Opportunities
  • Success rate of Six Sigma is 99.99966%
  • Three key holders of quality = Customer, Employee and Process
  • Six Sigma is not about quick-fix
  • 6σ was first implemented by Motorola Corporation in 1980
  • Traditional 6σ certification levels are:
    • Yellow Belt
    • Green Belt
    • Black Belt
    • Master Black Belt and
    • Champion
  • DMAIC model
    • Define
    • Measure
    • Analyze
    • Improve
    • Control
  • PDCA
    • Plan
    • Do
    • Check
    • Act
    • Define
    • Measure
    • Analyze
    • Design
    • Verify
  • DFSS = DMADV, also known as Design For Six Sigma