Here's an expurgated version of what I sent out to the enquiring party
Sunday. It includes comments contributed by members of this list and
others. Hopefully, it's the beginning of a helpful document.
Julian
~~~
... I've listed below some additional information that may prove useful
to developing your RFP ... This information includes links to resource
sites, and some opinions that I solicited from colleagues on the matter
...
Most of my colleagues agreed that RFP's be as comprehensive as possible.
Include as much as possible of the following:
* backgrounder on your firm;
* project goals;
* specific deliverables;
* capabilities and resources to be contributed by your firm to
the project;
* business case including assumptions and supporting data;
* relevant schemata of business processes to be
augmented/replaced by the deliverables;
* specific information on existing and planned hardware/software;
* parameters for selecting a vendor;
Specific points mentioned by my colleagues:
* "the RFP should only go out when there is a consensus within the
company on the direction the project would take, the needs the
project is supposed to meet in the first place, and the will to
see it through";
* "... a good RFP will say [to the vendor], "Here is exactly
what [the client] will be contributing to the development
process, and here's what we need from you, [the vendor]";
* Many indicated that "RFPs that are more about using a specific
technology rather than looking for a solution" are annoying.
Indeed, projects that use technology for the sake of technology
are often doomed to failure;
* RFP's should contain "clear indications that a chain of command
is (ideally, already) in place internally to handle both
[vendor]
requests for additional information and to be responsible for
ensuring that everyone on the client side is happy with the
direction [the vendor's] work is taking". Who on the client side
is responsible for signing off what aspects of the project?
* contact information for all client-side personnel, including
those who may not apparently deal directly with the vendor;
* deadlines (for all aspects of the project, including proposals
and other information from the vendor, and for the project
itself);
* "An RFP should tell you what the most important issues are to
the client (is it cost, quality or time)";
* budget figures (many clients prefer not to provide these to
vendors to their own detriment. The budget figure allows us
to determine the kind and sophistication of implementation
we should be aiming for. Does the client want a Chevrolet,
or a Maserati?);
* "A good RFP should tell you when the client will choose their
vendor". In addition, debriefing those vendors that were not
chosen is not only appreciated by vendors, but a valuable
experience for both the client and the vendor;
>From a single developer: [ Thanks Brent! ]
* what the client's existing in-house Web development skills
and experience level is;
* how much of that will be provided to me as I work with the
client on the project
* what the client's responsibilities will be for providing
content, scripting, translations, editing and similar services
~~~
LINKS:
CIO Research Centres: Intranets --
http://www.cio.com/forums/intranet/
A treasure trove of knowledge. Many resources (best practices, case
studies) that are useful in planning and implementing generic and
phase-specific strategies for intranets.
I especially recommend "Developing Your Intranet
Strategy" (http://www.cio.com/WebMaster/strategy/), an online
slide presentation. Begin
Key areas are the slides at "A Design Framework"
(http://www.cio.com/WebMaster/strategy/tsld047.htm) and "Management
Strategies" (http://www.cio.com/WebMaster/strategy/tsld158.htm)
***
The Project Profiler --
http://www.secretsites.com/profiler/set_partnering.html
[...]
While this companion to David Siegel's Secrets of Successful Web
Sites applies to developing marketing oriented sales sites
specifically, many of the questions and issues raised in the
project profiler are salient to developing intranet oriented RFP's
as well.
Indeed, I would recommend a quick look at this book.
***
Miscellaneous Search Engine Results --
I searched on "how to write an RFP" on several search engines, and
came up with some potentially useful results:
Structuring RFP's
http://www.internetraining.com/6art2.htm
http://www.asaenet.org/sections/technology/helppr4.htm
Developing Internet RFP's
http://www.netb2b.com/cgi-bin/cgi_article/monthly/96/11/01/article.04
--
meep! media, inc. BuzzwordBingo.com
Internet and Intranet Consulting Buzzword Bingo Cards
http://www.meep.com/ New! Java Crossword Game
(514) 288 5948 http://www.buzzwordbingo.com/
____________________________________________________________________
--------------------------------------------------------------------
Join The Web Consultants Association : Register on our web site Now
Web Consultants Web Site : http://just4u.com/webconsultants
If you lose the instructions All subscription/unsubscribing can be done
directly from our website for all our lists.
---------------------------------------------------------------------
