How to eliminate innovative web-site development of all diseases

One, requirements management--eliminating the source of all ills in software development
Summing up the products we've done before, in particular, unsuccessful products are always able to find some of these reasons, and in these reasons we are not difficult to find for the lack of reasonable management needs caused by a few problems, so there will be similar to "People do not know exactly what to do, but has been busy constantly developing" situation, to the end will appear "developed products are not users need products" Cup!
Demand is the root of the product, and the need for work has the greatest impact on the product. The source of product development, if the beginning of the wrong direction, the next work will be wrong to add the wrong, away from the "good products" more and more away, so we first grasp the source, orderly development of the product research process.
How can we manage our needs reasonably and orderly? We must establish a complete set of requirements management mechanism to manage the whole life process of demand from generation to extinction (demand), rationally and effectively allocate the company's limited manpower and material resources, and do the most cost-effective things.

Second, requirements practice--a solution to the problem
Requirements management practices include four processes: Demand collection, demand analysis, demand screening, demand processing.
2.1 Demand Collection
collects different users ' needs in a variety of forms, usually in the form of user interviews, questionnaires, test results, data analysis, etc. users: End users, marketers, editors, testers, leaders, etc. At this stage, the attributes of the requirements are recorded in detail, and the traceable feedback personnel are recorded, and the requirements of different users on the product are extensively recorded.
2.2 Requirements Analysis
Analyze requirements in the requirements analysis phase to determine their basic attributes and what business value they will bring to the product. Increase in user volume? In order to achieve this request to pay the staff, time and other costs, and finally calculate the demand for cost-effective, in the process of the main needs of the overall evaluation, clear the purpose and create value.
for some bugs or functional small changes such as the requirements, do not do a detailed analysis, generally determine the changes, directly into the demand processing.
2.3 Requirement Filtering
This phase of the work is combined with the status quo to deal with requirements, mainly to solve-do not do? How much? When do you do it? The form of a
needs review is mainly in the morning of the team, invite leaders to participate, the team members have page designers, front-end engineers, programmers, testers and other roles;
through a review, packaging multiple requirements, sorting out a version (or subproject) required for the demand point;
Document the packaged demand points, submit them for review by the leader, and confirm them into the development cycle;
2.4 Requirements Process
to develop the demand point for a defined version (or subproject), here mainly involves the development process, the detailed reference related development specification.

Chart 1 Requirements Management flowchart

Iii. collection of needs-participation by all
Demand collection for the entire requirements management process is the most important, decide what to do the data base, the demand collection is not the product design before the work, but a process through the always; it is not a matter of product personnel, but of all personnel;
Different people, different roles, can put forward their own expertise in the field of problems, different points of concern, in the demand acquisition stage, we are not afraid to find out what absurd needs, but to be afraid of missing reasonable needs ...

Source Address: http://ucd.lcduba.com/?p=85