Technical R&D Team Management Plan Proposal

table of Contents

 

Preface to Part One

aims

The second part of the team recommendations

A small group

The third part of the group plan

Team task management

Working atmosphere of the second group

1 Team member ability growth

3 Improve team members' happiness

Three teams work together

Four-group construction plan

Part IV 2021 Goals and Plans

annex

---

Preface to Part One

aims

The platform R&D department plans to set up 4 groups according to positions: product design group, front-end R&D group, back-end R&D group, and testing support group. The 4 groups have group leaders (supervisors), and the group leaders need to propose group management ideas this week. ,Requirements are as follows:

Ideas

1. Group work task management: group member task assignment, task tracking management, work efficiency improvement, delivery quality improvement, group member performance evaluation
2. Group work atmosphere management: the ability of group members to grow, group work atmosphere, and ideas for improving group members’ well-being
3. Work coordination between groups: collaborative management ideas, dispute resolution mechanisms, task coordination between groups, and external coordination needs to have external coordination management ideas
4. Group construction plan: group construction direction, 2021 construction target and implementation plan, and need to provide support from the department

The second part of the team recommendations

A small group

1. The platform R&D department is divided into 4 groups according to the functions of the personnel. The 4 groups belong to the department and are directly managed by the department.

The product design group, front-end R&D group, back-end R&D group, and testing support group, four groups have group leaders (supervisors) under the direct management of the department.

1. At the same time, set up the itmg base, dvp and dip business groups according to the product business lines, and set up the business group technical managers (technical directors), which belong to the direct management of the department.

1. Functional departments and business lines exist at the same time, which can be true or false according to the situation of the team.

Dividing teams according to functional departments is suitable for small teams with weak technical strength, and it is necessary to improve the cohesion of the team or department and the combat effectiveness of certain tasks.

Dividing teams according to business lines is suitable for situations where the team is large, the team has strong technical strength or can be quickly built, needs to be deep in the business line and has high-quality delivery and acceptance requirements, or the business is its lifeline.

 

Business line/functional department structure diagram

 

 

The third part of the group plan

Team task management

According to the monthly/quarterly planning task list, iterate quickly in accordance with the agile development model.

1. Group member task assignment

First, the task is split

Follow the smart principle task split (S = Specific, M = Measurable , A = Attainable, R = Relevant, T = Time-bound) in order to favor employees more clearly and efficiently work , but also to managers in the future implementation of the staff performance appraisal Provides assessment objectives and assessment standards, making the assessment more scientific and standardized, and ensuring the fairness , openness and fairness of the assessment . The following briefly introduces the specific content of the smart principle:

1. Specific

The so-called clarification is to use specific language to clearly state the behavior standard to be reached. Clear goals are almost the unanimous characteristic of all successful teams. One of the important reasons why many teams are unsuccessful is because the goals are ambiguous , or the goals are not effectively communicated to the relevant members.

1. Measurable

Measurability means that the goal should be clear, not vague. There should be a set of clear data as a basis for measuring whether the goal is achieved. If there is no way to measure the set goal, it is impossible to judge whether the goal has been achieved.

1. Attainable

The goal is to be acceptable to the executor. If the boss uses some administrative methods and the power of influence to force the goals set by himself on his subordinates wishfully, the typical response of the subordinates is a kind of psychological and behavioral resistance: I can accept it, but it's hard to say whether there is any final certainty whether or not to accomplish this goal.

1. Relevant

The relevance of a goal refers to the relationship between achieving this goal and other goals. If this goal is achieved, but is completely irrelevant to other goals, or has a low degree of relevance, then even if this goal is achieved, it will not be of great significance.

1. Performance indicators must have a clear deadline (Time-bound)

The time limit of the target characteristic means that the target has a time limit.

Second, the order of tasks is reasonable

Task pre-dependence and post-sequence logic follow consistency, continuity, and iterability.

Finally, the task granularity is moderate

Tasks can be based on the monthly/quarterly task list to select the highest priority tasks for milestone planning, atomic tasks, etc., atomic tasks are recommended for 3-5 days; milestone tasks are recommended for 2-4 weeks.

1. Task tracking management

From product PRD review, estimated construction period, expected delivery constraints, quality, etc.; to UI design draft delivery; then architecture design, task splitting, detailed design, development and delivery code, self-test, CODEREVIEW review, integration test, joint debugging test, version Consolidation, deployment, testing, etc.; then to testing, test reports, product acceptance and delivery. Any link tracking, early warning, crisis management mechanism, etc. will have an immeasurable impact on the overall product quality and delivery schedule.

The overall tracking management is divided into three aspects:

1. Product, UI design side

First of all, deliverables include business/product PRD, prototype, task function list, UI design, cut diagrams, styles, etc.

Secondly, large changes in requirements or reviewed requirements must be reviewed.

Then, the review participants must participate in the R&D leader and the test leader to reach an agreement. It is best to participate in R&D and test engineering, and UI designers also participate in the review.

It is best to pass to the UI designer, R&D and testing party only after the requirements are passed through repeated reviews.

1. R&D, testing

First of all, after receiving the product and UI deliverables, quickly communicate and consider the product design logic, estimated quality, conditional constraints, estimated construction period and the degree of matching between R&D strength and current situation. Generally, there is no problem.

Then, carry out architecture design, design review, task splitting and discussion, detailed design and review. This process must include R&D design review, and the architect participates in the review to ensure that the number of rework and rework is reduced.

Finally, enter the development stage, complete the development, self-test, code walkthrough or review (the person in charge of development must complete the tool walkthrough before review), start integration, joint debugging, and after joint debugging is completed, initiate a test and test smoke test , Function test, performance test, summary test report, and submit to product acceptance.

During the development and continuation of R&D work, technical managers or architects need to grasp and promote the smooth progress of R&D, predict technical difficulties, development workload, and ensure risk early warning, risk escalation, and unimpeded risk processing channels.

1. Acceptance, delivery

Acceptance and delivery are mainly completed by the product side.

1. Improve work efficiency

1. Product requirements are clearly designed and deliverables are complete, reducing the number and probability of rework, temporary changes, repeated communication and inefficient communication.
2. Training, inter-team training, business training, technical training, temporary technical seminars within the group; follow-up consideration of organizing a mentor to lead the guidance mechanism.
3. Tasks, sequence design is reasonable, and the delivery time is solidified, and milestone node delivery and acceptance are extracted.

 

1. Delivery quality improvement

1. Strengthen product user experience, user behavior, competitive product analysis, prediction and planning, and balance according to the actual difficulty of research and development.
2. Enhancing the overall strength of the R&D team, by hiring high-end technical personnel, organizing team training, motivating employees to improve themselves, guiding and rewarding mentors and follow-up models, etc. to enhance individual combat and collaboration, team combat and team collaboration capabilities.
3. Improve test coverage, scenario testing, frequency testing of main functions, and gradually plan and implement stress testing, performance testing, and limit testing.

1. Team member performance evaluation

Focus on incentives, and be equipped with disciplinary mechanisms to assist.

1. First, according to the number of tasks completed and the quality of completion.

Encourage employees with a large number of tasks completed and high quality; discipline employees with a small number of tasks completed and many bugs.

1. Secondly, it is measured according to the number of collaborative support of the team, the degree of matching of working methods, and the attitude.

Reward the team for synergy to obtain praise from the requesting party, and how well-matched working methods are, high efficiency, and too many good employees.

1. Finally, refer to discipline and attendance.

Working atmosphere of the second group

1 Team member ability growth

1. Task Distribution Science

The distribution of main tasks varies from person to person. Guidance and assistance, incentives and punishments vary from person to person at different times. Assign tasks with different challenges to different team members; assign different technical difficulties and workloads at different time periods, and provide guidance and help. Different; different incentives and punishments are given to the task execution results and quality.

1. Establish sustainable long-term business sharing, technology sharing mechanism is based on weekly/monthly units
2. Match employees according to the monthly/quarter task volume, help, and promote employees to achieve and grow

Guide and assist employees to match their own career plans with work tasks, help employees achieve their expected goals, and let employees feel a sense of accomplishment.

 

1. Working atmosphere in the group

1. Solidify team building activities

A team dinner is held every month/quarter to gradually solidify the work, business, technology, and communication mechanisms between teams. One party is the leading and responsible party, and the other party actively responds and cooperates to avoid the emergence and spread of critical areas.

1. Staff welfare construction

Expand the scope of employee benefits and existing benefits (depending on the actual situation)

1. Simplify the reimbursement process

After working overtime at 10 o'clock in the evening, the company will take a taxi home on WeChat; simplify the reimbursement process for overtime dinner at night, or unified reimbursement.

 

3 Improve team members' happiness

1. Create a sense of motivation and reward ceremony
2. Build and promote team culture
3. Create surprise opportunities and times within the group

 

Three teams work together

1. Collaboration between groups

Divide and build the team in two dimensions: business line, product and function; one entity and one virtual establish a three-dimensional collaborative pyramid structure of team employees, team leaders, and departments corresponding to the bottom network, middle team leader and top department.

 

1. Dispute settlement

First of all, the task team member responsibility system, if there is a stop, postponement, or quality warning, the team member must initiate an early warning to inform the direct team leader, and the team leader ensures that the early warning and early warning rise channel is smooth.

Then, if there is a dependency relationship between tasks and an early warning occurs, the person in charge of the task needs to promote and follow up to ensure that the task early warning ascending channel is unblocked.

Finally, the respective responsible parties of the task dependency relationship must ensure that the blocking task is solved in time and followed up.

1. Task coordination

1. The task belongs to the person in charge. Two or more people must be responsible for the task. There must be a leader who is responsible for the task. The person in charge of the task execution part can be responsible for follow-up and conversion.
2. The completion of pre-tasks must have corresponding review, accountability system, and clearly defined boundaries. The boundary can only be a line, not an area.
3. Collaborative tasks must belong to one responsible party at any point in time, not multiple parties, and can belong to different responsible parties at different points in time.

 

1. External collaboration

1. Define task priority and scope of external collaborative work
2. Arrange reasonable personnel
3. Timely follow up key node deliverables
    

Four-group construction plan

1. Group building direction

 

The first quarter of 2021

1. Mainly to ensure the smooth progress of basic back-end research and development work
2. Mainly to ensure the stability of back-end engineers
3. Improve engineers' awareness and expectations of technological interest

Second quarter of 2021

1. Focus on building the overall R&D strength of the team
2. Gradually cultivate the core backbone of business line technology
3. Thinking about the construction of hierarchical echelon within the R&D team

1. Need departmental support

1 Supplement the current situation of insufficient number of back-end engineers

2 Consider team building budget (can consider raising within the group)

3 The department needs to consider the size of the team's support line of business tasks based on the status quo of the number of back-end personnel, and ensure that it is within a reasonable range.

 

Part IV 2021 Goals and Plans

Serial number	Team stability	Team technical strength	Business support ability	Synergy
1	Motivate employees, actively participate in tasks, and get a sense of accomplishment from them	Work together to meet some small challenges appropriately	Support the smooth completion of basic business planning	Assist the department to achieve basic goals
2	Arrange team dinners and entertainment and fitness activities	Cultivate the team's centripetal force and encourage and support the creation of opportunities for it to participate in industry business technology forums	Guide and help employees complete challenging tasks	For cross-departmental collaborative work, encourage employees to actively participate and actively cooperate to complete
3	Consider and specify the reward mechanism to create a sense of reward ceremony. Consider and ensure that the channels for promotion of outstanding employees are smooth and promoted on time or even in advance.	Inspire and arrange business, technology sharing Cultivate and organize the smallest core employees in the group and the echelon of ordinary employees	Guide and motivate employees to take the initiative to undertake business support research and development work. And after the completion of the project, it actively resumed the market, found blind spots, made up for it, and improved employee awareness.	Summarize and review after the completion of the guidance and creation collaboration. Find deficiencies and sum up experience.

 

 

annex

1 PRD: A document describing product requirements

2 CODEREVIEW: Check whether there is code consistency, coding style, code safety issues, code redundancy, whether it is properly designed to meet the requirements (function, performance), etc. in the code.