As cloud computing grows along with services available newer options are now available for IT intensive shops. Organizations with a large IT staff may look to build their software to a customized version of what specifically is needed for that organization. This may be especially true if they are already using a component of software from Force.com, Zoho, Netsuite, Amazon etc. These vendors all offer platforms in which have open API's for you to build your own application on.
Before jumping in and building your own ERM to suit your specific needs consider these issues that should be overcome in order to proceed. If these can figured out then go ahead and let us know how you have overcome these issues. "Build it and they will come" and hopefully follow.
- What if the sme (subject matter expert) builds the application and then leaves, is there a strategy to continue use of the application and how?
- Will software applications developments and ITIL methodologies be implemented and followed, is there any reference to source code or documentation?
- How does a network administrator manage multiple applications that reside in the cloud and in-house?
- How is data manged if enterprise search is an initiative?
- How intricate is the integration between applications?
- Does this help or destroy the content management initiative or create silos and disparate systems?
- Who handles the support for multiple applications, what type of resources are required?
- Will you need an sme for each application that you build?
- How are the upgrades handled for each application and how often, does that include interfaces?
A related blog that sheds another perspective on this topic is Vinnie's over at Deal Architect The deal architect The end of packaged software as we know it ?
No comments:
Post a Comment