Course summary TDT4235 Tor Stålhane IDI / NTNU

What we try to do QA – Create trust to a product or service SPI – Solve fuzzy problems by –Identifying and describing the problem –Collect information to understand the problem –Select a potentially useful technique –Arrive at a useable solution

Create trust Product Tools and methods Trust Customer knowledge

A “soft” problem Problem Available tools and methods Possible solution Experience Method 4 Method … Method 2 Method … Method 7 Method 3 Method n Method 6 Method 1 Method 5

Summary of Quality Assurance – 1 QA is about two things: Having a way of working that is – Defined – there is clear description – Documented, written down for everybody to see – Communicated, everybody in the company knows about it – Agreed-upon, everybody in the company works this way Keeping our promises. When we have promised to do the job in a certain way, this is how it will be if nothing else is agreed upon later.

Summary of Quality Assurance – 2 The QA department or the QA responsible needs to Check that we keep our promises Look for improvement opportunities – New things to do – Things to change – Things we should stop doing

Summary of Quality Assurance – 3 Quality assurance is not software process improvement a way to keep status quo.

Summary of SPI – 1 This part of the summary will focus on the SPI part of the course. The main messages are: SPI => change Change => risk Risk can be reduced or controlled by – Collecting data – Analysing data

Summary of SPI – 2

Summary of SPI – 3 The amount and type of data that we need to collect will depend on our Willingness to accept risk Time frame – when do we need it Planning horizon

How much risk are we willing to take

The data collection process As shown in the next diagram, we wiull keep on collecting data until we Can reduce the decision risks to an acceptable level Run out of time

Collect info Perform risk Final SPI plan More time available Yes Plan SPI activities assessment Acceptable risk Yes No

Assess mitigation activities Assess cost Assess risk effect Within limits Acceptable Final SPI plan including mitigations No Yes

PDCA and risk The amount of risk we are willing to accept and the corresponding actions or lack thereof can be illustrated by using different versions of the PDCA cycle.

Plan Do Check Act NeedsImprovements SWOT / SWIR Gap analysis Planning Risk assessment Delphi analysis Data archeology KJ / affinity diagrams Pilot projects GQM Plotting techniques Statistical analyses Root Cause Analysis Risk assessment Introduce changes What are the results Post Mortem Analysis

Plan Do Check Act NeedsImprovements SWOT / SWIR Data archeology Delphi analysis Root Cause Analysis Risk assessment Introduce changes What are the results

Plan Do Check Act NeedsImprovements Planning GQM Pilot project Plotting techniques Statistical analyses Root Cause Analysis Risk assessment Introduce changes What are the results

Plan Do Check Act NeedsImprovements Gap analysis KJ / affinity diagrams Root Cause Analysis Risk assessment Introduce changes What are the results

Plan Do Check Act NeedsImprovements Post Mortem Analysis Risk assessment Introduce changes What are the results Gap analysis Risk assessment

ProcessProjectMeasurementAnalysis Relevant data Historical data ExperienceKnowledge PMA Improvement opportunities

ProcessProjectMeasurementAnalysis Relevant data Historical data ExperienceKnowledge GQM Improvement opportunities

ProcessProjectMeasurementAnalysis Relevant data Historical data ExperienceKnowledge Proactive SPI or Only subjective data – e.g. Delphi Improvement opportunities

What is the status? e.g. SWOT Management decidesSelect area Action Results Collect data Analyze data ActionResults