When the worm in the user's mind

When the worm in the user's mind

Thoughts on---Reading the Book of Revelation

Zhang Wan Leng Qiu Yi class 2014301500108

When he first read the revelation of Marty Cagan, he was deeply attracted by his profound description and deep analysis. This is a guide book dedicated to "How to build your favorite products". The author is also known as the most outstanding product Manager on ebay today. After studying the course of software engineering, I feel that the reading of this book has a more profound experience.

The author explained at the outset that a good product relies on a strong design. He doesn't think that creative products come from chance, and he feels that successful products follow certain rules. For example, defining a product requires the co-operation of a product manager, an interaction designer, and a software architect. Developers are not good at user experience design, because the developers are thinking of the implementation model, and the user is looking at the product concept model. Functionality (product requirements) and user experience design are inseparable, and so on. The corresponding ideas he put forward have been widely used in the design and development of modern software engineering.

I read this book is very relaxed, because in the original software engineering knowledge point of Use, the language used in this book is very humorous. It is very enjoyable to read. So I keep doing some reading notes while I'm reading.

First chapter of this book is the key role and its responsibilities. The concept of team role is emphasized throughout the book, and the team's configuration is the guarantee of the whole project quality. The book says that every 5-10 card-law staff is equipped with a product manager, and that the interaction designer can support the work of two product managers and that visual designers can support the work of four-bit interaction designers.

The second chapter is about product management and product marketing. First of all, these two are not the same concept, and many companies often appear to let marketers to define products, this is a misunderstanding. Because it ignores the mobile phone detailed product requirements of the steps, but also avoid the exploration of the difficult decision-making process of the product. And they often create things that are not available and are not viable. And the author proposed the corresponding solution. is to clearly define the responsibilities of the Product manager and the product marketing staff. and product managers and product marketers should communicate frequently to collaborate.

The third chapter is about product management and project management. Because many companies also exist in product management and project management overlap with each other phenomenon. The authors argue that it is important for Internet companies to separate these two responsibilities from each other, and that the project must be continuously promoted or the product release will be postponed. For the retail software, the two responsibilities are separated from the nature of the rain products. The responsibility of product management is to define valuable, usable, and workable works. Project management is concerned with how the plan is executed to deliver the product on schedule.

The fourth chapter is about product management and product design. This chapter focuses on the need to understand user experience design. Good products must provide a comfortable user, comfortable user experience is the product management and user experience together effect.

the fifth chapter talks about product management and software development . It explains that the product manager defines the product plan, and the development team knows which product ideas are feasible. They are responsible for product development and practice . The development team and the product Manager can work well together on the premise that each other recognizes each other's equality, that is, no one belongs to WHO. A developer is a group of people who know best how a product works .

The above is a summary of the first five chapters I have compiled. The first five chapters basically describe the relationship between product management and modules, and make it very clear that many companies are not only in the product direction for many times because they confuse a lot of similar concepts, the treatment of the relevant concepts is not in place to cause a lot of time the division within the company is very confusing. There is no option to place the verification in the right position, which results in a very low degree of fit between the product and the user,

Finish the product direction. I would like to talk about some of the most touching parts of this book, because in the beginning of software engineering we introduced the concept of waterfall model, and this book also describes in detail the "reasonable use of waterfall development method" in a chapter.

First the author pops up the main drawback of the waterfall development approach: Product validation is seriously lagging, the notconsistent plan is expensive, and the product cannot adapt to rapid market changes. Understanding the drawbacks of the waterfall approach in practice makes it easy to understand why you should use agile methods such as scrum and extreme programming. Waterfall-style development method is too idealistic, that people can meet all the problems, to grasp the needs of the whole. The practice proves that waterfall development is difficult to implement unless it is a very small project. If product software is developed using a traditional waterfall development approach, the delivery time of the product is usually later than expected. and users often find defects in the product, the development team also need to spend a lot of time and money to repair, perfect. If you have to use a waterfall development approach, the product manager should try to circumvent the above questions, and the first task is to explore the product phase. Prototype the product, and ask the target user to try it. Ensure product design is value, usable, and feasible. Only in this way can we improve the chances of success. It also saves the time and cost of the development team.

After reading the complete book, although some areas are not particularly understanding, it may be because of software engineering such a discipline is not too deep understanding. But such a book plus Li Xiaohong teacher for the software engineering class above the explanation let me deeply realize that software engineering is a very rigorous discipline, if only the code and not pay attention to the norms of the programmer can not assume a project development of the task. So after reading this book of Revelation, my understanding of software engineering has become more profound.

When the worm in the user's mind