Every software project carries within it the seeds of its own failure. Missed deadlines, defects that surface in production, scope that creeps until it consumes the budget — these are not accidents. They are the predictable consequence of what happens when quality is treated as an afterthought rather than a discipline.
Software Quality Plans: A How-To Guide for Project Staff is the book that changes that equation. Written by David Tuffley and grounded in IEEE Standard 730 — the gold standard for software quality assurance — this concise, authoritative guide gives project managers, quality engineers, and development teams a practical, immediately usable framework for building quality into a project from its very first day.
What separates this book from the dense, impenetrable standards documents that gather dust on IT department shelves? Clarity. Tuffley has translated the architecture of IEEE 730 into plain-language guidance that project staff can actually use — section by section, deliverable by deliverable, decision by decision. Every chapter of a quality plan is explained not merely in terms of what it must contain, but why it matters and how to make it work in a real project environment.
The book walks readers through the complete anatomy of a software quality plan: how to define measurable quality objectives that hold a project accountable; how to organise responsibilities so that nothing falls through the cracks; how to document standards in ways that survive team changes; how to structure reviews and audits that catch problems early rather than late; and how to manage suppliers, contractors, and purchased software products without losing control of quality.
Risk management receives its own treatment — a structured, repeatable approach to identifying, assessing, and containing the cost and schedule risks that kill projects. So too does configuration management, testing, problem reporting, corrective action, and the often-neglected but critical practice of the project debrief, where hard-won lessons are captured before the team disperses and memory fades.
What you hold in your hands is not a theoretical treatise. It is a working tool. Each section mirrors the structure of an actual quality plan document, complete with example tables, checklists, and worked illustrations that allow a project team to move directly from reading to doing.
Whether you are a project manager facing your first formal quality audit, a quality engineer trying to standardise practice across a portfolio of projects, or a developer who wants to understand what the quality function is actually trying to achieve — this book meets you where you are and takes you where you need to go.
Quality, Aristotle observed, is not an act. It is a habit. This book is how that habit is built.
"synopsis" may belong to another edition of this title.
David Tuffley PhD is lecturer and researcher at Griffith University in Australia. David is a Software Engineer, though his interests range across Comparative Religion, Philosophy, Psychology, Anthropology, Literature, History, Design and Architecture. David has been an academic since 1999. For 15 years before academia David was a consultant for public and private sector IT clients in Australia and the United Kingdom. He combines theory and practice in a focussed and disciplined way that has proved effective for solving problems for clients.
"About this title" may belong to another edition of this title.
Seller: GreatBookPrices, Columbia, MD, U.S.A.
Condition: As New. Unread book in perfect condition. Seller Inventory # 20947766
Seller: GreatBookPrices, Columbia, MD, U.S.A.
Condition: New. Seller Inventory # 20947766-n
Seller: California Books, Miami, FL, U.S.A.
Condition: New. Print on Demand. Seller Inventory # I-9781461130222
Seller: PBShop.store US, Wood Dale, IL, U.S.A.
PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Seller Inventory # L0-9781461130222
Seller: PBShop.store UK, Fairford, GLOS, United Kingdom
PAP. Condition: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Seller Inventory # L0-9781461130222
Quantity: Over 20 available
Seller: Ria Christie Collections, Uxbridge, United Kingdom
Condition: New. In. Seller Inventory # ria9781461130222_new
Quantity: Over 20 available
Seller: THE SAINT BOOKSTORE, Southport, United Kingdom
Paperback / softback. Condition: New. This item is printed on demand. New copy - Usually dispatched within 5-9 working days. Seller Inventory # C9781461130222
Quantity: Over 20 available
Seller: GreatBookPricesUK, Woodford Green, United Kingdom
Condition: New. Seller Inventory # 20947766-n
Quantity: Over 20 available
Seller: GreatBookPricesUK, Woodford Green, United Kingdom
Condition: As New. Unread book in perfect condition. Seller Inventory # 20947766
Quantity: Over 20 available
Seller: CitiRetail, Stevenage, United Kingdom
Paperback. Condition: new. Paperback. I N T R O D U C T I O NHow to Write Software Quality Management Plans is a plain-english, simplified version of IEEE 730 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 EHow 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 SHow 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 late This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability. Seller Inventory # 9781461130222
Quantity: 1 available