(This article also published in my public number "dotnet daily Essence article", Welcome to the right QR code to pay attention to. )
Preface: Today's content is a brief summary of me, hoping to get a beginner product manager without any experience with a general understanding of product design and demand analysis. Of course, because it is my own experience, so not necessarily the right and most effective.
How to design a product, and analysis of its needs, in fact, there are many books for us to learn and reference. From the Academy's "software Requirements" to the entrepreneurial "revelation: Build user-Favorite Products", as well as the chicken soup pie "Everyone is Product Manager", it is worth reading. It is true that by reading classic books, we can gradually get started with requirements analysis and product design, for example, I was 16 years ago when preparing for MCSD, through a book "Analyzing Requirements and defining solution Architecture (English version) of the entry requirements analysis. But here I want to summarize a simple step and some of the tools used to make it easier for friends who have never done this work to get to know and start getting started.
The specific contents are as follows:
- Say the vision of the product in a sentence. What is the value (value) of the product that I will provide for whom (WHO). Vision is the most important thing in product design and demand analysis, which determines the success or failure of a product. This step also to the user profile analysis, also known as role analysis. Forms and tools are not fixed, and generally use handy documentation tools to write text.
- Determine the scope of the product (scope) according to the vision. That is, to answer the product to do what do not do, generally speaking is a list of product characteristics. The scope may vary at different stages of development of the product. But be aware that everything is done or applies to all people's products, or does not exist, even if the existence is worthless. More. Similarly, you can use Word to write a text or attach a small number of illustrations to a document.
- Envision usage scenarios and business processes from the consumer's perspective, based on the characteristics identified by the scope. The scenario describes how the user will use each specific feature, and the business process is the process used. Scenario descriptions can be described in words, while business processes draw flowcharts with tools such as Visio.
- According to business process, get UML use case. Use cases are situations in which the system and external user interaction. For beginners, UML use cases are unfamiliar and difficult to accomplish in this area. So starting from here, you might need to develop engineer assistance to do it. The purpose of writing a use case is to interpret the business process as purely from the user's perspective into a computer-based activity. As long as the drawing tool can draw a use case diagram, of course, more professional software will be more handy, Visio can also be completed. Additionally, this step can be omitted if it is more difficult.
- Create a user story based on attributes and use cases. A user story is a fixed-format discourse, "What users, what are you going to do, to get what benefits", to describe the demand point in detail. A user story is simply a refinement of the feature. You can create epic user stories and then subdivide them to easily assess the granularity of your work. The best reference for user Story theory is "user stories and agile methods."
- Write a UI prototype. When it comes to scenario description and business process design, you can start drawing UI prototypes with some prototype tools, such as Mockups or PowerPoint. In particular, prototypes can be used to supplement the content of a user story that cannot be expressed in words.
Since this is an introductory introduction, many of the above steps are not in-depth and do not take into account the analytical steps of non-functional requirements. At the same time, the emphasis of this paper is to explain the requirement analysis process, so some steps related to design and development are omitted.
Finally, again, this is not a best practice, just a little introductory summary of the beginner's share.
Getting Started product manager how to analyze and design a product
