Friday 3 December 2021

Include project management into execution process


Speaking of "project management" we will think of information management, construction projects, etc. , in fact, everything is a project, our life is also a big project, in this large project, with a number of small projects, multiple stages, to build a complete life. This article talks about how to do a good job in project management, how to put project management into the details of the work.

Recently saw a paragraph, in my heart has a solidarity. The world we see people and things, there are surface world and the bottom world. For example, you see a person dressed, dressed, treated to talk, humble gentleman's wind, or you see a city in a well-organized, the road can not see a trace of debris, waiting area everyone in an orderly queue waiting for a taxi, or you see a wonderful football match, the two players fierce fighting, contributed to the climax of a stadium, let you excited.

This is the surface world we see, with hands, eyes, ears and things at our finger. But in such a surface world, must hide a bottom world, talk, easy-going friends, behind his education, support his resources;

In football, the formation of coaches and players is invisible to you and hidden in the underlying world beneath this surface world. To determine a person's success, the pinnacle of life is precisely his bottom world, and project management ability, is a person's work the most basic bottom ability.

When it comes to project management, we think of construction projects, information management systems, etc., but in fact everything is a project, our life is also a big project, in this big project, with a number of small projects, multiple stages, to build a complete life, inline activities, small projects built into different large projects.

Of course, today's topic is not about how to frame this big life project, but only from the perspective of project management, do a good job of project management, how to put project management into the details of the work.

I have the honor of contributing two software products from 0-1 to the company and serving as project manager for both projects. Both projects involved cross-project group collaboration and resource coordination, but the final two projects were delivered on schedule, with no one-day delay, resulting in more than 350 bugs, both of which resulted in a 99 per cent bug modification rate.

One of the projects was named the company's innovation project award, which is also a successful end to 2020. here, combined with 2020, i am responsible for a project, to share with you the experience of project management, and jun.

Overall planning

Being assigned to this project, i was a foggy, the first difficulty is to clearly do what, directional issues, but also need to consider the whole, how to make this project. so on the whole i listed a simple project plan and stage arrangement.

First of all, the analysis of the current state of the company, and i am responsible for the product is 0-1. this product has to be taken out for sale, so in October 2020, i hope to complete the delivery work, so that there are two months before the market warm-up period.

The final time frame was set, so i pushed back the approximate points in time for each stage, roughly divided into the following stages:

  1. demand research phase;
  2. project phase;
  3. product functional design stage;
  4. product development phase;
  5. testing and acceptance delivery phase;
  6. post-delivery phase.

These stages are not strictly divided according to our knowledge of project management, but rather a waterfall-style development approach. but there is a benefit to this, which is to facilitate the establishment of a clear project implementation path, that is, which stages we can complete this, and which stage the work we are currently doing can belong to.

But in the actual project development process, we take a waterfall and agile approach to the combination of. for example, the demand research stage is a complete and independent stage, we have done market analysis, user demand analysis, competitive analysis, in order to ensure the development of product understanding and the application of key technologies, in the process of competitive analysis, we asked the development manager to work with us to investigate the technical solutions used in the competition.

The goal is not just to use technology selection, but to give development key personnel an understanding of what we are doing, what the goal is, what technologies are available, to create a preliminary impression in their brains, and to reduce communication costs during the project and development phases.

In the demand research stage, we output the demand research report, competitive research report, research ability analysis report, and the company's existing system data bottom layer to do the relevant data combing, this part of the work by another product manager responsible for completing.

The output of the demand research stage is essentially to provide the basis for the next stage of project, of course, the demand research also uses the expert interview method, questionnaire, brainstorming and other methods in project management to collect information and obtain conclusions. The project start-up phase, which is a review by senior parties and project stakeholders to determine whether the direction is correct, what to do, what not to do, the approximate product framework and the appointment of the project manager, i am honored to be appointed project manager.

In the development phase, at first i took a very detailed scheduling plan for the project, but after about a week or two of work, i found that the project team is very proactive, with good results, decisively abandoned the detailed project monitoring methods.

Even the most basic morning and weekly meetings have been cancelled because developers want to be more dedicated to development and don't want too many meetings to take up their time. So we take the online work progress synchronization way, developers to their own development of the module deadline reporting, completion progress reporting, the expected completion time is also marked, to facilitate upstream and downstream developers to understand the progress of all parties, reasonable arrangements for their own work.

Product acceptance phase and post-acceptance stage, is the test and delivery department of various verification, we arranged for the research and development staff to submit various documents to support the delivery department to do the overall verification, such as database migration, deployment to the demonstration environment, the overall operating steps, database table structure and other handover, this process will not be repeated.

Overall, the entire development process is in accordance with the six stages of advance evolution, most of the work is completed before the prescribed time of each stage, on the horizontal line, the entire product development actually completed 15 days ahead of schedule development work.

Gradually refine


The above overall planning section, there are six stages, but the specific planning of these six stages is not very detailed from the beginning, it is a gradual detail process, the current stage in progress must be the most detailed, without experience or future stage is relatively rough.

For example, the current demand research stage, i put the demand research phase involved in the work of step-by-step split, such as the tender combing work, internal system data combing work, expert interview work, etc. , that bid combing work will actually be split down, such as from which channels to obtain tenders, the number of expectations, tender customer size, tender and the current product relevance is how ... (specific, enforceable, measurable, relevant)?

Each phase of the work is gradually to refine down the split, if a work feel that can not be carried out, the problem is that the demolition is not thin enough, too rough work will increase the difficulty of the work, the project team members can not be executed, and the results of the implementation can not be expected.

Therefore, on the basis of gradual refinement, the principle is to ask the research and development team and the person who will do it to evaluate whether to do it. you can ask him to tell you what he intends to do in the face of the task you have arranged, and if he can tell you exactly what he is going to do, it means that the person who arranged the task is competent.

Of course, the refinement of each stage is not the finer, the fuller the better, because this will waste a lot of experience, the first to dismantle the finer, as the project leader, on behalf of your entire project will be more implementation matters, more control points, so you will pay more experience. we don't like hands-on leadership, do we? because it means you don't have much room for your direct reports to play.

Similarly, project team members do not want to become a fully executed machine, so how detailed, how thin, depends entirely on your project team personnel, capable people, demolition of a little bit thick, so that he has room to play. poor ability to perform people, weak ability of people, a little more detailed demolition, the establishment of more control points and assessment points, a large task into a small task, reduce the difficulty of implementation.

Agile has a principle, appropriate, no over packing, so gradually refine this degree, need each project manager to grasp. the overall time node of the project, the situation of team resources, the tacit understanding of teamwork, etc. need to be fully considered.

If working with team members is the first time, discuss some of the ways and how to split them, agree, rather than enforce them. an execution plan that incorporates team ideas must be a better one, because team members are involved in thinking, have more awareness of the matter, and have a clear direction and perception of how to do it.

Solve the problem in a timely manner


A lot has been said before, it seems that this project is smooth sailing, but as the beginning says, smooth is the surface, but the bottom line is that every day there will be a variety of problems. for example, a previous discussion of good logic in the process of doing found that it is not available, to adjust, there must be a plan, is a big change or a small change, to assess the cost and value of adjustment.

For example, a well-done research and development staff, suddenly because of resource constraints, was transferred, and then you find that he was transferred may not have consulted you. for example, to do a function, are almost finished, the result of several leaders are not satisfied, no, must change, so overturn redo, modify the design more than a dozen times.

Every day there are all kinds of problems, it's just surrounded by questions, everyone will come over and tell you what's wrong, one way or another, and ask you what to do? i believe this is something that every project manager goes through, so what exactly should i do?

At this point, the experience of a project manager plays a big role. because some problems may seem small on the surface, but if they are not solved, inaction can cause larger problems.

For example, 

A small logical modification will take a turn and move the whole body, change may solve the current problem, but will trigger more subsequent changes and change costs. 


This requires the project manager to balance, if the current quality of the problem or customer and user experience perception is not very large, but modified will have a full-body impact, then the result may not change.


Some problems, is not changeable, such as i mentioned earlier, a function we have indeed completed, but, the stakeholders are not satisfied with ah, you do not change, the stakeholders back acceptance will not sign, that you can not hard scalp change, and before the change to fully communicate with the stakeholders, what they want, you can give different programs and let stakeholders do the choice of questions very important, remember the previous said, full communication is always good.

When it comes to solving problems in a timely manner, there is another topic, whether the solution to the problem is faster or better, the answer is bound to be whether. remember that in agile management, you learn a point of knowledge, when you have to make decisions, the later the better. because a problem is exposed, her underlying reason analysis is difficult, and the information and reasons you can get become clearer over time.

This is the difference between a junior project manager and a senior project manager, trying to fully define what the problem is, what is the cause, how to solve whether there are multiple scenarios, how much each different scenario costs, what is the value, and what should be done based on this scenario?

When to do is the right time. keeping the pace of problem solving in place is a very important ability of the project manager.

Carry full field

The project manager needed the ability of the carry whole field, the documentation, the plan in the row, the plan for discussion with the development, the X. 


Then conclude that the carry-on field requires the ability to pull horizontally and vertically. 


Vertically, how do you convince your company's leaders that this project can be successful in your management style and plan?


You need to put the facts reasonable, professional knowledge and experience are the conditions for bonus points. from a horizontal point of view, how to coordinate and pull through resources, put a thousand things that seem unenforceable, peeling, trying to break the break to find the entry point to start drying up, and can hand over the results.

In the context of the epidemic, more and more companies will be more inclined to short-term returns, whether it is the recovery cycle of funds, profit acquisition cycle, or the operation cycle of the project, time is gradually compressed, costs are gradually compressed. It has become one of the most important measures of a project.

So a good project manager needs to calculate costs and benefits for your project, to be precise, you need to understand how much your project costs and how long it will take to recover. this is why it is very important for you to persuade the top to be willing to do your project.

So supplementing the framework knowledge of project management and applying that knowledge to your project to practice is not necessarily the whole story, because different projects have different characteristics. 

But the essence of project management is to do a scientific management thing, to do good things, must first benefit the instrument. 


Therefore, in the process of project management combined with the knowledge of the project management framework, the formation of their own unique methodology is you can carry the whole field of the sharp instrument.

No comments:

Post a Comment