Lean QA (3 day course)

Wednesday 3, Thursday 4 and Friday 5 April 2013

9.00am - 5.00pm

BCS, 1st Floor, The Davidson Building, 5 Southampton Street, London, WC2E 7HA | Maps

Free of charge and open to all (BCS and non-BCS members)

Tom Gilb and Kai Gilb

Applications for places are to be sent directly to Soheir Ghallab

Please specify:

1. Why interested
2. Employment status
3. Which course(s)

This is for under-employed professionals.

Target audience:

People who are concerned with improving all quality aspects of products and services, while reducing the costs of testing and older forms of QC. Typical job titles are Test managers, QA and QC people. The approach is upstream and 'design quality in', so people interested in designing qualities into products will enjoy this too.

The Problem:

Testing costs too much, but is in fact ineffective. There are many proven methods for ensuring much better qualities, much sooner. But testers cannot be held responsible for deploying them. This is a CIO, CTO, QA-manager responsibility. Our 'lean' methods operate upstream, up front, pro-active, and with rapid learning.

Our solution:

We present a powerful selection of methods that can help you help to improve your software qualities dramatically, at low cost. All are freely adoptable. All can be tailored to your development environment immediately. All of them give measurable improvements.

  • Many real stakeholders have to be considered in QA. Not just the ‘user’ and ‘customer’ or the ‘tester’.
  • You can expect dozens of simple, but deep, and true, nuggets of real practical wisdom - from long experience and first hand practice.
  • You will not get re-iteration of conventional wisdom. You will get deep principles and methods that really work.
  • You will get the benefit of our decades of real experience internationally at IBM, HP, Boeing, Citigroup, JP Morgan, Credit Suisse, Siemens, Ericsson, Nokia, Philips, Rolls Royce, Intel and other top corporations.
  • This course is fact-based, on real life cases, of the lecturer, and others.

Detailed subject matter:

  • Stakeholder Quality: Stakeholder quality analysis and specification.
  • Quality Quantification: All quality requirements need to be quantified, to reflect all critical quality dimensions.
  • Quality by Design: Design Quality In! Don’t try to test it in. How to find and evaluate designs that give us needed quality levels. How to estimate impact of designs and architectures on requirement levels, as the basis for ‘assuring’ that we have later reached planned quality levels. Smart architecture for quality.
  • Quality Decision Tables: a practical tool for managing multiple qualities, multiple costs, and multiple architecture and strategy options - quantitatively and objectively.
  • Agile QC: Establish ‘agile quality control’, a quantified simple review process. This includes measuring the quality of requirements, designs, code, test plans. It will give people strong motivation to follow best standards practices.
  • Quantified Quality Process Gates: Quantified Process Entry and Exit Control, to drive learning, and practice, of your standards.
  • Quality by Feedback: Evolutionary Product Quality Development: one step above conventional ‘agile’ in dealing with quality. The Unity (111111) method for decomposing architecture into high quality increments.
  • Quantify Maintainability Requirements: Engineer a variety of maintainabilty qualities (Portability, Maintainability, Adaptability)