>I am currently part of a committee at my company that is putting
>proposal for our next generation of SCM tool. However, I need some help
from all you
>net-folks out there regarding "home grown" vs. third party tools.
>Does anyone out there have some hard numbers on how much (man/hours,
dollars) it really
>takes to support home grown tools, as opposed to third party tools? FYI,
my company is
>involved in Systems Integration and custom development of software, and
>700 people, and we would especially like to hear from companies with
Rob Lesieur made some good points that are worth bring up for your
company, although I think his support numbers are low. If you are not
marketing CM products, don't get into developing them. Commercial
companies have development teams of 50 or more developers (send me pvt
email and I'll name the co I know for sure).
Another thing to keep in mind is the underlying changes in technology
that are appearing (re Rob's comment of can you say text based interface..
;-). Application of GUI and object oriented databases and technologies.
Use of knowledge based approachs to build in more intelligence to your CM
database. Even if your company is using these technologies would they be
willing to apply there best people to an internal (can you say overhead...
) development with no hard $ return?
I am working on a very large project, >100 developers at my site alone.
At my site we have multiple CM databases. We are using a commercial tool,
which one is not important. Local DBA and tool support is provided by ONE
person. Once set up the tool is used by the development team as part of
its development process and requires minimal support. Oh that person also
acts as the lead support person for our project which involves many 100's
of developers accross many companies. You have got to get your management
to ask themselves if therre internal system could do the same.
Bob Ventimiglia, Austell, GA