I have already raised the topic of Technical Assignment. Today I want to touch upon this aspect of website development once again, since a good technical assignment is the most important component of success in a project, and it won’t hurt anyone to talk about this subject once again.
Aksi Marsovich
Intergalactic expert
Technical Task
This is a document that sets out all the requirements for the future website: from technical aspects to requirements for the design and content of the website. If we draw a parallel, this is like design documentation for building a house. The Technical Assignment is required both by the customer, so that they can understand what the website will be like at the end, and by the contractor, so that the working group from the web studio (agency) understands what to do and how to do it.
The Technical Task is not a panacea, since it latest phone number database is impossible to write an ideal TT and foresee all possible pitfalls. For example, during the development of a website, changes may occur in the customer's business processes from the IT market, or in the legislative field of the Russian Federation there are often innovations that can affect changes in the project.
The technical specifications are primarily required to understand the scope of work, agree on it with the customer and, based on the agreed technical specifications from the contractor, to formulate a detailed, transparent cost of work for the Customer of the website. Option: "Do you have a technical specification?" The customer's answer: "Of course I do, I'll send you my "wants" in an email now", fortunately, will not work. Why won't it work? Because in order to understand the entire logic of the website, it is necessary to describe all the modules of the website in detail. For example, you say: "I want a "get a consultation" button on the website." This information is very little, and in order to estimate the cost of work on programming this button, we need to understand:
What fields will be in the "get advice" form?
What fields will be required?
What will the thank you page for the application look like?
Where will the information about the application from the site go?
Is it necessary to connect third-party services to this form, such as an SMS gateway, CRM system or not?
Is it necessary to archive applications in the site's CMS?
It seems like there is one standard form, but there are so many questions about how this form will be implemented.
If we talk about the AXIOMA web studio, where I work, then, to a large extent, we do Technical Assignments for free. In particular, if we are talking about small projects such as single-page sites or multi-page, corporate sites. But if the customer comes with a request to evaluate an online store with a large number of different integrations or with the intention of making an Internet portal, then, in this case, we conclude an agreement with the client for the development of the Technical Assignment and implement it on a paid basis for a symbolic amount of money. We have separate specialists on staff who specialize exclusively in the development of such project documentation called "technical assignment for the development of a website" (online store, portal, mobile application). The development of a pilot version of the Technical Assignment, for example, for a corporate site, can take on average from 1 to 3 days. The approved estimate of work and the Technical Assignment are subsequently appended to the contract for the development of the site.
If you would like to receive a pilot version of the Technical Assignment from us, please fill out the brief in the selected service.
All the best to you and see you soon.