Specifications in the Internet-project management

 The contractor receives the relevant terms of reference of his clients usually before a planned project. Roughly outlined in this is how the project will take place and what targets in what time frame are defined. In many cases, the terms of reference as a requirements specification is known and it is made mostly in software development or in the media design, clear to each project and goal-oriented to be able to represent both sides. If a tender for several contractors to open the possibility of a bid, it is useful to make clear demands on the job-discharge with a well structured specifications already in the invitation to tender. The advantage is probably obvious to both sides. The customer has the possibility to select the contractor who not only most favourably, but above all very goal-oriented will carry out the project. It can recognize whether the concerned contractor has understood the targets as he sees it, and will implement as well. The contractor thus already has quite clear guidelines and targets to be achieved before a tender and must submit therefore his tender not in into the blue. 

 Stay flexible – changes see as progress

Although the terms of reference should of course available at best before the start of the project for the contractor, it can be yet still small and large changes have to be incorporated in the course of a project. Circumstances, it can also happen that the whole objective must still be changed, because knowledge that only germinate on during the implementation of the project, should be seen not purely negative. Rather, it is away to improve something and perhaps to create something never before. The original terms of reference should be created naturally completely by the customer, but the contractor should it also point out, that a project without changes and improvements on the way to the goal comes from in the rarest cases. Both sides should put on flexibility and not as something negative review. Otherwise the entire project management involves itself from the outset in policy discussions without any sense. Therefore the contractor must first check whether and to what extent the project at all in the form that the customer specifies translate. The contractor should write not simply large structural changes in the specifications, without having previously spoken with the client. As usual in practice a good communication is the key point for a successful project also

Not always easy, the way of the specifications to the requirements specification

While initially in a terms of reference the requirements of the customer even more generally are outlined and little details are included, more information in addition to the basic and essential requirements must be worked out in the specifications, the contractor created. You should be as specific and precisely formulated and go exactly to the wishes of that formulated by the customer in his terms of reference. The contractor should his creativity in the solutions as far as possible receive and own competence to introduce very goal-oriented. In practice, often also unclear terms are used for the specifications, such as target concept or feature specification, but also overall system specification or functional specification are quite common. Here, the terminology between specifications and specification comes unfortunately also often confused because both terms are used for both standard forms. The requirements specification is a formulation of the implementation of requirements of the customer according to the DIN 69901-5. According to the VDI guideline 2519 sheet 1 the specifications the implementation of customer requirements to describe how it originally has requested it in its terms of reference by the contractor

Check, advice and some - the final version

The customer should match all points with the original basic concept after the reception of the requirements specification and review. The ideas and wishes of the customer can be no longer acceptable in the course of the creation of the specifications have been changed or distorted, and so for the customer. These different points must be claimed immediately by receipt of requirements specification. Has the contractor started, the new approach to work, precious time is lost may him and for the customer delayed the implementation of the project at its worst for a long time. Project management should eliminate therefore necessarily together all emerging issues before the start of the processing of the requirements specification, because the communication of the two parties by means of the requirements specification is based on no legal basis. Would the contractor so complete a successful project and also be paid should he as possible good communications with his client look and this document also always in writing. The contractor should generally begin with the actual work if the customer has removed the specification. The contractor's obligation to cooperate envisages a confirmation of required of him, if he is compliant with the details and objectives of the requirements specification. Otherwise, it may stimulate but also changes or ask if the requirements in the specifications seem insufficient to him.

Not always easy, the way of the specifications to the requirements specification

The more precise the customer already formulated the tasks of the contractor and the objectives of the project in its terms of reference, the more successful the entire task behind is realized. But also in the specifications, the contractor must provide a concise and clear language in the descriptions. Here, tables and possibly sketches as well as diagrams that show are absolutely essential. Not the way the contractor wants to go, but only a detailed description of the required destination is important for the task. Just for projects that are located in the area of the Internet, must be paid also on the precise objectives and their formulation. Misunderstandings and confusion should be avoided in detailed discussions and all these meetings shall be recorded. And just in case the logs must be signed by important policy discussions always from both sides.

Not always easy, the way of the specifications to the requirements specification

Both sides can benefit from a further way of minimizing misunderstandings, by taking an external service provider for the creation of a requirements specification throughout. Just for large projects alone the linguistic peculiarities of the two parties vary widely, which makes difficult the formulation of the details for the contractor. Usually he is such in his terminology, that he clearly can bring over these details and aspects not for the uninitiated, a customer must often be considered as. So, a professional who is familiar with the particular pitfalls in this field, then creates a structured technical specifications with which the contractor as well as the customer can work well. Should, for example, a specification for a Web portal to create newly be customized, a certain structure of points to be drawn in a certain order must be respected. The service providers know very well out to stand the two parties so to speak as an interpreter available. Before so the danger arises that a project could fail due to a different level of knowledge and technical barriers, the two sides should be necessarily a such help for themselves.