"Turn" to the understanding of software PRODUCT

The timing of the product is to see the needs of the business, whether it is the implementation of the future, or the project into a product, these are not technical personnel can be considered, business development and planning, how to market refinement and so on if all by technical personnel to consider, the risk of product is very large. The greatest risk is the understanding of the product.

referring to "product", most of the technical staff, including a lot of company bosses, the first thought is the sales, that is, to avoid implementation, "SOFTWARE PRODUCT manufacturing cost is zero, Microsoft is so rich", this is a lot of people say to me, why do products.
based on this consideration, the technical staff tend to focus on the architecture design, focus on the configuration, zero implementation and other links, small software may be able to do, and for most small and medium-sized software companies, mainly to do is enterprise management software, the use of this idea will be a disaster, Enterprise management software is driven by the business, even if the mature software implementation cycle abroad is not much less than the custom development, based on the technical framework rather than the business to do product development, has not made the first set of thinking about the 0 cost of replication, there is no business application, think of the software provides organizations to support complex matrix, or even virtual organization , two-based product development is considered a crime, and from a lean perspective it is an over-design, a waste. If based on this idea to do products, it can be said that the risk of product failure is very large, technically for the general small and medium-sized companies, is not guaranteed.     
General products, middleware and system software of the product, I do not have this experience, cannot comment.

Enterprise management software, cut into an industry and field, can be product-based, but the product to a large extent, I think is a business term, is a combination of management ideas, implementation methods and other personalized elements of things, can not be easily copied and implemented, do not have a large-scale sales potential. Companies want to do well, rely on consultants, they want is best practise, technology in this field on the customer's impact is negligible, the project success depends on implementation, I see the implementation of foreign products with two times the development is no different.

if it is not a generic product or system software, do enterprise management software to zero cost implementation is not likely, the functionality provided by the product can never meet the customer's business requirements. And by selling software products to earn money, far less than by implementing consultants to earn the implementation fee to earn more money, the latter will give enterprise customers to bring management improvement.

How does a software company make a product? My opinion is:
1, find the right project and the right customers, do more projects;
2, in a certain field to accumulate industry experience, the establishment of model projects and successful cases, and the project product (refers to the concept of business products);
3, refining the management concept, and the concept and success stories combined, the implementation methodology;
4, find the next project, in the project development process of the original system reconstruction.

in the beginning, do not think about making a lot of money, first honestly do the project, but more work from the business, more important to the company is abstract and refining management ideas and business rules, the implementation method and project management experience, do a few successful cases, the product has a good foundation.

"Turn" to the understanding of software PRODUCT