Internet Product Methodology: Demand change cycle

Article Description: Just PM's work can not lack of project management, but also lack of demand for management, accidental reasons, and the team to share my project in the "Requirements change" understanding and management methods. Suddenly found before a lot of product thinking and detailed thinking of things, but never sorted out the methodology, the follow-up should be more than finishing the methodology.

The proportion of failed projects in the IT industry can explain that "project management" is a difficult thing to do, the reasons for the failure of the project thousands, I believe that demand management, change management requirements is a very important factor. Just PM's work can not lack of project management, but also lack of demand for management, accidental reasons, and the team to share my project in the "Requirements change" understanding and management methods. Suddenly found before a lot of product thinking and detailed thinking of things, but never sorted out the methodology, the follow-up should be more than finishing the methodology.

I think there is a need to be infinitely concerned about the change in demand, which is aimed at two points:
1, the process of managing requirements change is in fact the process of clarifying the project objectives and the process of self-perfection.
2, the need to change the virtual team's impact is to avoid the PM, whether it is the trust of the PM, or for their own frustration, are very important.

The requirements change cycle I've sorted is as follows:

1, the quality of demand
Requirements include research process, communication process, document output and so on, PM need as far as possible to think clearly, express clearly, including the overall situation, rhythm and details. The level of demand quality can play a decisive role in subsequent changes, and messy, porous requirements will inevitably lead to endless changes in demand. But the quality of demand is not absolute, to see the project, look at the open program, for Agile Development, quality requirements may be 70 points is enough, fast iterative is the hard truth. For major projects, it may take 80 points to review at all levels. But in any case 60 points is necessary, the need to achieve a certain quality to enter the development phase of the project, this is the general case to take the evaluation of the way.

2, the team understand the same
PM Team, Project Virtual team communication effect is the most important, to clear everyone's understanding consistent. PM to their own research, ideas, expectations described clearly is the first step, this is the necessary PM course. But it's more important to be clear that everyone's understanding is consistent. Know that many times different people for the same sentence, the same description of the paragraph, the understanding is likely to be inconsistent, which will inevitably lead to subsequent development inconsistencies. So it's important that everyone in the team understands the same thing, not just to brainwash people, but more importantly to get everyone to do the same thing.

3, the sooner you find the problem the better
The sooner the problem is discovered, the less disruptive it will be and the smaller the impact on the project's progress. There are a number of possible ways to keep an eye on development progress and daily routine stations are good methods. PM's responsibility of course is not to start the development of all things to the project manager (or development leader, or WHO) to manage, the correct way should be either themselves is the project manager, or they also participate in the management of the project, the minimum they have to keep in focus on the project progress.

4, actively face
You can't wait until you find a problem, or change or give up, you have to make a choice. In fact, often encounter some situations, so that we are very difficult to actively face, such as resource constraints, such as time constraints, such as too much trouble, such as not to the boss, for example, can not explain to the students, such as the students will despise and so on. But not as always is the next worst, positive face is the only way to solve the problem, but also have to use the way.

5, update the document in time
Although the document is not the most important, it is important to record changes. It is important for team members, or for themselves, to record changes. Everyone's memory is limited, every review is not recorded, every mail is messy, each meeting minutes are not formal. The only formal, reliable is the requirements of the document, will change the content of timely update not but good work habits, but also for the project team leader performance, anyone doing so will be respected by others.

6, Freeze time point
Too much demand, too much temptation, every one of us is a perfectionist. Whether from the user point of view, or from their own perfect hobby, or from the leadership of the task, it seems that all need to do things to the extreme. But the ultimate needs to be step-by-step, in order to avoid project delays, members discouraged, we need to have a frozen demand point of time. Colleagues in order to protect the team and project progress, to the strict self implementation, all the time to think about it, I have become the cause of the project failure, think about what I have done is not the problem itself, but not the solution to the problem.

7, the necessary compromise
Things are not perfect, and quickly iterate for eternity. Regardless of the technical cost or the human cost, all have the valve value, although the technology can not realize the idea, the human cost is often not a problem, but the time cost is real. Moreover, the world does not eat into a fat thing, there is no good luck. Compromise is necessary even every day to face, compromise is not to give up, but need careful thinking and planning. Perhaps the previous consideration is immature, perhaps the follow-up can be better arrangements.

8, after summing up, can progress, avoid the same mistakes.

Http://daxu.net/archives/1333.html