Summary
Authors: Wu Bochen
As IT has played an increasingly important role in modern life, according to the project management, pre-sales research, system development for many years of experience in the latest project management knowledge, we will manage this area to discuss the needs of IT projects. Management, especially how to establish a sound demand manual, and use those related requirements management template files to achieve demand change control. This paper discusses the demand management (RM) of modern IT projects from a combination of technical tools, templates, and empirical methods.
Keywords and keyword definitions: Brainstorming method, Delphi law, feature weighting method; RM: demand management, CCB: Change Control Committee, QFD: Quality Function Function, HOQ: Quality House.
Agreement: The concept of keywords and the techniques used in this article do not make detailed explanations, please refer to the relevant books, only discussed these uses in demand management here; the case information inside is not here Detailed explanation.
Quoted case: a city online approval project.
1 Overview
We know that the six elements of modern project management are: time, cost, quality, organization, scope, customer satisfaction, in fact, to meet these six elements, plan a good demand analysis is the premise of achieving these six factors, if we There is a problem in some phases of the project life cycle, and we may not know, this will affect the entire project cycle, regardless of how the plan is detailed, if the demand is wrong and the demand analysis is not in place, the project's control will not have any value, Forty-tenth percent of the IT software project is the "LeffingWell 1997) buried in the demand analysis stage, from a sense, the success of the project is based on the demand management of the project. success.
2 definition and characteristics of requirements
According to the IEEE project engineering standard vocabulary (1997), the description of the demand is as follows: The owner solves the problem or power required to achieve the purpose, and the system or system components must meet the contract, standard, standard, or other formal premises required. Conditions or power. In PMBOK, the project demand is agreed in the project.
The most significant feature of demand is "changing the project, as the project is gradually clear", project management is characterized by progress in progress, it can be seen that demand management and project management, this means demand The entire life cycle of the project may exist, so the process of project management is also indispensable.
The status of demand in project management and project implementation is important, the following structure reflects this relationship with a clear reflection:
As you can see from the above figure, demand analysis is very critical during the project, and each process is directly or indirectly associated with the demand.
3 How to get a demand
There are a variety of ways to get demand, telephone inquiry, on-site inspection, listen to users explain, read the relevant documents prepared by the user (such as bidding), in fact, these methods are Get method, we can achieve the following two types of technical means to achieve : Get (access) and PUSH (boot, feedback, excitation) are combined with each other to get our true demand, and these two processes must interact, usually we can filter a very experienced (including negotiating skills) The people who have a deep business and technical background, the people who are very good, diligent efforts, have served as demand engineers, and their work is working there, and his work is mainly defining the scope of the project and needs change management, through the various types of template documents we have compiled. Implementation of demand changes;
Generally speaking, IT integration needs include three different levels - business needs, user needs and functional requirements - including non-functional requirements: business needs provide the initial interests of new systems for customers and product developers, reflecting organizations or customers For systematic, high-level target requirements, they explain in project views and range documents; user demand documents describe the tasks that users must complete using the product, which is explained in the use of instance documents or scenarios; Define the software features that developers must implement, so that users can complete their tasks, which meet business needs, must have a certain business background and technical background, can discover customers from three different levels. According to our experience in the online approval project in a city, we adopt the following method, with each work record document filing: If you have reviewed a large amount of information and medical record formats, all kinds of emergency defense measures, statistical analysis report, system planning, The old system business status, historical data, also interviews the application experience of operator, many technical exchanges, special discussions and other forms of interactive discussions and analysis. This is a relatively thorough expectation of business, functionality, and users.
4 demand management
The job that needs to be done by the demand is to analyze, digestive and review, baseline development, demand instructions, which we are mainly focused on demand analysis and demand instructions.
4.1 Analysis
1) Establish a demand correlation map: Demand-related map is a simple model for defining the boundaries and interfaces between the system and the external entity of the system, and it also clarifies the information flow and material flow through the interface, through the related map, for user needs The agreed and confirmation and the CCB review are very critical.
2) Creating a development prototype: Creating a user interface prototype can be applied as follows: If developers or users cannot determine demand, develop a user interface prototype, which makes many concepts and possible things more intractive. The user will make the project participant to better understand the problems to be solved by evaluating prototypes. By developing protests, owners and integrators can understand business, explore potential information, and avoid unnecessary changes to user needs.
3) Analysis Feasibility: Analysis of the feasibility of demand in the permissible cost, performance requirements, analyze the feasibility of each demand implementation, clear the risk of interlinking each demand, including conflicts with other needs, external factors Dependent and technical obstacles, this is mainly used for internal review and development of technology lines. If it adopts .NET technology in what circumstances, we use J2EE technology, we fully have a full demand in 2003 e-government online approval system (business , Technology, user operator demand, existing system requirements, etc.) Do overall extraction analysis to determine the selection of technology lines.
4) Determine the demand priority: Determine the priority application analysis method of the demand to determine the priority of the use of instances, product features, or single requirements. Determine which features or which type of product will be included based on priority. When the requirements are allowed, each change is added in a particular version and the required changes are made in that version plan.
5) Establish models for demand: The graphical analysis model for building model needs is an excellent supplementary instructions for software demand specifications. They provide different information and relationships to help find incorrect, inconsistent, missing and redundant needs. Such models include data flow diagrams, entity relationship diagrams, state transform diagrams, dialog boxes, object classes, and interactions.
6) Write a data dictionary: It is difficult to make the team's ideas, and establish a suitable mechanism is exactly necessary. This is the data dictionary, the data dictionary is the definition of all data items and structures used to system. Ensure that developers use unified data definitions. In the demand phase, the data dictionary should at least define the customer data item to ensure that the customer and the development team are consistent definitions and terms. Analysis and design tools typically include data dictionary components.
4.2 Relationship model for establishing demand and product quality
Demand is a premise that the project is implemented correctly. If you don't grasp the user's needs, it is probably a vulnerability, and the final product will not be a real deliverable. We know that quality is a major factor in customer satisfaction. Quality has many influencing factors in the project. Here we focus on discussing demand and quality from the perspective of demand, so how to set up from demand. Quality control? Let's establish a idea as follows: All the customer's expectation needs to generate a conversion matrix product to deliver the deliverable customer satisfaction. The conversion matrix here is very critical, how to achieve the relationship between demand and quality, can be implemented by quality function assignment (QFD), can associate requirements (user expectations), product characteristics through QFD, here to use one Tools: House of Quality, I now use a case to explain this tool. In a city online approval project, we collect and organize many needs from customers: approval projects, report requirements, certification methods, work Stream requirements, data range and format, operation interface, medical management specification, etc. We have completed demand and how to implement the needs, as shown in the following figure:
In the QFD technology, the related influence relationship between engineering features is determined in the QFD technology, ie positive correlation (change in the same direction), does not correlate, and negatively correlated (reverse direction). The degree of correlation can be further subdivided into strong correlation, general related and weak related relationships, and express the correlation to the scale value, so that we can define a strong degree of strength: if it is uncertain, general Determine demand, strongly determine demand, etc., in this HOQ, other technical tools, such as feature weighting law, etc., the benefits of doing this are the main time, can make demand analysis and management to promote customers with time The change varies in a fixed frame, which is in line with the following curve, not to the extreme.
4.3 Demand Manual Writing Experience
The current demand manual has a fixed format and requirement, which can be obtained from the relevant books that specialize in demand instructions. In this paper, I focus on the experience of the demand manual, write excellent, there is no formula, which requires a lot of experience. To learn from your question found in the past document.
1) Adoption of IT project requirements Specification template Factors, we should take the requirements specifications and strolls to list many points: agreement, laws, regulations, demand classification, technical restrictions, technology and tools, etc., communicate with project officers, especially users, and then discuss, It can be discussed by the Brainstorming Method and Delphi method to determine the outline of the specification, but cannot follow this book.
2) The management of the additional document is worth noting that the demand manual is not a constant, we can track the new needs and demand changes by additional documents, which must establish a set of document collections, track the needs, to ensure development group steps Enter, generally these documents are considered: "Demand (or function) Change Application", "Demand (or Function) Change Specifications," Demand List One List ", etc. The benefits of doing this are to monitor the demand, guarantee the arrangement of the project, and let users know that the change is a very serious thing, preventing someone from being filed (because many problems in the real IT project) The legacy and exceed the problem of this project technology line to make up for problems, etc.).
3) When writing a demand manual, there may be some need to solve the needs. We must also use specialties to listen out, prevent leaks, but also to take that measures when we do implementing the implementation plan. Purchase other equipment, put relevant human or other means. 4) Demand must be confirmed, many projects, may developers who have not been confirmed by customers in order to protect their "interests", in fact, in the demand phase, our needs are to confirm with customers, such as data dictionary, interface Selection, technology line, function module, etc., the advantage of doing this is to prevent the need to grasp the ability, lack the necessary functions, and the other is to prevent developers from demand for gold, provide unnecessary functions.
5 summary
After discussing the role of demand management in the entire project life, combined with its own experience, and a case "a city online approval system" analyzes the demand management approach and the tools used, according to their own experience Propose a place to pay attention to the description instructions.
