Almost all software project products are the information set exported from the demand, and the demand has become the entrance for software R & D. People familiar with the IT industry have no objection to this kind of cognition.
Project requirements, as the name implies, meet the project needs and the goals and requirements of the project attached to the development of enterprise/organization management. The project team is an organization that strives to achieve the project's needs and objectives. During project construction, the project team will be concerned about the generalBusiness RequirementsThese business requirements include the basic work tasks of software systems such as functions, performance, structure, and interface to be built in the project. The vast majority of the team members will spend a lot of energy on such requirement acquisition, analysis, and demand implementation. For this reason, a detailed requirement tracking service clue is developed to facilitate future project acceptance and facilitate project success.
However, the project team should also pay attention to one requirement:Control Requirements. This type of requirement is the project requirement gradually required by Party A and the supervisor for project construction. For example, at the project meeting, Party A requires Party B to promptly explain the scope of the project, and the supervision party requires Party B to report on the concealed project several days in advance. This type of requirement is also a key factor affecting project success. In some project construction processes, the project contractor emphasizes the degree of implementation of the project's business needs and the scope of the project, and ignores the control requirements of Party A/supervisor, the progress of the project may be unsatisfactory for the contractor.
Another type of requirement is that it is a branch of business needs, a project requirement, or a project requirement, but it is a real requirement of enterprise business activities, this project does not fully cover such requirements. We call itPseudo-real requirement. For pseudo-real needs, demand analysts should break their contact across the board, because such requirements are not a concern of the project team. On the contrary, you care about them, they may also have many negative effects.
Summarize and compare the three types of differentiated requirements, as shown below:
|
Business Requirements |
Control Requirements |
Pseudo-real requirement |
Need to follow |
Urgent attention and key implementation |
Urgent concern |
No need to follow |
Processing priority |
High |
Highest |
None |
Who is responsible |
Demand Analyst |
Project Manager |
Demand Analyst |
Participate in project acceptance? |
Yes |
No |
Yes |
Impact on project success |
Very large |
Very large |
Large |
Business needs and control needs must be carefully obtained during the project construction process to be met one by one, while pseudo-real needs must be confirmed at the early stage of project construction. These three factors have a certain impact on the success of the project, and require the project team to keep an eye on the output and evolution of these requirements throughout the project lifecycle.
Three different requirements in project requirements