How much revelation did revelation give me? --------Book of Revelation

How much revelation did revelation give me?

In the search for the recommended software engineering related books, the introduction of the eye is Marty Cagan wrote "Revelation." I found the pdfof the book online andspent nearly five evenings reading the book. The contents of this book are many and broad, and each chapter is very concise. This book also makes me really realize that in a large software project, the software engineering course teaches a lot of knowledge in the end to play a role.

A good software product can be said to undergo 9,981 difficult, and the first difficult, is the product demand extraction, analysis and induction so that the product can be initially defined. I used to think that the most common use of market research was to distribute questionnaires, or to publish and disseminate relevant questionnaires online, and in fact, I intend to do so for my upcoming software development. However, Marty mentioned that the product manager needs to communicate with the users in a full face to fully tap the potential needs of the users and capture the product's creativity.

At the same time, in how to correctly treat customer demand,Marty stressed that the market should be investigated for product demand as an important reference rather than a street lamp, a good product needs to meet the needs of the product at the same time should have their own innovation and product creativity, while should remain surplus force, Leave a space to continue to develop, in order to continuously update the next stage of the product and improve the product. Rather than, determined to do a flawless product.

In the process of making a software, people will always pursue perfection and perfection constantly. As I participate in the software development of the game, our fixed topic is always changing, even the need to complete the function is not specifically identified, so we are in a very confused period, in the end what should be done?

The Book of Revelation mentions that two phases should be strictly defined, one defining the product, one executing the product, and the definition of the product should shift the focus of the work, rather than changing it with the new ideas every day, and the second stage is to focus on making the product after the first phase, Instead of following the everyday thoughts.

A software product architecture tends to use interface design as a template, and interface design is like a product's face, which determines whether or not the user will be using it at first sight. However, we tend to hold the old concept is: product demand analysis-definition of product-product background Development-interface design, interface design This is often the entire product function has been trained to start work. However, the Book of Revelation suggests that, in the analysis of product needs and in the face of customer needs, interface designers should also face customers, participate in the entire product requirements analysis and define the process of the product. This is the idea that I have never had before, because I made the mistake of "thinking that I know the user's desired product interface". Let the interface designer face the customer, participate in the entire product demand analysis and define the product process, more able to produce a "user favorite" interface rather than "good-looking" interface.

To tell you the truth, I always thought that the product documentation was "useless" throughout the software development process. Because everyone in the meeting will understand what needs to be done, what needs to be done, people are not very willing to go through a lengthy product specification. and for management and product teams, product documentation can easily be a cover-up, as if everything went well. As a result, many teams now like to solve this problem in an agile way.

However, there is still a need for the product documentation, as this document is not just about the development team and the product manager, but more about the testers, the trial customers and the operators, a vague concept that can easily be overlooked in a few small details that may later be caused by environmental instability The user is not ideal for use.

Marty that the best product documentation should be a prototype of a high-fidelity product, because it's a very intuitive way to tell everyone how this product is used, what it does, and how it works. But I think that if it's a small startup development team, they don't have much time and energy to quickly make a high-fidelity prototype to do the product documentation, so it's a good idea for these development teams to adopt an agile approach to solving the problem with the product documentation.

When it comes to agile, at the very beginning, I think the agile approach makes the job easier, and even the omission of product planning, which allows product developers to no longer adhere to the traditional development process. However, the idea is clearly wrong, and the use of agile methods still needs to define the direction and purpose of the product, setting the standard for measuring the success of the product. Just using agility can shorten the planning time and use iterative iterations to deepen communication between product developers and users. At the same time,Marty that if the agile method used in custom software is applied to the software team of product development, it is doomed to encounter many problems. Because the product architecture of the development product is not able to redesign the architecture easily, it is feasible for custom software products. Therefore, if the software development team wants to adopt an agile approach, it should clearly identify the differences between the product and the custom product, and understand the book requirements for developing the product.

We mentioned the waterfall model in class, but also said that the model's shortcomings, and its improved version-V- waterfall model. It also says many models, such as fountain models, spiral models, and so on. However, I think many of the pioneering and innovative teams should now be using waterfall models. How to use waterfall development method rationally? Marty has his own opinion.

The waterfall model is done in stages, because its process is predictable and is still loved by management. Using a waterfall model, however, can lead to a serious lag in product validation, a costly change plan, and a fast-changing market requirement. Therefore, Marty that the primary task is to produce prototypes for the target customers in defining the product phase. However, I think that the small entrepreneurial innovation team is not able to meet this rapid prototyping requirements, so the fountain model seems to be more suitable for such teams to use.

In our previous meetings on software development, there was little visible progress, and some people were in the "Peep screen" and "drop-off" status, and in many cases there was a disagreement and there was no point in talking about it at all. In this case, I often have a headache, I feel that the development project is very difficult to make a good product within two months. Later, after reading the Book of Revelation, I found the most basic things that I did not do from the beginning. There is no definition of this product needs to complete the function of the "priority" for this product which aspect of the most important, each has their own views, we are not at all a rhythm, at the same time we are also muddle forward, there is no very clear progress bar, we should do what after what to do. Feel if there is a software PRODUCT function priority, we can crack each other, but also can continue to go forward, like the customs to play small strange, although the same does not know the limit in where, but the direction of walking more clear, we have a consistency, the meeting efficiency will be much higher, because everyone knows " What we should do now and for some time in the future. "

After reading the Book of Revelation, the most important feeling is that "the original software engineering is the correct way to open it," rather than what it was assumed before. I also have a new definition of software engineering This course and its content, not a bunch of beautiful "pretence" and make the software product of the grid looks a lot higher "label", but really play a very important role, but also have an indispensable role, but these things are often overlooked or not considered particularly important.

How much revelation did revelation give me? --------Book of Revelation