How to Write Software Quality Management Plans
I N T R O D U C T I O N
How to Write Software Quality Management Plans is a plain-english, simplified version of IEEE 730 -1989 Standard for Software Quality Assurance Plans.
This how to guide specifies the format and contents of a quality plan. It identifies the practices and processes to be applied during a project to ensure that the deliverables conform to the agreed requirements.
It also identifies the quality objectives of the project, which are statements about measurable aspects of project and quality management.
The quality plan includes the:
scope and objectives of the quality aspects of the project quality deliverables that the project will produce process by which those deliverables are produced organisation and staffing which will perform the quality functions responsibilities of those involved
S C O P E
How to Write Software Quality Management Plans applies to the medium to large scale software development projects.
O B J E C T I V E S
How to Write Software Quality Management Plans provides project and quality managers with a guide for the development of the quality plan. It addresses:
quality related aspects of the project to be considered during the
planning stage of the project the project's quality objectives, quality deliverables
and how they are to be managed the need for consistent content and formatContribution to IS Quality. As with the Project Plan, the literature of software quality recognises the importance of comprehensive planning for those aspects of a software development project that bear most closely upon its success.
Given that up to 70% of IT development projects fail (in terms of either not being completed, or completed but not used by the client due to it unsuitability), due in part to inadequate planning and execution of the project, this how to guide is an valuable aid for project planners to address the important quality-related activities. It is is an easy to use checklist, as defined by IEEE 730, and template to achieve this end.
In the same way as a systematic and comprehensive Statement of User Requirements can capture a more complete set of requirements, a project plan as provided by this how to guide allows the project manager to make sure he/she has considered all relevant quality matters in the planning stage, allowing them to avoid, as far as possible, unpleasant surprizes later.
V I E W - S A M P L E S
Click here to see the contents list.
Click here to see a sample of the plan.
Note formatting may be affected in conversion from Word to HTML.
D O W N L O A D - F R E E - U S E F U L - S A M P L E S
Two brief (~10 pages each) how to guides can be downloaded for free. They are zip files containing rtf & pdf copies of the documents.
They are useful and relevant to any software development project and are intended to give prospective buyers of the full featured range of TCS how to guides an indication of their quality and usefulness.
Click here to download How to Perform Risk Management (.docx format).
Click here to download How to Perform Project Estimates (.docx format).
A B O U T T H E A U T H O R
How to Write Software Quality Management Plans was written by David Tuffley, who combines a successful commercial career as a quality management consultant with academic involvement at the School of ICT, at Griffith University, Australia, where he lectures and is engaged in postgraduate research in IS Quality.
See Client list.
O R D E R Y O U R C O P Y N O W
This guide, proven over the past five years at large commercial and public sector sites, could save you thousands of dollars in consultancy fees. Or put it another way, you could not buy even an hour of a good consultant's time for the price of this valuable How To guide. Yet consultants routinely spend weeks or months implementing procedures similar to those contained in this guide.
Ordering your copy of this excellent How To guide for only US$24.95 is easy. Buy It
Transaction Record. Your credit card transaction will be processed using the latest secure processes by CCNow (TCS's authorized online retailer). Your credit card transaction statement will show CCNow.
Delivery Information. You will receive a download link by email soon after you place the order. The download contains the deliverables in MS Word (.docx) and PDF. The documents are your master copy.
How to Use the Documents. Save the master as a working document. Read the reference text that details what needs to be written, and to what level of detail. Then write what needs to be written, and delete the reference text, leaving the completed document. The structure is embodied in the template. Documents can be converted to HTML for intranet/internet delivery if desired, using your wordprocessor's inherent HTML conversion capabilities, or by using proprietary conversion software that builds contents hierarchies that greatly facilitates navigation. Contact TCS for more information.
Transaction Record. Your credit card transaction will be processed using the latest secure processes by CCNow (TCS's authorized online retailer). Your credit card transaction statement will show CCNow.
O T H E R T C S P U B L I C A T I O N S
Client list Complete Library (all of the below + 19 extra) 
User Manuals Software Requirements Specifications Capture IS User Requirements Software Test Documentation Software Design Descriptions Configuration Management Plans Version & File Software Development Documentation Software Project Agreements Software Project Plans Software Quality Management Plans Software Project Review & Audits Software Project Terms of Reference Perform Software Project Metrics Initiate Software Projects Software project procurement & handling client supplied materials
R E T U R N T O T C S H O M E P A G E
Site design by David Tuffley.