Two monks carrying water and water, three monks carrying water and no water drinking------the organization structure of IT project management

Speaking of Project manager post, the general idea is that a project can only have a project manager, otherwise the responsibility is unclear, shifting. The IT project requires two or even three project managers. What is the reason?

A typical IT project (which does not contain purely technical or tool-like projects) is the realization of transforming the user's needs into an IT system. There is a contradiction between the demand and the realization. The demand is uncertain, the plan cannot be unfolded, the demand scope changes, the realization plan also must change accordingly. It seems that the scheme can only follow the demand, and there is no contradiction. But the real situation is that it system implementation is not as flexible as some vendors promise, anytime, anywhere, how to change. Even with this flexibility, the resources that are spent are irreversible. This is like a game, two people back to back, a person holding a picture, another person according to the description of the painting. Business people speak of his business, and it people draw a system program. But they don't know each other what they see. Before the results are phased out, the person in the business does not know whether the IT person understands his intentions correctly. Once the deviation is understood, a picture will void the repaint. IT project management methodology revolves around the goal of a one-time "paint" success. The organization of the project is to ensure that both the requirements and the implementation of the program are always responsible for the final results, and in the case of external suppliers, they are sometimes added to third-party project managers.

The project manager from the business side, to ensure a clear description of the requirements, the resources he mobilized is often the business backbone of the business, while the IT project manager, according to his understanding of the business to make the system implementation, he mobilized resources are programmers or external software vendors. Once the requirements are not fulfilled, or if more resources are needed, the project manager will agree on the problem itself and advise on how to solve the problem, but the decision must be made by the Project Management Committee or the project sponsor (investor). Only the initiator can choose whether to crop the demand or increase the demand to make decisions about the resources that are out of reach. Simply put, the initiator has the right to decide whether the painting (or part) is redrawn.

If there is only one project manager, this contradiction will be on one person, can not be exposed. This project manager often makes decisions based on his or her own position. If a project manager comes from a business unit, what happens is that the project needs cannot be determined, and once the project is started, many people will involuntarily become perfectionists. There is a mentality: I spend money, of course, the more the more cost-effective. But I do not know, such a project is like falling into the mire, in any case can not get rid of these two feet mud. If the IT staff as a project manager, the common problem is: The system is done, very good, users to use it. When the user jumps out, this is not what I want at all. It is one of the most commonly said "IT systems and business two skins".

It projects, starting with the project structure, from project managers to project members, like playing "man-to-man". Each stage of the outcome of the two sides agreed, only to agree, there are differences, the level of submission. Need to restrict each other to the bucket of water leveled, end to the temple, calculate into a fruition.

This is the project, there is tension between each other, go in one Direction


This is not a project, but we do one thing together, a person's strength is not enough, so many people

Two monks carrying water and water, three monks carrying water and no water drinking------the organization structure of IT project management