H1-B Visas are a tricky subject. They are given out in a limited number per year (65,000 is the cap for 2017) and are sought by corporations in order to bring in what is considered specialized labor which cannot be found locally.
There are several restrictions associated with the application process....mostly designed to prevent the H1-B visa worker form taking over the jobs of US workers.
The problem is that there have been numerous cases where workers have been exchanged against a (presumably) lower paid worker who was brought in with a H1-B visa.
The practice has been always been viewed with disdain but it looks like there are a few things happening which might limit the appeal of H1-B visas in the future...or at least it won't be that easy anymore to exchange workers on a 1 to 1 basis.
One meaningful change to the law which is in the works is that workers will be able to contest their firing if they believe they are being laid off and being exchanged with a H1-B visa employee.
This is what seems to have happened at Abbott Labs in April 2016. Apparently 150 tech employees were let go and on the way out were asked to hand over their security credentials to newly incoming H1-B workers.
Of course every employee had to sign a Non Disclosure/Disparaging Agreement in exchange for severance....so details are hard to come by.
For more details read: Abbott labs lets 150 people go
One employed though did not sign the agreement and is speaking up. Consequently it now looks like some politicians have picked up on the issue and are going to strengthen regulatory oversight.
Given the current political climate this should hardly come as a surprise.
Given the abuse in the H1-B program additional regulation might be a really good thing.
Regulations of course might not do the trick if the abuse is fraudulent.
Fraudulent abuse like the one initiated by Infosys and fined in 2013 is obviously much more serious than misuse and might deserve more scrutiny.
For More information read: Infosys pays record 34 Mio fine for immigration fraud
At the end of the day it will require a combination of better regulations and enforcement of existing laws to plug the hole through which the system has been abused. Corporations need access to talent and hopefully revisions to the law will not change that. At the same time US workers should also not be shortchanged...so let's hope that lawmakers will strike the right balance.
A collection of comments,newsworthy articles and posts dealing with outsourcing and BPO services by Steve Benger
- Home
- Which Are Better..Indian or Philippines Call Centers ?
- Why Your Business Will Benefit From Outsourcing
- Is Your Web Presence Up To Par ?
- How IBM's Watson Might Kill The Call Center Industry
- How To Test Your Outsourced Software Development
- Guerrilla CEO…How To Adapt When Needed
- Think Your Don't Need a Business Mobile App? Think Again!
How A Two Speed IT Structure Can Give Any Company The Edge...
It is a concept which has not gone mainstream yet but it has been gathering a following now for a few years.
I am talking about the concept of having a Slow Speed IT lane and a High Speed IT lane within the same organization.
Over the past years a lot of companies have embarked upon the digital transformation the market place (their customers) have demanded.
Digital transformation means a lot of different things to different people but most commonly the following IT challenges are understood to be part of the digital transformation package:
I am talking about the concept of having a Slow Speed IT lane and a High Speed IT lane within the same organization.
Over the past years a lot of companies have embarked upon the digital transformation the market place (their customers) have demanded.
Digital transformation means a lot of different things to different people but most commonly the following IT challenges are understood to be part of the digital transformation package:
- Online Systems (Web Applications)
- Mobile Apps
- Social Media
The challenge is of course that things happen much faster on the web (the digital marketplace) than a lot of IT organizations are used to operate at. An IT department which has been supporting the legacy component of an organizations IT infrastructure does usually not need to move very fast.
Legacy systems are ordinarily updated rather infrequently...so there is often times the mindset that being slow or deliberate is not a bad thing. There are still plenty of organizations which run enterprise software off an AS/400 and/or use Windows Vista.
The issue of course is that this mindset is producing a competitive disadvantage in the digital marketplace.
Companies are falling behind in their Key Performance Indicators vis a vis their more aggressive, digitally savvy peers.
CIO's and Decision makers do realize that a huge part of addressing the shortcomings is to foster a culture which is more geared towards the Digital Marketplace.
Needless to say...sometimes this is easier said than done.
Often times the very same decision makers which are tasked with spearheading the transformation are part of the culture where slow and deliberate is good.
So..the question of how to get ahead of the curve and transform into the Digital Marketplace deserves to be looked at.
Perhaps the easiest and most practical solution is to outsource the Digital Transformation to outsourcing companies who have a lot of experience in that area while maintaining the existing In House IT infrastructure.
The effect is what is being called a Two Tier IT infrastructure. One lane is High Speed (Digital Transformation and Strategies) and the other lane, Slow Speed lane, deals with Core Legacy and Maintenance.
There are a few advantages operating a two tier IT infrastructure. Presumably the outsourcing provider is up to date on the latest technologies and even more important, stays up to date...thus ensuring that the organization is able to outperform its competitors.
The core IT team remains relatively unaffected and can concentrate on the issues they have proven to be good at.
In combination the two Speed Lanes can offer a successful blueprint how an organization can become more agile while maintaining the continuity needed to safeguard existing business processes.
Jamaica Clearly Seems To Be The Best Horse In The Barn For Xerox.....
I had written about the Jamaican BPO sector before. It is clearly a niche market with only 17,000 employees as of right now (albeit it is growing at a 20 % plus rate) but it has some distinct advantages over the more traditional outsourcing countries.
It has some pretty good universities which produces a fair amount of talent, it is in the same time zone as the US (same time zone as Chicago) , salary levels are about 70 % below US salary levels and the official language is English.
Perhaps the single biggest advantage is the typical very "sunny disposition" of the average Jamaican...one will be hard pressed to find a Jamaican who is openly in a bad mood.
No company has placed a bigger bet onto the Jamaican BPO sector than Xerox. The total BPO workforce of Xerox in Jamaica is about 7000 right now...giving Xerox about 18 % market share in an industry which is usually much more fragmented.
The 7000 headcount of Xerox makes them the biggest employer in Jamaica (after the government of course).
Most interestingly, Xerox investment into Jamaica seems to be paying off for them. Internal Key Performance Indicators (KPI's) are hard to come by but a recent article (see here) disclosed that the Jamaican BPO office has a 98.5 % satisfaction rating with its healthcare clients...which should make them one of the highest rated office within Xerox.
One reason given why the offices is doing so well is low turnover. The Jamaican office has apparently the lowest turnover of all Xerox locations worldwide. In an industry which is characterized by high attrition rates that feat is obviously remarkable and undoubtedly leads to higher customer satisfaction.
Jamaica obviously lacks the infrastructure and population to be attractive to the major players in the BPO industry. The headcount required to make a dent in their operation for the biggest BPO players cannot be reasonably made available in Jamaica.
The lesson learned from the Xerox experience though is that on a more individual level companies looking for a good alternative to set up their BPO operation Jamaica might be a good idea.
It has some pretty good universities which produces a fair amount of talent, it is in the same time zone as the US (same time zone as Chicago) , salary levels are about 70 % below US salary levels and the official language is English.
Perhaps the single biggest advantage is the typical very "sunny disposition" of the average Jamaican...one will be hard pressed to find a Jamaican who is openly in a bad mood.
No company has placed a bigger bet onto the Jamaican BPO sector than Xerox. The total BPO workforce of Xerox in Jamaica is about 7000 right now...giving Xerox about 18 % market share in an industry which is usually much more fragmented.
The 7000 headcount of Xerox makes them the biggest employer in Jamaica (after the government of course).
Most interestingly, Xerox investment into Jamaica seems to be paying off for them. Internal Key Performance Indicators (KPI's) are hard to come by but a recent article (see here) disclosed that the Jamaican BPO office has a 98.5 % satisfaction rating with its healthcare clients...which should make them one of the highest rated office within Xerox.
One reason given why the offices is doing so well is low turnover. The Jamaican office has apparently the lowest turnover of all Xerox locations worldwide. In an industry which is characterized by high attrition rates that feat is obviously remarkable and undoubtedly leads to higher customer satisfaction.
Jamaica obviously lacks the infrastructure and population to be attractive to the major players in the BPO industry. The headcount required to make a dent in their operation for the biggest BPO players cannot be reasonably made available in Jamaica.
The lesson learned from the Xerox experience though is that on a more individual level companies looking for a good alternative to set up their BPO operation Jamaica might be a good idea.
Who Is Winning The Outsourcing Cloud Wars ?....
Undoubtedly the rise of the cloud over the past few years has created tremendous dislocations within the IT sector. Outsourcing hardware and infrastructure needs started with moving equipment into data centers, took on a life of its won and ended with the rise of companies who had never been in the "hardware business" before.
Players like Amazon (AWS) and Google (GCP) who were never a factor as a provider of the technical backbone for corporations are now firmly entrenched in a lot of organizations. Microsoft, who was always present through their software solutions is now battling it out with everyone else as a cloud provider (Azure).
Then there are the established players who have built their own cloud to support their operations.
Perhaps no company has been more aggressive in developing its cloud than Salesforce. Their entire business has been built to be cloud centric from the start...and one can argue that the cloud made their business possible.
For CEO's and CIO's at companies operating their own cloud the question of whether one of the big 3 players in the field (AWS, AZURE , GCP) might do a better job than their own Internal Data Centers always gets deliberated.
The cost / benefit analysis is rather difficult in many situations. Not only does the company stand to loose certain functionality, it also has to consider the reputational effect when a technology company operating its own cloud effectively concedes defeat and moves its cloud to one of the big 3.
Yet, this is exactly what happened at Salesforce. Salesforce has chosen Amazon's AWS to power most of their core services. (Sales Cloud, Service Cloud, App Cloud, Community Cloud , Analytics Cloud)
It is a rather stunning announcement. Salesforce who has been on the forefront of running perhaps the single most successful cloud business there is decided to move a significant portion of its cloud to a company which was barely in the business of operating a cloud service 10 years ago. (AWS was started in 2006)
Undoubtedly this is an event which will ring the bells at a lot of corporations who operate their won cloud. If the preeminent cloud centric business decides to outsource their cloud to AWS - what justification can be found by other companies to continue operating their own cloud ?
Salesforce might have been early ..but it just rang the exit bell for pretty much every company to close up their own cloud.
Players like Amazon (AWS) and Google (GCP) who were never a factor as a provider of the technical backbone for corporations are now firmly entrenched in a lot of organizations. Microsoft, who was always present through their software solutions is now battling it out with everyone else as a cloud provider (Azure).
Then there are the established players who have built their own cloud to support their operations.
Perhaps no company has been more aggressive in developing its cloud than Salesforce. Their entire business has been built to be cloud centric from the start...and one can argue that the cloud made their business possible.
For CEO's and CIO's at companies operating their own cloud the question of whether one of the big 3 players in the field (AWS, AZURE , GCP) might do a better job than their own Internal Data Centers always gets deliberated.
The cost / benefit analysis is rather difficult in many situations. Not only does the company stand to loose certain functionality, it also has to consider the reputational effect when a technology company operating its own cloud effectively concedes defeat and moves its cloud to one of the big 3.
Yet, this is exactly what happened at Salesforce. Salesforce has chosen Amazon's AWS to power most of their core services. (Sales Cloud, Service Cloud, App Cloud, Community Cloud , Analytics Cloud)
It is a rather stunning announcement. Salesforce who has been on the forefront of running perhaps the single most successful cloud business there is decided to move a significant portion of its cloud to a company which was barely in the business of operating a cloud service 10 years ago. (AWS was started in 2006)
Undoubtedly this is an event which will ring the bells at a lot of corporations who operate their won cloud. If the preeminent cloud centric business decides to outsource their cloud to AWS - what justification can be found by other companies to continue operating their own cloud ?
Salesforce might have been early ..but it just rang the exit bell for pretty much every company to close up their own cloud.
Strange News...Indian Outsourcing Company PLans To Hire 25,000 Workers
An Indian Outsourcing / BPO company has announced that it intends to hire 25,000 workers. The number is obviously staggering on a lot of levels and reading the newspaper article one has to wonder if the company will ever manage to do so.
Never the less..the number is certainly eye catching..and that might very well be part of the reason why it is publicized. Makes for some good PR.
Horizon Outsourcing Solutions is an Indian based provider of BPO solutions and currently has a headcount of "only" 3000. As such it is looking to grow its employee count by a heft 900 % in the next two years.
The hires are apparently semi skilled/non skilled..as per the company. As such the focus will be on providing telephone and back office related BPO services.
It speaks to the depth of the Indian job market that a number likes this can be thrown out without being ridiculed. It will be interesting to watch if Horizon can pull it off. If so..it would certainly be a testament to some serious management skills.
Full article with the release can be found here: Indian Company Wants To Increase Headcount By 900 %
Never the less..the number is certainly eye catching..and that might very well be part of the reason why it is publicized. Makes for some good PR.
Horizon Outsourcing Solutions is an Indian based provider of BPO solutions and currently has a headcount of "only" 3000. As such it is looking to grow its employee count by a heft 900 % in the next two years.
The hires are apparently semi skilled/non skilled..as per the company. As such the focus will be on providing telephone and back office related BPO services.
It speaks to the depth of the Indian job market that a number likes this can be thrown out without being ridiculed. It will be interesting to watch if Horizon can pull it off. If so..it would certainly be a testament to some serious management skills.
Full article with the release can be found here: Indian Company Wants To Increase Headcount By 900 %
Does Agile Makes Software Development More Expensive...Yes And No...Here Is Why
I am in the business of providing outsourced software development. When we design the requirements of a new software development a Requirement Manager will go through the entire project with the client and find out what specifically the client needs.
Often times the client is not necessarily aware of all the requirements it has when the project starts. There are general ideas, but sometimes the general concept has not been completely thought out.
A good Requirement Manager can be extremely beneficial in a situation like this. He/She will think along with the client and sketch out in technical terms what functionality the developers have to code.
The requirements then form the basis of the development model.
In a traditional development model (Gantt Charts and Milestones) at certain predetermined intervals the clients get a chance to review an interim product built and, once approved, the next step of the product will be developed.
The Agile development is different in so far that the client stays much more involved in the development. There is a constant back and forth (usually daily) with questions raised by the developers (typically through the Project Manager) and being answered by the client.
For a more in depth explanation of what an Agile project development looks like see here
Testing of certain functionalities happens much more frequently and often times unrelated development steps are being conducted at the same time.
The whole idea of an Agile project development (versus Gantt and Milestones) is to make the client more involved, thus enabling him to constantly improve upon the final product. Nonsensical development is supposed to be recognized earlier on..thereby reducing 'errand" development time.
One can argue which approach is better. I certainly feel Agile is the way to go.
One inherent side effect which develops out of the Agile Project Management approach are changing requirements. What typically happens is that the more the client gets involved in the development process and gets to play around with the product...the more the client gets a feel for what the final solution should truly look like under real life conditions.
Consequently a client will update the requirements. Features get added and / or amended.
Needless to say...the adding of additional features makes the development more expensive. Every time an additional feature is added more hours have to be paid for.
Therefore the argument has been made that Agile is "more expensive".
I wholeheartedly disagree with that opinion and, as a matter of fact, believe that an Agile approach will make the development cheaper.
That might seem counter intuitive at first..but here is why.
It is a simple fact that the Minimum Viable Product built ( MVP , the first development) is always just the first step to a more final product. As soon as the MVP is out and people start using it there is feedback coming in, suggesting updates and improvements.
Using an Agile approach ensures that the MVP is a much better solution than the MVP built using a simple Gantt based approach.
Precisely because the client has been more involved in the development and was able to add and/or update features while development was still going on less actual software development (= less developer time) had to be done.
It is obviously much cheaper to add a feature at an early stage (or amend functionality) when there are less interconnections to be worried about. By completing these changes earlier in the project a significant time saving can be accomplished versus changes to a released Minimum Viable Product built.
The Agile Development approach delivers a reduction in development time because the product release will be much closer a a more "More Final Product".
Using a Gantt development approach the costs to bring a Minimum Viable Product to a a more Final Stage Product are often times significant.
Anyone who has been in the Software Development Business long enough can tell stories where entire functionality modules were just missed...and had to be created after the fact (the MVP built) at great expense.
Using Agile a better MVP gets created, one which much more resembles a Final Product. Because the MVP built using the Agile approach is better the overall development costs are reduced.
Often times the client is not necessarily aware of all the requirements it has when the project starts. There are general ideas, but sometimes the general concept has not been completely thought out.
A good Requirement Manager can be extremely beneficial in a situation like this. He/She will think along with the client and sketch out in technical terms what functionality the developers have to code.
The requirements then form the basis of the development model.
In a traditional development model (Gantt Charts and Milestones) at certain predetermined intervals the clients get a chance to review an interim product built and, once approved, the next step of the product will be developed.
The Agile development is different in so far that the client stays much more involved in the development. There is a constant back and forth (usually daily) with questions raised by the developers (typically through the Project Manager) and being answered by the client.
For a more in depth explanation of what an Agile project development looks like see here
Testing of certain functionalities happens much more frequently and often times unrelated development steps are being conducted at the same time.
The whole idea of an Agile project development (versus Gantt and Milestones) is to make the client more involved, thus enabling him to constantly improve upon the final product. Nonsensical development is supposed to be recognized earlier on..thereby reducing 'errand" development time.
One can argue which approach is better. I certainly feel Agile is the way to go.
One inherent side effect which develops out of the Agile Project Management approach are changing requirements. What typically happens is that the more the client gets involved in the development process and gets to play around with the product...the more the client gets a feel for what the final solution should truly look like under real life conditions.
Consequently a client will update the requirements. Features get added and / or amended.
Needless to say...the adding of additional features makes the development more expensive. Every time an additional feature is added more hours have to be paid for.
Therefore the argument has been made that Agile is "more expensive".
I wholeheartedly disagree with that opinion and, as a matter of fact, believe that an Agile approach will make the development cheaper.
That might seem counter intuitive at first..but here is why.
It is a simple fact that the Minimum Viable Product built ( MVP , the first development) is always just the first step to a more final product. As soon as the MVP is out and people start using it there is feedback coming in, suggesting updates and improvements.
Using an Agile approach ensures that the MVP is a much better solution than the MVP built using a simple Gantt based approach.
Precisely because the client has been more involved in the development and was able to add and/or update features while development was still going on less actual software development (= less developer time) had to be done.
It is obviously much cheaper to add a feature at an early stage (or amend functionality) when there are less interconnections to be worried about. By completing these changes earlier in the project a significant time saving can be accomplished versus changes to a released Minimum Viable Product built.
The Agile Development approach delivers a reduction in development time because the product release will be much closer a a more "More Final Product".
Using a Gantt development approach the costs to bring a Minimum Viable Product to a a more Final Stage Product are often times significant.
Anyone who has been in the Software Development Business long enough can tell stories where entire functionality modules were just missed...and had to be created after the fact (the MVP built) at great expense.
Using Agile a better MVP gets created, one which much more resembles a Final Product. Because the MVP built using the Agile approach is better the overall development costs are reduced.
Subscribe to:
Posts (Atom)