We’ve all heard the horror stories. Tech implementations gone wrong can haunt an organization.
Whether a vendor didn’t properly set the expectation of the nonprofit, or the nonprofit in question simply didn’t do their research, surprises in a tech implementation will happen. However, if a nonprofit is adequately primed by their vendor, these problems should be minimal.
Follow these 3 steps and your nonprofit’s cloud implementation should go off without a hitch.
Build a business model
By taking the time to build a business model, or a series of valid business reasons, will help your cloud vendor better understand how you plan to utilize the technology, and ultimately deliver your nonprofit a better product. More specifically, it will help them understand performance requirements, resource requirements, lifecycle cost estimation, and required risk treatment measures.
Your business model should have enough detail so your potential cloud vendor can accurately estimate costs. Including in your business model information on user characteristics, numbers of users, how they’ll be using it, variance in usage rates (more or less busy during different times of the year, data quantity and other data characteristics, and how you project usage will increase over time are great places to start.
Assess risk management
No matter what you’re doing, there’s risk associated with it. Understanding this, and considering the cost to manage and handle these risks is a critical step.
Does the cloud solution meet the quality need of your organization? Does the cloud solution provide the value for the money? Does this cloud solution work within your organization’s culture? Will the cloud solution adequately meet performance requirements.
Plan for implementation
If you’ve ever prepared an outsourcing arrangement, preparing a cloud implementation is a very similar process. This planning should cover myriad topics and areas of your organization. Here’s a list of things you should begin looking at:
• Preparatory work to make application and infrastructure ready for integration with the cloud solution;
• Perform risk and security assessments;
• Updating organizational continuity plans;
• Preparing an end of life plan to disengage with the provider and transition service and data while assuring business continuity;
• Updating architectural artefacts;
• Performing acceptance testing; and
• Managing business transition and organisational change.
• Agencies must also put in place the internal capability and resources need to manage the cloud service on a daily basis. Ongoing operational activities include:
• Monitoring performance and service levels;
• Responding to incidents and service disruptions;
• Analysing, coordinating, prioritising and implementing configuration changes to meet emerging requirements and user feedback;
• Managing configuration documentation;
• Coordinating planned upgrades or outages;
• Reconciling invoices against services provided;
• Managing the relationship with the CSP;
• Administering governance arrangements; and
• Handling service or contract disputes.