Tom Gilb

Tom Gilb (born 1940, California) has lived in UK since 1956, and Norway since 1958.
He is the author of 9 published books, including  “Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage”, 2005.
He has taught and consulted world-wide for decades, including having direct corporate methods-change influence at major corporations such as Intel, HP, IBM, Nokia. He has had documented his founding influence in Agile Culture, especially with the key common idea of iterative development. He coined the term ‘Software Metrics’ with his 1976 book of that title. He is co-author with Dorothy Graham of the static testing method  ‘Software Inspection’ (1993). He is known for his stimulating and advanced presentations, and for consistently avoiding the oversimplified pop culture that regularly entices immature programmers to waste time and fail on their projects.
More detail at www.Gilb.com

All Real Stakeholders: Many (30-40) multiple stakeholders to consider in QA: not just ‘user’ and ‘customer’. This is a Scrum ‘Product owner’ responsibility: but how well is it done in practice? We believe done badly, and have constructive advice for doing it better.

All Quality Requirements Quantified: Quantified multidimensional quality requirements to define the project-relevant ‘Q’ in QA. Quality is far more than bug freeness!

Managing Designs that give Qualities: Estimated Impact of Designs and Architectures on Requirement Levels as the basis for Assuring that we have later reached planned Quality levels. How to manage multiple qualities quantitatively.

Lite Measurement of Requirements and Specs:  All Agile Quality Control (QC) of Specifications (Spec QC). Includes Requirements, Designs, Codes, Tests) to give strong motivation to follow best standards practices better by factor of 100..

Quality Gateways the Work: Process Entry and Exit numeric standards (100x improvement) for compliance to specification standards: no Garbage In Please.

Practical Defect Prevention Process: Real Process Improvement early, frequently, measurably, in all projects.

Rapid Evolutionary iteration: do real QA weekly, and incrementally.  Incremental value delivery, data collection, feedback, analysis and change:  for early value delivery, for cost control, for intelligent prioritization, for team and process validation of effectiveness,

Quantify Maintainability Requirements: Long Term Thinking about Maintenance and Change capabilities: avoid short sightedness.

Case Study of Real QA – Confirmit, Norway: Quantified Qualites Driven up front. Including their testing practices. Using Gilb’s Evo method.