In the search for some other data I’ve recently been look through Capers Jones “Applied Software Measurement” (2008). It is packed full of interesting statistics and I really must buy a copy and read it in more detail. Anyway, Jones gives his hypothesis of project in this table:
Type of development | Number | % |
End-user | 2,500 | 2% |
Agile | 20,000 | 13% |
Web | 12,500 | 8% |
Systems | 8,750 | 6% |
MIS | 70,000 | 45% |
Commercial | 3,250 | 2% |
Outsource - US | 17,500 | 11% |
Outsource - offshore | 15,000 | 10% |
Military | 7,750 | 5% |
Total | 157,250 | 100% |
Jones puts the number of Agile projects at 13%, firmly inside the range I give. Of course there are two caveats here. Firstly, the ways Jones has sliced and diced the numbers leaves me wondering how he has counted military work running Agile, and outsourced work running Agile.
Second, how do we know if a piece of work is Agile or not? All the evidence I have tells me that an awful lot of teams are saying they are “Agile” and frankly aren’t. As Kevlin Henney suggested on re-twittered (from somewhere or other) recently a better question to ask is “How are you Agile?”
I’ll get Jones book and read it some more. One other thing he mentioned stood out: getting metric on software projects is hard. He says its like searching through debris, lots of rubbish then occasionally a nugget. Which sums up how I feel about software metrics now. Its quite like I imagine archaeology.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.