Tuesday 14 December 2021

Do the project before you must understand the strategy

When taking over a new project, the project manager must first learn as much about the project as possible from various aspects.


Such as:

1. What is the project. 

What exactly is it, who is proposing it, and what problems are being solved.

2. People involved in this project. 

Such as investors, specific business stakeholders, operators after the completion of the project, technical supervisors, etc.

in addition to the complex structure of the owner's units, many other units will also be involved, such as project supervision companies, the owners' industry authorities and so on.

3. After a basic understanding of the customer's situation. 


The following thing is to understand their company's views on the project.

The most important thing is whether senior leaders value it, which determines whether the company will provide the strongest support you can when you need resources.

4. Before you plan your overall project. 

Get a rough idea of the resources you have. the first is time, and now the market is competitive, often many projects require completion within an almost impossible time frame.

There are some equipment preparation, the project needs large critical equipment to be booked as soon as possible, no matter whether the equipment or people and other equipment, waste is your time.

5. Make a project description. 


A good project description not only describes exactly what you are going to do (primarily what to do, not how to do it), but also to be thorough about how to check.

6. Is it time to make the master plan? 

No, you now know the customer's goals and the resources at your fingertip, so before you plan, you need to fully communicate resource issues with your manager and customers.

7. knowing what to do and what you have in hand and your overall strategy for this project, it is time to set up a project team.

Many project managers don't have the right to choose their own team members, so try to use your influence to find the people you want. the composition of the members varies according to the project, the difference is large, it is difficult to have any specific requirements, but, must have people who are proficient in the customer's business.

Unified contact, customer designated a person and the project team to communicate, can not leadership, are a few words, if they disagree, then you have only offended the leadership of the choice. therefore, the project will be set the rules at the beginning, the project team only recognize the views of one person, what requires you to first unified and then talk to me, i do not want to get involved in your internal business units between the contradictions.

All requirements changes should be written, remember! there are many advantages to doing this: there is documentary evidence, and later he wants to change it, you have the evidence he asked for before, tell him: you have said so before. easy to change the management of demand, how the history of how the requirements slowly evolve can be seen clearly, so as to better understand the customer's objectives.

8. Now you have to face three groups of people: 

Your leaders, your team members, and your customers, and communicate with them to let them know what you're going to do, when to prepare them for what, and these things will be your main job.

9. Make a plan. 

The first is to find a few key team members, such as customer business experts, system analysts and so on, do a project module division work.

Here's a thing to behold: there are many ways to accomplish a goal, and you choose one that you know best, rather than looking perfect, that will reduce your project's risk.

Sometimes customers will be moved by a new technology, insist that you adopt that new technology, you should tell him: you choose me to do this project, i should be allowed to do things in their favorite way, the new technology is attractive, because there are not many people to lose.

No comments:

Post a Comment