Many of the Requests for Information or Requests for Proposals are extended documents with the significant proportion related to procurement compliance. Often the details on the solution are not that clear. Here is the skeleton of what you need to have:
- Critical success factors. What are the high level expectations of what will determine whether the solution has been worth the effort!
- Business requirements. Technical requirements are not business requirements. What is the actual underlying operational, commercial and financial requirements that are driving the solution. Not the perceived or interpreted requirements.
- Provide your assumptions around the stated functional requirements of the solution that underpin the business requirements. The functional requirements should address not only the technology that is to be acquired but the underlying processes and the human interaction required.
- Lay out a scope of work that address the functional requirements. These need to not have any ambiguity. The solution will failure if the client and vendor are not aligned.
This article was originally published over on LinkedIn: The skeleton of a Request for Information for Information Technology projects
Please drop a comment below if you have any information to contribute further to the topic.
Post a Comment