SPI-LEAM: Software Process Improvement through the Lean Measurement method ~ (Petersen, K., & Wohlin, C., 2010)

Bas Hovestad (4104129)

Authors Kai Petersen

• Ph.D. Student at Ericsson AB • Blekinge Institute of Technology in Sweden

Topic

Claas Wohlin• Professor of Software Engineering • Pro Vice Chancellor of Blekinge Institute of

Technology

Software Process Improvement through the Lean Measurement method

Origins:• Lean software development• Quality Improvement Paradigm (QIP)

Purpose Integrating the Quality Improvement Paradigm (QIP) (Basili &

Green, 1994) and Lean development software principles (translated to software engineering by Poppendieck & Poppendieck (2003)).

• QIP: Support continuous process improvement• Lean: Eliminate ‘waste’ -> all activities and work products that do not

contribute to the customer value

Main phases1) Individual inventory measurement

2) State of process determination3) State of process analysis

Process Deliverable Diagram

Measure individual inventories Relevant inventories (not

more than 5) for the organization are identified

Sub-inventories are selected and measured

The inventory is visualized on a radar chart

Determine state of process

Analyze state of process

Determine threshold for overload situations of sub-inventories.

Set inventory levels.

Create situation analysis

Improvement scenarios are developedif room for improvement is found

ExampleDimension Specification

Goals - Enable continuous software process improvement leading to a lean software process.

Questions Q1: What is the performance of the development process in terms of inventories?

Metrics Test cases (individual inv.) Unit test (sub.-inv.); Function test; Integration test; System test; Acceptance test

Change requests (individual inv.) CR under review; Approved CRs; CRs ready for impact analysis; CRs in test

Faults and failures (individual inv.) Internal faults and failures (test); External faults and failures (customer)

Fault-slip-through (quality) Req. review slippage; Unit test slippage; Function test slippage

How to measure?

Specific methods per inventory

What to measure?

Effort to implement inventory

Visualize effort per inventory Combine inventories and qualitymeasurements

Analyze data

Recommend improvements

Related LiteratureRoots:

• Quality Improvement Paradigm (Basili & Green, 1994)

• Toyota’s manufacturing system (JIT) (Monden, 2012).

• Agile and lean practices (Petersen, 2011).

Case studies:

• Implementation lean principles (Middleton, 2001).• Confirmed by Perera and Fernando (2007)

Tools:

• Value Stream Mapping Mujtaba, Feldt, and Petersen (2010).

Applications of method:

• Not yet, but mentioned by Herranz, Colomo-Palacios, and Amescua-Seco (2013).

Thanks for your attention

Questions?