[deathofsocrates]

it is highly dependent on the engineering practices applied and the team structure as well. i'd suggest to check the team topologies book by Matthew Skeleton which suggests to form teams according to the software architecture instead of business needs. The "release often and small", "go with microservices", "independent release cycles" and many other things coming from different needs either derived by the competency in market or the buzz words are either not applied properly or the engineering managers are not able to see that the underlying/existing structure requires changes before you go down those roads. I also think the test automation practices are not well adapted/applied generally because the innovations in that area are massive lately. So its rather a principle and angle than it has anything to do with the codebase or the number of people working on a project. Generally i do not agree that it is decreasing but maybe most of those big projects may need more time to adapt the industrial changes or maybe they will vanish in time anyway because of their competitors are eventually do a better job on the long run.