Shulou(Shulou.com)06/03 Report--

Today, the editor shares a detailed explanation of Agile Project Management-MVP. Maybe you are no stranger to Agile Project Management, or have never understood Agile Project Management. But don't worry, today the editor will explain the principles of agile project management with the simplest description.

MVP: minimizing feasible products is one of the core ideas of lean product development.

The book user Story practice mentions "user stories and IEEE830". The former focuses on the goals of the new product from the user's point of view, rather than the attribute list of the new product, and we can design a better solution to meet the user's needs; the latter needs to write a detailed and rigorous requirements statement that focuses on the requirements list rather than the user's goals.

In the chapter of lean product development, we learned that the core idea of lean is "aimed at eliminating waste and adding value". MVP is not only an imperfect product, nor is it just a way to bring a product to market earlier. MVP is a process that requires us to go through this process over and over again: come up with bold hypotheses and find the easiest way to verify whether the hypotheses are valid. Then calibrate it with the experimental results.

When making a product, we will make a lot of assumptions. Assuming that you know what users' needs are, what kind of design they need, what kind of marketing strategy they need, what is the most useful framework, how to continue to make profits, etc., there are always some assumptions that are wrong. The problem is that we can't know what went wrong beforehand.

SO, whether it's making a product, writing code, or marketing planning, ask yourself two questions:

What is the boldest assumption?

What is the easiest way to verify whether the hypothesis is true?

For example:

Suppose you have a good product idea to develop a mobile phone for the elderly, which integrates voice, location, intelligent applications, secure encryption, intelligent photography, weather broadcasting, IP6 waterproofing, high battery life and other functions. As a result, component teams, financing, after half a year or 12 months to become a "national treasure" price, product development, tragedy also came, into the market you found that this group only needs to press the button, font, voice loud enough.

It is too costly to wait months or more to reach these key conclusions. At best, a long time is wasted; at worst, the company is dead. "doing useless work with high efficiency is the most useless thing."

MVP is to verify while learning, completely focus on the needs of users, bold assumptions, find out the easiest way, small steps to verify.

Conclusion: adopt the right strategy and constantly verify and improve the product through the feedback of the target user / market, so as to eliminate all kinds of waste in product research and development and increase the value of the product. The premise is that the product must meet the two basic elements of "the smallest product, available".

In fact, whether daily life or nature, have given us a lot of tips, the following picture, what will you feel?

This is the end of the detailed explanation on Agile Project Management-MVP. Of course, there are not only the above methods of analysis, but the editor can ensure that its accuracy is absolutely no problem. I hope that the above content can have a certain reference value for everyone, and can be put into practice. If you like this article, you might as well share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.