How traditional PM is to infiltrate the Internet

Recall just joined Tencent's time, all let the first start of the author's heart is very disturbed, here Wood has a traditional project big plan, Wood has very clear traditional standard requirements specifications, all kinds of wood, we are bunt battle, quickly run. At the same time the project is small and intensive, two times a week, demand, such as rain, and the past has done at every turn one or two years, but also shorter than three months more than the project, it is a bit more dexterity than expected, once overturned the author of the concept of the project. Fortunately, I met a good mentor and a very strong brother. In half a year of groping and temptation, the brothers were the author of many toss, still continue to support, thanks to the mentor and team brothers. Now half a year past, a variety of bitter tangle, sweet aftertaste, write down and share with you, I implore you to shoot brick guidance.

Before writing, do a summary of the groundwork, in chronological order, will expand the content of the following points:

Look more ask, small step evolution, clear direction, focus;

The process of carding, training habits, encourage communication, improve efficiency;

Clarity of responsibility, clear interface, moderate planning, orderly and agile;

The concept of guidance, the inevitable, open cooperation and common growth.

These contents are from the beginning to join the team so far experience, but also the way over the course, nature is not just the general outline of the above, and look at the start.

See more questions, small steps evolve

Every one has the ideal youth, in is entrusted with the heavy duty time, all hoped that oneself immediately can devise, the gas dead GE to match the ovary, three fire a burning, flag to Rusan. In fact, the ideal is very plump, the reality is very bone feeling, three fire down, either burning a pot of charred, or burning a pot of half-cooked.

Thanks to the teacher repeatedly told, asked to see more questions, so I quietly put out his torch, calm down to observe. I asked myself three questions:

1, the overall development of the electrical business model is what;

2, the team is facing the problem is what;

3. Where is the project manager's position in this team?

To answer these three questions is a long article, not much to say here, the meaning of this is that when the PM first to a new team, is a Chinese medicine Hango approach to intervene, or the current popular violent demolition of the way to intervene. In particular, the traditional IT project manager from the students, must face up to the Internet in the project management of the particularity, the need for flexible integration, small step forward, in the maintenance of team output, further improve team efficiency.

When I first entered the team, the Hango was naturally used:

-Hope, look at the team atmosphere, the environment, working methods;

-Smell, some people may ask, the team can be smelled of things, tell you there is, that is the team members of the emotional smell, they generally do not say or write in the face, but the intentions can be smelled;

-asked, the above three is to ask themselves, in addition to also ask the team, such as asking the team where they feel uncomfortable, where the feeling is very troublesome, always to detect the current pain point as the goal;

-Cut, the appearance saw, you have to in-depth to understand, cut is a solid to get into some practical work, from the practice to verify, to find a variety of good to keep the bright spots, as well as a variety of pain points to adjust.

The following author to share the early days of the author of the fruit will be the story, this is a story about Hango.

Small skills to share the fruit will: just to the group, the first round, very not accustomed to find that there is no regular meeting, is for hope. Continue to find new students, not only is the author himself, in the initial period of the smell of melancholy, because the sense of distance to eliminate a bit difficult, is to smell. A round of interviews, the general reaction of the comrades meeting still need to open, but no one has the time to organize, is to ask. In the first two weeks, there is no regular time to focus on a variety of communication and feedback, so that the day-to-day work of the overall focus of the whole, this is cut. The pulse is complete, start the right remedy, the team meeting must open, the team construction also must open, but, is separate to do? Or does it work together? The author's answer is to combine, is both a team meeting, but also a regular team building. How do you do it? First, with the development of leader communication, for some funds, at each regular meeting to buy some fruit, the meeting is called the fruit, the first to talk about the business, after eating fruit open exchange, the atmosphere of the meeting is active a lot, and the mission to build two affordable.

Project management is a very flexible thing, Hango can let the author is to start with the needs of the team as a starting point, and then open in line with the long-term interests of the team to improve the door of continuous improvement. At the same time a variety of people-oriented small skills may be able to receive miraculous, we can exert creativity, do better.

Clear direction, focus

At the beginning of this section, let's start with some very practical questions:

-The team is very busy every day, but the parties still say not support, how to do?

-Demand from many directions, can do not do, how to do?

-All kinds of scattered consultation, support requirements flying, how to do?

These problems in reality in the old team is very common, as a team that has worked for many years, our team is actually very bitter force, in addition to the main platform of electricity, all other business have support, you come to me to not lively, but the team members only so many, quite tired posture.

After the first round of Hango, you can find that with the team's current human situation, only the existing main platform to carry out full support, otherwise it is the force does not catch. So the team has a highly consistent desire to focus on supporting the business, back to the support of the main platform and the continuous improvement of the basic technology framework itself, but has not been thinking about how to focus on cutting.

This is an imminent thing for the team, not good treatment, will drag the team into a muddy mud, in this muddy, each upstream can not be fully satisfied, they suffer from exhausted, downstream testing and operation dimension is also immersed in it. This time, we need to help the team to determine the direction of the team, and then find all levels of boss communication, reposition the team's position and objectives, to conduct appropriate business cutting.

Some people ask, you say focus on the focus ah, too much water, wood dry goods, then we have dry goods, the team in the intention to focus on the following considerations:

1, the current support of the business, whether the company and the Department of strategic consistency?

2, the company and the Department of strategic display is not suitable for the author to support the business, whether the overall gradual transfer out?

3, the company and the Department of strategic display should be supported by the author of the business, whether the highly customized part of the transfer out?

4. Will these transfers cause damage to the long-term interests of the company and the department?

The first three points are some of the key points in the team's business screening, and the final point is the ultimate principle of whether the team decides to transfer. If you violate the 4th, advise everyone not to mention the handover, this must be a team. Because of the long-term accumulation of product managers and technical leader, focused programs come out faster, at the same time very fortunate that the team focused on the attempt to get the strong support of the leadership, eventually some of the business is fully transferred, some of the customization part of the handover, very smooth realization of the focus again.

If a team is already on the running, then it is necessary to look at their business, focus on whether the team is still focused on their own business, energy is limited, after all, the team's brothers are not leaves asked.

Comb the flow and cultivate the habit

The team was initially involved, the business was focused, and the questions remained, such as:

-demand is still flying, development scheduling is still very confused, how to do?

-The Development brothers did a lot of work, but the outside world still asks repeatedly, what are you doing?

-Product managers often want to know the progress can only find the corresponding development brother often urge to ask, how to do?

-Test daily Feedback said, this turn is too random, now come to one, now and again, no plan also no notice, how to do?

-Yun-Dimensional said your release is too messy, too casual, how to do?

-Other Brothers department said, want to cooperate with you, the demand is swollen Santi, mention you will do, how to do?

In fact, this pile of problems, are involved in the process of the problem, specifically, is the need to find who to mention, what standards can be ranked, testing when the intervention, where the information published and so on.

工欲善其事, prerequisite, tools are very important, some people use Microsoft Project, someone with Excel, others only use the whiteboard. Electronic business has been used by the company's own research and development management platform, to be honest that this platform tool is not a more perfect tool, but the combination of practical flexibility to use, but also to the team to bring greater help. Therefore, combined with research and development management platform, solve the above problem team using the following methods:

1, all needs must mention the research and development management platform, the demand must go through product group's product manager to access, solves the demand source the question;

2, all requirements must be the Product manager and the corresponding development review can be transferred to the needs of the team, the product group must be within the group needs rating, so that effectively solve the problem of scheduling difficulties, scheduling objectives become clear;

3, the option of the project manager and the development of leader hand, the control of the entrance, so that the development and follow-up to the implementation of the process is protected, but also effectively avoid the so-called black life;

4, scheduling and review, development, testing, product tripartite participation, to solve the test until the transfer of the knowledge of the problem, but also effectively promote the links of active communication and collaboration;

5, to the outside world, all progress and demand information from the research and development management platform to obtain, with the help of research and development management platform to achieve information transparency.

In fact, the measures are not many, but the resulting effect is very significant, the current team's regular scheduling will be less than half an hour a week, testing and development collaboration is also a lot smoother, the demand flow is clear, the parties will not be confused with how to submit the demand. Since all the information has been circulated on the research and Development management platform, the information is highly concentrated, at the same time has the credibility, and can be explored at any time. Anyone who wants to know what the team is doing is becoming very simple, open the team's research and development management platform, where the maximum use of tools to make the information transparent.

The process does not need to be complex, the process here is to let things rule-based, let the work smoothly and orderly, good process does not cause trouble, only bring orderly, efficient and transparent work information. The process is not required because of the specification, but because of efficiency, order and communication.

Tips Sharing: Application research and development management platform in practice is the most painful, so that each piece of information status and the actual situation to synchronize. At the beginning, most people are not accustomed to the system in sync state, the author team also have such distress. In order to improve this situation, a harmless punitive measure has been introduced, and if someone is not updated in time at the weekly regular review, it must donate 10 dollars to the team's fruit fund. Development leader and team members alike, in this thank brothers, in the author repeatedly find brothers to fruit fund, brother's active cooperation, gratified is, now receiving funds more and more difficult, because this represents the synchronization of the state has become a habit, thanks again for the cooperation of the brothers.

Symbolic small donation is good, similar to small safflower flower, the real goal is in the process of implementation of the habit of promoting habits, and eventually create new habits to actively drive the process, into the team's blood. Internet people are active, active, independent thinkers, and the whip is not appropriate to wave here. There is no need for a good team here, the good team is that the brothers will take the initiative to pass all the good, or bad news, and then the big guys to solve, or together to cheer.

Encourage communication and improve efficiency

I am also an old programmer, still clearly remember the following several distinct scenes:

-Boss asked, why make this appearance, answer Yue products let dry, boss batch yue, pig brain ah let dry what;

-Do a good product is waiting for praise, this day boss issued a commendation mail, Wood has its own name, grief and indignation unceasingly, the heart rises small resentment, dissatisfaction accumulate in;

-See brother sigh with regret talent, boss Blind, quietly ran away, heart born desolate.

After a slightly older look, really is boss no eye, really is the product is not reliable, not also, just give up the expression of power, passive, passive, and repeatedly passive, so really put themselves into the corner, in the division in the already, two do not fall well.

Every boring programmer has a philosopher living in his heart, the author is most willing to use dumplings filled with the teapot to compare the development of the brothers. They are all very talented, but they are very silent. No matter how unreasonable the demand, they are accustomed to a slight resistance, they began to concentrate on how to achieve. No matter how great the product is, in the celebration mail even if not listed their names, they will only silently in the hearts of bitterness under the bitter force. Many people say, is this related to efficiency? I would like to say that a great relationship, very related!

The author has not been too long to work, in terms of experience, compared with a happy to express their feelings, often to maintain a happy development brother, is the most effective development brother, is also the most unlikely to silently jump to make you depressed to cry the development of brothers; a willing to share the development of brothers, is the fastest growth, It is also the most helpful development brother who can help improve the effectiveness of the whole team. A development brother who dares to express the correct opinion when demand comes, is like a door-keeper, and is a development brother who can guarantee the team's output is always high quality.

The team's six months of practice in this area are:

-Open a bi-weekly sharing, each issue let development brothers go up to share their experience and experience;

-Ask at least why, if there are any better alternatives, when the requirements are reviewed;

-Encourage the brothers to communicate with each other, encourage the brothers to come out from the RTX, face-to-face communication;

-Encourage the brothers to put forward optimization suggestions on their work and team;

-At the regular meeting, although the research and development management platform has enough information, still ask the brothers to express themselves freely.

Each development brother is a bonanza, PM we want to let brothers not just will be slightly hot pot mouth, PM we also want to let the brothers to open the teapot lid, light up their full hot and carefully cooked dumplings, after the mysterious harvest it. With the author of the team's two-week share as an example, each period of content and share the witty lines are often let people admire. Now, the team's goal is, in the second half, to let some of the development brothers embark on the whole electric business hall.

Communication is a very systematic project, we have no way to improve the communication ability of all of us at once, but we can encourage the communication behavior itself, so as to improve the willingness and ability of communication.

Clarity of responsibility, clear interface

Responsibility is a very interesting thing, once spread to a lot of people, we will habitually put it from their own body pinned to other people, this is not related to the noble or not, as the author of the old home often said, a dragon water grain full Warehouse, two dragons flood the river bottom dry.

In the author's team, at first the related contradictions will appear in two places:

-The demand state is not transparent, can not quickly what needs to be queued up, which requirements have actually been released;

-External to the team when the need, may be to find TL, may be to find a few product managers, or perhaps directly to the development of a brother or project manager;

This actually led to some confusion, the 1th solution is relatively simple, the demand can be fully dismantled, implementation to the person, one responsibility clear, and secondly, the workload assessment can be more accurate. Supplemented by the previous mentioned fruit will fund donation system, the demand state of circulation more timely and credible. At present, after the process has been set down, after a period of implementation, we have formed a day to see the state and circulation of good habits, fruit funds to collect donations more difficult is higher.

The 2nd will be more troublesome, need the team both inside and outside the two-way interaction to promote, and finally set a few basic criteria:

-All requirements must be evaluated by the product group, through the joint review with the development side and Test side;

-developers, development leader and project managers should be involved in the follow-up of the Product manager when receiving external requirements;

-Product group According to the current business direction, the division of labor, clear related responsibilities and interface direction, in the parties to ask, you can easily find the corresponding product interface person.

Once need to come, the development group is like the grass boat borrow arrows in the straw, often by slashing demand directly bombardment, knee don't know how many arrows. A few axe down, first of all, the product group, the development of the Division of responsibility, and then further positioning the product interface, all of a sudden the sky clean, locust arrows rain no more, the demand began like a trickle of water from the product group slowly. Thank you for the hard work and support of our brothers in the front line.

We should listen to all kinds of complaints, encourage the truth, and try to redefine the responsibilities and redefine the rights and obligations of the brothers when they are annoyed by all kinds of foreign noises.

Moderately planned, orderly and agile

When I first came to the team, I was often asked:

-Can you hurry, faster, we're not agile?

-Why do we have to plan, don't we respond faster?

-The team has no time to waste, we can not finish the brain immediately realize, see the effect?

And so on and so on, it seems to be quick, agile is fast; it seems that there is no need for planning because it changes; it seems that everything is a very quick response, a very quick test, without the need for directional guidance and evaluation. So is it possible for the team to do it without losing the plan or the speed?

First back to the reality of the team, the first time in the team, the team planning is relatively weak, emphasizing the weekly schedule to respond quickly to a variety of business needs. In the process of taking over, the scheduling has become a big problem, so that everyone has a headache, while more long-term planning has become difficult, in the day-to-day hard, there is no time to look at the direction. So decide on a modest plan to give the team a rough idea of what to expect for a while, and still turn on the weekly iterations to respond to sporadic, urgent needs. The overall planning chain and the general emergency response adjustment after the status quo is as follows:

In the diagram above, there are several branches of unplanned requirements, such as urgent and complex requirements, which will be developed in a project iteration by entering the monthly plan of the month according to the principle of precedence, and in the case of an emergency and complex requirement.

In this combination of long and short iterations, the author team can be more effective to maintain a certain degree of planning, but also to the day-to-day emergency needs of timely response. There is the order and rhythm of moderate planning without losing the agility of delivery and response.

It is hard to say whether this approach is agile or traditional RUP, which is more like a tailored practice to refer to both, without the best methodology for treating all ills, for no silver bullet. I throw a brick here, I hope all the team can give themselves a fit of good clothes.

The concept of guidance, the inevitable

"I have a steel whip will you play!......" Ah Q brother had a dream is to take the steel whip when the leader. Can we learn from him? At least it is also highly educated, and again, I am a general pm, hand also really have no steel whip! is not the steel whip things can not be pushed, the United States and the party with historical experience to tell you that propaganda work is an organization's family heirloom. Back on the ground, it's not easy to do something when you're working on a team, and the following questions are usually challenged:

-The team is working well, why should we follow these measures?

-What are the advantages and disadvantages of doing this?

-Soft resistance, coping with the treatment, and so do not urge to quietly stop.

Of course, there will be some other problems, a few typical examples to do, in the process of implementation, the promoters pushed hard, the implementation of the guys also accept hard. Personal experience, prior publicity is important before a measure is implemented, that is, to conduct a series of guiding publicity in the team before implementation, and to really take the long-term interests of the team as the starting point.

The purpose of the nonviolence is to clean up the possible misunderstanding area in advance, which will effectively prevent misunderstandings in the execution, lead to a variety of far-fetched interpretations, and even cause conflict, and the team also has the opportunity to prepare fully in advance, to dissolve the resistance that may be encountered, triggering the motivation to try. If it is really a good measure, it is also good for the team, then in advance after the full guidance, will inevitably be able to do, with less effort.

Share the author of the team to promote the two-week sharing, the team has been a fortnight to share, but because of busy and other reasons, did not continue. How can we mobilize our enthusiasm when we reopen today? We are focused on discovering the benefits of sharing for everyone, and if there are tangible benefits, these benefits are broadly as follows;

-bi-weekly sharing can give everyone stage, let everyone try to show their director;

-bi-weekly sharing allows you to absorb other people's experience and broaden their horizons;

-Before sharing the preparation, can effectively summarize their experience, promote their own growth;

-Capacity-sharing is an important part of a person's comprehensive capacity and contributes to long-term development within the division.

And so forth, there is no false benefit. The nonviolence must be believable, true, and considerate of the team members so that team members will be willing to believe and willing to devote themselves to doing this thing. The current team of fortnight sharing is very good, each issue of comrades will be actively prepared, but also speak of each style.

Open cooperation and grow together

This topic is relatively large, open cooperation is the general trend, like QQ online shopping in the previous days to access the Alipay, Tencent also began last year to advocate the opening of the entire platform. Winning organizations and individuals will receive more positive support and feedback, allowing the team to thrive in a healthier atmosphere.

This part does not say what experience, more is a message, Tencent Power, and even the whole of Tencent, large areas need the cooperation of various groups, small aspects to the product group, Development Group, test group, operation and Maintenance group, the cooperation between the Operations group, we can together. Implementation to the individual, for the development of the need to try to understand the product Managers KPI pressure, the product manager to try to understand the development and testing of these back-end brothers trivial and difficult, the team understand each other, support each other, we together and the electric business grow together.

In the author team, the team will also have some attempts, such as the development team of the Forum, not limited to the development of technology sharing itself, will always invite product managers, operations, testing to share their work and experience, thereby promoting the understanding and cooperation of all parties.

I mentioned the part of the business of the highly customized part of the transfer of business units to deal with their own, in this matter, in fact, from the point of view of cooperation, they do their best thing, the author team to provide the bottom of the technical platform, the business side according to their own will more rapid response customization, the director of the exhibition, in the cooperation of mutual benefit.

At the same time, the team is also committed to the construction of the operating platform, the maximum of the relevant operational cooperation ability to open up, so that the operation can be a case of the results of the independent optimization, the platform on the line, a lot of the operation of the students gave a very warm welcome, this is a win

There is also a team of encouraging communication, clear responsibilities and interface, these are to allow individuals and teams more open, can be better to work together to form a collective combat effectiveness.

Open and cooperation, the team will continue, the team's future, must be more open, but also more understanding of cooperation.

The final conclusion

Scattered written a lot, from the traditional to Internet projects, at first contact will feel the contrast is relatively large, but in essence, we all hope that the team stability, high efficiency, orderly implementation, high quality, transparent information, high trust. The selfish thought that the distance did exist, but not more than imagined farther. There are many things are interlinked, such as all should be people-oriented, planning as a tool to process the establishment of team customs, performance as the goal. The level of execution is different from that of inclination, and the big vein is still the same.

The last list of individuals to feel the difference, for you to refer to. Planning is important, but it's not the only thing that matters, such as the need for teams to respond to higher-priority bursts of demand at any time; The project is not necessarily planning to all-inclusive the overall delivery, the big project can be broken down to do, such as to maintain the rapid small steps of the iteration, continuous delivery; The process is not necessarily to be stuck to the dead, in fact, can catch big and small To maintain the autonomy of the team, for example, after the team matures, you can try to delegate partial options; priority is not immutable, in fact, every time the priority may be converted, so need to update the adjustment; The team must cherish the good, because the Internet is a large number of small projects strung up by the big business , you will be with your team in n many small projects together forever.

Project management, in fact, there is no way to copy copy, different teams, different large environment, will have their own different practice options, the operation of no advantages and disadvantages, only whether the most suitable for their own team's consideration. In this throw brick piece, expect to get more response, mutual exchange promotion.