1. EXPLICIT RISK SPECIFICATION
All managers/planners/engineers/testers/quality assurance people shall
immediately in writing, integrated in the main plan, specify any
uncertainty, and any special conditions which can imaginably lead to a
risk of deviation from defined target levels of system performance.
2. NUMERIC EXPECTATION SPECIFICATION
The expected levels of all quality and cost attributes of the system
shall be specified in a numeric way, using defined scales of measure,
and at least an outline of one or more appropriate ‘Meters’ (test or
measuring instruments for determining where we are on a scale).
3. CONDITIONS SPECIFIED
The requirements levels shall be qualified with regard to when where and
under which conditions the targets apply, so there is no risk of us
inadvertently applying them inappropriately.
4. COMPLETE REQUIREMENT SPECIFICATION
A complete set of all critical quality and cost aspects shall be
specified, avoiding the risk of failing to consider a single critical
attribute.
5. COMPLETE DESIGN SPECIFICATION and
IMPACT ESTIMATION
A complete set of designs or strategies for meeting the complete set of
quality and cost targets will be specified. They will be validated
against all specified quality and cost targets (using Impact Estimation
Tables). They will meet a reasonable level of safety margin. They will
then be evolutionarily validated in practice before major investment is
made. The Evo steps will be made at a rate of maximum 2% of budget, and
2% of ‘project time’, per ‘incremental trial’ (Evo step) of designs or
strategies.
6. SPECIFICATION QUALITY CONTROL
NUMERICALLY EXITED
All requirements, design, impact estimation and Evolutionary project
plans, as well as all other related critical documents such as
contracts, management plans, contract modifications, marketing plans,
shall be ‘quality controlled’ using the Inspection method [GILB93]. A
normal process Exit level shall be that ‘no more than 0.2 Major Defects
per page maximum, can be calculated to remain, as a function of those
found and fixed before release, when checking is done properly’ (e.g. at
optimum checking rates of 1 logical page or less per hour).
7. EVOLUTIONARY
PROOF-OF-CONCEPT PRIORITIES
The Evolutionary Project Management method [GILB98, GILB88] will be used
to sense and control risk in mid-project. The dominant paradigms will
be: -
-
2% steps
-
high value to cost
with regard to risk delivered first.
-
high risk strategies
tested ‘offline to customer delivery’, in the Backroom of development
process, or at cost-to-vendor, or with ‘research funds’ as opposed to
project budget.
|
