In the development process there comes a time when the agency such as something and doing, and the result is not visible. At this point, guiding the company’s employees, customers always get nervous. Since the process of programming and assembly sometimes takes three to four weeks, by the end of this period, they get nervous a lot.
Project manager working with the customer and knowing full well what is happening at the agency, which acted contractor, every day I watched as the marketing director was running across the ceiling, shouting: "They have be thrown!". This, gentlemen professionals, a small illustration of what a man feels responsible for the budget, after it you have given this same budget.
During a timeout associated with the programming, the project rests on the professionalism of project managers from both the web-studio and from the company. Calmly answering questions, they will be able to calm leadership. But if people are not competent, which, unfortunately, happens more often … But something I forgot her.
After two or three weeks after you approve the design, you’ll be sent a link to the site. To your site … It is not the address that you have planned, but it will (albeit incomplete) work. Site to test the.
The theory sounds good. However, the practice of theory is somewhat different. In theory it is assumed that the site is transferred to the customer immediately and all. In reality, the transfer takes place gradually. This is done because the agency wants, first, as soon as possible to show the result, and secondly, to save money on testing. Part of the customer is able to catch the bug himself. Therefore, agency staff will spend less of their time.
This situation leads to some difficulties: the programmer must not only shut down, but to make corrections, which found customers. The number of iterations increases and, consequently, increases the time of the project.
How to be a project manager from the customer?
It is not necessary to show the first version of his leadership. Test yourself. Engage your friends. Directors of the intermediate results is better not to introduce. Because intermediate results are always far from what was assumed in the beginning, and just as they are far from the final product.
If the site surrender piecemeal, as if their test?
1. Working / not working elements.
- Complete all the links and see where they lead and lead if at all. Does the text links page header?
- The menu items, if implemented in the form of images - whether written texts? Is bear a hyperlink?
- Forms to enter the text: a work which font in input text, which saves your information through forms?
- Does autocomplete (pull-down box with options for text previously entered in the form of, for example, e-mail addresses)?
2. Access: Are all the functions on the delimitation of the rights to edit the various pages are implemented?
- Register online for multiple users and identify them for different access rights. Look, there are the same described the possibility of changing the site with the possibility of sales.
3. Cross-browser compatible.
There are special programs that allow you to test your website in different browsers. But this is the part of the testing, which should ensure the agency. You will only need to put yourself Internet Explorer 6.0 or 7.0 (at the same time they are placed, but very difficult), Opera 9 and Firefox, and third in line to test your site in each of them.
4. System Administration.
- Try to create new partitions, rename existing ones, to change the nesting level of the section, add text, edit it, add a picture to put down a link.
- Note: the texts on this site are placed exclusively from the editors of the "Notebook." If you’re like I am now, typing an article in Microsoft Word, you must first perekopirovat it in notepad, and then just insert the site. If you want to do everything directly - use the html mode in the system of administration. And the notebook, and html-mode "cut off" the internal formatting tags that Word automatically inserts into all of its documents. These tags affect how the text will look on the Web. Chance to get not what you planned, with this copy is great. Although the management change and improve. And perhaps, after a while the council will no longer be as useless.
5. Overall design.
- It is necessary to compare the design layout and html-version of the site. How to make links through which the user has already passed, and those whose content he has not looked? How are icons? Does the boundaries of texts and forms with those that were drawn in the design? Are the distances between the elements of those that were included in the layout, like the colors in your browser to the colors in your layout?
- Make the color can not completely identical to any one designer. That looks like the color, depending on your monitor settings. Red, of course, do not turn green, but that can easily change color. Do not be surprised and do not worry about it.
6. The implementation of the functional.
- Do all done, or it may be something missing?
How to describe and how to send bugs agency?
Create a single document that you will be making all the errors found on the site.
The document you forward the agency. The agency will correct the error. You ottestiruete site for a new, paying attention primarily on those aspects that were identified in the bug-tracking. In the process of re-testing of new bugs come out … There are usually about three iterations. But there is more.
After the studio will send you more or less final version of the site, attracted to the testing of all interested employees. You can even arrange a little competition: who finds the most errors. In the description please give name and version of browser, through which the error was found.
Those bugs will be fixed, you can simply remove from the table. And in order to avoid confusion in the iterations (which is not less than three) are better to create separate worksheets in ekselevskoy table.
Exactly the same test should be done after the site will be posted on the hosting.