Six Sigma For Software: Dr. Thomas Fehlmann Euro Project Office AG, Zurich, Switzerland E-Mail: Web
Six Sigma For Software: Dr. Thomas Fehlmann Euro Project Office AG, Zurich, Switzerland E-Mail: Web
Six Sigma For Software: Dr. Thomas Fehlmann Euro Project Office AG, Zurich, Switzerland E-Mail: Web
to success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Six Sigma for Software
Dr. Thomas Fehlmann
Euro Project Office AG, Zurich, Switzerland
E-mail: thomas.fehlmann@e-p-o.com
Web: www.e-p-o.com
www.swisma.ch
www.ch-open.ch/sigs/chop
2
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Six Steps to Six Sigma for Software
1. WHAT is Six Sigma? Does it apply to software?
2. WHY do we need Six Sigma For Software?
3. HOW do you implement Six Sigma in the workplace? Can the
theory really be put into practice?
4. WHERE has Six Sigma been applied successfully? Are there
success stories in software, and in which companies?
5. WHEN should Six Sigma be used? How does it fit into a Software
Development and Deployment project?
6. WHO can make an impact using Six Sigma? What are the
organizational and skills requirements? How does it fit into your
Six Sigma program?
3
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
What is Six Sigma?
A Management Strategy
Making targets transparent
Focusing on customers
Meeting the targets
Measurements
Targets
Achievements
DANGER
METRICS
IN USE!
4
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
One Sigma Distribution
Only
about
60%
within
tolerance
Others
some-
where
outside
tolerance
needing
a fix
tolerance
threshold
6 6
5
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Six Sigma Distribution
All actual measured cases
with tolerance
A process that executes on
6 level will yield results
within the tolerance interval
with 99.99966% probability
6 corresponds to only 3.4
defects per 1 million defect
opportunities
A defect is what affects
customer satisfaction
tolerance
threshold
6 6
6
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Customer
finds the Defects
Customer
finds the Defects Defects
Mistakes, Bugs, and Defects
Tester
finds Bugs
Tester
finds Bugs Bugs
Developer
finds Mistakes
Developer
finds Mistakes Mistakes
7
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Common Defects in ICT
In ICT Projects
Often targets are not
clear
Risks have not been
assessed
Resources are not
committed
In Software
No measurements
not even functional
sizing
No customer related
metrics are established
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
Start Start
Goal Goal
Time
V
a
l
u
e
8
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Six Steps to Six Sigma for Software
1. WHAT is Six Sigma? Does it apply to software?
2. WHY do we need Six Sigma For Software?
3. HOW do you implement Six Sigma in the workplace? Can the
theory really be put into practice?
4. WHERE has Six Sigma been applied successfully? Are there
success stories in software, and in which companies?
5. WHEN should Six Sigma be used? How does it fit into a Software
Development and Deployment project?
6. WHO can make an impact using Six Sigma? What are the
organizational and skills requirements? How does it fit into your
Six Sigma program?
9
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
ICT Cost is a Burden
Hidden costs in % of turnover
0 1 2 3 4 5 6
0%
10%
20%
30%
40%
Sigma
DPMO 500000 308537 66807 6210 233 3.4
(Defects per Million Opportunities)
Average Organisation
v 15%
Best in class
< 5%N
Services, Projects, ICT
+33%
Source: Concepts, Innsbruck; GE; own measurements
10
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Goal
Create an ICT environment
that effectively solves
customers problems
It works the first time
It is reliable
It tolerates change
Use project management
practices that are suitable
for ICT
Create software based
systems reliably in time and
budget
Start Start
Goal Goal
Time
V
a
l
u
e
11
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Key
The Six Sigma approach:
Set the goal
Define Define
Define the metrics
Measure Measure
Measure where you go
Analyze Analyze
Improve your
processes while you go
Improve Improve
Act immediately if
going the wrong path
Control Control
12
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Six Steps to Six Sigma for Software
1. WHAT is Six Sigma? Does it apply to software?
2. WHY do we need Six Sigma For Software?
3. HOW do you implement Six Sigma in the workplace? Can the
theory really be put into practice?
4. WHERE has Six Sigma been applied successfully? Are there
success stories in software, and in which companies?
5. WHEN should Six Sigma be used? How does it fit into a Software
Development and Deployment project?
6. WHO can make an impact using Six Sigma? What are the
organizational and skills requirements? How does it fit into your
Six Sigma program?
13
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
How to implement Six Sigma For Software?
Principle No 1: Use customer related metrics
Use Combinatory Metrics to cover all topics
Principle No 2: Adjust to moving targets
Your goals may need change; accept change and
manage it accordingly
Principle No 3: Enforce measurement
Do not enforce meeting targets
14
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Three Metrics for ICT
We use three kinds of metrics:
Progress track project related
Combinatory metrics product related
Bug count quality related
15
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Combinatory Metrics Cause - Effect Analysis
Maximum Value Table
Deliverable Impact for Customers
16
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Combinatory Metrics Cause - Effect Analysis
Correlation Matrix (QFD)
Deliverable Impact on Customers Success Factors
= strong relationship
= medium relationship
= weak relationship
17
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Goal Goal
Customers
Needs
Market
Segments
Start Start
Product
Features
Acceptance
Competition
Cause - Effect
Measurement
Dependency
New Lanchester:
Who wins?
Perceived
Solution
Development
Processes
Combinator
Deciders Deciders
Realizators Realizators
Customer
Feedback
Evaluation
Competitive
Analysis
Usability Test:
How are we
perceived by target
customers?
Enablers Enablers
Capability
Maturity
Perceived
Quality
How good
are we?
Feature Cost
Parametrics
Comprehensive QFD for Software
18
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Goal Goal
Customers
Needs
Market
Segments
Usability Test:
How are we
perceived by target
customers?
Start Start
Acceptance
Competition
Cause - Effect
Measurement
Dependency
New Lanchester:
Who wins?
Perceived
Solution
Development
Processes
Perceived
Quality
Combinator
Enablers Enablers
Deciders Deciders
Realizators Realizators
Customer
Feedback
Evaluation
Competitive
Analysis
Capability
Maturity
How good
are we?
Product
Features
Parametrics
0
11
22
33
44
126 176 226 276 326 376 426 476 526 576
151 201 251 301 351 401 451 501 551
Hours (in K) New Functions
User Range
Feature Cost
Comprehensive QFD for Software
19
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Profil Customer's Needs
Customer' s Needs
S
a
l
e
s
P
o
i
n
t
s
R
e
a
d
y
T
o
P
a
y
C
o
m
p
e
t
i
t
i
o
n
C
u
s
t
o
m
e
r
S
e
g
m
e
n
t
s
M
a
n
a
g
e
m
e
n
t
A
d
j
u
s
t
m
e
n
t
s
Profile 2 2 5 3
CN-F Function a.1 Competency to answer inquiries 5.0 25 5.0 5.0 5.0 5.0
a.2 Confidentiality 3.8 19 1.7 4.0 4.5 3.9
a.3 Suitability for business needs 4.1 20 2.8 3.0 4.8 4.4
CN-Q Quality a.4 Short Development Cycles 3.9 20 5.0 5.0 3.0 4.1
a.5 Functionality where you need it 3.6 18 4.6 3.0 4.2 2.5
a.6 Social competency 3.8 19 3.8 2.0 4.5 4.0
a.7 Communication 4.3 21 4.0 4.0 4.8 3.8
25
Solution Approach
Customers
Needs
VoC
New
Lanchester
Kano
Solution
Approach
Note:
o Agile Programming
o Mechanism for
adding priorities
o Discussion Forum
What are the capabilities
needed to meet those
customers needs?
Solution Characteristics
SC-S Interfaces
b.1 Browser Style GUI
b.2 Keep to XSQL Standard
b.3 Open Interfaces
SC-D Development
b.4 Agile Programming
b.5 Reusable classes
b.6 Customer's Priorities for Extensions
SC-M Management
b.7 Active Portfolio Management
b.8 Reliable Functionality
b.9 Moderated Discussion Forum
20
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Solution Characteristics
B
r
o
w
s
e
r
S
t
y
l
e
G
U
I
K
e
e
p
t
o
X
S
Q
L
S
t
a
n
d
a
r
d
O
p
e
n
I
n
t
e
r
f
a
c
e
s
A
g
i
l
e
P
r
o
g
r
a
m
m
i
n
g
R
e
u
s
a
b
l
e
c
l
a
s
s
e
s
C
u
s
t
o
m
e
r
'
s
P
r
i
o
r
i
t
i
e
s
f
o
r
E
x
t
e
n
s
i
o
n
s
A
c
t
i
v
e
P
o
r
t
f
o
l
i
o
M
a
n
a
g
e
m
e
n
t
R
e
l
i
a
b
l
e
F
u
n
c
t
i
o
n
a
l
i
t
y
M
o
d
e
r
a
t
e
d
D
i
s
c
u
s
s
i
o
n
F
o
r
u
m
E
f
f
e
c
t
i
v
e
P
r
o
f
i
l
e
(
i
)
S
e
l
e
c
t
i
o
n
C
r
i
t
e
r
i
a
Customer' s Needs
b
.
1
b
.
2
b
.
3
b
.
4
b
.
5
b
.
6
b
.
7
b
.
8
b
.
9
0
.
4
a.1 Competency to answer inquiries 5.0 167 5.0
a.2 Confidentiality 3.8 140 4.2
a.3 Suitability for business needs 4.1 E 147 4.4
a.4 Short Development Cycles 3.9 124 3.7
a.5 Functionality where you need it 3.6 E 126 3.8
a.6 Social competency 3.8 E 130 3.9
a.7 Communication 4.3 137 4.1
Raw Weight 128 104 93 143 86 118 115 114 161 161
Optimization +33 -38 -15
Solution Profile 5.0 2.0 2.9 4.4 2.7 3.7 3.6 3.1 5.0
Suitable For Measurement Sum (
i
-
i
)
2
= 0.38
Convergence Factor 0.4
P
r
o
f
i
l
e
(
i
)
0
1
2
3
4
5
0 1 2 3 4 5
Finding Solution Characteristics that meet Customers Needs
Optimum
Solution Profile x
1
Best approximation
to Goal Profile
y = (x
1
)
Distance
between
Solution
Profile and
Goal Profile
21
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Forward Planning Set Profiles for Goals Topics
Solution Characteristics (SC)
Customers Needs (CN)
Key Process Areas (KPA)
Solution Characteristics (SC)
Result: Required solution profile for
Key Process Areas (KPAs)
C
u
s
t
o
m
e
r
s
N
e
e
d
s
Solution Characteristics
S
o
l
u
t
i
o
n
C
h
a
r
a
c
t
e
r
i
s
t
i
c
s
Key Process Area
CN
SC
KPA
Solution Profile 5.0 4.7 4.2 3.9 3.5 3.5 3.4 3.3 3.0 2.7 2.2 2.1 2.1 2.0 1.5 1.5 1.4 1.3
0
1
2
3
4
5
22
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Capability Maturity Measurement
Set the goals
Use Combinatory Metrics
Measure the capability
Mind the gaps
And improve!
Top Processes Assessment
Importance Results
c.11 Software Product Engineering 5.0 4.7
c.14 Quantitative Process Management 4.7 3.2
c.12 Intergroup Coordination 4.7 2.3
c.2 Software Project Planning 4.2 3.8
c.17 Technology Change Management 4.1 3.3
c.1 Requirements Management 3.8 4.3
c.18 Process Change Management 3.3 3.5
c.9 Training Program 3.2 4.3
c.13 Peer Reviews 2.3 3.0
c.7 Organization Process Focus 1.6 1.4
c.15 Software Quality Management 1.5 1.6
c.3 Software Project Tracking and Oversight 1.4 1.2
c.6 Software Configuration Management 1.1 3.6
c.16 Defect Prevention 0.5 3.7
c.8 Organization Process Definition 0.4 1.2
c.10 Integrated Software Management 0.4 0.5
c.4 Software Subcontract Management 0.2 1.3
c.5 Software Quality Assurance 0.1 2.3
3.0 3.1
Goal Actual
The
Four Tops
The Ten
Valuable
The
Basics
S
o
f
t
w
a
r
e
P
r
o
d
u
c
t
E
n
g
i
n
e
e
r
i
n
g
I
n
t
e
r
g
r
o
u
p
C
o
o
r
d
i
n
a
t
i
o
n
T
e
c
h
n
o
l
o
g
y
C
h
a
n
g
e
M
a
n
a
g
e
m
e
n
t
P
r
o
c
e
s
s
C
h
a
n
g
e
M
a
n
a
g
e
m
e
n
t
P
e
e
r
R
e
v
i
e
w
s
S
o
f
t
w
a
r
e
Q
u
a
l
i
t
y
M
a
n
a
g
e
m
e
n
t
S
o
f
t
w
a
r
e
C
o
n
f
i
g
u
r
a
t
i
o
n
M
a
n
a
g
e
m
e
n
t
O
r
g
a
n
i
z
a
t
i
o
n
P
r
o
c
e
s
s
D
e
f
i
n
i
t
i
o
n
S
o
f
t
w
a
r
e
S
u
b
c
o
n
t
r
a
c
t
M
a
n
a
g
e
m
e
n
t
0
1
2
3
4
5
SW Development Excellence
23
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Key Process Areas Key Process Areas
Deployment
R
e
q
u
i
r
e
m
e
n
t
s
M
a
n
a
g
e
m
e
n
t
S
o
f
t
w
a
r
e
P
r
o
j
e
c
t
P
l
a
n
n
i
n
g
S
o
f
t
w
a
r
e
P
r
o
j
e
c
t
T
r
a
c
k
i
n
g
a
n
d
O
v
e
r
s
i
g
h
t
S
o
f
t
w
a
r
e
S
u
b
c
o
n
t
r
a
c
t
M
a
n
a
g
e
m
e
n
t
S
o
f
t
w
a
r
e
Q
u
a
l
i
t
y
A
s
s
u
r
a
n
c
e
S
o
f
t
w
a
r
e
C
o
n
f
i
g
u
r
a
t
i
o
n
M
a
n
a
g
e
m
e
n
t
O
r
g
a
n
i
z
a
t
i
o
n
P
r
o
c
e
s
s
F
o
c
u
s
O
r
g
a
n
i
z
a
t
i
o
n
P
r
o
c
e
s
s
D
e
f
i
n
i
t
i
o
n
T
r
a
i
n
i
n
g
P
r
o
g
r
a
m
I
n
t
e
g
r
a
t
e
d
S
o
f
t
w
a
r
e
M
a
n
a
g
e
m
e
n
t
S
o
f
t
w
a
r
e
P
r
o
d
u
c
t
E
n
g
i
n
e
e
r
i
n
g
I
n
t
e
r
g
r
o
u
p
C
o
o
r
d
i
n
a
t
i
o
n
P
e
e
r
R
e
v
i
e
w
s
Q
u
a
n
t
i
t
a
t
i
v
e
P
r
o
c
e
s
s
M
a
n
a
g
e
m
e
n
t
S
o
f
t
w
a
r
e
Q
u
a
l
i
t
y
M
a
n
a
g
e
m
e
n
t
D
e
f
e
c
t
P
r
e
v
e
n
t
i
o
n
T
e
c
h
n
o
l
o
g
y
C
h
a
n
g
e
M
a
n
a
g
e
m
e
n
t
P
r
o
c
e
s
s
C
h
a
n
g
e
M
a
n
a
g
e
m
e
n
t
E
f
f
e
c
t
i
v
e
P
r
o
f
i
l
e
(
i
)
Solution Characteristics
c
.
1
c
.
2
c
.
3
c
.
4
c
.
5
c
.
6
c
.
7
c
.
8
c
.
9
c
.
1
0
c
.
1
1
c
.
1
2
c
.
1
3
c
.
1
4
c
.
1
5
c
.
1
6
c
.
1
7
c
.
1
8
0
.
8
1
.
0
b.1 Browser Style GUI 5.0 E 214 4.2 226 4.6
b.2 Keep to XSQL Standard 2.0 99 1.9 112 2.3
b.3 Open Interfaces 2.9 128 2.5 146 3.0
b.4 Agile Programming 4.4 254 5.0 244 5.0
b.5 Reusable classes 2.7 157 3.1 182 3.7
b.6 Customer's Priorities for Extensions 3.7 206 4.1 199 4.1
b.7 Active Portfolio Management 3.6 214 4.2 218 4.5
b.8 Reliable Functionality 3.1 167 3.3 178 3.6
b.9 Moderated Discussion Forum 5.0 245 4.8 237 4.9
Measurement 4.3 3.5 1.2 1.9 3.0 2.0 2.1 3.2 4.3 2.8 4.7 4.3 2.0 3.2 4.3 2.0 2.6 2.0
Raw Weight 144 109 119 92 99 105 120 138 137 146 195 104 88 133 131 81 105 81 195
Optimization +20 +20 -70 -35 -45 -45 -40 -30 +80 +20
Solution Profile 4.2 3.3 1.3 1.5 1.4 1.5 2.0 3.5 3.5 3.0 5.0 4.7 2.2 3.4 3.9 2.1 2.7 2.1
Sum (
i
-
i
)
2
= 1.88
Convergence Factor 0.8
Sum (i-
i
)
2
= 2.99
Effect. Deviation 1.0
Sum of (
i
-
i
)
2
= 1.15
Process Maturity Gap 0.6
G
o
a
l
P
r
o
f
i
l
e
(
i
)
T
o
t
a
l
M
e
a
s
u
r
e
d
I
m
p
a
c
t
(
i
)
0
1
2
3
4
5
0 1 2 3 4 5
Cause- Effect Rel ati onshi p
Strong 9
Medi um 3
E Weak 1
Deployment and Combinatory Metrics for Key Process Areas
Thats how well we meet
solution characteristics
y
2
= (x
2
)
Measured
Maturity
Profile x
2
Optimum
Maturity
Profile x
1
24
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Backward Controlling
Matrices in the reverse order
What Customers Needs can we fulfill
with such Solution Characteristics?
What Solution Characteristics can we
achieve with such KPA capability?
Metrics
For Key Process Area deployment:
C
u
s
t
o
m
e
r
s
N
e
e
d
s
Solution Characteristics
S
o
l
u
t
i
o
n
C
h
a
r
a
c
t
e
r
i
s
t
i
c
s
Key Process Area
CN
SC
KPA
Sum (
i
-
i
)
2
= 1.88
Convergence Factor 0.8
Sum (i-
i
)
2
= 2.99
Effect. Deviation 1.0
Sum of (
i
-
i
)
2
= 1.15
Process Maturity Gap 0.6
25
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Six Sigma Metrics For Software
Convergence Factor
Tells you how good your QFD is
How well the solution matches the goal topic
Effective Deviation
Tells you how well you are doing
If youre doing the right things
Process Maturity Gap
Tells you if you do things right
Related to, but not equal to CMM scale
Sum (
i
-
i
)
2
= 1.88
Convergence Factor 0.8
Sum (i-
i
)
2
= 2.99
Effect. Deviation 1.0
Sum of (
i
-
i
)
2
= 1.15
Process Maturity Gap 0.6
26
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Combinatory Metrics Matrix with Measurement
Solution Characteristics
B
r
o
w
s
e
r
S
t
y
l
e
G
U
I
K
e
e
p
t
o
X
S
Q
L
S
t
a
n
d
a
r
d
O
p
e
n
I
n
t
e
r
f
a
c
e
s
A
g
i
l
e
P
r
o
g
r
a
m
m
i
n
g
R
e
u
s
a
b
l
e
c
l
a
s
s
e
s
C
u
s
t
o
m
e
r
'
s
P
r
i
o
r
i
t
i
e
s
f
o
r
E
x
t
e
n
s
i
o
n
s
A
c
t
i
v
e
P
o
r
t
f
o
l
i
o
M
a
n
a
g
e
m
e
n
t
R
e
l
i
a
b
l
e
F
u
n
c
t
i
o
n
a
l
i
t
y
M
o
d
e
r
a
t
e
d
D
i
s
c
u
s
s
i
o
n
F
o
r
u
m
E
f
f
e
c
t
i
v
e
P
r
o
f
i
l
e
(
i
)
S
e
l
e
c
t
i
o
n
C
r
i
t
e
r
i
a
Customer' s Needs
b
.
1
b
.
2
b
.
3
b
.
4
b
.
5
b
.
6
b
.
7
b
.
8
b
.
9
0
.
4
0
.
7
a.1 Competency to answer inquiries 5.0 167 5.0 177 5.0
a.2 Confidentiality 3.8 140 4.2 157 4.4
a.3 Suitability for business needs 4.1 E 147 4.4 169 4.8
a.4 Short Development Cycles 3.9 124 3.7 138 3.9
a.5 Functionality where you need it 3.6 E 126 3.8 135 3.8
a.6 Social competency 3.8 E 130 3.9 141 4.0
a.7 Communication 4.3 137 4.1 141 4.0
Measurement 4.6 2.3 3.0 5.0 3.7 4.1 4.5 3.6 4.9
Raw Weight 128 104 93 143 86 118 115 114 161 161
Optimization +33 -38 -15
Solution Profile 5.0 2.0 2.9 4.4 2.7 3.7 3.6 3.1 5.0
Sum (
i
-
i
)
2
= 0.38
Suitable For Measurement Convergence Factor 0.4
Sum (i-
i
)
2
= 1.07
Effect. Deviation 0.7
Sum of (
i
-
i
)
2
= 0.25
Process Maturity Gap 0.4
G
o
a
l
P
r
o
f
i
l
e
(
i
)
M
e
a
s
u
r
e
d
I
m
p
a
c
t
(
i
)
0
1
2
3
4
5
0 1 2 3 4 5
Thats how well
we fulfill customers
needs: z = (y
2
)
i
= a
i,j
*
j
Measured
Solution Profile y
2
27
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Combinatory Metrics Three Metrics for Success
Solution Characteristics
B
r
o
w
s
e
r
S
t
y
l
e
G
U
I
K
e
e
p
t
o
X
S
Q
L
S
t
a
n
d
a
r
d
O
p
e
n
I
n
t
e
r
f
a
c
e
s
A
g
i
l
e
P
r
o
g
r
a
m
m
i
n
g
R
e
u
s
a
b
l
e
c
l
a
s
s
e
s
C
u
s
t
o
m
e
r
'
s
P
r
i
o
r
i
t
i
e
s
f
o
r
E
x
t
e
n
s
i
o
n
s
A
c
t
i
v
e
P
o
r
t
f
o
l
i
o
M
a
n
a
g
e
m
e
n
t
R
e
l
i
a
b
l
e
F
u
n
c
t
i
o
n
a
l
i
t
y
M
o
d
e
r
a
t
e
d
D
i
s
c
u
s
s
i
o
n
F
o
r
u
m
E
f
f
e
c
t
i
v
e
P
r
o
f
i
l
e
(
i
)
S
e
l
e
c
t
i
o
n
C
r
i
t
e
r
i
a
Customer' s Needs
b
.
1
b
.
2
b
.
3
b
.
4
b
.
5
b
.
6
b
.
7
b
.
8
b
.
9
0
.
4
0
.
7
a.1 Competency to answer inquiries 5.0 167 5.0 177 5.0
a.2 Confidentiality 3.8 140 4.2 157 4.4
a.3 Suitability for business needs 4.1 E 147 4.4 169 4.8
a.4 Short Development Cycles 3.9 124 3.7 138 3.9
a.5 Functionality where you need it 3.6 E 126 3.8 135 3.8
a.6 Social competency 3.8 E 130 3.9 141 4.0
a.7 Communication 4.3 137 4.1 141 4.0
Measurement 4.6 2.3 3.0 5.0 3.7 4.1 4.5 3.6 4.9
Raw Weight 128 104 93 143 86 118 115 114 161 161
Optimization +33 -38 -15
Solution Profile 5.0 2.0 2.9 4.4 2.7 3.7 3.6 3.1 5.0
Sum (
i
-
i
)
2
= 0.38
Suitable For Measurement Convergence Factor 0.4
Sum (i-
i
)
2
= 1.07
Effect. Deviation 0.7
Sum of (
i
-
i
)
2
= 0.25
Process Maturity Gap 0.4
G
o
a
l
P
r
o
f
i
l
e
(
i
)
M
e
a
s
u
r
e
d
I
m
p
a
c
t
(
i
)
0
1
2
3
4
5
0 1 2 3 4 5
Effective
Deviation
Convergence Factor
Process
Maturity Gap
28
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Six Steps to Six Sigma for Software
1. WHAT is Six Sigma? Does it apply to software?
2. WHY do we need Six Sigma For Software?
3. HOW do you implement Six Sigma in the workplace? Can the
theory really be put into practice?
4. WHERE has Six Sigma been applied successfully? Are there
success stories in software, and in which companies?
5. WHEN should Six Sigma be used? How does it fit into a Software
Development and Deployment project?
6. WHO can make an impact using Six Sigma? What are the
organizational and skills requirements? How does it fit into your
Six Sigma program?
29
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
A Case Study
Small niche company
Software for business communications
Worldwide market
Serving businesses with large customer bases
Limited resources
Customer Orientation
Metrics Approach
Target: CMM 4 for software development
o I.e. development processes managed by metrics
Big Vision
http://www.gmc.net/
30
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Capability Maturity Measurement
The real case
GMC Software Technology
Software process improvement
since Dec. 2000
Now ISO 9001:2000 certificate!
Key Processes
Importance
The Four Tops
PL-1.1 Customer's Needs 5.00 4.10 1.20
PL-2.0 New Feature Request 4.90 4.08 -
PL-2.2 Detailed Design 4.47 2.08 1.59
PL-2.3 Implementation 4.42 3.62 1.95
The Ten Valuable
PL-1.3 New Market Requirement 4.28 3.76 1.59
PL-6.5 Beta Release Test 4.24 3.37 -
PL-5.9 Customer Release 3.80 2.98 -
PL-3.4 User Training 3.78 2.56 -
PL-4.4 Issue Management 3.73 3.05 -
PL-6.4 Code Review 3.72 2.58 1.95
PL-6.8 Acceptance Testing 3.70 3.10 1.17
PL-6.2 Alpha - Internal Test 3.52 3.82 -
PL-2.4 Release Planning 3.49 3.19 1.95
PL-7.1 Configuration Management 3.48 3.00 1.18
The Basics
PL-4.2 Hot Fix 3.41 3.02 -
PL-8.7 Partner Strategy 3.40 2.57 1.36
PL-7.6 Knowledge Repository 3.39 2.80 -
PL-1.2 Project Proposal 3.34 3.21 1.20
PL-8.1 Audits 3.12 2.40 -
4.04 3.12 1.57
Goal 09/2003 12/2000
Maturity
C
u
s
t
o
m
e
r
'
s
N
e
e
d
s
N
e
w
F
e
a
t
u
r
e
R
e
q
u
e
s
t
D
e
t
a
i
l
e
d
D
e
s
i
g
n
I
m
p
l
e
m
e
n
t
a
t
i
o
n
N
e
w
M
a
r
k
e
t
R
e
q
u
i
r
e
m
e
n
t
B
e
t
a
R
e
l
e
a
s
e
T
e
s
t
C
u
s
t
o
m
e
r
R
e
l
e
a
s
e
U
s
e
r
T
r
a
i
n
i
n
g
I
s
s
u
e
M
a
n
a
g
e
m
e
n
t
C
o
d
e
R
e
v
i
e
w
A
c
c
e
p
t
a
n
c
e
T
e
s
t
i
n
g
A
l
p
h
a
-
I
n
t
e
r
n
a
l
T
e
s
t
R
e
l
e
a
s
e
P
l
a
n
n
i
n
g
C
o
n
f
i
g
u
r
a
t
i
o
n
M
a
n
a
g
e
m
e
n
t
H
o
t
F
i
x
P
a
r
t
n
e
r
S
t
r
a
t
e
g
y
K
n
o
w
l
e
d
g
e
R
e
p
o
s
i
t
o
r
y
P
r
o
j
e
c
t
P
r
o
p
o
s
a
l
A
u
d
i
t
s
0
1
2
3
4
5
SW Development Excellence
31
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Competitive Advantage Customer' s Business Obj ectives
S
u
p
p
o
r
t
E
x
i
s
t
i
n
g
B
u
s
i
n
e
s
s
A
p
p
l
i
c
a
t
i
o
n
s
A
d
a
p
t
s
t
o
N
e
w
B
u
s
i
n
e
s
s
A
p
p
l
i
c
a
t
i
o
n
s
I
n
t
e
g
r
a
t
e
s
a
n
d
c
o
m
p
l
e
m
e
n
t
s
o
t
h
e
r
c
o
m
m
u
n
i
c
a
t
i
o
n
c
h
a
n
n
e
l
s
A
t
t
r
a
c
t
s
N
e
w
C
u
s
t
o
m
e
r
S
e
g
m
e
n
t
s
G
e
t
t
i
n
g
S
t
a
r
t
e
d
w
i
t
h
P
r
i
n
t
N
e
t
T
I
m
p
o
r
t
f
r
o
m
O
t
h
e
r
F
o
r
m
a
t
s
&
L
e
g
a
c
y
A
p
p
l
i
c
a
t
i
o
n
I
n
p
u
t
D
a
t
a
D
e
s
i
g
n
&
C
o
m
p
o
s
i
t
i
o
n
P
r
o
d
u
c
t
i
o
n
J
o
b
F
l
o
w
O
u
t
p
u
t
f
o
r
V
a
r
i
o
u
s
M
e
d
i
a
R
e
d
u
c
e
D
e
p
e
n
d
e
n
c
y
f
r
o
m
I
T
D
e
p
a
r
t
m
e
n
t
O
r
d
e
r
M
a
n
a
g
e
m
e
n
t
S
y
s
t
e
m
M
a
n
a
g
e
m
e
n
t
R
e
t
u
r
n
o
n
I
n
v
e
s
t
m
e
n
t
Competition
C
B
O
-
1
.
1
C
B
O
-
1
.
2
C
B
O
-
1
.
3
C
B
O
-
1
.
4
C
B
O
-
2
.
1
C
B
O
-
2
.
2
C
B
O
-
3
.
1
C
B
O
-
3
.
2
C
B
O
-
3
.
3
C
B
O
-
3
.
4
C
B
O
-
3
.
5
C
B
O
-
4
.
1
C
B
O
-
4
.
2
C
B
O
-
4
.
3
Rating Relative
PrintNet T 1 6 9 8 8 7 5 9 9 9 6 9 8 4 8 112 1
Competition 1 2 8 5 6 5 5 5 4 4 4 6 3 5 6 7
144 2
Competition 2 3 7 5 7 5 5 3 3 3 4 8 1 5 5 6 202 3
Competition 3 1 8 5 7 5 5 4 3 3 4 8 1 5 5 6 98 1
Competition 4 2 8 5 6 5 5 4 3 3 4 6 3 5 4 7 136 2
Competition 5 2 5 5 4 4 5 5 5 5 6 7 3 7 5 6 143 2
Competition 6 4 8 6 7 5 5 7 7 7 6 7 2 6 5 5 333 4
Competition 7 4 6 6 8 7 7 6 8 8 7 8 8 7 4 5 379 5
Competition 8 3 8 5 6 4 3 5 6 6 6 6 2 5 7 5 223 3
Solution Characteristics Weight Factors 3 3 3 5 5 4 3 4 5 3 3 2 5 4
Our Weight 16 28 26 36 32 18 29 34 44 19 31 18 20 35 1 44
Competition Weight 20 17 22 23 23 18 17 20 26 23 11 14 25 25 21 26 44
Our Achievement 1-5 Scale 2 3 3 4 4 2 3 4 5 2 4 2 2 4 44 1 1895
Competition's Achievement 1-5 Scale 2 2 2 3 3 2 2 2 3 3 1 2 3 3 32 0 1022
(relative to Weapon's Strength) Better than the Competition 36% E
2
= 1.85
Competition: yellow
Our Solution.: green
M
a
r
k
e
t
S
h
a
r
e
W
e
i
g
h
t
0 1 2 3 4 5
0
1
2
3
4
5
New Lanchester Measurements
With New
Lanchester you
measure the
strength of
your weapons"
Perceived
features
How well
you meet
customers
needs
GMC experienced
2003 30% growth
and significant
market share gains
Better than the Competition 36%
32
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Sum (
i
-
i
)
2
= 2.54
Convergence Factor 0.9
Sum (i-
i
)
2
= 8.07
Effect. Deviation 1.6
Sum of (
i
-
i
)
2
= 5.04
Process Maturity Gap 1.2
Feature Cost Deployment and Measurement
Parametrics
Parameter-driven cost model
Identifies and analyzes feature cost
Combinatory Metrics
Cost Drivers
Product Features
Customers Needs
Which target costing meets customers
needs?
How well is our actual costing?
Cost Drivers
CN
PF
CD
P
r
o
d
u
c
t
F
e
a
t
u
r
e
s
C
u
s
t
o
m
e
r
s
N
e
e
d
s
Product Features
33
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Six Steps to Six Sigma for Software
1. WHAT is Six Sigma? Does it apply to software?
2. WHY do we need Six Sigma For Software?
3. HOW do you implement Six Sigma in the workplace? Can the
theory really be put into practice?
4. WHERE has Six Sigma been applied successfully? Are there
success stories in software, and in which companies?
5. WHEN should Six Sigma be used? How does it fit into a Software
Development and Deployment project?
6. WHO can make an impact using Six Sigma? What are the
organizational and skills requirements? How does it fit into your
Six Sigma program?
34
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Experiences
Used since 1998 for
Airline Service
E-Banking service
Software
Development
IT Service
Deployment
Top-of-the-art
Business
Communications
35
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Experiences
Advantages
Project ends in time &
budget
No project stops
Customers see
improvement
Early warning
Enables management
control
Transparency
Disadvantages
Cultural Change
Management becomes
measurable
People fear loss of
creativity
Requires innovation
management
No hideouts
36
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Experiences
Sigma Level Reached
Airline Service: 3.1
Columbus (bank): 2.8
IT Service (bank): 1.8
GMC: 1.5 3.3
CMM Level
N/A
Between 0.8 and 2.6
1.4
1.8 3.2
37
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Six Steps to Six Sigma for Software
1. WHAT is Six Sigma? Does it apply to software?
2. WHY do we need Six Sigma For Software?
3. HOW do you implement Six Sigma in the workplace? Can the
theory really be put into practice?
4. WHERE has Six Sigma been applied successfully? Are there
success stories in software, and in which companies?
5. WHEN should Six Sigma be used? How does it fit into a Software
Development and Deployment project?
6. WHO can make an impact using Six Sigma? What are the
organizational and skills requirements? How does it fit into your
Six Sigma program?
38
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Role of the Project Office
You need dedicated experts who have the necessary
measurement skills
To effectively measure
To provide the metrics
Using tools like QFD, New Lanchester, Function Points
These experts constitute the Project Office
They must not be dependent from neither
Supplier, nor
Customer
39
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
The Role of the Project Office
Customer Supplier
Project Responsible
of Customer
Project Responsible
of Customer
Project Leader
Supplier
Project Leader
Supplier
e.g.
User Representative
e.g.
User Representative
e.g.
Parameter adaptation
e.g.
Parameter adaptation
e.g.
IT Representative
e.g.
IT Representative
e.g.
Training
e.g.
Training
e.g. Subcontractor
standard application
e.g. Subcontractor
standard application
e.g. Subcontractor
for technology
e.g. Subcontractor
for technology
Customer Management
Purchasing
Controlling
Customer Management
Purchasing ng
Controlling
Supplier Management
Account Manager
Practice Mgmt
Competence Centers
Supplier Management
Account Manager
Practice Mgmt
Competence Centers
Steering Committee
Project sponsor
Management
Steering Committee
Project sponsor
Management
e.g.
Implementation Team
e.g.
Implementation Team
e.g. Business Process
Owner
e.g. Business Process
Owner
Project Manager
Project administration
Project Manager
Project administration
40
Success
for your
project
Proposal
Management
Product
Development
Project
Office
Supplier
Management
Change
Management
Conclusion
Creating Software has become even more important. But
the focus changes from bug free kernel functionality to
usefulness business functionality
Six Sigma for Software implementation relies on ICT
Project Management and software process improvement
Six Sigma brings major benefits
For ICT Software and Services
Cost engineering provides maximum value for customers
The key to measurements are Combinatory Metrics