Let's imagine a couple of developers start LittleProject™ inside of a company. No Unit Testing, no Jenkins, no Docker, a single development environment... "why would you want more? It would be overkill."
The project is successful and grows bigger and bigger. More developers are added. A couple of testers are hired. Then, after a few months, the group has grown to around 20 people, and the manager starts to realize that LITTLEProject's™ growth has slowed down to a crawl because of the development process the team is using is obsolete or inadequate for this scale, like hiting a "methodologic roof".
LITTLEProject™ is not little anymore, and no longer can advance at a steady pace unless you improvethe the development process used. Is there a name for this effect?
Complete this sentence: "Our development is stagnant until we change our development process. (We are/Our project) is/has __________"
About what I mean by "development process":
The problem LittleProject is facing is NOT related to things like "we are using X technology (PHP vs NodeJS, or MySQL vs NoSQL, for instance) and it doesn't scale well". I'm talking about missing, misusing or choosing the wrong methodology and practices, which may include things like:
- using bug tracker
- using VCS
- manual SASS compilation versus automation
- defining a common coding style guideline (no matter which one)
- unit testing
- regular meetings
- etc... ((This is not a list of the things LittleProject™ is missing, just an example of the kind of things as opposed to technologies (mentioned above) like programming languages, target operating system or database managers ))
About what I am exactly asking for:
This question is, essentially, a word-request question. I'm not looking for an analysis of the situation or advice to solve it, just a name for it.