According to a press release by Gartner, the rise of bring your own device (BYOD) programs is the single most radical shift in the economics of client computing for business since PCs invaded the workplace.
Actually, BYOD started when, in 2009, Intel initially recognized a growing trend among its employees to bring their own device to work, and connect it to the corporate network. Ever since, it has seen an increasing adoption by companies. Many companies have adopted it as an alternate strategy to allow employees to use their personally owned devices to work with enterprise applications and access data.
Now that SaaS has crossed the chasm and is not an “alternative”, BYOD can bring real benefits, such as reduced spending by the companies on buying devices and upgrading them, lesser procurement headaches, and faster turnaround for using the latest technology.
But, BYOD came with many strings attached. Some typical areas of concern which threw up challenges were:
- Data breach and security
- Management policies
- Reimbursement policies
- List of types of devices allowed
- Technology support
If you are considering introducing BYOD in your projects, then all the above factors have to fall in place for you to be able to implement BYOD effectively. Here are five steps which will make your project management easier with BYOD:
1. Draft BYOD policies for your project:
Draft BYOD policies for your own project vis-à-vis the company’s BYOD policies. Over and above company’s legal and security policies, this could include:
- A list of possible devices that are permitted under the BYOD scheme and your project’s specific technical needs.
- The “necessary and sufficient” conditions under which upgrading technology is permitted.
- Expense reimbursement policies for employee-owned devices that are used under BYOD.
- Approval process for upgrading and maintenance of the devices.
- Project data ownership guidelines.
2. Declare data ownership:
Every project generates critical data which has its own data security and ownership policies set as per customers’ requirements. It will be better if the project manager separately declares data access and ownership policies in lines with his/her own company as well as those set by the project stakeholders. If you are initiating the BYOD approach for the first time it will help to conduct an orientation session with the team and continuously monitor the same.
The project manager should also coordinate with the support staff to understand the possible controls that can be set up on the devices in order to successfully implement restrictive data access and ownership policies.
3. Choose a SaaS project management tool:
With most of the application software available as SaaS, BYOD has become a reigning reality. Since employees get to choose their devices, they truly enjoy working on their devices. Such conduct makes a good case for using project management solutions that are SaaS-based, with features for collaborative teamwork even under distributed team set-ups. BootStrapToday provides you with all this and more. Check it out for FREE.
4. Factor in an MDM 2.0 Solution
To ensure that the BYOD approach in your project is a hit, make sure that your company already has budgeted for an MDM 2.0 solution. If not, then before you implement the BYOD in your project, get approvals for the IT support to have an MDM 2.0 solution.
An MDM 2.0 solution provides centralized visibility to the devices and users that connect to the corporate network, and allows the IT support to manage the devices by applying the corporate security policies. It also focusses on data creation and update, and remotely lock and wipe a device, which helps to protect the data stored on the device when it is lost or stolen.
With such a solution, you can coordinate with the support staff to ensure your project specific needs are implemented provided of course that they comply with the corporate security policies.
5. Track your BYOD compliance:
It is important that you keep a track of performance under the new BYOD approach for your project. You should develop your own checklist of the factors against which project management under BYOD needs to be judged. For example, with the help of IT support, you can get the right set of reports to understand your team’s compliance with the laid security policies. You could also track device performance. You have to ensure that it does not affect the developer productivity.
How do you think project management with BYOD can be improved?
(Photo credit: http://techsource.datacom.com.au/TechKnowledge/?Tag=BYOD)