Implementing Intranet on Speed: I did finish it ...
I noticed I never closed my comments on the intranet
implementation - in general, a roaring success, based on the following
criteria:
- Project completed at minimal cost - we used DotNetNuke, a nifty little
open-source portal that works on Microsoft's .Net platform. Many
resources
exist that list free
and inexpensive
modules to add on to the basic functionality, plus tutorials
and help
in tweaking the system.
- Project completed quickly - about three weeks from
start to current, although we has done a little bit of research over
the summer. It's not "finished", it will never be "finished", but the
platfrom is there, basic content is available, folks are using it,
and we've plugged it into our ongoing maintenance tools so we can
keep track of requirements and requests
- Self-sufficient Content Managers - within two
weeks, three different departments had completed their internal sites
/ pages, with minimal assistance from IT.
- Simple, sustainable Administration processes -
we're taking advantage of as much functionality as we can, like
self-registration, password reminders, etc. Plus, we've hooked up a
number of feedback links so folks can immediately ask for help, get
questions answered, etc.
- Extensible platform for the future - we've already
shown how easy it is to extend the portal with inexpensive ($20-100,
that it!) modules; also, we've got some proof-of-concept things
cooking for the exefcs, who are ultimately looking for an "executive
dashboard" of metrics for the business.