There's something that I also think devs need to be aware of with BYOD. Most companies have you sign an IP transfer clause as a part of your hiring paperwork.
The clauses vary, but in effect they state that the company owns all of your intellectual property.
BYOD opens a vector for a company to grow that ownership.
If you ever wanted to have a side project? Company owns it. Write a book? That's also the company's property.
It'd be dangerous to assume that because they offered BYOD that they revisted those clauses.
Nice article.
There's something that I also think devs need to be aware of with BYOD. Most companies have you sign an IP transfer clause as a part of your hiring paperwork.
The clauses vary, but in effect they state that the company owns all of your intellectual property.
BYOD opens a vector for a company to grow that ownership.
If you ever wanted to have a side project? Company owns it. Write a book? That's also the company's property.
It'd be dangerous to assume that because they offered BYOD that they revisted those clauses.
I was not aware of this prior to reading your suggestion. Do you know of a case study that demonstrates a lack of proper revision for BYOD policies?
This sounds fundamentally dangerous and can cause licensing issues.
I don't know of a study, but I have been at plenty of companies that issued BYOD policies that didn't address preivously existing IP transfer clauses.