General IT project management related basic concepts (record)

PS, speaking of it (PM) project management, but also to mention the workplace two little understanding:

1. Choice is more important than effort;

2. Position is more important than ability.

Because it project management is now generally divided into the following three types of roles:

1. Product Manager, product-oriented---lack of business model;

2. Project manager, project-oriented---familiar with the general mode, have certain experience;

3. Technical manager, technology-oriented---have more depth and breadth of accumulation;

But most companies are not so clear, most of the body and many roles, the United States its name: Project manager, technical director, Department manager and so on, of course, according to the actual situation of the focus of the difference

It project management, in fact, is also a two key:

1.IT, which is for IT. And it's natural base attribute is processing (operation) + storage, which is now two mainstream cloud technology;

2. Project management, i.e. project management. In fact, whether it is an IT project, management is mainly human management, not technology and so on.

Here, I'll take you for a second. Several series of resource management in project management:

1. Cost accounting;

2. Contract management;

3. Asset Management;

4. Business Partner management;

5. Work together;

6. Schedule management;

7. Document management;

Wait ~

Nine management concepts for IT Project management:

0. Integrated management;

1. Scope (requirement) management;

2. Time management;

3. Cost management;

4. Quality management;

5. Human resources management;

6. Communication resources;

7. Procurement management;

8. Risk management;

The above sort is a bit of the basis of OH ~ and so on, such as 2,3,4 triangle relationship or something ...

It project management general life cycle:

1. Start, project;

2. Planning, design;

3. Implementation, implementation;

4. Closure, knot.

Of course, there are all kinds of requirements management, change management, test release and so on.

However, the whole process should be in the supervision, control, and the above each cycle should have a variety of corresponding outputs,

Unlimited documentation (like these two days I'm going to think about how to write a copy of what the schema document!) ), design, code, system, etc.

Models and patterns in common major software engineering (Project management):

1. Waterfall model---standardized documents;

2. Iterative mode---cycle iterative process;

3. Agile mode---with people, communication as the core;

The above, of course, there are other, there is no fixed pros and cons, why is it!

The above is a bit n big! There are other n more, do not want to---can only generalize slightly:

1. Management tools, text, graphics, sound and other---Unlimited code tools, analysis & design tools, project tools and so on;

2. Comprehensive ability, communication, coordination, analysis, logic, etc.

3. Thinking level, personality charm and so on miscellaneous.

N. What mind Mapping, UML, MRD/PRD, engineering, performance optimization, functional testing, coverage eg ...

In fact, a higher level, management generally divided into two kinds: humanized Management & Standardized management, but most of the time is used together, and the focus is different.

Finally, the general project management is nothing special, the problem is (as with the technology implementation) in the exception of the treatment scheme,

This needs a bit of experience, experiences, a bit specific analysis of the philosophy of the problem ...

General IT project management related basic concepts (record)