How business needs are managed during it implementation

At present, most of the enterprise IT construction and management lag behind the business change, not to mention the leading enterprise development. For these enterprises, it to the enterprise business support or promotion, is the business needs to a certain extent to determine. Overall, enterprise IT development will depend on business needs, not it investments.

The general practice of the enterprise is to compare the typical turnkey project, the business unit needs, the IT department to plan and organize the implementation of the project, the business unit final acceptance evaluation and use, IT department responsible for system maintenance and update. This is often the result of the system is not good, not applicable, or can not keep up with the development of the business, the business unit is unwilling to use, eventually become equipment, waste investment, and the only benefit may be to the enterprise related personnel on a vivid reality of the user training class, spend money to buy lessons.

Generally, before and after the IT project on-line, will do the demand research, and require business parties to sign the need to confirm. And in the subsequent project promotion process, generally will freeze the business demand does not make the change response. This will cause the system after the line with the business needs to match the deviation, the degree of demand is directly related to the project effect, business user requirements change, which increases the system officially on-line time, affecting the project acceptance, it will be criticized. If the project is more complex, the IT department is afraid of error, the pre-demand investigation time is relatively long, the application launch cycle corresponding increase, the business unit waits too long, the satisfaction will be reduced.

Therefore, in order to promote the enterprise IT construction, adapt to the business management needs, must let the business Department deeply participates in it construction, fully activates the business Personnel's initiative. If the enterprise has not previously adopted this model, can choose one or two business units, pilot some labor-saving, improve efficiency of the system, the business unit quickly feel the benefits of technology, will lead to other departments gradually formed the habit of proposing various needs.

In the process of building and perfecting IT system, enterprises need to actively manage the needs of business users, and optimize and perfect the system according to the situation. Therefore, IT department has the IT project construction management, the system maintenance function, needs in the system entire life cycle to the business demand to manage effectively, becomes particularly important.

One is to try to gradually establish a demand-based management model, which can be used to quantify demand management, it realization, business expectation, etc., and consider whether the project satisfies the business expectation. Take demand management as an example, in the beginning of the establishment of IT systems, users can synchronize the use of log, so that the management, the business layer of every user can always understand the use of the overall enterprise system, which systems use more frequency, which functions with more, which features less. Through such constant accumulation, the formation of a new concept within the Enterprise: a system used well, first of all from the business sector needs to be raised well, the business unit should be responsible for these needs. If the business unit puts forward a requirement, but does not actually use these functions, the original requirements are not well presented.

As more and more requirements come from the business, Kanban management can be further introduced to classify requirements. Requirements are divided into functional requirements, interface requirements, use requirements, and so on, the main, important requirements will be written on the Kanban board, so that everyone can see which requirements are queued, which needs are being addressed, which needs have been resolved, as far as possible to be open, transparent, to be able to obtain the relevant departments and personnel understanding, support and cooperation.

The other is that the IT department should help the business to make better demands. Through the establishment of a good communication model, IT departments and business units work together to study business changes, changes in requirements, and further explore the rationality of demand. The IT department, after receiving a demand, does not immediately put into the work needed to implement it, but first initializes the requirements, explores the motivations behind the demand, understands the real idea of the business unit, the idea of the manager, the idea of the technician, and the parties reach agreement. The planning and execution phase begins when the content of the requirements is determined to be reasonable.

For IT department and party B, usually the most headache is not the project-based needs, but from the user's usual fragmented needs, or simply don't tell the demand, there is only a general demand framework. First of all, scattered demand often comes from the improvement of one of the existing functions, or the temporary need to deal with some of the data. In the face of these scattered needs, the general Enterprise's IT department will take the delaying tactics, as far as possible not to respond, in fact, the better way is to embrace demand, embrace change. A good system is designed, and a good system is used. A system in the user's use, inevitably because of the user's habits and business changes, to generate a variety of needs, and IT departments through small repair minor changes, can gradually let the system become friendly and easy to use. Conversely, if a system does not make any changes, the user is gradually unwilling to use, the system will be wasted.

As for the latter, in the case of unclear business requirements, the implementation needs can be suspended and the business unit should continue to study and improve. Of course, if you have the ability, you can first build some prototype system, to guide the business unit thinking, and constantly participate in the system trial, further clear and perfect demand.

Third, we should strengthen the IT department's own team building. In the construction of the project, it is best for the IT team to be relatively fixed and to be transformed as the business grows. Enterprise IT department in the project management, in the party B after the entry, not only "contractor" supervision of party B's work progress, but also to understand the business's IT requirements and implementation plan, to carry out demand matching analysis. Once the system is online, the IT team still does not know the internal design details. Based on this, it teams need to have higher technical skills, including control requirements, design of the main technical path, in the long run, it is more conducive to the ability and value of IT team shaping.

According to personal experience, IT system construction is a constant compromise, IT departments, business units and contractors tripartite compromise. The more complex the system, the more so, enterprises to grasp the large and small, to achieve the main functional requirements, the use of demand and interface requirements, some outstanding demand as long as not affect the overall situation can also be left to follow up the upgrade to achieve. From this point of view, IT system project construction and new house decoration in fact, the owner of the ability to consider a comprehensive, leaving the regret will be less, or irrelevant, overall is a relatively successful.

This article is from the "sky High bird fly, sea wide with diving" blog, please be sure to keep this source http://xjlegend.blog.51cto.com/59163/1600642

How business needs are managed during it implementation