Your browser does not support JavaScript!
http://iet.metastore.ingenta.com
1887

Managing Quality and Risk

Managing Quality and Risk

For access to this article, please select a purchase option:

Buy chapter PDF
£10.00
(plus tax if applicable)
Buy Knowledge Pack
10 chapters for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Name:*
Email:*
Your details
Name:*
Email:*
Department:*
Why are you recommending this title?
Select reason:
 
 
 
 
 
Troubled IT Projects: prevention and turnaround — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

Quality plans and risk management plans must result in project tasks to be actioned, tracked and managed to completion, otherwise the vendor's quality plans and risk management plans are simply shelfware. One of the biggest causes of troubled projects is vendor over-confidence in their abilities. A vital role of an independent QA organisation is to detect this problem and ensure that plans are realistic and achievable. Quality is delivered through: specifying quality requirements in tangible, real-world terms; defining and using appropriate software development processes; controlling quality through the use of appropriate V&V processes; independent QA reviews to ensure that quality attainment plans and quality control plans are being executed; defining and using appropriate processes to preserve quality throughout the life of the software. All of the above are defined in the quality plan, a crucial input to project estimation and planning. The goal of risk management is to reduce project overspend and slippage, and thereby to maximise quality. Risks must be identified and analysed to determine their probability and impact. Risk reduction actions can then be defined to re engineer the risk profile. What is left is the residual risk. Residual risk can be examined using best, likely and worst case scenarios, and appropriate contingency strategies and plans defined. Automated statistical tools can indicate the residual risk contingency which should be set aside to provide the desired confidence level that the contingency will not be exceeded.

Inspec keywords: software quality; quality control; statistical analysis; project management; organisational aspects; risk management

Other keywords: quality attainment plans; independent QA reviews; quality management; risk profile; project planning; risk management plans; quality control; project estimation; vendor over-confidence; risk reduction actions; residual risk contingency; quality requirements specification; software development processes; QA organisation; automated statistical tools; shelfware

Subjects: Software engineering techniques

Preview this chapter:
Zoom in
Zoomout

Managing Quality and Risk, Page 1 of 2

| /docserver/preview/fulltext/books/pc/pbpc003e/PBPC003E_ch10-1.gif /docserver/preview/fulltext/books/pc/pbpc003e/PBPC003E_ch10-2.gif

Related content

content/books/10.1049/pbpc003e_ch10
pub_keyword,iet_inspecKeyword,pub_concept
6
6
Loading
This is a required field
Please enter a valid email address