[Sigia-l] Extranet software

[Tim Salam]

There seems to be a great deal of confusion coming from my a) possibly poor
choice of words and b) lack of time to fully explain.

Yes, my statement that "build-from-scratch is inherently wasteful" was
misleading in that I believe I didn't explain myself thoroughly enough (just
don't have the time these days!).

Allow me to preface my comments by saying that there is hardly any such
concept as a truly "packaged" app - the vast majority of installations I've
heard of were a round of customization based on the foundation of a software
package.  For this discussion, we can call them "hybrid installs."

Ok, while there are several ways to develop or introduce an app to an
environment, I will boil it down to the following. Oh, and I hope everyone
(Ziya) doesn't become upset regarding my wanton use of generalities here:

1. Typical build-from-scratch project.  Typical (read: inherent)
characteristics include:
	- More time spent than a hybrid install. (most expensive)
	- More people involved (highest error rate).
	- Advantage: custom-tailored to project goals.
	- Disadvantage: Besides typical disadvantages of any full-blown project,
the expense is often the largest.

2. Straight, un-customized package install. Typical (read:
inherent)characteristics include:
	- Fastest implementation time on average. (cheapest)
	- Least amount of people involved. (lowest error rate)
	- Advantage: For those who need it five minutes ago. Quick!
	- Disadvantage: Typically poor match to needs, usually doesn't scale well
(if at all), etc.

3. Hybrid installation (customization based on a foundation of packaged
code).  Typical (read: inherent) characteristics include:
	- Fast implementation time on average. (average expense)
	- Minimal amount of people involved. (average error rate)
	- Advantage: custom-tailored to project goals.
	- Disadvantage: I'm still working on this one...

My ultimate choice and what our company does is one of two things for any
given client:

A. Customize the same base of code we developed over a year ago, over and
over.  We also upgrade the foundation regularly, thus improving all
implementations (past as well - the software is web-based).

or..

B. Start with a scalable, customizable third-party packaged app as the
foundation then customize until it meets all project goals.

So, why do I think "build-from-scratch" is inherently wasteful?  Well, the
definition of "inherent" is an intrinsic, essential characteristic of
something.  Compared to the way I have grown used to doing things,
"build-from-scratch" in inherently wasteful.  These project inherently take
more time - that's wasteful when given the option to do hybrid installs.
These projects take more money and manpower, thus are more expensive and
error-prone - that's wasteful.

I've been on ALL sizes of projects, with timelines ranging from 2 years to 3
days.  I've seen more time and money get wasted than I care to count.  It is
these experiences that have a) formed the direction and vision of my company
and b) formed my opinion.

In short, just my thoughts on the matter.  I now owe the list one good
IA-related email or response. :)

Tim Salam
Vice President
Essemble IT Solutions
http://www.essemble.com
+1 602-246-0499 voice
+1 480-332-5521 cell
+1 602-795-8622 fax