The design of the website does not end with accepting appearance. A clear division of stages helps to determine decisions, deadlines and responsibility also for the subsequent maintenance of the site.
Name the result of each stage
The list of “projects, programming, implementation” is too general to cooperate efficiently. At each stage, write down what you will receive for evaluation and what needs approval. For the structure it may be a map of subpages and a draft of navigation, for the project – views based on agreed content.
The company planning the website in Warsaw can implement the arrangements at meetings or remotely. More important than the form of the meeting are written decisions and one current version of materials available to all participants.
Separate range from ideas for later
New features appear during the work. Save them with the reason for the addition, but do not assume that each has to go to the first edition. Rate the impact on content, design, programming and checking the whole.
Example: an additional language version is not just a copy of several screens. It requires translated materials, switching support and updates responsibility. If it appears after acceptance of the scope, the plan needs to be agreed again.
Count the maintenance separately
One-time payment for the execution of the site does not mean no later expenses. Domain, hosting, licences, care and development can be settled differently. Comparing proposals, ask for a clear separation of these items.
Prepare three sets:
- the work needed to be started;
- cyclically renewed services;
- changes ordered according to the needs.
At each item, write down who orders it and where the renewal notifications are sent. This helps to avoid interruptions from the organization rather than from technology itself.
Close project by transferring responsibility
The reception should include access to the panel, the materials and a list of open cases. changes in scope and Hosting Selection.
