当前位置：网站首页>Lightweight project management ideas

Lightweight project management ideas

2022-04-23 21:56:00 【InfoQ】

In the process of project management , We cut more PMP The project management method is applied in the actual project management . The author thinks , From the core content of the project , We can focus on demand management 、 Problem management 、 Task management for lightweight project management , On this basis, the stakeholders 、 risk 、 cost 、 quality 、 Progress management .

In the process of project management , We tend to confuse needs with problems . In a nutshell , Demand is yes and no 、 The category of good and bad , In other words, this demand either has , Or not , Or not satisfied enough , The process of meeting requirements is mainly to make users more satisfied . The demand is fuzzy , To what extent is satisfaction , Sometimes it is influenced by subjective evaluation .



The question is right and wrong 、 The category of right and wrong , In other words, the problem must be that there must be an error , The process of correcting errors is the process of solving problems . Solving the problem is to eliminate the dissatisfaction of users . The question is usually to determine 、 Definite , Solved is solved , No solution is no solution .


therefore , In the course of the project , It is very necessary for us to clearly define whether the user is raising a demand or a problem . If needs and problems are mixed together , It's not easy for us to sort out the priorities , It's not easy to define the scope of the project .


In the process of the project, how to make the project members, including users, easily distinguish whether it is a requirement or a problem , So that they can be managed separately ？


I think it can be explained in this way , We've analyzed it before , The demand must be followed by Why（ Why? ）, That's the purpose , Requirements must be used to achieve a certain purpose , Then we can ask the user to input the purpose when raising the demand （ You can also write down the impact if you are not satisfied ）.


alike , For questions , Since it's a mistake , Then there must be something right , We can ask users to describe what should be correct when asking questions , This makes it easier to distinguish . We can use a graph to show ：


null
remarks ： We can also more simply distinguish between needs and problems , Requirements can generally be described as what I want , The problem can be described in reverse as what I don't want .


The essence of a project is the process of meeting needs and solving problems （ The premise is the needs and problems within the scope of the project , Therefore, the scope of the project is very important , Projects with scope spread , It's hard to do well ）, Therefore, our idea of project management around needs and problems is no problem , We also discussed how to define whether it is a demand or a problem , We have solved the problem of result management in project management （ The satisfaction of needs and the solution of problems are result oriented ） The problem of .


In addition to result management, project management , We also have to focus on the process （ The author believes that from the perspective of life , We should pay more attention to the process , Because the results of human life are the same , That is, we should pay more attention to life experience ）, So what is the carrier of process management ？ The author believes that we can take task management as the carrier , The source of tasks is needs and problems , Therefore, the carrier of our third project management is the task , The task can be understood as the concretization of the work plan . The purpose of completing the task is to meet the needs and solve the problems .


In this case , Three carriers based on project management ： demand 、 problem 、 Mission , We can build a lightweight project management system , For the sake of understanding , Our diagram is as follows ：


null

With this lightweight project management system , Then we can use the tools we want to use to implement . Whether it's Excel It is also a special drawing board tool , It's all right .


In fact, this idea can be extended to the handling of any matter , Because of all kinds of things we encounter in work and life , Or meet the needs , Or deal with the problem , It is necessary to define clearly whether to meet the needs or deal with the problems .


Because the definition is different , The treatment is different , If it's a demand , Then the first step is to find out what the demand is , To explore the purpose behind , If it's a problem , Then the first step is to understand what is right , In this case , When we deal with things , The first step is not wrong , The efficiency and accuracy of handling things will be improved .


Last , There is another important point to note . Dealing with problems , It is often the responsibility of one party , The pressure will shift to the party who solves the problem , Because people usually know who caused the problem , Who solves the problem . This is more obvious in the informatization project , As long as it's a problem , It is often Party B who is primarily responsible for solving , The pressure is also mainly on Party B , I believe that all friends who are Party B's consultants have deep experience . If it is to meet the demand , It is often the cooperation between Party A and Party B to complete , Because Party A will also think that the satisfaction of demand requires the cooperation of both parties , Originally, the project team includes personnel from both sides . Such responsibility and pressure shall be borne by both parties , More conducive to the achievement of project objectives .


therefore , The author thinks , In the process of project management , It is necessary to turn problems into requirements as much as possible , What is not clear and correct should be , Should be defined as demand , So as to gather the strength of both sides as much as possible , More conducive to the achievement of project objectives .


This point , Of course, it is beneficial to Party B , Because this will make party a more cautious in putting forward the demand , The demand is also more reasonable . Because if it is defined as a problem , Then Party A usually feels no responsibility and pressure , It will be very easy to put forward , Once converted into a demand that requires both parties to undertake and invest , The proposer itself will become cautious , This is undoubtedly very beneficial to the management of project scope . In fact, this is also beneficial to Party A , If a project needs boundless , The problems are endless , Ultimately, it is also unfavorable to the whole project , In fact, the ultimate damage is Party A and Party B .

版权声明
本文为[InfoQ]所创，转载请带上原文链接，感谢
https://yzsam.com/2022/113/202204232147335758.html

边栏推荐

猜你喜欢

随机推荐