Thinking and summary of R & D Efficiency

author |   Tianrong

Preface

Before talking about efficiency , I want to talk about being a technician or a technology TL, What is the core value of R & D ？

I read an article before , It's interesting , Share your ideas ：

• T Outsourcing company ： The core competitiveness is not technology , It's a quick response 、 Provisioning consolidation 、 Project cost control .
• Enterprise informatization company ： The core value of R & D has three levels ： The first level is to use technology to better support the business ; The second level is to use technology to promote business , Use your own business experience （ Serve many customers ） Help customers ; The third level is to use experience accumulation to influence the industry .
• Product companies that solve specific scenarios and problems ： The core value lies in technology , Focus and do technical depth .

What are our core values ？

（1） Efficiently support the business ： One is support , One is efficiency

• brace ： The requirement for us is ： Phasing and business objectives , Alignment of landing products .
• Efficient ： Thinking about R & D efficiency . Explain our value with data

（2） Influence the industry with technology ： This requires continuous accumulation and thinking .

（3） Build technical barriers and technical infrastructure , Ensure system stability , Healthy and sustainable business development .

A lot of times , We have been thinking about how to efficiently support the business . There are many articles shared on Alibaba technology sharing platform or online , Every TL We also have our own methodology for the situation of our team . Today, I combine the situation I face , Share your thoughts .

Personal thinking

Think separately from several dimensions ：

1. R & D process efficiency ： Split phase , Find the key problem , Put forward a plan

（1） Demand stage

problem ： The need is repeated , The demand is not clear , Demand dispute

Solution ：

1） Ensure the validity of requirements , Clarify the scope of business value and needs , And ensure the consistency of requirements understanding .

2） Content of requirements , First, communicate and focus in a small range ; Wait for the needs to be discussed clearly , Then pull relevant students to participate .

3） When the demand is controversial , To avoid repetition , Pull the relevant students together to focus .

4） Daily needs , Schedule regularly , Sunyatong .

（2） R & D stage ： The production efficiency in research and development is explained separately .

（3） Joint commissioning and testing stage ：

problem ： The efficiency of joint commissioning is low , Environment unavailable , The quality of the test code is low

Solution ：

1） Fore and aft end separation , Each has Mock The ability of

2） Daily environmental management , Degraded system service dependency , Ensure that the test environment issues

3） Benchmark test cases , Smoke testing , Automated script testing , Ensure the quality of the test .

（4） Release stage ：

problem ： High release frequency ; Locating problems takes time ; Deployment time

Solution ：

1） Merge the publishing systems at the same time .

2） Agree with the business on the release frequency , Control the release cycle .

3） System depends on governance , Reduce deployment time ; And pack in advance

4） It takes time to troubleshoot problems , Provide corresponding troubleshooting tools .

2. Production efficiency of R & D

For R & D process production , We will improve R & D efficiency from the following aspects ：

（1） Full link technical specifications ：

Every process , Unify standards by standardizing documents , And through publicity and examination , Let everyone know the content . And through a typical case of exposure , Strengthen the value of normative content .

（2） The full link service can be configured

• u Page configurable ： form , List of pp. , Details page , The document page and other middle and background pages can be configured . Typical cases ： Suitable page construction
• u Logic can be matched ： Business parameters can be configured ; Business rules can be configured ; Typical cases ： Category characteristics ;
• u The model can be matched ： Define the data table or business model in the form of metadata + Typical cases of two ways to expand fields ： Category properties  ;NBF Modeling platform
• u service & Process planning ： Second composition based on atomic service capability . Typical cases ：AECP Service choreography for ;NBF Service arrangement of

Atomic tool capabilities based on appeals , Combined with product factory and solution capability , Link horizontal and vertical business configuration capabilities , Form a layered configurable view of full link services .

（3） Unified lateral support tool

A support tool that connects the commonalities within the team , Build a . such as excel Batch import and export , Approval process , Notification tools, etc .

（4） Nonfunctional code

• Use scaffolding ： One click generation application engineering , Including dependent jar Bag, etc .
• Code specification template ： Error code template ; Log template ; Engineering structure, etc
• Middleware isolation layer ： Including use cases
• General tools ： External open source tool classes ; General class of business abstraction ; Self developed abstract general tool class ;
• Business standard interception ： The user login ; Service exception handling ;dao Execution time of
• stability ： Current limiting ; Apply self-test ;

Abstract the common code of all applications , Precipitate into jar, In the project, by default .

（5） Deployment delivery ： Deployment manual guidance ; Unified troubleshooting tools ;

（6） Interface documentation ：web Layers follow swagger standard ; Competence center / The tool follows the interface specification documents and client Use case description of .

（7） Clear boundaries of system collaboration

We're landing , There are often system calls , Problems such as system dependency , It is recommended to start at the initial stage , Define these key issues , Then look for TL or pm Coordinate to solve .

3. R & D collaboration effectiveness

Through process specifications and templates , Agree on your cooperation mode

（1） Daily Q & a collaboration process

 

（2） Project process management

Through the following campaign template , Synchronize project progress ：

 

（3） Daily demand scheduling

Agree on the demand scheduling cycle , Fixed time , And communicate needs through collaborative management tools .

Later, you can use collaborative management tools , Analyze statistics .

4. R & D personnel effectiveness

（1） Learning and training ：

Through continuous learning , Or by leveraging other teams , Improve the technical level .

By precipitating team norms , file , Cases and other schemes , Let's complement our knowledge .

Summarize through the second round , Precipitation typical cases , Internal sharing , Avoid repeated mining .

（2） The test

Learning alone is definitely not enough , It also needs to be strengthened through examinations . You can use this tool ： Alibaba online examination system .

Performance indicators

Develop indicator data for the process , Monthly drying and comparison , Analyze the data , Positioning effectiveness . Key indicators can be referred to ：

（1） Requirements lead time , Number of requirements delivered , Number of projects

（2） Code committed

（3）Bug Count

（4） Online problems and faults

summary

By optimizing the R & D process , And there is clear data quantification , Prove the value of R & D to the business .