Kwik Fit
I think in future contracts will go down an outcome based approach where as long as the code is produced to the required spec, does it really matter what qualifications the developer has in the past? I use the Kwik Fit analogy - if I have my exhaust replaced I go to a specialist, they give me a price and a time. I dont analyse the mechanics qualifications or a schedule of what they are doing - all I want them to do is deliver on time and on budget and that they phone me if there is a problem.
What is being recommended here is a return to Waterfall. If you are capable of defining your project (the diameter of the exhaust pipes, the acceptable db level of the muffler, the acceptable CO, CO2 and particulates in the exhaust), then this will work in IT.
You'll quickly find that the specifications will take forever to write (if they are written at all). be out-of-date by the time the products are delivered and lead to cost overruns and frustrations by all.... very similar to the criticisms of Waterfall.
When IT is standardized (ie: major paradigm shifts cease) and business processes are standardized across companies and industries, this will be a realistic approach. Until then, it's primariliy wishful thinking.
