It Project Management User Requirements

User requirements for specific bidding projects are generally reflected in sow statement of work or bidding documents. From the perspective of user expectations, the user needs are the features that the product should possess in terms of functionality or functionality to solve users' actual problems.For IT projects, it is best to determine user requirements in the project startup phase. User requirements are an important input in the scope of software projects.,In the planning or implementation phase of the project, it is still determined that the user needs will inevitably be spread or the issue of gold plating.. Unclear and uncontrolled project scope is an important cause of frequent changes and delays in IT projects.

1. Relationship between user requirements and product requirements

User requirements are from the perspective of specific users, while product requirements are from the launch of generic products, which is the most important difference between the two. Without considering the product requirements or product versatility, the final product of the project can only meet the requirements of specific users. This is a list of transactions. First, the marketing scope of the product is narrow, at the same time, it is not conducive to launching generic products to form the core competitiveness of enterprises.

User requirements need to be converted to product requirements. The focus of the transformation is to consider the commonality of user requirements, and to consider how to make the product meet more user needs every time it has one feature. Collect User Requirements-> analyze and classify-> root of the requirement-> extract commonalities-> form product requirements. Product requirements formed in this way are conducive to the generalization of products in the future. In the process of software product development, we use various Architecture elements such as frameworks, public components, and layers to meet product scalability and configuration, rather than simply meeting current user needs, in this way, more work may be required in the software development process, but the cost is completely worthwhile.

2. Relationship between user requirements and software requirements

User requirements are analyzed, developed, and mined to form software requirements. The scope of the product has been determined based on user requirements and product requirements. Software Requirement development is a task in the project implementation stage, and its important input is the scope of the product. User requirements are from the user's perspective, while software requirements are mostly from the system implementation perspective. The user needs to answer what I want, and the software needs to answer the system's way to provide the user with what you need.

Demand mining and development are important to solve software requirements. What are the requirements raised by users? What are the problems they face? What are the solutions they propose from their own perspectives. Therefore, the software requirements cannot be developed based on what the user wants. Instead, the software needs to clarify the problems and root causes and determine whether there are better solutions to the problems the user may face from the perspective of the software system, this is also the importance of system analysis that software engineering emphasizes.

Generally, users are not clear about software systems or software development. Therefore, user requirements do not consider the ease of use, performance, and security of functions. In software requirement development, this is also an important non-functional requirement. If a function is not easy to use or is not easy to use, the user cannot be satisfied.

3. Collection and investigation of user requirements

　　Users' business scenarios, business processes, business rules, organizational structures, and job roles are important user requirements.. The purpose of the survey is to clarify the current situation and problems of the user's business, rather than simply asking what the user wants. The actual problems faced by the user must be explored through what the user wants. A farmer in cultivated land may tell you that he wants to farm his cattle 24 hours a day without eating or drinking. If he wants to develop products with this demand, it will inevitably fail. At this time, you need years of experience from consultants and field personnel, and advanced business management methods and models. With this, you will tell the farmer what he needs may be an automatic ploughing machine that is cheaper than a cow.

　　Collect User Requirements-> discover user problems-> explore root causes through analysis of business processes and rules-> propose better solutions. Only products developed in this way can truly solve user problems and improve efficiency. Only when software products create value for customers can they be realized.

4. unrealistic requirements

Users have a comparison mentality, and sometimes the demand is not what they really need.It may also be that we blindly introduce others' best practices when doing demand analysis.The best practice is omnipotent. These are extremely ineffective practices. In the process of developing user needs, we should develop solutions that can solve users' actual problems with minimal investment.

If you are selling laptops, what should you do if a user only tells me the most expensive laptop? Whether to develop the most expensive computer for immediate profit or not. If we lose more mainstream users for the profit of a few user groups, we will always lose the candle.