iSixSigma

Defining Opportunity in SS project in Software

Six Sigma – iSixSigma Forums Old Forums Software/IT Defining Opportunity in SS project in Software

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #26802

    Whitehurst
    Participant

    Hi,
    I would like to know how to define a opportunity while calculating a DPMO. Can some one please explain this with expamples from software development.

    0
    #65116

    Don Strayer
    Participant

    Some black belts insist that an entry field in a form, for instance, is one opportunity.  That makes sense if you’re black box testing.  If you’re white box testing or doing code inspection  you’ll find many more opportunities in the underlying code.  Start with the proper definition of defect — a variance that is outside customer specifications.  I advise my clients to start with the requirements, define what would constitute a defect for each requirment, then identify where each defect might occur.  And keep the ratio 1:1.  You may find more than one opportunity for the same defect or more than one defect that might occur at the same opportunity.  Adjust your counts accordingly or you’ll skew the DPMO and sigma.
    This is assuming that you’re looking at the quality of the software product.  If you’re looking at the quality of the software development process, which you must ultimately do, you need to look for specific places in the process where a defect may be injected into the product.

    0
Viewing 2 posts - 1 through 2 (of 2 total)

The forum ‘Software/IT’ is closed to new topics and replies.