Last week, in a blog article, I discussed the challenges of preparing to consult with a company and advise them on issues related to enterprise mobility. I shared that it is helpful to send questions in advance so you know what kind of environment you are walking into. Since that article I have thought of a few more questions which I have listed here:
Do you need an SDK (software development kit) to customize and/or edit your own mobile applications?
Do you want to develop your own mobile application in-house, buy off-the-shelf or contract with a third party for a custom mobile application?
If you want to develop in-house, are your stakeholders patient enough to wait for the final product? What are the costs to the business of not delivering on time?
If you develop in-house, who will support new versions of the mobile operating systems and new mobile devices?
Which business unit will budget to pay for upgrades to mobile operating systems and mobile devices? They change every few months? Do you really have developers that will be available for all of these updates and upgrades?
How will you support it? What is the plan for supporting mobile applications and mobile devices?
What countries will be using it?
What data plans does the company want to use in each country?
How will you manage the data plans?
What is the policy for replacing missing or damaged mobile devices?
Which business unit will pay for lost devices and data plans?
What is the process for approving mobile access to ERPs and business processes?
Syclo, a co-innovation partner of SAP in the mobility space, speaks of supporting any data source, any network, any device, any industry, any process and anywhere in the world. Doing that all for one enterprise takes getting a few questions answered. What other questions should we add to this list?