TerryB, no offense taken. As mentioned, when I started out in this career, we coders did it all. Then our profession matured; some prefer to count the leaves on the trees (coders) & some prefer to ensure the forest is healthy, optimally thriving, & all the bits & parts are peaceably coexisting.
If I may, I think you might've missed the message. Our implementation time has skyrocketed because we've outsourced the architect role along with the coding. It isn't just that outsource teams DON'T want to abide by data/database design standards, it's that their failure to do so has resulted in their creations being unimplementable -- we won't even get into the tonnage of resources necessary to make these abominations functional for users.
If they HAD followed standards, the geometric increase in the time it now takes for our technical team to trot the new app out for the users to actually use would NOT be happening. We know this because we know the entirety of the hardware, software, & communications architecture of the organization & work in concert to keep it humming along as best as we can -- they don't. When standards are NOT followed, we have to create new & unique techniques for implementing & connecting everything up. These new & unique techniques create unnecessary complexity which -- I don't know about your shop, but before outsourcing we were doing our best to simplify -- is contrary to both the demands of our executive leadership & industry best practices.
I've been reading a lot lately on the way(s) large companies handle 'big data', & the level of analysis & coordination (read: data administration & architects) required to keep the wheels moving, & I think if folks believe it's the coders who are doing all of that, those folks are naïve at best & deluded at worst.
No offense intended, TerryB.