An overview of IT project managers

Step into the 30, although still on the road of technology, but also consider changing a function ... Not to say do not like technology, but feel that on the one hand and people to maintain the ability to communicate, because always do technology, suddenly found that it seems very unlikely to chat with people, a chat on the topic, feel a lot of time a lot of words are wasting time, this will not only affect their mentality, will affect life and family. Do not know is not as long as I am a person have this feeling ... Moreover, compared to the development of a long time, project management this piece of things or understand a little (according to the company's internal development experience in the summary), a little, summed up a little, more than the pressure of the body! Hahaha ...

1. Main responsibilities

A. Organization and management of the whole process of the project itself

B. Internal and external coordination: I. Manage customer relationships; II. Management Team

2. Main work

The main work will be on the life cycle of the project:

Pre-sales-"project development-" delivery-"finishing-" maintenance

In general, in addition to maintenance, other stages require the involvement of the project manager. Among them, the stage of project development contains 4 elements: A. Company; b. Team; c. customer; d. partner.

Of course, each stage is important, especially during the project development phase, and 4 elements need to be coordinated.

3. Quality required by the project manager

If you want to engage in the career of the project manager, what qualities are needed, mainly, should have the following points:

A. Leadership, the ability to unite teams and identify the next goal.

B. Responsibility, no matter what occupation, responsibility is always essential.

C. be optimistic and proactive. The project will always encounter a lot of difficulties, if there is no fight to kill the small strong spirit, it is really difficult to complete the project. At least in our industry companies, I see not one of the projects is very smooth, so very worried ah ....

D. Bear the pressure and distinguish the battlefield. Project inevitably out of trouble, encounter difficulties will have a lot of pressure, each role has its own battlefield, the programmer completed the bug, the project manager to deal with customers, are not easy to live, mutual understanding with each other is true love.

4. Managing elements

A.scope

B.time

C.cost

D.quality

Scope as the periphery of the circle, the other three elements as fulcrum, the formation of an inner-cut triangle, of course, the inner-tangent triangle of the various sides and focus can be different, but once the scope is determined, the other elements to be trade-offs and tradeoffs.

5. Planning and Workload estimates

When the scope of the project is determined, it is necessary to break down the requirements into individual usecase, the amount of tasks each role takes on each usecase, the sequencing of the tasks, and the resource provisioning on the critical path.

As for the estimated workload, this job is not unfamiliar to programmers, in the new industry, I do not know the domain knowledge, estimating the workload is a headache, it is best to have experienced seniors to help, otherwise the accuracy of the estimate is difficult to grasp. But on the other hand, this is also a approximate estimate, not too nervous, can estimate 3 time, and take full account of the risk, that is, a. At least, B. When it is most likely to take place, and in which case the project manager will try to control the risk of the project.

An overview of IT project managers