As a leader, how to control the code version and demand development when the epidemic comes| Community essay solicitation

Current epidemic situation

Undertaking 【 At the head of the epidemic , As  Leader  How to manage the team ？】 That article , Grasp the management of team members and task allocation under the current epidemic, and make relevant planning and improvement , But after all, we still belong to the development department , So for ” How to control code version and requirement development “ It's very important , So for Leader Of me , How to solve and plan the management system in this special stage ？

Headache

When it happens that I am not in the team or the company , For the consolidation of versions and the integration of versions 、 Online and the burden of responsibility , It's a little inconvenient for me , So how to ？ It is crucial for the current personnel planning , At present , Our team mechanism system , The related hierarchical mode has been completed , Because of the independence of functions , In terms of version , I'll go from the second floor 6 Of the persons in charge , Take two people as the current version ： Principal and subordinate principals . Of course, each version will not be handled by different people in turn , Not always these two people .

• The person in charge ： It is mainly responsible for the migration of relevant version codes, the overall promotion of version progress, and the coordination of the requirements review and function development progress tasks of the principals in relevant sub groups .

• From the person in charge ： Mainly as the main person in charge backup, At the same time, the leader is also responsible for the relevant version management and the coordination of relevant personnel . Take the planning and processing of the whole current version as relatively stable , And for special or temporary emergencies , It's also a good deal partner, This is the so-called short plan for one person , The two of them are the controller .

Responsibility contracting

The responsibility contract system is adopted for the allocation of version requirements and functions , I learned the idea of site learning , ha-ha , Mainly to stimulate big guys KPI Motivation .

• KPI:  In fact, the reward is to manage the evaluation of each group on the difficulty of receiving functions and the final delivery progress and quality of related functions , It doesn't involve performance , I will only do relevant incentives for rewards . Some of them will ask , Why not do the average distribution of function difficulty , That's because we are actually in the actual scene , Independence of different fields , As a result, it is impossible to really balance the related difficulties and functions , So analyze the specific problems in detail !

• The reward system ： As a team leader, Certainly in terms of departmental bonuses , The Department bonus system will be proposed , Special will buy some delicious food for the first three groups as a reward   ha-ha , Besides , The performance score will also be higher , It will increase our year-end bonus and salary adjustment amount .

Version Registration

Because the version has too many functions , Because many versions may not be in our plan , So we will make a registration audit form based on each migrated version , It is convenient to record the corresponding person in charge 、 Version online time 、 Merge version records and source version relationships , The main contents are as follows ：

• Registration time ： It can be understood as the time when the version moves out

 

• Version name

 

• Version field ： Belong to that business field

 

• Version owner

 

• Version source ： It represents the migration based on that version

 

• The version is merged into the main branch

• Version test time

 

• Version online time

 

• remarks

Code review

For code review review, In fact, it is mainly the group leader , Organize relevant at each stage review meeting , Take me with you every time , And will be registered , It belongs to one of the categories of performance appraisal .

Version merge

No matter how many versions of this , Will not be affected , Every time the version is closed and launched , Will be related to the notification of the merger of all current versions , Main treatment methods ：

• Merger time ： When a certain version is blocked .

• Combined version ： Version in progress

• Merger personnel ： You need to merge the corresponding version ” Version Registration Form “ The corresponding person in charge , To perform git Merge versions , And create the corresponding tag Record .

Parting proverbs

Time is not the , If the time flow . Looking back on a year , Intertwined with numerous feelings , Everyone has written down their own time marks . Win this epidemic battle , It depends on the efforts of each of us . I hope we can , Don't believe in rumors 、 Don't tale , Follow the doctor's advice , Protect your health , At the same time, once you find someone around you suspected of infection , We must report to the health department in time , Life is the most precious !