Workshop Two

WORKSHOP TWO 3

WorkshopTwo

WorkshopTwo

Manypeople have been left wondering on how to develop and establish aBYOD policy and how to see its implementation in the best waypossible. Each idea has with it many significant questions that oneneeds to ask himself, your IT associates and your team of executives.One way of supporting a BYOD policy is to give specification on thedevices that are permitted. During the old days of BlackBerryservices, it was simple and clear. Today, there are a variety ofphones based on iOS as well as handheld androids. It is crucial tomake a decision exactly on the meaning of “bring your own device.”This could mean “your own iPhone but not your own Android phone(Miller, Voas &amp Hurlburt, 2012).

Anotherthing is to find an establishment of a strict security policy for alldevices. Users do not always want their devices to have lock screensor passwords. They view them as problems when they want to accesstheir phones. You should also give a clear definition of a servicepolicy for devices under the criteria of BYOD. Finally, you shouldclarify on the ownership of apps and data (Gwaltneyet al., 2015).

Manyfirms embrace BYOD programs imagining that they will save costs.However, the policy may turn out not to be as cost-effective asimagined before. BYOD can be profitable only under strict measures.It should be known that it is not a guarantee to make BYOD savings.Many providers of wireless devices give special rates to the firmsthat purchase devices and plans of data in large number. If BYOD isallowed in an individual business, then that business must as wellbuy software for managing a mobile device (Miller, Voas &ampHurlburt, 2012).

References

Gwaltney,C., Coons, S. J., O’Donohoe, P., O’Gorman, H., Denomey, M.,Howry, C., &amp Ross, J. (2015). “Bring Your Own Device”(BYOD)The Future of Field-Based Patient-Reported Outcome Data Collection inClinical Trials?. TherapeuticInnovation &amp Regulatory Science,49(6),783-791.

Miller,K. W., Voas, J., &amp Hurlburt, G. F. (2012). BYOD: Security andprivacy considerations. ItProfessional,(5), 53-55.