Merle Randlepp
Agile Coach
Merle Randlepp
Agile Coach
How to prepare a good online procurement? Sample technical specifications
It is impossible to overestimate the importance of the technical specification, i.e. the quality of the terms of reference of the software solution. You get what you ask for. I am sharing here a sample technical specification document, which you can either use as a basis or review whether you forgot anything important.
The content of the terms of reference also depends on whether it has been decided to make one or two procurements. The sample document below is suitable for two procurement variants, where the design and prototype already exist and the main technical implementation is ordered. If you order the web from scratch, you have to add the missing part.
The main recommendation is not to go into too much detail in the terms of reference. Don’t describe actions that are too specific, such as what this or that button should do when clicked. Write down your business needs so that the main things are said and you get a sufficient overview of the functionality, BUT without getting bogged down in details.
If the prototype already exists, the developer can quickly get an overview of the scope by comparing the story and the image. A shorter initial task also saves the time of the parties and does not lock the customer into extremely detailed requirements, but leaves the normal development room of the implementation phase for minor changes.
The model document contains the following chapters:
1. Purpose and scope of the procurement
why and what is being procured; what has been done in advance and what are the input materials
2. Overview of the existing system
brief background information on the current situation
3. Requirements for the new system
what kind of technical platform and architecture is expected
4. Visual design, views, prototype
references to existing additional materials, e.g. business analysis, UX/UI analysis, CVI, prototype (wireframe), etc.
5. Functional requirements
A sufficiently thorough overview of the required functionality
6. Data migration
Order a full data migration only if absolutely necessary, because it is quite expensive work. At the same time, transferring the newsletter to the list of recipients is basic and easy.
7. Non-functional requirements
Sample requirements are provided, they can always be deleted.
8. ANNEXES
If you have any good suggestions for improvements, write to me info@agilecoach.ee
Happy use!
DISCLAIMER: The document below has been created as a sample technical description of the website and has been prepared based on my personal experience. Use this document only as a reference and determine the final requirements based on your organization’s needs.
Related topics
How to prepare a good online procurement? Selection of procurement conditions
In my previous blog post, I talked about the selection of evaluation criteria as one of the most common typical mistakes when preparing a public procurement. In fact, there are several other conditions in the procurement that should be paid more attention to.
How to prepare a good online procurement? Selection of assessment criteria
For an IT project manager who will carry out
a new procurement Lately, I have had a succession of online procurement projects on my desk, in the course of which I have helped the client to prepare procurement documents for either a website or a mobile application, including the technical terms of reference.
Every new contact is an opportunity for new and exciting collaboration - write or call me, and let's discuss how I can help you.
The first consultation and proposal are always free.
