SlideShare a Scribd company logo
1 of 40
Putnam’s Effort-Duration Trade-Off Law: Is the 
Software Estimation Problem Really Solved? 
Han Suelmann 
October 7th, 2014
Putnam’s study – reference 
L.H. Putnam, 
“A generic empirical solution to the macro software sizing 
and estimating problem,” 
IEEE Transactions on Software Engineering, 
vol. 4, pages 345 ─ 361, 
July 1978. 
2
3
Agenda 
• Putnam’s study: results and influence 
• Putnam’s approach 
• Intermezzo – A statistical pitfall 
• Critical evaluation: 
o dataset is very limited 
o model and assumptions are unclear 
o analysis is incorrect 
• Other studies provide no corroboration 
• Simulation study demonstrate incorrectness 
5
6
Putnam’s study: results and influence 
Claims: 
• Generic empirical equations that describe size – effort – 
duration relationships. 
• Method will produce accurate estimates. 
• Only a few quick reference tables and a pocket calculator 
needed. 
• Trade-off law: K ~ 1 / T4. 
7
Putnam’s study is very influential 
Influence: 
• incorporated in estimation software 
• many references 
• sometimes cited as authoritative 
8
Putnam’s approach 
1) Gather data on effort (K), duration (T) and size (S). 
2) Define difficulty: D = K / T 2 
3) Define productivity: P = S / K 
4) Find relationship between D and P. 
Result: P ~ D -0.67 
5) Perform basic algebraic manipulations to find 
relationships between S, T, and K. 
Result: S = C ∙ K1/3 ∙ T4/3, 
3 
S 
and therefore: . 
9 
4 
T 
K 
The crucial relationship… 
10 
K 
2 T 
D  
S 
K 
P  
difficulty 
productivity
Putnam’s approach 
1) Gather data on effort (K), duration (T) and size (S). 
2) Define difficulty: D = K / T 2 
3) Define productivity: P = S / K 
4) Find relationship between D and P. 
Result: P ~ D -0.67 
5) Perform basic algebraic manipulations to find 
relationships between S, T, and K. 
Result: S = C ∙ K1/3 ∙ T4/3, 
3 
S 
and therefore: . 
11 
4 
T 
K 
Intermezzo – A statistical pitfall 
• Two researchers examine relationship between S and K. 
• Both assume linear relationship. 
• Researcher 1 writes K = aS + b 
• Researcher 2 writes S = a’K + b’ 
12 
S 
K 
S 
K
Researcher 2’s does his linear fit
Intermezzo – The results are quite different 
• Researcher 1 writes K = aS + b and finds 
(1) K = 1.01 S −0.02. 
• Researcher 2 writes S = a’K + b’ and finds 
(2) S = 0.50 K + 3.0. 
• Researcher 2 then derives 
(3) K = 2.02 S – 6.2. 
14
Researcher 1: does her fit
Intermezzo – A statistical pitfall 
• Researcher 1 writes K = aS + b and finds 
(1) K = 1.01 S −0.02. 
• Researcher 2 writes S = a’K + b’ and finds 
(2) S = 0.50 K + 3.0. 
• 
Researcher 2 then derives 
(3) K = 2.02 S – 6.2. 
16 
^ 
^ 
^
Linear fit: minimising least squares 
S 
K
Critical evaluation (1) – dataset is very limited 
• only 13 projects 
• all US Military 
• 4 are left out => 9 projects remaining 
18
Critical evaluation (2) – model is unclear 
19 
size 
duration 
effort 
 Putnam does not make clear and consistent 
choices regarding model structure. 
 Only one parameter to capture effort-duration 
interaction
Critical evaluation (3) – analysis 
20
Critical evaluation (3) – analysis 
21
Critical evaluation (3) – analysis 
22
Critical evaluation (3) – analysis 
23
Critical evaluation (3) – analysis 
24
Critical evaluation (4): 
Difficulty – Productivity relationship 
Putnam’s reasoning: 
More precisely notated: 
25 
2/3 P D 
 
 
 
K 
S 
1/3 4/3 S  K T 
ˆ 2/3 P  D 
ˆ ˆ 2/3 4/3 ??    S K K T 
2/3 
2 
 
 
 
 
 
T 
K
Other studies − Corroboration by Putnam et al. 
Putnam & Putnam, “A data verification of the software fourth 
power trade-off law,” (Proc. of the Int. Soc. of Parametric Analysts – 6th Annu. 
Conf., vol. III(I), pp. 443–471, 1984.) 
Putnam & Myers, “Measures for excellence – Reliable 
software on time, within budget”, (Englewood Cliffs: Yourdon, 1992.) 
Confirmed that K ~ 1 / T4, but… 
Found (Dunsmore et al., 1986) and admitted (Putnam & 
Myers, n.d.) to be based on circular reasoning. 
26
Other studies – No corroboration from Jeffery 
Jeffery (1987): 
• 47 MIS in 4 large organisations 
• Find P as a function of K and T. 
Result: 
• P ~ K−0.47T −0.05 
• essentially no productivity – duration relationship 
• comparison with Putnam’s P ~ K−0.67T 1.33 
• no confirmation 
• strictly speaking: no refutation either 
27
Other studies – No corroboration from 
Barry, Mukhopadhyay, and Slaughter 
Barry, Mukhopadhyay, and Slaughter (2002): 
Ansatz: ln K = … + β1 T 
Result: β1 = 0.000677 ± 0.000103, p = .031. 
So – larger duration predicts larger effort. 
28
Other studies – Team size affects effort, so…? 
Putnam & Myers (n.d.): larger team size predicts larger 
effort: 
Teams of 5 or less have better productivity than teams of 20 
or more. 
Supported by other studies. Example (Rodríguez et al.): 
PDR ~ (average team size)^0.57 
But… 
• translation to effort-duration trade-off unclear 
• interpretation in terms of causation dubious 
29
Several interpretations are possible… 
30 
larger 
team size 
more 
effort
Simulation (1) 
Goal: check whether the analysis issues really lead to 
incorrect results. 
Method: 
• generate simulated data with known structure 
• analyze simulated data, following Putnam’s approach 
• check whether results are consistent with assumptions 
31
Simulation (2) 
Model assumptions: 
• Size, effort, and duration are unrelated random numbers. 
• Log-normal distributions. 
• 1000 projects. 
32
Simulation (3) – analysis 
33
34 
K 
2 T 
D  
S 
K 
P 
Simulation (4) – result 
Fit yields: 
ln P  0.67ln Dconstant 
After transformation: 
After some manipulations (same as Putnam’s): 
K Yet, no 
35 
0.670.02 P  D 
1 
  
4.1 0.4 
T 
relationship 
actually exists!
Simulation (5) – coincidence? 
For convenience, write s = ln S, k = ln K, and t = ln T. 
Difficulty and productivity: 
• ln D = k – 2t 
• ln P = s – k 
Derive the slope of P against D: 
D P 
cov(ln , ln ) 
2 
 
 
k 
 
(ln | ln ) 2 2 
Follow Putnam closely, finding K ~ T u , with 
 
  which yields u = − 4 if  8 
36 
. 
var(ln ) 4 
k t 
D 
B P D 
  
  
2 
2 
 
u 
1 
k 2 
 
t 
k 
 
t
Simulation (6) – result 
37 
 S K 
Conclusions 
38 
Claims: 
• Generic equations that 
describe size – effort – 
duration relationships. 
• Method will produce 
accurate estimates. 
• Trade-off law: K ~ 1 / T4. 
Limited dataset, 
no corroboration 
Not addressed 
Faulty analysis, 
no corroboration
Conclusion 
39 
No credibility for 
Putnam’s result 
Putnam’s 
original study 
was wrong 
No 
corroboration
The bad news 
• Handling statistical 
relationships as if exact. 
• Interpreting statistical 
relationship as causal 
relationships without 
sufficient support. 
40 
Both issues are 
rather common in 
the estimation / 
metrics literature.
Question time

More Related Content

Similar to Iwsm2014 putnam revisited (han suelmann) for publication

LINEAR SEARCH VERSUS BINARY SEARCH: A STATISTICAL COMPARISON FOR BINOMIAL INPUTS
LINEAR SEARCH VERSUS BINARY SEARCH: A STATISTICAL COMPARISON FOR BINOMIAL INPUTSLINEAR SEARCH VERSUS BINARY SEARCH: A STATISTICAL COMPARISON FOR BINOMIAL INPUTS
LINEAR SEARCH VERSUS BINARY SEARCH: A STATISTICAL COMPARISON FOR BINOMIAL INPUTSIJCSEA Journal
 
similarity measure
similarity measure similarity measure
similarity measure ZHAO Sam
 
S1 - Process product optimization using design experiments and response surfa...
S1 - Process product optimization using design experiments and response surfa...S1 - Process product optimization using design experiments and response surfa...
S1 - Process product optimization using design experiments and response surfa...CAChemE
 
dimensional_analysis.pptx
dimensional_analysis.pptxdimensional_analysis.pptx
dimensional_analysis.pptxDinaSaad22
 
Size Measurement and Estimation
Size Measurement and EstimationSize Measurement and Estimation
Size Measurement and EstimationLouis A. Poulin
 
Tutorial: Context In Recommender Systems
Tutorial: Context In Recommender SystemsTutorial: Context In Recommender Systems
Tutorial: Context In Recommender SystemsYONG ZHENG
 
Class X Mathematics Study Material
Class X Mathematics Study MaterialClass X Mathematics Study Material
Class X Mathematics Study MaterialFellowBuddy.com
 
(L5)(U3)Laws of Algebra of Propositions.pdf
(L5)(U3)Laws of Algebra of Propositions.pdf(L5)(U3)Laws of Algebra of Propositions.pdf
(L5)(U3)Laws of Algebra of Propositions.pdfSumitSrivastava631987
 
3 --graphing
3  --graphing3  --graphing
3 --graphingmjalexlee
 
Parallel Algorithms K – means Clustering
Parallel Algorithms K – means ClusteringParallel Algorithms K – means Clustering
Parallel Algorithms K – means ClusteringAndreina Uzcategui
 
Master Thesis Defense
Master Thesis DefenseMaster Thesis Defense
Master Thesis DefenseFilipo Mór
 
The t Test for Two Related Samples
The t Test for Two Related SamplesThe t Test for Two Related Samples
The t Test for Two Related Samplesjasondroesch
 
22_RepeatedMeasuresDesign_Complete.pptx
22_RepeatedMeasuresDesign_Complete.pptx22_RepeatedMeasuresDesign_Complete.pptx
22_RepeatedMeasuresDesign_Complete.pptxMarceloHenriques20
 
Chemistry t1
Chemistry t1Chemistry t1
Chemistry t1enpi275
 
1_--_sci_method.ppt
1_--_sci_method.ppt1_--_sci_method.ppt
1_--_sci_method.pptMervatMarji2
 
t-tests in R - Lab slides for UGA course FANR 6750
t-tests in R - Lab slides for UGA course FANR 6750t-tests in R - Lab slides for UGA course FANR 6750
t-tests in R - Lab slides for UGA course FANR 6750richardchandler
 
Presentation on Computational fluid dynamic smulation and benchmarking a dess...
Presentation on Computational fluid dynamic smulation and benchmarking a dess...Presentation on Computational fluid dynamic smulation and benchmarking a dess...
Presentation on Computational fluid dynamic smulation and benchmarking a dess...kush verma
 

Similar to Iwsm2014 putnam revisited (han suelmann) for publication (20)

LINEAR SEARCH VERSUS BINARY SEARCH: A STATISTICAL COMPARISON FOR BINOMIAL INPUTS
LINEAR SEARCH VERSUS BINARY SEARCH: A STATISTICAL COMPARISON FOR BINOMIAL INPUTSLINEAR SEARCH VERSUS BINARY SEARCH: A STATISTICAL COMPARISON FOR BINOMIAL INPUTS
LINEAR SEARCH VERSUS BINARY SEARCH: A STATISTICAL COMPARISON FOR BINOMIAL INPUTS
 
similarity measure
similarity measure similarity measure
similarity measure
 
S1 - Process product optimization using design experiments and response surfa...
S1 - Process product optimization using design experiments and response surfa...S1 - Process product optimization using design experiments and response surfa...
S1 - Process product optimization using design experiments and response surfa...
 
T3
T3T3
T3
 
dimensional_analysis.pptx
dimensional_analysis.pptxdimensional_analysis.pptx
dimensional_analysis.pptx
 
Size Measurement and Estimation
Size Measurement and EstimationSize Measurement and Estimation
Size Measurement and Estimation
 
Tutorial: Context In Recommender Systems
Tutorial: Context In Recommender SystemsTutorial: Context In Recommender Systems
Tutorial: Context In Recommender Systems
 
Class X Mathematics Study Material
Class X Mathematics Study MaterialClass X Mathematics Study Material
Class X Mathematics Study Material
 
(L5)(U3)Laws of Algebra of Propositions.pdf
(L5)(U3)Laws of Algebra of Propositions.pdf(L5)(U3)Laws of Algebra of Propositions.pdf
(L5)(U3)Laws of Algebra of Propositions.pdf
 
3 --graphing
3  --graphing3  --graphing
3 --graphing
 
Introduction to data mining and machine learning
Introduction to data mining and machine learningIntroduction to data mining and machine learning
Introduction to data mining and machine learning
 
Parallel Algorithms K – means Clustering
Parallel Algorithms K – means ClusteringParallel Algorithms K – means Clustering
Parallel Algorithms K – means Clustering
 
Master Thesis Defense
Master Thesis DefenseMaster Thesis Defense
Master Thesis Defense
 
The t Test for Two Related Samples
The t Test for Two Related SamplesThe t Test for Two Related Samples
The t Test for Two Related Samples
 
22_RepeatedMeasuresDesign_Complete.pptx
22_RepeatedMeasuresDesign_Complete.pptx22_RepeatedMeasuresDesign_Complete.pptx
22_RepeatedMeasuresDesign_Complete.pptx
 
Chemistry t1
Chemistry t1Chemistry t1
Chemistry t1
 
1_--_sci_method.ppt
1_--_sci_method.ppt1_--_sci_method.ppt
1_--_sci_method.ppt
 
sigir2018tutorial
sigir2018tutorialsigir2018tutorial
sigir2018tutorial
 
t-tests in R - Lab slides for UGA course FANR 6750
t-tests in R - Lab slides for UGA course FANR 6750t-tests in R - Lab slides for UGA course FANR 6750
t-tests in R - Lab slides for UGA course FANR 6750
 
Presentation on Computational fluid dynamic smulation and benchmarking a dess...
Presentation on Computational fluid dynamic smulation and benchmarking a dess...Presentation on Computational fluid dynamic smulation and benchmarking a dess...
Presentation on Computational fluid dynamic smulation and benchmarking a dess...
 

More from Nesma

2024-04 - Nesma webinar - Benchmarking.pdf
2024-04 - Nesma webinar - Benchmarking.pdf2024-04 - Nesma webinar - Benchmarking.pdf
2024-04 - Nesma webinar - Benchmarking.pdfNesma
 
Agile Team Performance Measurement webinar
Agile Team Performance Measurement webinarAgile Team Performance Measurement webinar
Agile Team Performance Measurement webinarNesma
 
Software Cost Estimation webinar January 2024.pdf
Software Cost Estimation webinar January 2024.pdfSoftware Cost Estimation webinar January 2024.pdf
Software Cost Estimation webinar January 2024.pdfNesma
 
Nesma event June '23 - How to use objective metrics as a basis for agile cost...
Nesma event June '23 - How to use objective metrics as a basis for agile cost...Nesma event June '23 - How to use objective metrics as a basis for agile cost...
Nesma event June '23 - How to use objective metrics as a basis for agile cost...Nesma
 
Nesma event June '23 - NEN Practice Guideline - NPR.pdf
Nesma event June '23 - NEN Practice Guideline - NPR.pdfNesma event June '23 - NEN Practice Guideline - NPR.pdf
Nesma event June '23 - NEN Practice Guideline - NPR.pdfNesma
 
Nesma event June '23 - Easy Function Sizing - Introduction.pdf
Nesma event June '23 - Easy Function Sizing - Introduction.pdfNesma event June '23 - Easy Function Sizing - Introduction.pdf
Nesma event June '23 - Easy Function Sizing - Introduction.pdfNesma
 
Automotive Software Cost Estimation - The UCE Approach - Emmanuel Mary
Automotive Software Cost Estimation - The UCE Approach - Emmanuel MaryAutomotive Software Cost Estimation - The UCE Approach - Emmanuel Mary
Automotive Software Cost Estimation - The UCE Approach - Emmanuel MaryNesma
 
The COSMIC battle between David and Goliath - Paul Hussein
The COSMIC battle between David and Goliath - Paul HusseinThe COSMIC battle between David and Goliath - Paul Hussein
The COSMIC battle between David and Goliath - Paul HusseinNesma
 
Succesful Estimating - It's how you tell the story - Amritpal Singh Agar
Succesful Estimating - It's how you tell the story - Amritpal Singh AgarSuccesful Estimating - It's how you tell the story - Amritpal Singh Agar
Succesful Estimating - It's how you tell the story - Amritpal Singh AgarNesma
 
(Increasing) Predictability of large Government ICT Projects - Koos Veefkind
(Increasing) Predictability of large Government ICT Projects - Koos Veefkind(Increasing) Predictability of large Government ICT Projects - Koos Veefkind
(Increasing) Predictability of large Government ICT Projects - Koos VeefkindNesma
 
CEBoK for Software Past Present Future - Megan Jones
CEBoK for Software Past Present Future - Megan JonesCEBoK for Software Past Present Future - Megan Jones
CEBoK for Software Past Present Future - Megan JonesNesma
 
Agile Development and Agile Cost Estimation - A return to basic principles - ...
Agile Development and Agile Cost Estimation - A return to basic principles - ...Agile Development and Agile Cost Estimation - A return to basic principles - ...
Agile Development and Agile Cost Estimation - A return to basic principles - ...Nesma
 
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...Nesma
 
Project Succes is a Choice - Joop Schefferlie
Project Succes is a Choice - Joop SchefferlieProject Succes is a Choice - Joop Schefferlie
Project Succes is a Choice - Joop SchefferlieNesma
 
Afrekenen met functiepunten
Afrekenen met functiepuntenAfrekenen met functiepunten
Afrekenen met functiepuntenNesma
 
Agile teams get a grip - martijn groenewegen
Agile teams   get a grip - martijn groenewegenAgile teams   get a grip - martijn groenewegen
Agile teams get a grip - martijn groenewegenNesma
 
The fact that your poject is agile is not (necessarily) a cost driver arlen...
The fact that your poject is agile is not (necessarily) a cost driver   arlen...The fact that your poject is agile is not (necessarily) a cost driver   arlen...
The fact that your poject is agile is not (necessarily) a cost driver arlen...Nesma
 
Software sizing as an essential measure past present and future - Dan Galorat...
Software sizing as an essential measure past present and future - Dan Galorat...Software sizing as an essential measure past present and future - Dan Galorat...
Software sizing as an essential measure past present and future - Dan Galorat...Nesma
 
A benchmark based approach to determine language verbosity - Hans Kuijpers - ...
A benchmark based approach to determine language verbosity - Hans Kuijpers - ...A benchmark based approach to determine language verbosity - Hans Kuijpers - ...
A benchmark based approach to determine language verbosity - Hans Kuijpers - ...Nesma
 
Software sizing the cornerstone for iceaa's scebok - Carol Dekkers
Software sizing the cornerstone for iceaa's scebok - Carol DekkersSoftware sizing the cornerstone for iceaa's scebok - Carol Dekkers
Software sizing the cornerstone for iceaa's scebok - Carol DekkersNesma
 

More from Nesma (20)

2024-04 - Nesma webinar - Benchmarking.pdf
2024-04 - Nesma webinar - Benchmarking.pdf2024-04 - Nesma webinar - Benchmarking.pdf
2024-04 - Nesma webinar - Benchmarking.pdf
 
Agile Team Performance Measurement webinar
Agile Team Performance Measurement webinarAgile Team Performance Measurement webinar
Agile Team Performance Measurement webinar
 
Software Cost Estimation webinar January 2024.pdf
Software Cost Estimation webinar January 2024.pdfSoftware Cost Estimation webinar January 2024.pdf
Software Cost Estimation webinar January 2024.pdf
 
Nesma event June '23 - How to use objective metrics as a basis for agile cost...
Nesma event June '23 - How to use objective metrics as a basis for agile cost...Nesma event June '23 - How to use objective metrics as a basis for agile cost...
Nesma event June '23 - How to use objective metrics as a basis for agile cost...
 
Nesma event June '23 - NEN Practice Guideline - NPR.pdf
Nesma event June '23 - NEN Practice Guideline - NPR.pdfNesma event June '23 - NEN Practice Guideline - NPR.pdf
Nesma event June '23 - NEN Practice Guideline - NPR.pdf
 
Nesma event June '23 - Easy Function Sizing - Introduction.pdf
Nesma event June '23 - Easy Function Sizing - Introduction.pdfNesma event June '23 - Easy Function Sizing - Introduction.pdf
Nesma event June '23 - Easy Function Sizing - Introduction.pdf
 
Automotive Software Cost Estimation - The UCE Approach - Emmanuel Mary
Automotive Software Cost Estimation - The UCE Approach - Emmanuel MaryAutomotive Software Cost Estimation - The UCE Approach - Emmanuel Mary
Automotive Software Cost Estimation - The UCE Approach - Emmanuel Mary
 
The COSMIC battle between David and Goliath - Paul Hussein
The COSMIC battle between David and Goliath - Paul HusseinThe COSMIC battle between David and Goliath - Paul Hussein
The COSMIC battle between David and Goliath - Paul Hussein
 
Succesful Estimating - It's how you tell the story - Amritpal Singh Agar
Succesful Estimating - It's how you tell the story - Amritpal Singh AgarSuccesful Estimating - It's how you tell the story - Amritpal Singh Agar
Succesful Estimating - It's how you tell the story - Amritpal Singh Agar
 
(Increasing) Predictability of large Government ICT Projects - Koos Veefkind
(Increasing) Predictability of large Government ICT Projects - Koos Veefkind(Increasing) Predictability of large Government ICT Projects - Koos Veefkind
(Increasing) Predictability of large Government ICT Projects - Koos Veefkind
 
CEBoK for Software Past Present Future - Megan Jones
CEBoK for Software Past Present Future - Megan JonesCEBoK for Software Past Present Future - Megan Jones
CEBoK for Software Past Present Future - Megan Jones
 
Agile Development and Agile Cost Estimation - A return to basic principles - ...
Agile Development and Agile Cost Estimation - A return to basic principles - ...Agile Development and Agile Cost Estimation - A return to basic principles - ...
Agile Development and Agile Cost Estimation - A return to basic principles - ...
 
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...
 
Project Succes is a Choice - Joop Schefferlie
Project Succes is a Choice - Joop SchefferlieProject Succes is a Choice - Joop Schefferlie
Project Succes is a Choice - Joop Schefferlie
 
Afrekenen met functiepunten
Afrekenen met functiepuntenAfrekenen met functiepunten
Afrekenen met functiepunten
 
Agile teams get a grip - martijn groenewegen
Agile teams   get a grip - martijn groenewegenAgile teams   get a grip - martijn groenewegen
Agile teams get a grip - martijn groenewegen
 
The fact that your poject is agile is not (necessarily) a cost driver arlen...
The fact that your poject is agile is not (necessarily) a cost driver   arlen...The fact that your poject is agile is not (necessarily) a cost driver   arlen...
The fact that your poject is agile is not (necessarily) a cost driver arlen...
 
Software sizing as an essential measure past present and future - Dan Galorat...
Software sizing as an essential measure past present and future - Dan Galorat...Software sizing as an essential measure past present and future - Dan Galorat...
Software sizing as an essential measure past present and future - Dan Galorat...
 
A benchmark based approach to determine language verbosity - Hans Kuijpers - ...
A benchmark based approach to determine language verbosity - Hans Kuijpers - ...A benchmark based approach to determine language verbosity - Hans Kuijpers - ...
A benchmark based approach to determine language verbosity - Hans Kuijpers - ...
 
Software sizing the cornerstone for iceaa's scebok - Carol Dekkers
Software sizing the cornerstone for iceaa's scebok - Carol DekkersSoftware sizing the cornerstone for iceaa's scebok - Carol Dekkers
Software sizing the cornerstone for iceaa's scebok - Carol Dekkers
 

Recently uploaded

Encryption Recap: A Refresher on Key Concepts
Encryption Recap: A Refresher on Key ConceptsEncryption Recap: A Refresher on Key Concepts
Encryption Recap: A Refresher on Key Conceptsthomashtkim
 
Abortion Pills For Sale WhatsApp[[+27737758557]] In Birch Acres, Abortion Pil...
Abortion Pills For Sale WhatsApp[[+27737758557]] In Birch Acres, Abortion Pil...Abortion Pills For Sale WhatsApp[[+27737758557]] In Birch Acres, Abortion Pil...
Abortion Pills For Sale WhatsApp[[+27737758557]] In Birch Acres, Abortion Pil...drm1699
 
CERVED e Neo4j su una nuvola, migrazione ed evoluzione di un grafo mission cr...
CERVED e Neo4j su una nuvola, migrazione ed evoluzione di un grafo mission cr...CERVED e Neo4j su una nuvola, migrazione ed evoluzione di un grafo mission cr...
CERVED e Neo4j su una nuvola, migrazione ed evoluzione di un grafo mission cr...Neo4j
 
Incident handling is a clearly defined set of procedures to manage and respon...
Incident handling is a clearly defined set of procedures to manage and respon...Incident handling is a clearly defined set of procedures to manage and respon...
Incident handling is a clearly defined set of procedures to manage and respon...Varun Mithran
 
From Knowledge Graphs via Lego Bricks to scientific conversations.pptx
From Knowledge Graphs via Lego Bricks to scientific conversations.pptxFrom Knowledge Graphs via Lego Bricks to scientific conversations.pptx
From Knowledge Graphs via Lego Bricks to scientific conversations.pptxNeo4j
 
Team Transformation Tactics for Holistic Testing and Quality (NewCrafts Paris...
Team Transformation Tactics for Holistic Testing and Quality (NewCrafts Paris...Team Transformation Tactics for Holistic Testing and Quality (NewCrafts Paris...
Team Transformation Tactics for Holistic Testing and Quality (NewCrafts Paris...Lisi Hocke
 
Auto Affiliate AI Earns First Commission in 3 Hours..pdf
Auto Affiliate  AI Earns First Commission in 3 Hours..pdfAuto Affiliate  AI Earns First Commission in 3 Hours..pdf
Auto Affiliate AI Earns First Commission in 3 Hours..pdfSelfMade bd
 
[GeeCON2024] How I learned to stop worrying and love the dark silicon apocalypse
[GeeCON2024] How I learned to stop worrying and love the dark silicon apocalypse[GeeCON2024] How I learned to stop worrying and love the dark silicon apocalypse
[GeeCON2024] How I learned to stop worrying and love the dark silicon apocalypseTomasz Kowalczewski
 
The mythical technical debt. (Brooke, please, forgive me)
The mythical technical debt. (Brooke, please, forgive me)The mythical technical debt. (Brooke, please, forgive me)
The mythical technical debt. (Brooke, please, forgive me)Roberto Bettazzoni
 
COMPUTER AND ITS COMPONENTS PPT.by naitik sharma Class 9th A mittal internati...
COMPUTER AND ITS COMPONENTS PPT.by naitik sharma Class 9th A mittal internati...COMPUTER AND ITS COMPONENTS PPT.by naitik sharma Class 9th A mittal internati...
COMPUTER AND ITS COMPONENTS PPT.by naitik sharma Class 9th A mittal internati...naitiksharma1124
 
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024SimonedeGijt
 
Workshop - Architecting Innovative Graph Applications- GraphSummit Milan
Workshop -  Architecting Innovative Graph Applications- GraphSummit MilanWorkshop -  Architecting Innovative Graph Applications- GraphSummit Milan
Workshop - Architecting Innovative Graph Applications- GraphSummit MilanNeo4j
 
Transformer Neural Network Use Cases with Links
Transformer Neural Network Use Cases with LinksTransformer Neural Network Use Cases with Links
Transformer Neural Network Use Cases with LinksJinanKordab
 
GraphSummit Milan - Neo4j: The Art of the Possible with Graph
GraphSummit Milan - Neo4j: The Art of the Possible with GraphGraphSummit Milan - Neo4j: The Art of the Possible with Graph
GraphSummit Milan - Neo4j: The Art of the Possible with GraphNeo4j
 
Prompt Engineering - an Art, a Science, or your next Job Title?
Prompt Engineering - an Art, a Science, or your next Job Title?Prompt Engineering - an Art, a Science, or your next Job Title?
Prompt Engineering - an Art, a Science, or your next Job Title?Maxim Salnikov
 
A Deep Dive into Secure Product Development Frameworks.pdf
A Deep Dive into Secure Product Development Frameworks.pdfA Deep Dive into Secure Product Development Frameworks.pdf
A Deep Dive into Secure Product Development Frameworks.pdfICS
 

Recently uploaded (20)

Encryption Recap: A Refresher on Key Concepts
Encryption Recap: A Refresher on Key ConceptsEncryption Recap: A Refresher on Key Concepts
Encryption Recap: A Refresher on Key Concepts
 
Abortion Pills For Sale WhatsApp[[+27737758557]] In Birch Acres, Abortion Pil...
Abortion Pills For Sale WhatsApp[[+27737758557]] In Birch Acres, Abortion Pil...Abortion Pills For Sale WhatsApp[[+27737758557]] In Birch Acres, Abortion Pil...
Abortion Pills For Sale WhatsApp[[+27737758557]] In Birch Acres, Abortion Pil...
 
CERVED e Neo4j su una nuvola, migrazione ed evoluzione di un grafo mission cr...
CERVED e Neo4j su una nuvola, migrazione ed evoluzione di un grafo mission cr...CERVED e Neo4j su una nuvola, migrazione ed evoluzione di un grafo mission cr...
CERVED e Neo4j su una nuvola, migrazione ed evoluzione di un grafo mission cr...
 
Abortion Clinic In Johannesburg ](+27832195400*)[ 🏥 Safe Abortion Pills in Jo...
Abortion Clinic In Johannesburg ](+27832195400*)[ 🏥 Safe Abortion Pills in Jo...Abortion Clinic In Johannesburg ](+27832195400*)[ 🏥 Safe Abortion Pills in Jo...
Abortion Clinic In Johannesburg ](+27832195400*)[ 🏥 Safe Abortion Pills in Jo...
 
Abortion Clinic In Springs ](+27832195400*)[ 🏥 Safe Abortion Pills in Springs...
Abortion Clinic In Springs ](+27832195400*)[ 🏥 Safe Abortion Pills in Springs...Abortion Clinic In Springs ](+27832195400*)[ 🏥 Safe Abortion Pills in Springs...
Abortion Clinic In Springs ](+27832195400*)[ 🏥 Safe Abortion Pills in Springs...
 
Incident handling is a clearly defined set of procedures to manage and respon...
Incident handling is a clearly defined set of procedures to manage and respon...Incident handling is a clearly defined set of procedures to manage and respon...
Incident handling is a clearly defined set of procedures to manage and respon...
 
From Knowledge Graphs via Lego Bricks to scientific conversations.pptx
From Knowledge Graphs via Lego Bricks to scientific conversations.pptxFrom Knowledge Graphs via Lego Bricks to scientific conversations.pptx
From Knowledge Graphs via Lego Bricks to scientific conversations.pptx
 
Abortion Clinic In Pretoria ](+27832195400*)[ 🏥 Safe Abortion Pills in Pretor...
Abortion Clinic In Pretoria ](+27832195400*)[ 🏥 Safe Abortion Pills in Pretor...Abortion Clinic In Pretoria ](+27832195400*)[ 🏥 Safe Abortion Pills in Pretor...
Abortion Clinic In Pretoria ](+27832195400*)[ 🏥 Safe Abortion Pills in Pretor...
 
Team Transformation Tactics for Holistic Testing and Quality (NewCrafts Paris...
Team Transformation Tactics for Holistic Testing and Quality (NewCrafts Paris...Team Transformation Tactics for Holistic Testing and Quality (NewCrafts Paris...
Team Transformation Tactics for Holistic Testing and Quality (NewCrafts Paris...
 
Auto Affiliate AI Earns First Commission in 3 Hours..pdf
Auto Affiliate  AI Earns First Commission in 3 Hours..pdfAuto Affiliate  AI Earns First Commission in 3 Hours..pdf
Auto Affiliate AI Earns First Commission in 3 Hours..pdf
 
[GeeCON2024] How I learned to stop worrying and love the dark silicon apocalypse
[GeeCON2024] How I learned to stop worrying and love the dark silicon apocalypse[GeeCON2024] How I learned to stop worrying and love the dark silicon apocalypse
[GeeCON2024] How I learned to stop worrying and love the dark silicon apocalypse
 
Abortion Pill Prices Mthatha (@](+27832195400*)[ 🏥 Women's Abortion Clinic In...
Abortion Pill Prices Mthatha (@](+27832195400*)[ 🏥 Women's Abortion Clinic In...Abortion Pill Prices Mthatha (@](+27832195400*)[ 🏥 Women's Abortion Clinic In...
Abortion Pill Prices Mthatha (@](+27832195400*)[ 🏥 Women's Abortion Clinic In...
 
The mythical technical debt. (Brooke, please, forgive me)
The mythical technical debt. (Brooke, please, forgive me)The mythical technical debt. (Brooke, please, forgive me)
The mythical technical debt. (Brooke, please, forgive me)
 
COMPUTER AND ITS COMPONENTS PPT.by naitik sharma Class 9th A mittal internati...
COMPUTER AND ITS COMPONENTS PPT.by naitik sharma Class 9th A mittal internati...COMPUTER AND ITS COMPONENTS PPT.by naitik sharma Class 9th A mittal internati...
COMPUTER AND ITS COMPONENTS PPT.by naitik sharma Class 9th A mittal internati...
 
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024
Wired_2.0_CREATE YOUR ULTIMATE LEARNING ENVIRONMENT_JCON_16052024
 
Workshop - Architecting Innovative Graph Applications- GraphSummit Milan
Workshop -  Architecting Innovative Graph Applications- GraphSummit MilanWorkshop -  Architecting Innovative Graph Applications- GraphSummit Milan
Workshop - Architecting Innovative Graph Applications- GraphSummit Milan
 
Transformer Neural Network Use Cases with Links
Transformer Neural Network Use Cases with LinksTransformer Neural Network Use Cases with Links
Transformer Neural Network Use Cases with Links
 
GraphSummit Milan - Neo4j: The Art of the Possible with Graph
GraphSummit Milan - Neo4j: The Art of the Possible with GraphGraphSummit Milan - Neo4j: The Art of the Possible with Graph
GraphSummit Milan - Neo4j: The Art of the Possible with Graph
 
Prompt Engineering - an Art, a Science, or your next Job Title?
Prompt Engineering - an Art, a Science, or your next Job Title?Prompt Engineering - an Art, a Science, or your next Job Title?
Prompt Engineering - an Art, a Science, or your next Job Title?
 
A Deep Dive into Secure Product Development Frameworks.pdf
A Deep Dive into Secure Product Development Frameworks.pdfA Deep Dive into Secure Product Development Frameworks.pdf
A Deep Dive into Secure Product Development Frameworks.pdf
 

Iwsm2014 putnam revisited (han suelmann) for publication

  • 1. Putnam’s Effort-Duration Trade-Off Law: Is the Software Estimation Problem Really Solved? Han Suelmann October 7th, 2014
  • 2. Putnam’s study – reference L.H. Putnam, “A generic empirical solution to the macro software sizing and estimating problem,” IEEE Transactions on Software Engineering, vol. 4, pages 345 ─ 361, July 1978. 2
  • 3. 3
  • 4. Agenda • Putnam’s study: results and influence • Putnam’s approach • Intermezzo – A statistical pitfall • Critical evaluation: o dataset is very limited o model and assumptions are unclear o analysis is incorrect • Other studies provide no corroboration • Simulation study demonstrate incorrectness 5
  • 5. 6
  • 6. Putnam’s study: results and influence Claims: • Generic empirical equations that describe size – effort – duration relationships. • Method will produce accurate estimates. • Only a few quick reference tables and a pocket calculator needed. • Trade-off law: K ~ 1 / T4. 7
  • 7. Putnam’s study is very influential Influence: • incorporated in estimation software • many references • sometimes cited as authoritative 8
  • 8. Putnam’s approach 1) Gather data on effort (K), duration (T) and size (S). 2) Define difficulty: D = K / T 2 3) Define productivity: P = S / K 4) Find relationship between D and P. Result: P ~ D -0.67 5) Perform basic algebraic manipulations to find relationships between S, T, and K. Result: S = C ∙ K1/3 ∙ T4/3, 3 S and therefore: . 9 4 T K 
  • 9. The crucial relationship… 10 K 2 T D  S K P  difficulty productivity
  • 10. Putnam’s approach 1) Gather data on effort (K), duration (T) and size (S). 2) Define difficulty: D = K / T 2 3) Define productivity: P = S / K 4) Find relationship between D and P. Result: P ~ D -0.67 5) Perform basic algebraic manipulations to find relationships between S, T, and K. Result: S = C ∙ K1/3 ∙ T4/3, 3 S and therefore: . 11 4 T K 
  • 11. Intermezzo – A statistical pitfall • Two researchers examine relationship between S and K. • Both assume linear relationship. • Researcher 1 writes K = aS + b • Researcher 2 writes S = a’K + b’ 12 S K S K
  • 12. Researcher 2’s does his linear fit
  • 13. Intermezzo – The results are quite different • Researcher 1 writes K = aS + b and finds (1) K = 1.01 S −0.02. • Researcher 2 writes S = a’K + b’ and finds (2) S = 0.50 K + 3.0. • Researcher 2 then derives (3) K = 2.02 S – 6.2. 14
  • 15. Intermezzo – A statistical pitfall • Researcher 1 writes K = aS + b and finds (1) K = 1.01 S −0.02. • Researcher 2 writes S = a’K + b’ and finds (2) S = 0.50 K + 3.0. • Researcher 2 then derives (3) K = 2.02 S – 6.2. 16 ^ ^ ^
  • 16. Linear fit: minimising least squares S K
  • 17. Critical evaluation (1) – dataset is very limited • only 13 projects • all US Military • 4 are left out => 9 projects remaining 18
  • 18. Critical evaluation (2) – model is unclear 19 size duration effort  Putnam does not make clear and consistent choices regarding model structure.  Only one parameter to capture effort-duration interaction
  • 19. Critical evaluation (3) – analysis 20
  • 20. Critical evaluation (3) – analysis 21
  • 21. Critical evaluation (3) – analysis 22
  • 22. Critical evaluation (3) – analysis 23
  • 23. Critical evaluation (3) – analysis 24
  • 24. Critical evaluation (4): Difficulty – Productivity relationship Putnam’s reasoning: More precisely notated: 25 2/3 P D    K S 1/3 4/3 S  K T ˆ 2/3 P  D ˆ ˆ 2/3 4/3 ??    S K K T 2/3 2      T K
  • 25. Other studies − Corroboration by Putnam et al. Putnam & Putnam, “A data verification of the software fourth power trade-off law,” (Proc. of the Int. Soc. of Parametric Analysts – 6th Annu. Conf., vol. III(I), pp. 443–471, 1984.) Putnam & Myers, “Measures for excellence – Reliable software on time, within budget”, (Englewood Cliffs: Yourdon, 1992.) Confirmed that K ~ 1 / T4, but… Found (Dunsmore et al., 1986) and admitted (Putnam & Myers, n.d.) to be based on circular reasoning. 26
  • 26. Other studies – No corroboration from Jeffery Jeffery (1987): • 47 MIS in 4 large organisations • Find P as a function of K and T. Result: • P ~ K−0.47T −0.05 • essentially no productivity – duration relationship • comparison with Putnam’s P ~ K−0.67T 1.33 • no confirmation • strictly speaking: no refutation either 27
  • 27. Other studies – No corroboration from Barry, Mukhopadhyay, and Slaughter Barry, Mukhopadhyay, and Slaughter (2002): Ansatz: ln K = … + β1 T Result: β1 = 0.000677 ± 0.000103, p = .031. So – larger duration predicts larger effort. 28
  • 28. Other studies – Team size affects effort, so…? Putnam & Myers (n.d.): larger team size predicts larger effort: Teams of 5 or less have better productivity than teams of 20 or more. Supported by other studies. Example (Rodríguez et al.): PDR ~ (average team size)^0.57 But… • translation to effort-duration trade-off unclear • interpretation in terms of causation dubious 29
  • 29. Several interpretations are possible… 30 larger team size more effort
  • 30. Simulation (1) Goal: check whether the analysis issues really lead to incorrect results. Method: • generate simulated data with known structure • analyze simulated data, following Putnam’s approach • check whether results are consistent with assumptions 31
  • 31. Simulation (2) Model assumptions: • Size, effort, and duration are unrelated random numbers. • Log-normal distributions. • 1000 projects. 32
  • 32. Simulation (3) – analysis 33
  • 33. 34 K 2 T D  S K P 
  • 34. Simulation (4) – result Fit yields: ln P  0.67ln Dconstant After transformation: After some manipulations (same as Putnam’s): K Yet, no 35 0.670.02 P  D 1   4.1 0.4 T relationship actually exists!
  • 35. Simulation (5) – coincidence? For convenience, write s = ln S, k = ln K, and t = ln T. Difficulty and productivity: • ln D = k – 2t • ln P = s – k Derive the slope of P against D: D P cov(ln , ln ) 2   k  (ln | ln ) 2 2 Follow Putnam closely, finding K ~ T u , with    which yields u = − 4 if  8 36 . var(ln ) 4 k t D B P D     2 2  u 1 k 2  t k  t
  • 36. Simulation (6) – result 37  S K 
  • 37. Conclusions 38 Claims: • Generic equations that describe size – effort – duration relationships. • Method will produce accurate estimates. • Trade-off law: K ~ 1 / T4. Limited dataset, no corroboration Not addressed Faulty analysis, no corroboration
  • 38. Conclusion 39 No credibility for Putnam’s result Putnam’s original study was wrong No corroboration
  • 39. The bad news • Handling statistical relationships as if exact. • Interpreting statistical relationship as causal relationships without sufficient support. 40 Both issues are rather common in the estimation / metrics literature.

Editor's Notes

  1. Going to discuss this paper. Many know something about the results; few have read the paper.
  2. This is what it looks like.
  3. Most famous conclusions: equations describing relationship between size, effort and duration of software development projects.
  4. .
  5. Claims: “empirical”, “general”, “will produce accurate estimates”, easily done. Effectively: estimation problem solved!
  6. [Claims] Effectively: claimed comprehensive solution for software estimation. Trade-off law: K ~ 1/T^4. [Influence] In software. References soon after publication as well as recently. Makes it worthwhile to examine study & results critically. Focus on effort/duration relationship. Estimation of duration and staffing variations over the course of a project are also in the Putnam paper, but will not be discussed here. Does not imply my agreement or approval
  7. [Claims] Effectively: claimed comprehensive solution for software estimation. Trade-off law: K ~ 1/T^4. [Influence] In software. References soon after publication as well as recently. Makes it worthwhile to examine study & results critically. Focus on effort/duration relationship. Estimation of duration and staffing variations over the course of a project are also in the Putnam paper, but will not be discussed here. Does not imply my agreement or approval
  8. gather data; in Putnam’s case: US military. Size is LoC. define difficulty D=K/T^2. Variable name “difficulty” justified by observation: small D => easier systems; large D => hard systems productivity = S/K find relationshop by doing a double-logarithmic plot of prod against diff manipulate (insert definitions of D and P) to get “software equation” S=… manipulate to find trade-off law K=…
  9. Crucial relationship is that between productivity and difficulty. Many think sw eq derived from Rayleigh-Norden curves, but it is not. Derived from empirical data in this way.
  10. gather data; in Putnam’s case: US military. Size is LoC. define difficulty D=K/T^2. Variable name “difficulty” justified by observation: small D => easier systems; large D => hard systems productivity = S/K find relationshop by doing a double-logarithmic plot of prod against diff manipulate (insert definitions of D and P) to get “software equation” S=… manipulate to find trade-off law K=…
  11. Before critically examining Putnam’s approach: an intermezzo to demonstrate a common statistical pitfall. Assume 2 researchers examine relationship between size and effort. Assume linear relationship for simplicity, to bring out the issue more clearly. Res.1 asks: how much effort does it take to build a system of size S. Res.2 asks: what size can be produced given effort K. Write eqs K= and S=, and draw the corresponding data plots. THEY USE THE SAME DATA, but note the orientation of the axes. I demonstrate with FAKE data, but REAL analysis.
  12. Simulated data and the fit made by researcher 2.
  13. Researcher 1 derives K= directly from data. Researches 2 derive S=, and then manipulates the result to get an expression for K. Results are quite different. (FAKE but same data, REAL analysis!)
  14. Same data (flipped plot) Solid line = fit by Res.1 Dashed line = relationship derived by Res.2 Note that solid line is (by definition) the best fit for predicting effort. So the correct (=best) fits for predicting effort and for predicting size are not the same. Quite different. Res. 2 finds stronger dependency. Surprise?
  15. Rewrite results, making estimations explicit. The hat is in the wrong place.
  16. No. Fitting S=f(K) minimises vertical distances. Fitting K=f(S) minimises horizontal distances. Does not yield the same relationship in a different notation, but a different relationship. General tendency: noise makes the fitted line flatter, and the inverted slope steeper. In other words: manipulations make relationships stronger than they really are.
  17. “General” solution is based on only 13 projects from one organisation. 4 are “different” (standards, application type) and are not analysed. Putnam’s equation essentially based on 9 projects from one organisation, which seems insufficient support for accurate and generic equations.
  18. Putnam switches between predicting productivity from difficulty, size from effort and duration, effort from size and duration. No clear and consistently applied choice of model structure. Duration may affect effort, as claimed by Putnam. But effort may also affect duration: if more work needs to be done, it will probably take longer to do it. Putnam does not distinguish the effects, does not distinguish between prediction and causation, and has only one parameter to account for the strength of two effects.
  19. Putnam’s analyses contain incorrrect derivations. Let’s discuss one in detail: derivation of trade-off law from software equation. This is Putnam’s software equation. Raise to 3rd power.
  20. Switch lhs and rhs. Divide by T^4 and C^3. Find trade-off law. Now, take a look at what really happens.
  21. Software equation is not true exactly. It’s only a statistical relationship. It can, at best, be interpreted as estimating S given K and T. Denote “estimated value” by hat. Obtain a more precise notation of the software equation. Follow the same steps.
  22. Hat is in the wrong place.
  23. Not a legal manoeuvre. So, even if one accepts the software equation (which I do not), the trade-off law doesn not follow as a correct estimation of effort.
  24. But can we even accept the sw eq as a starting point? The same issue is relevant here. Left: Putnam’s derivation. Right: With the hats inserted. Because K-hat depends on S, I see nowhere to go. Question: Is all the criticism just formalistic mathematics, without practical consequences? No, it’s not. Come back to that in a few minutes.
  25. P&P and P&M did claim corroboration of K ~ 1/T^4, using dataset of hundreds of projects. However, Dunsmore et al. showed this was based on circular reasoning. Was admitted by Putnam & Myers. So does not need to be further covered here further.
  26. Jeffery examined P as a function of both K and T. (Instead of D=K/T^2.) 47 MIS, 4 large organisations. Found result quite different from Putnam’s; essential no relationship between P and T. No confirmation. (Note that Putnam could never have found Jeffery’s result, because the ratio of the exponents of K and T is fixed.) Strictly speaking: no refutation: neither Putnam nor Jeffery specifies accuracy of results.
  27. Barry, Mukhopadhyay & Slaughter analysed 18 projects, enhancements to mainframe applications. Found that larger duration predicts larger effort. Makes sense: if more work needs to be done, it will probably take longer to do it.
  28. Putnam & Myers have put forward an argument based on effects of team size. (Is in the same paper as the admission of circularity.) Reasoning: trying to speed up a project causes large effort increases. Evidence: larger team size predicts larger effort. Larger teams have worse productivity than small teams. Relationship corroborated by several other studies: … HOWEVER: (1) no straightforward way to derive the trade-off (only that there is one, not the -4) (2) interpretation dubious.
  29. … alternative interpretation … reality is probably a mixture, so we do not know how strong the effect really is
  30. I had promised to get back to one important question: Is all the criticism just formalistic mathematics, or does it have consequences? Did a simulation to check this. Will Putnam’s approach really yield incorrect results? … (create a situation in which we know what the correct answer is) …
  31. Simplest of all: just unrelated random numbers. No relationships. No trade-off, so we shouldn’t find one if Putnam’s approach is correct. Created fake data, assuming log-normal distributions.
  32. This is what the data look like, if we plot P against D, as did Putnam. May come as a surprise that there is any relationship at all, starting from random numbers.
  33. But have a look at the definitions. Effort is in def of D and of P, causing a relationship between them.
  34. Follow in Putnam’s footsteps. Same fit, same result. Transform into power law. Reproduce Putnam’s algebraic manipulations, and find same result (within error bounds). We find a relationship that is not really there.
  35. Coincidence? No, analysis can be done analytically. … And of course, I chose the parameters to reproduce Putnam’s results. Could have derived any negative value I wanted from unrelated random numbers, just be selecting appropriate values for the SD’s.
  36. Find same result. (Or different one, depending on choices.)
  37. Generic equations: very small dataset, one organisation, no coroboration. Accurate estimates: not addressed by Putnam. (Only a claim in the abstract.) Trade-off: incorrect analysis, no corroboration. Despite elaborate search: did not find a single study corroborating Putnam’s results, except the circular study.
  38. Inevitable conclusion: no credibility for either the sw eq or the trade-off law. They should no longer be used.
  39. End of story? Unfortunately – no. Some of the issues discussed here are quite common in the estimation and metrics literature. Especially handling of statistical relationships as if exact, and their interpretation as causal relationships without further ado. E.g., there are at least 4 studies interpreting the relationship between team size and effort (or productivity) as evidence that larger teams cause more effort. What to do? (1) Take care in handling statistical relationships. Remember the basics. (2) Read with care. (3) Use simulations to test an approach. Some problems can be found doing the simplest of simulations, using unrelated random numbers. Simulations can be especially powerful if some (realistic) causal effects that are not part of the analysis in put into the data.