Tech and Government - Procurement stats
-
Upload
paul-matthews -
Category
Business
-
view
446 -
download
0
Transcript of Tech and Government - Procurement stats
![Page 1: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/1.jpg)
Why collaborate on Software Procurement?
A.K.A. What’s the problem?
![Page 2: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/2.jpg)
IT Project success and failure
52%
19% 29%Challenged: Major cost/time/functionality issuesCanceled before com-pletionSuccess
Source: The Chaos Report 2015
![Page 3: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/3.jpg)
Success vs Failure: 5 Characteristics
Size Complexity Methodology (eg Agile vs Waterfall)
Cost Estimation
Team culture
![Page 4: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/4.jpg)
Results by project size
Small Moderate Medium Large Grand0%
10%20%30%40%50%60%70%80%90%
100%
62%
21%9% 6% 2%
FailureSuccess
Source: The Chaos Report 2015
![Page 5: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/5.jpg)
How often is price estimation right?
Never Sometimes Usually Always0%
10%
20%
30%
40%
50%
60%
70%
SmallLarge
Source: IITP Software and Procurement Survey (2014)
![Page 6: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/6.jpg)
Never Sometimes Usually Always0%
10%
20%
30%
40%
50%
60%
70%
Large
Source: IITP Software and Procurement Survey (2014)
How often is price estimation right?
![Page 7: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/7.jpg)
Vendor reaction to price overrun
Do Nothing Renegotiate Cut corners Inflate costs Withdraw0%
10%20%30%40%50%60%70%80%90%
SmallLarge
Source: IITP Software and Procurement Survey (2014)
![Page 8: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/8.jpg)
Fact:We generally can’t predict the cost of [complex] software up front.
Yet we still use cost as a criteria?
![Page 9: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/9.jpg)
Source: The Chaos Manfesto 2012
![Page 10: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/10.jpg)
Agile and NZ Procurement Compatibility
Not compatible Reasonably Very0%
10%20%30%40%50%60%70%80%
Source: Those with Agile experience from IITP Software and Procurement Survey (2014)
![Page 11: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/11.jpg)
Fact:Agile works better for software.Agile succeeds 3x as often, but isn’t [perceived to be] very compatible with how we procure software.
![Page 12: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/12.jpg)
So what’s the challenge?
Bringing good software processes and good procurement together.
![Page 13: Tech and Government - Procurement stats](https://reader036.fdocuments.in/reader036/viewer/2022081520/58a3ab211a28ab9e6a8b5af7/html5/thumbnails/13.jpg)
Thanks!