Horizon of the software project

This visualization was born in the head about a year ago. Found a picture in the archive, I decided to share with Habr's readers.
The idea is simple. There is a dependence of the required level of the programmer (s) on the project and the possibility of developing a technical task on it. In addition, there is a dependence of the necessary participation of a manager in a project, whose responsibilities are to plan, define tasks on time, and control their execution.
Any project can determine the horizon, based on the sign of a possible elaboration of technical specifications. Accordingly, we determine the level of the programmer and the participation of the manager. On the other hand, based on the level of the programmer, it is possible to understand which projects will be solved by his forces most effectively.

In my practice, I dealt with projects of a very low level of the horizon, based on the proposed scheme. The role of the manager in such a project is unenviable, since standard procedures do not give effect. This can be seen in the diagram.

If the programmer "from God" to entrust the trivial task, then it is like a cannon on sparrows. But there are tasks for which it is impossible to develop a technical task, and here the usual approaches to programming and management will not work.
')
The most important conclusion that I would like to draw is that there is no uniform approach to the management and implementation of software projects. It is necessary to think about the project itself which set of people and approaches will most effectively reproduce it.