The development case is considered, some problems are identified, the need for a dialogue is formulated.
Development case
The developer is "stuck" over a simple task. I was engaged in the task for two weeks. After two weeks of work, I made changes to the repository for 10-20 lines of code. The task report contains many technical details. In the report, he stated the need for additional time to finalize the task.
If the case is obvious to you, then you don't need to read further.
List of problems
Budget overruns. The developer has spent a lot of time on a simple feature and requires additional time.
The developer is not able to argue the need for large time expenditures for a simple feature.
Possibility of conflict with the developer.
The ability to demotivate the developer. The developer is not happy with the quality of the existing system. The developer tried to improve the system. The problem has not been completely solved. But the developer has little motivation to work with a low-quality system.
Possibility of degradation of the developer's attitude to the manager. From the developer's point of view, the manager does not understand the importance of the details of technical reasoning in improving the quality of the system.
The possibility of further precedents of "building locks" by the developer. The developer may ignore the instructions of the manager and independently allocate time to improve the quality of the system. Due to the main features, i.e. with reduced costs for core functionality that makes a profit.
The developer does not know how to translate the technical details of the proposed solution into the language of user benefits.
The developer cannot articulate why the poor quality of the system leads to a deterioration in the business performance of the product.
, . . .
. , .
. ( .)
, , , .
.