it seems to me that most of our work in managing and monitoring software projects circles around the key value add activity - coding seems to be a binary activity (it is done or not done)
are we really examining how software is getting created? our management techniques look at code creation as a black box activity... there is no key insight into how code has been written - even though there is a cursory question: has code review been done? this is akin to toyota not asking how cars are produced, but investigating value chains in all the ancillary activities..
even alternate software development life cycles like agile seem to look at aggregates in the life cycle.... is this a key area to evaluate our work methods and look at sources of innovation? or is it so commoditised that it does not matter?
