Many of the problems that come out of projects, whether process delays or cost overruns at the process level, or defects and omissions at the product level, have their origins in the way projects are established and initiated. Many project charters and scope statements already embed the seeds of what will become project failures at a later date. This research initiative is looking at the characteristics that result in such failures, particularly at the integration points between Six Sigma and information technology process models.

A key first step in tailoring is to decide what project perspective is most relevent. Options include the use of Six Sigma to include the development process or standards, or using Six Sigma to produce a systems product:

If a systems product is sought, the tailoring of an appropriate development lifecycle will depend upon the level and combination of design and implementation risk to be encountered on the project:

Development of a project charter and work breakdown structure can then commence.