Moscow priority ranking method is a priority technology used in project management and software development. So that developers, product managers and customers can realize the importance of each requirement delivery.
Generally speaking, "not this time" will be removed in the project discussion stage. All the requirements seem important, but if the delivery time is tight, "You can have it" will delete the first batch, followed by "You should have it".
We analyze from the perspective of Internet product development:
Wechat, Alipay, Didi ... These successful products already have many functions, but initially they all opened the market with simple core functions. For example, WeChat voice message, circle of friends, Alipay free transfer, payment, Didi taxi function. Later, we added a dazzling array of functions, but we used the original function the most. Attracting users, satisfying users' pain points and cultivating users are the initial necessary functions.
And some failed products often have many functions from the beginning, euphemistically called "comprehensive" comprehensive access to the market. In the end, "everything is done, everything is poor", and the development and operation team is miserable-too many goals, tight time, unable to keep up with the configuration, and the team's attention is also very scattered.
Developing an Internet product, from research, product planning, design, development, testing, and listing, has a long cycle and many variables. Usually, when developing a product, the minimum feasible product (MVP) is made first, and then the product is modified by testing and collecting user feedback. Only in this way can we finally meet the needs of the market.
In order to reduce risk and improve speed, we should shorten each iteration as much as possible. How to shorten each iteration? It's actually quite simple. Try to verify only a few core functions in each cycle and iteration, and the whole process will become faster. If you think more and do more at the beginning, then the time of an iteration will be lengthened, the speed will be slow and the risk will be great.
First, list all the functions, and then divide them into four categories according to certain rules: must have, should have, can have, and not this time.
So what are the rules of sorting? In the article Why Companies Need to Prioritize Features Better, the author introduces three methods:
This is very useful for risky projects. The risk is unknown. To reduce risks, it is best to reduce the unknown and use knowledge to reduce the unknown. The following signals will help you understand that it is time to stop thinking about these functions and start thinking about reducing risks.
The team said, "We don't know if this is feasible ..."
The person in charge of the product said, "I don't know how the customer will react to this."
The architect said, "I'm not sure if this platform supports this feature."
The business analyst said, "I haven't figured out that part of the demand yet."
The tester said, "How can I measure it?"
For each of the above examples, it is a clear signal of lack of knowledge, which hinders the relevant personnel from moving forward with confidence.
Give an example of payment method: "The user experience model shows that 15% of people click the Paypal button to complete the payment process. Shopping cart abandonment rate is also 15%. The realization of Paypal as a payment method will greatly reduce the abandonment rate of our shopping carts and bring about 10%- 15% revenue growth. " Very clear, isn't it? How to calculate the potential revenue growth of this function?
Create a comparable standard to measure the current income gap.
Quantify potential revenue growth (percentage or USD)
Compare the increase in revenue (more than one year) with the cost of creating this feature.
All functions related to increasing income are sorted by decreasing income.
"The old platform needs 10 seconds for each transaction, while the new platform needs 7 seconds for each transaction. Moving the function to the new platform will save 30% time for each transaction, and we will do more than 6.5438+0 million transactions every month. " Very clear, isn't it?
However, most situations in real life will be more complicated and chaotic. The following are the tips recommended in the book Why Companies Need to Better Optimize Functions to Save Costs:
If all tasks are of high priority, it means that there is no priority.
I have seen a joke of a Japanese programmer before: the product manager is the domestic slave of the customer, and the programmer is an animal, which is also borrowed from other people's homes. Use it hard.
It would be much happier if every project insisted on sequencing and iterative development according to the Moscow method!