Distribution of responsibility for the code of a long-lived large project

Suppose you are a project manager for a large project with a lot of code that has been developed over time. For some parts of the code team, there is knowledge; for others, not.

It is good to distribute responsibility between teammates in some wise way. There is no problem with code whose author is still in the team. But this approach should be developed in order to avoid a lengthy decision on the appointment of a person with every change to the old code. This can lead to lengthy discussions and a lot of time.

What approaches, hints, methods, processes could you propose to make the process of assigning code without responsibility to a new team an effective, transparent and reasonable way?

I would like to add that I am not trying to get all developers to know all parts of the projects at the moment, but only to cover all areas of the code by responsible persons.

+3
source share
1 answer

Even if you specifically stated that you do not want to spread all the knowledge for the whole team, I highly recommend this. Or at least avoid having only one person know what is going on on some module.

, . : ", - X, - Z ..". , . . , , (, ""... ; , ).

, . , - , " ".

+2

Source: https://habr.com/ru/post/1762413/


All Articles