Programmer growth chapter 27: how to evaluate requirements priorities?

There are many sources of demand for the project , Finally, the products sort out what to do , What don't do . As I said before, when reviewing requirements , Be clear about the purpose of this version . These functions are the means to achieve the goal .

In general , We all default that the product or technical director prioritizes the requirements . For example, high priority 、 in 、 low . In fact, this is not enough detail , What are the high priority criteria ？

Want to do a good job in priority management , First of all, we have to formulate a set of Standards . It doesn't have to be very accurate , But it must be available and open .

Any need , All have their value . Its value is mainly divided into ： Commercial value 、 User value .

Commercial value ： Directly bring profits to the company 、 Achieve long-term strategic goals 、 Reduce operating costs and other functions .

User value ： Enhance user experience 、 Improve user efficiency 、 Solve user pain points and other functions .

So , We can get a two-dimensional four quadrant diagram

thus , We can get ：

High business value 、 Demand for high user value ： Do it right away ;

High user value 、 Demand for low business value ： Do it when resources are free ;

Low user value 、 Demand for high business value ： Do it selectively or in another way ;

Low commercial value 、 Low user value requirements ： Don't do .

Why should we give priority to business value ？ Because there is no commercial value , The project cannot last . Every demand needs human resources , In the case of limited resources , We can only focus on high business value 、 On the demand of high user value .

After excluding some requirements through the value dimension , There will still be two equally high business values 、 High user value task conflict . We can choose to continue to subdivide , Continue to divide according to the two dimensions of emergency and cost , You can get ：

emergency 、 Low cost and high business value 、 Demand for high user value ： Priority comes first ;

emergency 、 High commercial value at high cost 、 Demand for high user value ： The second priority ;

No urgent 、 Low cost and high business value 、 Demand for high user value ： The third priority ;

No urgent 、 High commercial value at high cost 、 Demand for high user value ： The priority ranks fourth ;

Most companies , Rarely need to be dismantled to this extent , If this happens , I think it's a good thing , Companies should recruit more people as soon as possible to accelerate the landing of business value .

Can the project requirements change ？

After the general requirements are determined , It's best not to make temporary changes . Except in special circumstances . What is a special case ？ This is the advantage of making requirements priority rules , If there is more urgent 、 Low cost and high business value 、 Demand for high user value . We can change . As long as members of the team agree with this rule , It will be easier to implement .

What if the leaders don't follow the rules to change their needs ？

Who bears the responsibility, who makes the decision . If the leader wants to change the demand temporarily , And after the department head has fed back the impact of the change , Still so . We still have to listen to the leaders . At the same time, explain this truth to the team . And the position of the leadership station is different , The high-value tasks we think are not necessarily right from the perspective of leadership .

There may be many similar situations in the company , Everyone may have different opinions , Finally, it always needs someone to make a decision . Before making a decision , We can make suggestions . But if a resolution has been made . Then you can only execute .