Thoughts on how to manage technology

Thoughts on how to manage technology

 

This series of articles is written by ex_net (Zhang jianbo). Please indicate the source for reprinting.
Http://blog.csdn.net/ex_net/article/details/8592574
Author: Zhang jianbo mailbox: 281451020@qq.com Phone: 13577062679 welcome to exchange calls!

 

 

Baidu encyclopedia explains "Technology Management" in this way. Technical Management usually refers to the management work in the technical industry. managers generally have a high level of technology and lead their managed teams to complete a certain technical task. In actual operations of technical management, the emphasis is on the technical distribution, technical orientation, and technical supervision of the managed teams. Managers use their technical knowledge and capabilities to improve the efficiency of the entire team and then complete technical tasks.

In practical work, we are faced with growing teams. I am often confused. Today I forget this, and tomorrow I think of it. I often act as a "fire-fighting teammate. Tomorrow, when the night is quiet, I will always be wandering. I can't always "fire" every day, right? What's more, some problems are not what you are good at, or you don't understand.

At present, our team has formed the development architecture of "Hardware group" and "software group. The hardware Group involves "51 Single-Chip Microcomputer", "arm", and "arm" technologies. The product covers multiple product lines, including alarm, video monitoring, and building intercom. The software involves "Web Application-based project management software", "WPF-based Intelligent Integrated Building Management Platform", and "B2C e-commerce software. Every day, we face a huge line of products and complicated technologies. I always feel exhausted.

Timeline 1 passes every day, and the progress of each project is not very smooth. Slow progress. I often think about how to accelerate product development? Is there a way to stop yourself from being so tired, but the team can make it faster?

Technical Management may be a problem faced by many technical directors?

Two years ago, four or five of my colleagues followed me. At that time, we may not be able to talk about technical management. Now the entire team is more than 20 people, all of which are pure technical development teams. It is really hard to manage them.

In recent months, I began to figure out some "Source code management" and introduced him to "using SVN for Technical Management".

Because our team is divided into "Hardware group" and "software group ". For hardware groups, in general, every Member is doing things in such a process as "determining requirements, checking materials, drawing schematics, drawing PCB diagrams, circuit board proofing, purchasing components, welding assembly, testing, burning software, and whole machine debugging "., test ". According to these steps, I began to try to use SVN to build a warehouse to manage these materials. At the same time, the approval of the "technical team lead" and "department manager" has gradually become based on SVN.

As shown in, software products and hardware products are divided under product products. Manage hardware products according to the following specifications

/Product name [up to 8 letters] | ___ PRD product requirement document (PRD) | ___ Sch schematic | ___ layout PCB version | ___ Doc documentation | |__ datasheet related component data manual | ___ remarks and important instructions | ___ code source code (Compressed)

At the same time, in the workgroup, assign each member a sub-directory corresponding to the fixed folder on their local computer. You can also synchronize the Member's working directory with the specified SVN directory (, equivalent to a backup ).

The product manager (technical team lead) regularly checks the progress of members and extracts "Product Information" from the member's working directory into the "product directory ".

Ideally, I just need to look at several fixed product folders (haha ).

 

For software products, after development in recent years, I feel like a "marathon ". Therefore, for the software, a "SVN account" is assigned to each member, the specified path is configured, and the "read/write" permission is developed for them for development. For example, Configure permissions as follows:

[repos:/product/software/lydj/mms]xzl=rw[repos:/product/software/zjzf]zmk=rwzjh=r[repos:/product/software/zjzf/ynlx]zmk=rwzjh=rycf=rw

The product manager (technical team lead) conducts regular evaluations and inspections. I regularly read the svn analysis report.

Next, I plan to find another analysis software for the svn repository. You can dynamically analyze the development progress. To put it bluntly, you can calculate the number of words you have typed ".

All of the above are just a bit of experience that has been coming out recently for your discussion. You are welcome to give more comments.