The decision to outsource a new application development often times seems like a rather daunting tasks for a business executive who has never supervised outsourced application development.
The simple truth is that not all companies have the In House tech staff who is experienced in organizing and supervising outsourced software development.
Fortunately the proper way to be successful when outsourcing software development is really not that complicated. Below is a 6 step list which, when followed, should ensure that your outsourced software development will no go off the rail.
Please note that the steps below are only applicable once you have selected the right outsourcing provider. Obviously, if your selected outsourcing partner does not deliver on the technology it can get rather tricky.
Step 1: Requirements Management and Audit
You start with the most important item first. A detailed analysis of the requirements is key. Each capability of what the software needs to do has to be properly documented. Additionally you have to assign the proper permissions, (edit, read, modify, delete and so on) to each user level which is authorized to access the data relevant to that function and or feature. There is a good chance that your Outsourcing Provider will have a Requirement Manager on staff who will guide you through the process. If not...assign a member of your team that responsibility. Once you have the requirements down schedule meetings with the Lead Developer or Team Leader and run through all the requirements to clarify any misconceptions which might arise. A well thought out requirement list will ensure that your application has all the features you need while avoiding excess development time which might arise due to changes and/or additions which become otherwise necessary.
Step 2: Testing Tools
Once the outsourced software development team starts working testing of what is produced becomes the most important task. The Quality Assurance needs to stay on top of the development process to make sure that the development is correctly aligned with the requirements. Gantt and/or waterfall charts should be used to structure the development process into easy to follow steps. (the sprints). Your outsourcing partner will have a dedicated QA team (Quality Assurance). However, you or the person tasked with supervising the development will need to make sure that testing is done in accordance with the progress the developers make. It goes without saying, testing should never be done on the live app...a dedicated testing environment is something your outsourcing partner should have set up for the entire development process.
Step 3: Timelines
Besides the quality of the product timeliness of the development effort should be your second most important priority. You want your development effort to stay on track. As such it is vital that prior to development the estimated time and allocation of resources is done. Reputable outsourcers will provide detailed estimates as to how long the development of certain milestones (broken into sprints) will take. By tracking actual hours spent versus the estimate you will be able to easily ascertain if the project is on schedule. Reputable software development firms will have that process down by using specific project management software which makes them accountable based upon the hours pent versus a prior estimate.
Step 4: Consistent Feedback
It goes without saying...your outsourcing partner needs to know what you think. You need to regularly review how the software works and test it. Based upon your testing you need to provide feedback as to what features are to be amended and changed. It is much easier to change requirements early on while the particular feature is still under development. If you do not have the time to engage in regular testing assign the task to someone else and make them responsible to provide the needed feedback.
Step 5: Solicit Advise From Your Outsourcing Partner
You might have very specific ideas as to what the software needs to do. However, often times the outsourcing provider might have some very valuable ideas as to how to build a "better mousetrap". Technology moves at rapid speeds and there is a pretty good chance that your outsourcing provider has a good idea of how to improve upon desired functionality without adding much to the development effort. By cooperating and soliciting feedback throughout the process you will end up with a better product; without necessarily making it more expensive.
Step 6: Test After It Is All Done
There is nothing more disruptive then having a new software release out with your customers and/or staff and then realizing that there is a problem. It is never good to roll back a software release. The problem might be with the functionality or feature or with platform compatibility. Therefor you will need to make sure that once you have the final product ready to go that it is performing as required and that it works on the platforms your business needs to support. (various browsers and operating systems, desktops, tablets and phones). The above might seem trivial...but I have personally encountered software releases where quite a few remote team members of a customer were still working on XP and Vista even though the requirements were to be compatible with Windows 7 and up. Proper beta testing can avoid disruption in business processes prior to making the software operational.
Supervising outsourced software development is easier than people often times think. By following the steps outlined above there is a pretty good chance that your project will go off without a hitch.
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!
Showing posts with label Software outsourcing. Show all posts
Showing posts with label Software outsourcing. Show all posts
Delivery Centers Are Becoming Popular in Latin America for IT Companies...Here is why
One of the issues with offshore software development is always the delivery. Development talent (especially high level) in Asia is not necessarily keen to stay up overnight to supervise the delivery of software. The back and forth required makes it a time consuming task and working on the other side of the clock makes it an unattractive job for talent in Asia.
Conversely...US personnel involved in the delivery has limited desire, for the most part, to work well into the night to ensure a smooth delivery.
One solution to the problem which has been gaining popularity by globally operating IT organization is establishing delivery centers in South/Latin America. (LATAM) Latin America is considered "Nearshore"...as such it offers some of the advantages of a true offshore operation while at the same time eliminating the disadvantages of offshore providers.
The most commonly cited advantages cited as a reason to establish an Nearshore Delivery Center are as follows:
Conversely...US personnel involved in the delivery has limited desire, for the most part, to work well into the night to ensure a smooth delivery.
One solution to the problem which has been gaining popularity by globally operating IT organization is establishing delivery centers in South/Latin America. (LATAM) Latin America is considered "Nearshore"...as such it offers some of the advantages of a true offshore operation while at the same time eliminating the disadvantages of offshore providers.
The most commonly cited advantages cited as a reason to establish an Nearshore Delivery Center are as follows:
- Cost Arbitrage: LATAM does offer substantial cost savings over US based operations
- Quality IT Talent: Depending upon in which country the delivery center is established Quality IT personnel are easy to come by. The education system is generally considered good and a steady flow of new graduates in Computer and Science related fields ensures that new supply is available.
- Close Alignment in Time Zones: Working throughout the US business day is a breeze. Most LATAM countries are only 1 or 2 hours off CST time...as such the work schedules are aligned.
- Good Business Climate: Generally speaking the LATAM countries which are a natural fit for a Development Center offer a good business climate. Countries like Mexico, Costa Rica, Brazil, Colombia and Argentina are well established democracies with little political risk.
- Easy Travel: Most of the popular LATAM destinations centers are easy to reach via plane from the US.
- Language Capabilities: The dominant languages in the LATAM countries are Spanish, Portuguese and English. Therefor language barriers are usually limited and can be overcome relatively easy.
- Access to Local Markets: Some of the LATAM countries (Brazil) have rather draconian taxes and laws restricting the import of goods and services. Establishing a local delivery center (beachhead) often times circumvents these rather restrictive policies, thus enabling globally operating companies to access local markets more easily.
Executives in charge of ITO have been looking at Asia for the longest time as the solutions provider for all things IT related. A more balanced view has been emerging which suggests that certain aspects of the ITO value chain can be better accomplished by mixing Offshore and Nearshore solutions into one comprehensive package.
It might be to early to tell...but there is a good chance that LATAM will become the go to destination for Delivery Centers...the advantages are striking and might justify the higher expense (compared to offshore).
Assuming favorable currency rates and no political changes it seems safe to assume that the trend of setting up delivery centers in LATAM countries will continue.
How To Manage Your Outsourced Software Project....A Step By Step Guide
For corporations which are new to the concept of outsourcing software development the mechanics of how to properly supervise and structure the dialogue between the onshore and offshore team might seem a bit intimidating at first.
2.
Collaboration between the members of an In House team is rather simple...in most cases it is as simple as walking over to someone'd desk or just picking up the phone.
It is a bit more tricky (or so it seems) with an offshore team. Not only are the members of the team separated by 1000's of miles..they also often times are working on the other side of the clock with a limited ability to overlap work hours.
Consequently the question of how to collaborate is rather valid.
The single most importation item to collaborate a software development is the use of specific collaboration software which is used to supervise and structure the entire process. Using a proper coloration tool (assuming it is being used by the onshore and offshore team) will do wonders for the development.
There are plenty of software solutions out there which offer collaboration, some of them are even available free of charge. We use Active Collab for all of developments but there are plenty of other solutions available. (https://www.activecollab.com/)
A Software like Active Collab offers the ability to properly organize Task Management, Team Collaboration, Time Tracking and even the corresponding invoicing.
One important thing to remember...Active Collab or its peers is not a tool to control development. It is not being used to verify the work is actually being done. As such the users of the software are relying on proper reporting of hours worked on a voluntary basis.
There are specific tools available to supervise that alleged work is truly being done. I will address that in a separate blog post. (Hive Desk)
I have included some screenshots which displays some of the functionality of Active Collab.
A great way to gain a good understanding of what a software like Active Collab can do for you is to subscribe to a trial. Almost all of the vendors offer a free trial.
In order to provide you with a better understanding of some of the functionalities I have included five screenshots with explanations as to what is shown.
1.
A snapshot of a task list is shown below. Developers work off the task list to move through the process. Typically each specific development step is assigned to a developer as part of the task list.
2.
Once the task list is created the developers work off the task list and report their progress on the update page.
3.
Separately the developer report the hours worked on each task. Assigned hours to a task and hours actually spent can then easily be reconciled
.
4.
The developers report their progress and raise questions or issues as part of the daily discussion. The daily discussion is typically used to address technical issues.
5.
The General Discussion area is where Top Level Discussion are being held. Management will use that to check in on the overall status of the development.
How To Close The Productivity Gap When Outsourcing Web Design Work ...A Real Life Example
It is well known that outsourcing does have some disadvantages. One of the biggest ones every user of outsourcing services has to battle with is the issue of productivity gap vis a vis the onshore worker.
Experienced users of outsourcing services know that the productivity gap is real...and they have some specific strategies to make sure that it is as small as as possible in the beginning.
Over time and with proper integration of the outsourced worker the productivity gap will shrink...and often times the offshore worker might become more productive than the onshore worker.
Below is the real life experience of one of my customers. The customer is a web development and design firm. When the company needed to increase headcount they decided to hire 2 web developers overseas and integrate them into their team of onshore web developers.
With our help the company devised a specific, 6 Step plan to integrate the developers.
Step 1:
The company assigned each one of the developers to a designer in their US office. The offshore designer were deemed junior to the onshore designers. In the event of vacation and/or sickness the onshore developers/designers would cover for each other and supervise the offshore designers. Importantly though...the offshore designers were not supposed to cover for each other.
Step 2:
Daily Skype Meetings. A schedule was set whereby each design team would meet up via skype once a day. In the beginning the meetings primarily served as a "get to know each other" opportunity. It was deemed important that a team spirit was created among the onshore and offshore designer and in order to foster it the Skype meets were deemed mandatory.
Step 3
It was decided that collaborative tools were to be used instead of emails. Specifically it was agreed that skype was going to be used for screensharing. Active Collab ( https://www.activecollab.com/) was to be used for the submission , feedback and related questions regarding any project assigned to the offshore designers.
Step 4
In order to enable the President to verify that the offshore designers were in fact working and not just playing video games both offshore workers were put on Hivedesk (http://www.hivedesk.com/). By using Hivedesk any perception that the offshore workers might not dedicate the hours needed towards the client were eliminated. It was agreed that the offshore workers were on a 9 hour workday with a one hour flex break.
Step 5
In order to properly integrate the offshore workers the company decided on a set course of action as to what the offshore designers were supposed to do. It was agreed that the offshore designers were going to build only webpages after the initial design had been approved by the client. The senior designer/developer (onshore) was responsible for the home page design and built. As such the offshore worker had only limited ability to bring their own design ideas into any project. The site tree and structure was already there and thus the offshore workers were to finish out the site after the approval of design and site structure.
Step 6
All communication between the client and the company was to be handled by the onshore developer/designer. The client would not communicate with the offshore worker.
Results/Conclusion:
The steps described above might seem simple in itself. The end result though was that a well functioning team developed between the onshore and offshore developer.
Within a few weeks the offshore designer became attune to the thinking of the onshore team leader and started to adopt and instinctively follow the design ideas of the team leader without having to engage in extensive back and forth.
The relationship stated to click, enabling the team leader to increase the level of responsibilities assigned to the offshore designer.
The company realized significant financial benefits and increased the size of the offshore team to 6 designers within one year.
Experienced users of outsourcing services know that the productivity gap is real...and they have some specific strategies to make sure that it is as small as as possible in the beginning.
Over time and with proper integration of the outsourced worker the productivity gap will shrink...and often times the offshore worker might become more productive than the onshore worker.
Below is the real life experience of one of my customers. The customer is a web development and design firm. When the company needed to increase headcount they decided to hire 2 web developers overseas and integrate them into their team of onshore web developers.
With our help the company devised a specific, 6 Step plan to integrate the developers.
Step 1:
The company assigned each one of the developers to a designer in their US office. The offshore designer were deemed junior to the onshore designers. In the event of vacation and/or sickness the onshore developers/designers would cover for each other and supervise the offshore designers. Importantly though...the offshore designers were not supposed to cover for each other.
Step 2:
Daily Skype Meetings. A schedule was set whereby each design team would meet up via skype once a day. In the beginning the meetings primarily served as a "get to know each other" opportunity. It was deemed important that a team spirit was created among the onshore and offshore designer and in order to foster it the Skype meets were deemed mandatory.
Step 3
It was decided that collaborative tools were to be used instead of emails. Specifically it was agreed that skype was going to be used for screensharing. Active Collab ( https://www.activecollab.com/) was to be used for the submission , feedback and related questions regarding any project assigned to the offshore designers.
Step 4
In order to enable the President to verify that the offshore designers were in fact working and not just playing video games both offshore workers were put on Hivedesk (http://www.hivedesk.com/). By using Hivedesk any perception that the offshore workers might not dedicate the hours needed towards the client were eliminated. It was agreed that the offshore workers were on a 9 hour workday with a one hour flex break.
Step 5
In order to properly integrate the offshore workers the company decided on a set course of action as to what the offshore designers were supposed to do. It was agreed that the offshore designers were going to build only webpages after the initial design had been approved by the client. The senior designer/developer (onshore) was responsible for the home page design and built. As such the offshore worker had only limited ability to bring their own design ideas into any project. The site tree and structure was already there and thus the offshore workers were to finish out the site after the approval of design and site structure.
Step 6
All communication between the client and the company was to be handled by the onshore developer/designer. The client would not communicate with the offshore worker.
Results/Conclusion:
The steps described above might seem simple in itself. The end result though was that a well functioning team developed between the onshore and offshore developer.
Within a few weeks the offshore designer became attune to the thinking of the onshore team leader and started to adopt and instinctively follow the design ideas of the team leader without having to engage in extensive back and forth.
The relationship stated to click, enabling the team leader to increase the level of responsibilities assigned to the offshore designer.
The company realized significant financial benefits and increased the size of the offshore team to 6 designers within one year.
Should You Ever Visit Your Outsourcing Provider ?...Here Is What You Need To Consider
Big corporations with budgets of millions of dollars do it all the time..they visit their outsourcing provider...wherever they are located. Often times, and if the budget warrants it, they actually have a representative embedded with the outsourcing team..or at the very least have a local rep which looks after the relationship.
There are significant advantages to be realized...which is the reason why they do it.
The question I get asked sometimes if smaller scale projects are worth while to warrant a visit.
The short answer it "Sometimes"..and it depends.
There are a few things which go into the evaluation of whether or not a visit can make a difference.
That travel in almost every case leads to second or even third world countries and cities which require connecting flights. As such the decision to travel requires a more significant investment as it relates to time and money.
Below are some of the considerations a small business owner with a smaller project might want to consider to decide if the trip is worth his/her time.
Consideration 1
How long is the estimated time to completion of your project?
If the project is estimated to be completed within 6 weeks even a substantial overrun in time to completion might no be material to your business. If on the other hand estimated time to completion is 8 months..then a visit might make it more likely that the project will be on time.
Consideration 2
How expensive is your project...and are you responsible for cost overruns ?
This might be the cardinal question...if your project is only 5k...even a 40 % cost overrun amounts to only a 2 k difference. From a financial cost/benefit analysis it might make no sense to visit. If on the other hand the project is spec'ed out at 100 k...a 40 % increase would add an additional 40 k in expenses. Avoiding the additional expense might make it worth your time to go.
Consideration 3
When should you go and visit?
Assuming you have a time to completion numbered in months and a budget which, if there were a significant cost overrun, would make it economically feasible to plan a visit...you need to decide when you should visit. As a general rule..the earlier in the process you visit ..the better it will be. Your outsourced software development team will not get a lot of client visits. If you visit them you will l leave a definite mark on their thinking and they will be much more attentive to your needs for the remainder of the project.
Consideration 4
Will my visit make a difference as it relates to schedule and costs?
The short answer is unequivocally ...YES. It will. I can assure you that there is a pretty good chance that you might be the only client visiting the developers that year. If you buy them a meal, perhaps some drinks...you can be assured that there will be a lot of goodwill created. The Goodwill will translate into more diligence as to your project, saving you time and money.
Consideration 5
Do you have the time to go and spend at least a week with the team?
This consideration is something only you can decide. f you do have the time and like to travel to areas / cities which are usually not mainstream travel destinations...it might be a good idea.
Consideration 6
Does it make financial sense to travel?
I briefly touched on it in consideration 2. There is obviously little point in spending 5k on travel if the total project is 5k. As such there is a relationship between travel expenses and expected benefits. There is though another way of looking at it...and a lot of companies are utilizing that strategy. An alternative way to look at the projects costs is to include travel expenses upfront in your calculation. The combined project cost and travel expenses then make up the Total Project Costs. If the total Project Cost is sufficiently below what onshore development will cost you..then u have found the economic justification for travelling to your Outsourcing Provider.
At the end of the day the decision to travel is an individual one every business owner needs to decide for him/herself. I can attest to the fact that it will be beneficial.
Some people like to travel...and some do not. I have a client which always makes it a point to travel overseas to visit the software development team. For him it is a vacation in disguise, fully tax deductible.
That reasoning might not appeal to other business owners...but if you do have the time and like to explore different countries..this is certainly one way to make it tax deductible. And this is often times all the motivation a small business owners need.
Onshore, Nearshore or Offshore Software Development...here are some pros and cons
The day has come where you decide to outsource a software development project. There might be multiple reasons why but you now face the task of how to do it and get it done.
For someone who has never outsourced software development this might seem like a rather daunting task. After all...how do you get from idea to conclusion without having major hiccups on the way.
Business is all about proper execution of strategy...and you should treat your outsourcing approach the same way.
One of the first decisions has to be the geograpic which decision as to what type of outsourcing you want to pursue. There are 3 different categories of outsourcing available to you. Each comes with positives and negatives associated with their relative geographic area.
The table below provides some insight into some of the considerations you may want to entertain. The point of vies used is from a US perspective.
If you are based in Europe the geographic point of view provided below are obviously somewhat different.
At the end of the day it really comes down to what the company is prepared to pay...and the trade off the company is prepared to accept if it decides to pursue a lower cost provider.
There is little doubt that onshore development is the easiest one to manage. The downside is of course that the expense is by far the highest.
Conversely, true offshore development in Asia is usually the cheapest. A lot of corporations are comfortable with offshore development and are prepared to accept some of the difficulties working with a company on the other side of the clock.
For someone who has never outsourced software development this might seem like a rather daunting task. After all...how do you get from idea to conclusion without having major hiccups on the way.
Business is all about proper execution of strategy...and you should treat your outsourcing approach the same way.
One of the first decisions has to be the geograpic which decision as to what type of outsourcing you want to pursue. There are 3 different categories of outsourcing available to you. Each comes with positives and negatives associated with their relative geographic area.
The table below provides some insight into some of the considerations you may want to entertain. The point of vies used is from a US perspective.
If you are based in Europe the geographic point of view provided below are obviously somewhat different.
Definition
|
The Pros
|
The Cons
|
Onshore
Any development
partner which resides in your country is typically considered an outsourced
onshore development
|
No cultural
issues which can lead to misunderstandings
Same time zone,
cooperation during the day is a breeze
Easy to visit
the development partner, domestic flight, train or car trip
Consequently it
is easy to supervise
|
Onshore development is the most expensive. Reputable firms easily charge well above 150 US-$ for contract work
Onshore software
development firms frequently outsource their work to offshore providers. As a
client you might never learn about it. Hence you might overpay.
In some cases
onshore firms are very much tied into business networks which are closely
aligned with your business. Ideas or concepts you deem as confidential are
leaking to other companies in your space. This can happen through staff
attrition or related development work
|
Nearshore
A company which
resides in neighboring countries with a time zone difference of perhaps up to 4 or 5 hours is usually considered
Nearshore. Examples are South America, Canada, Jamaica
|
The provider is
removed but you still have between 4 to 6 hours of overlap in the time zones,
enabling you to efficiently cooperate throughout the day.
Pricing will be
significantly cheaper than onshore pricing.
There is a
certain cultural alignment. Developers in nations mentioned as nearshore
providers are used to the US way of thinking.
|
Nearshore development is not a radical solution. It is more expensive than offshore development as such a lot of the advantages are mitigated.
Nearshore
provider are not easy to reach. Travel times are frequently more than 8 or 10
hours and flight is the only option.
Nearshore
providers might have significant language barriers.
|
Offshore
Offshore
Development is usually associated with development done on other continents
with significant time zone differences. Examples are Asia and Europe
|
Offshore
providers are usually the cheapest by a wide margin.
Not unusual to
find development companies with big product portfolios and a lot of related
work experience.
Because true
offshore development companies tend to be bigger in size they usually have
defined processes to manage a relationship
|
Offshore Development centers reside on the other side of the clock. Time zone differences are usually 8 hours or more.
The command of
the English language is often times average. Only Project Managers and Senior
Developers speak good English.
Work hours
usually only overlap up to 4 hours.
|
At the end of the day it really comes down to what the company is prepared to pay...and the trade off the company is prepared to accept if it decides to pursue a lower cost provider.
There is little doubt that onshore development is the easiest one to manage. The downside is of course that the expense is by far the highest.
Conversely, true offshore development in Asia is usually the cheapest. A lot of corporations are comfortable with offshore development and are prepared to accept some of the difficulties working with a company on the other side of the clock.
How Many Jobs Will The Outsourcing Industry Loose To Robots ?...Here Is An Educated Guess
The rise of robots will undoubtedly lead to the loss of jobs within the outsourcing industry. Everyone knows it...but no one has been able to come up with a legitimate number as to what the total might be.
For the first time though there is a number which can be quoted with some authority. HFS Research, a US based Analyst for the global services sector, tried to quantify job losses associated with the rise of the robots and automation. It came up with an estimate of about 1.4 Million in job losses by 2021.
The job losses are concentrated in the area of low skilled jobs, those which are highly repetitive and do not require a formalized education.
The total numbers have already been disputed by Nasscom (India's Industry Association For Software Services). It points out that there will be a huge demand for higher talent to get the automation and robotic processes going which effectively will partially offset the job losses.
It remains to be seen what the final numbers will be...but at the very least the BPO/Outsourcing industry has been put on notice that there are challenges ahead.
For the first time though there is a number which can be quoted with some authority. HFS Research, a US based Analyst for the global services sector, tried to quantify job losses associated with the rise of the robots and automation. It came up with an estimate of about 1.4 Million in job losses by 2021.
The job losses are concentrated in the area of low skilled jobs, those which are highly repetitive and do not require a formalized education.
The total numbers have already been disputed by Nasscom (India's Industry Association For Software Services). It points out that there will be a huge demand for higher talent to get the automation and robotic processes going which effectively will partially offset the job losses.
It remains to be seen what the final numbers will be...but at the very least the BPO/Outsourcing industry has been put on notice that there are challenges ahead.
Romania Is The European Hotspot For Fin Tech Development
Anyone who has ever had to supervise significant FinTech Development knows the problems associated with it. FinTech development requires a rather unique combination of skill sets.
Not only does the development team need to be up to date on the latest technologies..it also needs a pretty good understanding of financial markets and the supporting logic behind it.
What makes FinTech development so unique is a requirement for very efficient (=fast) code. Often times FinTech applications are competing for 1/1000th of a second..so any unnecessary hicks ups in the code render the software at a competitive disadvantage. The use the latest and most efficient languages and language environments are a true necessity.
On top of that a lot of the applications requires a pretty good understanding of the algorithms supporting the FinTech development. There is a rather steep learning curve associated with the proper use of the formulas required to make an application succeed.
That combination is not always easy to come by. However...Romania seems to be specifically targeting those skill sets to get its software development industry going.
It clearly seems to be working, a bunch of European financial powerhouses have set up shop in Romania.
Their reasoning being that they not only find good local development talent, the talent is also well educated as it relates to the financial markets. The local university offers a combined Computer Science, Math , Economics curriculum which makes their graduates "prime" for the challenges encountered in FinTech Development.
The total numbers of developers available in Romania is of course minimal compared to countries like India, Phillipines or China.
Regardless though, it is an interesting niche solution for specialized niche development.
Not only does the development team need to be up to date on the latest technologies..it also needs a pretty good understanding of financial markets and the supporting logic behind it.
What makes FinTech development so unique is a requirement for very efficient (=fast) code. Often times FinTech applications are competing for 1/1000th of a second..so any unnecessary hicks ups in the code render the software at a competitive disadvantage. The use the latest and most efficient languages and language environments are a true necessity.
On top of that a lot of the applications requires a pretty good understanding of the algorithms supporting the FinTech development. There is a rather steep learning curve associated with the proper use of the formulas required to make an application succeed.
That combination is not always easy to come by. However...Romania seems to be specifically targeting those skill sets to get its software development industry going.
It clearly seems to be working, a bunch of European financial powerhouses have set up shop in Romania.
Their reasoning being that they not only find good local development talent, the talent is also well educated as it relates to the financial markets. The local university offers a combined Computer Science, Math , Economics curriculum which makes their graduates "prime" for the challenges encountered in FinTech Development.
The total numbers of developers available in Romania is of course minimal compared to countries like India, Phillipines or China.
Regardless though, it is an interesting niche solution for specialized niche development.
Part 2...How To Safeguard Your Intellectual Property When Outsourcing Software Development
In my previous blog post I talked about the challenges clients face when picking an outsourcing vendor. (see here for the blog post Part 1)
The problem of how to ensure that the Intellectual Property is safeguarded is less of a problem for bigger companies dealing with bigger outsourcing providers. There is a certain advantage to be gained by going for size...and I vouch to say that bigger, in most cases, is better when it comes to the protection of a companies IP.
For smaller companies looking to get a limited project done though the bigger outsourcing vendors are not really an option. Most of the bigger and reputable BPO vendors won't even enter into a relationship unless the annual revenue out of the contract exceeds at least 500 k.
As such a lot of domestic companies are usually stuck with one of two scenarios:
Either develop onshore and pay onshore pricing or develop offshore and take all the risks associated with it. Unfortunately either one of those options are not ideal.
There is though a third option available to flexible outsourcing vendors and their clients which offers the benefit of outsourced pricing while offering maximum legal protection and avenue for recourse to the company.
We offer our clients to contract our services through a domestic corporation. (US based). A jurisdiction is chosen which is satisfactory to the client. Additionally, and only if the client desires, we do offer arbitration instead of court litigation. (we ordinarily use JAMS).
The key point is that the US company our client contracts with carries an errors and omissions policy with an insured value on every claim well in excess of any conceivable damages.
We find that clients who are concerned about the reach of law and the ability to enforce a legal claim are more than happy to pay the small premium in rates over our offshore/Non Us pricing to gain the piece of mind needed.
No one buys insurance on a vehicle expecting it to be used. In the unfortunate event that is has to be used it will remove financial damages and offers a needed comfort level.
An outsourcing partner which offers a strong errors and omissions policy should be looked at the same way. No one expects it to be used (or wants it)...but in the unfortunate event that is needs to be used it offers a mechanism to get properly compensated.
The problem of how to ensure that the Intellectual Property is safeguarded is less of a problem for bigger companies dealing with bigger outsourcing providers. There is a certain advantage to be gained by going for size...and I vouch to say that bigger, in most cases, is better when it comes to the protection of a companies IP.
For smaller companies looking to get a limited project done though the bigger outsourcing vendors are not really an option. Most of the bigger and reputable BPO vendors won't even enter into a relationship unless the annual revenue out of the contract exceeds at least 500 k.
As such a lot of domestic companies are usually stuck with one of two scenarios:
Either develop onshore and pay onshore pricing or develop offshore and take all the risks associated with it. Unfortunately either one of those options are not ideal.
There is though a third option available to flexible outsourcing vendors and their clients which offers the benefit of outsourced pricing while offering maximum legal protection and avenue for recourse to the company.
We offer our clients to contract our services through a domestic corporation. (US based). A jurisdiction is chosen which is satisfactory to the client. Additionally, and only if the client desires, we do offer arbitration instead of court litigation. (we ordinarily use JAMS).
The key point is that the US company our client contracts with carries an errors and omissions policy with an insured value on every claim well in excess of any conceivable damages.
We find that clients who are concerned about the reach of law and the ability to enforce a legal claim are more than happy to pay the small premium in rates over our offshore/Non Us pricing to gain the piece of mind needed.
No one buys insurance on a vehicle expecting it to be used. In the unfortunate event that is has to be used it will remove financial damages and offers a needed comfort level.
An outsourcing partner which offers a strong errors and omissions policy should be looked at the same way. No one expects it to be used (or wants it)...but in the unfortunate event that is needs to be used it offers a mechanism to get properly compensated.
Part 1...How To Safeguard Your Intellectual Property When Outsourcing...And Which Country Is The Best For Your Outsourced Software Development
It is often times an afterthought...but it really should be a huge part of your evaluation when you assess whether or not to outsource your next software development project.
I am talking about Intellectual Property Theft...and what you can do about it.
Anyone who has been in the outsourcing business as a vendor has seen it before.
A potential client has huge reservations because he had tried outsourcing before. He had some very bad experiences. The software application written on the client's behalf was reused or resold or simply not delivered. The potential client had simply been cheated.
Outsourcing Software development typically means dealing with a company located in countries like India, China, Malaysia, Mexico, Indonesia, Thailand, Philippines, Brazil, Bulgaria or Egypt,...just to name the most popular ones.
The question to ask is what safeguards can be put in place to make sure that no Intellectual Property Theft occurs.
The simple answer is that there is very little which can be done. A vendor who resides on the other side of the planet in a country where intellectual property protection rights are either non existing, weak or simply not being enforced can steal from a client with relative impunity.
Of course..most vendors are reliable and can be trusted. yet...the question remains...what can a decision maker do to safeguard the Intellectual Property he is about to hand over or have developed ?
One good place to start is the United States TR Special 301 list. This list is annually compiled by the US congress and list all the countries which are known for Intellectual Property Theft. Inclusion on the list is because of weak domestic laws to safeguard such Intellectual Property and/or the failure of the judicial and executive branch to enforce such laws.
In short...the list shows all the countries known to be as potential cheaters, In those countries the theft of Intellectual Property is frequent and there is little or no recourse available to the company.
What is perhaps most noteworthy about the list is what is not included. The only country among the traditional outsourcing countries which is not included are the Philippines.
The Philippines earned its exclusion from the list by having Intellectual Property laws modeled after US laws and a legal system which is independent enough that legal claims are fairly adjudicated.
Another key advantage the Philippines offer are that the general mindset of the population is as such that they are law abiding. Crime rates are low and there is a general respect for the other person's property.
I am obviously generalizing here...not every vendor located in China, India or Russia is bad..and not every vendor located in the Philippines should be trusted without exercising due diligence.
It is also worth while to note that bigger corporations who have the legal muscle to institute claims all over the world are less likely to get cheated than a smaller company (relatively speaking) which lacks the will and / or the money to go the litigation route.
I am talking about Intellectual Property Theft...and what you can do about it.
Anyone who has been in the outsourcing business as a vendor has seen it before.
A potential client has huge reservations because he had tried outsourcing before. He had some very bad experiences. The software application written on the client's behalf was reused or resold or simply not delivered. The potential client had simply been cheated.
Outsourcing Software development typically means dealing with a company located in countries like India, China, Malaysia, Mexico, Indonesia, Thailand, Philippines, Brazil, Bulgaria or Egypt,...just to name the most popular ones.
The question to ask is what safeguards can be put in place to make sure that no Intellectual Property Theft occurs.
The simple answer is that there is very little which can be done. A vendor who resides on the other side of the planet in a country where intellectual property protection rights are either non existing, weak or simply not being enforced can steal from a client with relative impunity.
Of course..most vendors are reliable and can be trusted. yet...the question remains...what can a decision maker do to safeguard the Intellectual Property he is about to hand over or have developed ?
One good place to start is the United States TR Special 301 list. This list is annually compiled by the US congress and list all the countries which are known for Intellectual Property Theft. Inclusion on the list is because of weak domestic laws to safeguard such Intellectual Property and/or the failure of the judicial and executive branch to enforce such laws.
In short...the list shows all the countries known to be as potential cheaters, In those countries the theft of Intellectual Property is frequent and there is little or no recourse available to the company.
What is perhaps most noteworthy about the list is what is not included. The only country among the traditional outsourcing countries which is not included are the Philippines.
The Philippines earned its exclusion from the list by having Intellectual Property laws modeled after US laws and a legal system which is independent enough that legal claims are fairly adjudicated.
Another key advantage the Philippines offer are that the general mindset of the population is as such that they are law abiding. Crime rates are low and there is a general respect for the other person's property.
I am obviously generalizing here...not every vendor located in China, India or Russia is bad..and not every vendor located in the Philippines should be trusted without exercising due diligence.
It is also worth while to note that bigger corporations who have the legal muscle to institute claims all over the world are less likely to get cheated than a smaller company (relatively speaking) which lacks the will and / or the money to go the litigation route.
How One Company Overspent On Its Outsourcing By 500 % ...The Dirty Truth Every CEO Should Know
Quite a while ago ago I talked to a company which was looking to kick off a bigger software project. They never went ahead with it and it was just another deal which did not bear fruit. Nothing unusual about it.
What makes it newsworthy though is that the CEO of the company reached out a few months ago and asked if we were to able to pick up the maintenance and service for the software they had developed.
Obviously a pretty easy thing to do. We priced it out, arranged for the delivery of the software (source code) and got to work. As is customary in those situations we had a few developers read through the code with the goal to familiarize ourselves with the code and the functionality.
As part of the code review we found some developer comments (once again...nothing unusual). What made it a bit unusual was that burred in the code were clear references as to which company had actually written the code.
This is where things got interesting. Below is a quasi recap of the the conversation I had with the CEO, our client.
Steve: So....when XYZ (company name embedded in the code) developed the API they...
CEO Interrupts me: Who is XYZ ?
Steve: The guys who developed the code
CEO: No..they aren't
Steve....(pause...does not say anything)
CEO: What makes you say that ?
Steve: Well..there are clear references in the code that they are the author of the software you delivered
CEO: What ?...I don't understand...we had it written by XXX
The CEO (our client) then took it upon himself to get to the bottom of the issue. Did not take him to long to find out as to what had happened.
The company which he had contracted with to develop the software had outsourced the entire development to a provider in India.
The CEO was rather flabbergasted that this was possible. He had paid premium pricing (his words) assuming that the product was going to be developed onshore in the US. Doing the math by using our rates he figured he had spent about 250k more than what he should have paid.
Obviously 250k can be a lot or very little money for a corporation. In this case the company is privately owned and the CEO happens to be the majority shareholder. Company is doing well...so money was (or is) not the issue.
The issue for the CEO was simply that he felt he had been taken advantage off...led to believe that it was an onshore development when in reality all of the work (or vast majority) was done offshore.
And this brings us to the dirty truth every CEO should know.
A lot of software development billed at domestic developer pricing is parsed out to providers offshore.
Decision makers should be aware that not in every case what is sold as a domestic development is actually developed domestically.
There is obviously a certain added comfort level for a US company to deal with a US based software development company. The CEO/Decision Maker might feel more comfortable...but the truth of the matter is that the company might not be exactly getting what it has paid for.
What makes it newsworthy though is that the CEO of the company reached out a few months ago and asked if we were to able to pick up the maintenance and service for the software they had developed.
Obviously a pretty easy thing to do. We priced it out, arranged for the delivery of the software (source code) and got to work. As is customary in those situations we had a few developers read through the code with the goal to familiarize ourselves with the code and the functionality.
As part of the code review we found some developer comments (once again...nothing unusual). What made it a bit unusual was that burred in the code were clear references as to which company had actually written the code.
This is where things got interesting. Below is a quasi recap of the the conversation I had with the CEO, our client.
Steve: So....when XYZ (company name embedded in the code) developed the API they...
CEO Interrupts me: Who is XYZ ?
Steve: The guys who developed the code
CEO: No..they aren't
Steve....(pause...does not say anything)
CEO: What makes you say that ?
Steve: Well..there are clear references in the code that they are the author of the software you delivered
CEO: What ?...I don't understand...we had it written by XXX
The CEO (our client) then took it upon himself to get to the bottom of the issue. Did not take him to long to find out as to what had happened.
The company which he had contracted with to develop the software had outsourced the entire development to a provider in India.
The CEO was rather flabbergasted that this was possible. He had paid premium pricing (his words) assuming that the product was going to be developed onshore in the US. Doing the math by using our rates he figured he had spent about 250k more than what he should have paid.
Obviously 250k can be a lot or very little money for a corporation. In this case the company is privately owned and the CEO happens to be the majority shareholder. Company is doing well...so money was (or is) not the issue.
The issue for the CEO was simply that he felt he had been taken advantage off...led to believe that it was an onshore development when in reality all of the work (or vast majority) was done offshore.
And this brings us to the dirty truth every CEO should know.
A lot of software development billed at domestic developer pricing is parsed out to providers offshore.
Decision makers should be aware that not in every case what is sold as a domestic development is actually developed domestically.
There is obviously a certain added comfort level for a US company to deal with a US based software development company. The CEO/Decision Maker might feel more comfortable...but the truth of the matter is that the company might not be exactly getting what it has paid for.
India Is Still The 800 Pound Gorilla In IT Outsourcing...
India might have lost its leadership in call centers to the Philippines...but it certainly does not show any signs of slowing down when it comes to ITO (IT Outsourcing).
There is certainly strength in raw numbers. With a population of almost a Billion people India is basically the only place in the world where a major company can set up with the goal to hire a 1000 software engineers and not running into problems as to pricing and general availability of talent.
The building of technology centers where a few thousand engineers can be supervised under one roof has always been the one advantage none of India' competitors in the global outsourcing world can match.
India's National Association of Software and Service Companies (Nasscom) just announced that the sector increased employment by about 230,000 in 2015. Total employment for the sector now stands at about 35 Million.
By their own estimate the Indian BPM sector (Business Process Management) has now captured approximately 56 % of the total global market for IT related outsourcing services.
These are huge numbers. If you consider that the entire population of the Philippines is only about 98 million and India employs just in ITO 35 Million...it really shows that there is strength in raw numbers.
Of course, only few companies really have a need to hire hundred's of developers and for most companies there are other places in the world to get their ITO done as good or perhaps even better than what India has to offer.
At the end of the day it only matters what your own outsourcing team is capable off...as such there is really no strategic advantage outside of sheer numbers India can offer.
Never the less though...the numbers are impressive.
India's Nasscom Releases 2015 Revenue And Market Share Numbers
There is certainly strength in raw numbers. With a population of almost a Billion people India is basically the only place in the world where a major company can set up with the goal to hire a 1000 software engineers and not running into problems as to pricing and general availability of talent.
The building of technology centers where a few thousand engineers can be supervised under one roof has always been the one advantage none of India' competitors in the global outsourcing world can match.
India's National Association of Software and Service Companies (Nasscom) just announced that the sector increased employment by about 230,000 in 2015. Total employment for the sector now stands at about 35 Million.
By their own estimate the Indian BPM sector (Business Process Management) has now captured approximately 56 % of the total global market for IT related outsourcing services.
These are huge numbers. If you consider that the entire population of the Philippines is only about 98 million and India employs just in ITO 35 Million...it really shows that there is strength in raw numbers.
Of course, only few companies really have a need to hire hundred's of developers and for most companies there are other places in the world to get their ITO done as good or perhaps even better than what India has to offer.
At the end of the day it only matters what your own outsourcing team is capable off...as such there is really no strategic advantage outside of sheer numbers India can offer.
Never the less though...the numbers are impressive.
India's Nasscom Releases 2015 Revenue And Market Share Numbers
Is Your Outsourcing Operation Bloated ?..Probably Yes...
Most companies enter into outsourcing relationships on a FTE basis. (Full Time Equivalent). The engagements are not project based but rather utilize a Lease To Hire model. (LTH). The Lease to Hire model basically means that the company buys the use of personnel on a Full Time Basis.
Once the outsourcing team is established and commences its work the most relevant Key Performance Indicator being watched is utilization of the employee. There are various tools to measure the KPI's as it relates to the utilization rate of the employee. For call centers and customer service operations it is rather simple (time on phone. time on call), for software development there are auditing tools available to make sure that the developers do not "slouch".
However, one particular problem with outsourcing is that the outsourced operation is really good at the troubleshoot...but perhaps not so good at looking at the root of the problem as to why the troubleshoot happened in the first place.
Consequently faulty software or procedures tend to stay around much longer than they should. Everyone is content with resolving the trouble tickets but no one is looking how to change procedures or applications so that the trouble ticket does not happen anymore.
Of course..the very same operational characteristic can be found in a domestic business environment. What makes it more of an issue in an outsourced offshore environment is that it takes key management much longer to realize what is going on.
And this brings us to the "Bloat" your outsourcing operation might have accumulated. If you do not periodically (or better yet...have a constant quality improvement program) review the source of trouble tickets and scan for improvement to be made...you might have built up your outsourced team well above your actual operational needs if those issues were fixed.
Implementing a procedures which reviews the source of a trouble ticket and/or increase operational efficiency will result in less contacts needs by your customers. Reducing the point of contacts will then lead to reduced need of FTE employees...thus reducing the manpower bloat you might be experiencing.
Once the outsourcing team is established and commences its work the most relevant Key Performance Indicator being watched is utilization of the employee. There are various tools to measure the KPI's as it relates to the utilization rate of the employee. For call centers and customer service operations it is rather simple (time on phone. time on call), for software development there are auditing tools available to make sure that the developers do not "slouch".
However, one particular problem with outsourcing is that the outsourced operation is really good at the troubleshoot...but perhaps not so good at looking at the root of the problem as to why the troubleshoot happened in the first place.
Consequently faulty software or procedures tend to stay around much longer than they should. Everyone is content with resolving the trouble tickets but no one is looking how to change procedures or applications so that the trouble ticket does not happen anymore.
Of course..the very same operational characteristic can be found in a domestic business environment. What makes it more of an issue in an outsourced offshore environment is that it takes key management much longer to realize what is going on.
And this brings us to the "Bloat" your outsourcing operation might have accumulated. If you do not periodically (or better yet...have a constant quality improvement program) review the source of trouble tickets and scan for improvement to be made...you might have built up your outsourced team well above your actual operational needs if those issues were fixed.
Implementing a procedures which reviews the source of a trouble ticket and/or increase operational efficiency will result in less contacts needs by your customers. Reducing the point of contacts will then lead to reduced need of FTE employees...thus reducing the manpower bloat you might be experiencing.
The Dirty Truth - Your Outsourcing Team Might Be To Young ?
One issue I frequently discuss with corporations which have outsourcing relationships with other vendors is that they are often times not happy with the performance provided. There is not one single performance matrix which is leading corporations to that conclusion but rather this is often times an across the board assessment of the relationship. The attitude is that it works, albeit not great.
Some of the frequently mentioned Key Performance Indicators which lead to that assessment are :
I am often times amazed that the prevailing mindset seems to be that this is just "fine" and lesser performance is to be expected when outsourcing. After all...pricing is low enough that it does still make economic sense. (and I am sure that is true for a lot of outsourcing relationships).
Let me perfectly clear...I am the first one to admit that there is a productivity gap between an onshore and offshore software developer.
What is important to realize though is that with familiarity the productivity gap will start shrinking right away. The actual gap remaining after a month or two month is subject to debate...in my opinion it is not uncommon that the gap will be eliminated completely, but as I said...it is subject to debate.
As such the question needs to be looked at why the feeling is so often that the quality of the work is just not great. In my experience and when discussing the outsourcing strategy I usually learn that in situations like the ones described above the outsourcing vendor is looked upon as a cost center.
The most important factor in negotiating any outsourcing deal is most often the hourly rate or team rate being charged. Corporations will negotiate to get the lowest rate to realize the most savings.
The strategy does of course makes sense to the corporation...but the flip side of the coin is that it does then lead to shortcoming in the composition of the development team.
A low rate will lead to a team which is predominately staffed with junior developers, supervised by a few senior guys. The problem with that approach is that the Junior developers are afraid of the power wall...they lack the authority and confidence to challenge their immediate superiors or anyone from the client side.
Consequently the back and forth which ultimately results in a more productive and informed process is lacking.
Of course not every corporation is going to willingly spend more money on its offshore development team to change the mix up of the team. It might be a good investment though...just exchanging one or two junior developers with mid-level developers might create the bridge the team needs to overcome the power wall, both internally and externally.
If the budget is set in stone another option is to exchange 3 junior against 2 mid level developers (given the team size allows for it). It should be cost neutral but it is my experience that the change in team dynamic will boost productivity and improve the overall KPI's despite the reduction in team size.
Some of the frequently mentioned Key Performance Indicators which lead to that assessment are :
- Development Sprints take to long to completion
- Sprints are simplified by reducing the number of sub tasks
- Q&A takes to long
- Average time for bug fixes
I am often times amazed that the prevailing mindset seems to be that this is just "fine" and lesser performance is to be expected when outsourcing. After all...pricing is low enough that it does still make economic sense. (and I am sure that is true for a lot of outsourcing relationships).
Let me perfectly clear...I am the first one to admit that there is a productivity gap between an onshore and offshore software developer.
What is important to realize though is that with familiarity the productivity gap will start shrinking right away. The actual gap remaining after a month or two month is subject to debate...in my opinion it is not uncommon that the gap will be eliminated completely, but as I said...it is subject to debate.
As such the question needs to be looked at why the feeling is so often that the quality of the work is just not great. In my experience and when discussing the outsourcing strategy I usually learn that in situations like the ones described above the outsourcing vendor is looked upon as a cost center.
The most important factor in negotiating any outsourcing deal is most often the hourly rate or team rate being charged. Corporations will negotiate to get the lowest rate to realize the most savings.
The strategy does of course makes sense to the corporation...but the flip side of the coin is that it does then lead to shortcoming in the composition of the development team.
A low rate will lead to a team which is predominately staffed with junior developers, supervised by a few senior guys. The problem with that approach is that the Junior developers are afraid of the power wall...they lack the authority and confidence to challenge their immediate superiors or anyone from the client side.
Consequently the back and forth which ultimately results in a more productive and informed process is lacking.
Of course not every corporation is going to willingly spend more money on its offshore development team to change the mix up of the team. It might be a good investment though...just exchanging one or two junior developers with mid-level developers might create the bridge the team needs to overcome the power wall, both internally and externally.
If the budget is set in stone another option is to exchange 3 junior against 2 mid level developers (given the team size allows for it). It should be cost neutral but it is my experience that the change in team dynamic will boost productivity and improve the overall KPI's despite the reduction in team size.
Who Knew...Jamaica Is Becoming A Major BPO Hub
Of course, by pure numbers Jamaica lags the traditional outsourcing destinations like the Philippines and India. Never the less...the country has steadily increased its footprint in the BPO sector. It is estimated that the country will be home to about 20,000 ICT BPO jobs by the end of 2016.
Obviously 20,000 is not a big number when you compare it to the main outsourcing centers in the world. Given a total population of about 2.7 Mio though the government is realizing that the BPO sector is worth to be promoted. At the given growth rate of 20 % the sector will employ about 1 % of its population by 2018/2019.
Jamaica's inroads into the global BPO industry are driven by an advantage none of the traditional outsourcing destinations can match. It shares the same time zone as Chicago (CST), therefor collaboration throughout the work day is seamless.
Jamaica's predominant language is English....another advantage why US BPO companies like to establish a presence there.
The local salary structure makes it highly feasible to outsource technology talent. The median salary in the Jamaican IT industry is about 150k Jamaican Dollars (about US- $ 1,220). The rate is therefore comparable (and even lower) to what has to be paid for local talent in India or the Philippines.
One issue is the relative small size of the Jamaican labor market. It is clear that with increased demand for IT staff local salaries are sure to rise. Given that the BPO industry is notoriously price sensitive it seems likely that the strategic advantages Jamaica enjoys will be buffered by the disadvantage of increases in salaries in the BPO sector.
Never the less, for the time being Jamaica might be a good place to establish a BPO center.
Obviously 20,000 is not a big number when you compare it to the main outsourcing centers in the world. Given a total population of about 2.7 Mio though the government is realizing that the BPO sector is worth to be promoted. At the given growth rate of 20 % the sector will employ about 1 % of its population by 2018/2019.
Jamaica's inroads into the global BPO industry are driven by an advantage none of the traditional outsourcing destinations can match. It shares the same time zone as Chicago (CST), therefor collaboration throughout the work day is seamless.
Jamaica's predominant language is English....another advantage why US BPO companies like to establish a presence there.
The local salary structure makes it highly feasible to outsource technology talent. The median salary in the Jamaican IT industry is about 150k Jamaican Dollars (about US- $ 1,220). The rate is therefore comparable (and even lower) to what has to be paid for local talent in India or the Philippines.
One issue is the relative small size of the Jamaican labor market. It is clear that with increased demand for IT staff local salaries are sure to rise. Given that the BPO industry is notoriously price sensitive it seems likely that the strategic advantages Jamaica enjoys will be buffered by the disadvantage of increases in salaries in the BPO sector.
Never the less, for the time being Jamaica might be a good place to establish a BPO center.
Why Accountability Is Key To A Successful Outsourcing Relationship....
The worst situation which can potentially arise when outsourcing any type of business process is when the communication link between the onshore client and the offshore outsourcing provider gets broken.
I always like to say before the business relationship went sour the communication went dead.
The simple truth of the matter is that not every onshore employee is excited to work with a company based in India, Philippines or Eastern Europe (or some other country which is hardly known to onshore staff),
That hesitation sometimes can lead to a lack of communication which then can create a viscous cycle. Because of the lack of feedback from the client the quality of the work product starts to slip. The degradation in quality leads to even further resentment by onshore staff.
Needless to say, problems like the above combined with time and cultural differences as well as a language problem have crushed more than a few outsourcing deals.
At the end Senior Management looks at the entire outsourcing relationship and wonders why it does not seem to be working as well as they think it should.
In order to avoid a scenario where the entire outsourcing relationship falls apart it makes sense to implement the 7 rules and guidelines shown below:
The over reaching goal is to foster a culture of accountability. Making the onshore staff responsible at an early stage and creating a joint responsibility for the KPI's will produce better results.
If the above is properly implemented the onshore staff will not be able to just point fingers to the offshore provider and issue blame.
By instituting this level of accountability your new outsourcing relationship should be off to a good start.
I always like to say before the business relationship went sour the communication went dead.
The simple truth of the matter is that not every onshore employee is excited to work with a company based in India, Philippines or Eastern Europe (or some other country which is hardly known to onshore staff),
That hesitation sometimes can lead to a lack of communication which then can create a viscous cycle. Because of the lack of feedback from the client the quality of the work product starts to slip. The degradation in quality leads to even further resentment by onshore staff.
Needless to say, problems like the above combined with time and cultural differences as well as a language problem have crushed more than a few outsourcing deals.
At the end Senior Management looks at the entire outsourcing relationship and wonders why it does not seem to be working as well as they think it should.
In order to avoid a scenario where the entire outsourcing relationship falls apart it makes sense to implement the 7 rules and guidelines shown below:
- Early in the process designate at least one person, better a team of people who will be in charge of managing the day to day operation of your outsourcing relationship. Include them in the meetings as early in the process as possible. The goal is to familiarize them with the inner workings of the deal as well as giving your outsourcing provider early and easy access to the Relationship Managers.
- Senior Management has to clearly define Key Performance Indicators (KPI'S) which it wants to meet. The KPIs have to be clearly laid out in such a way that both, onshore local relationship management and offshore provider are made jointly responsible for reaching them. They have to be joint at the hip....one parties failure will be deemed the other parties failure as well.
- Insist on daily meetings between key personnel..ideally twice a day. Use a video conferencing tool (skype is fine too). It might seem trivial but the use of video will greatly enhance familiarity between key personnel and thus will increase productivity.
- Insist on reports. Develop a report structure which is being fed to Senior Management at predetermined intervals. (daily, weekly). The reports you receive should be based upon the prior discussed KPI's. Also...make clear that both teams, onshore and offshore will be jointly held responsible for failure.
- Have regular meetings with both teams (joint meetings). Once again, video conferencing is preferred. Address any issues you might have in reaching KPIs. Solicit suggestions to improve performance.
- Have individual meetings with each team (the onshore and the offshore team, video once again). Get them to spill the beans if there is any sand in the relationship. Use the information to fine tune instructions during the next joint meeting.
- Set realistic expectations. For the teams as well as for the company. It is well established that outsourcing has an initial productivity gap versus the comparable onshore solution. That productivity gap will close over time. Your KPIs will be your measuring stick.
The over reaching goal is to foster a culture of accountability. Making the onshore staff responsible at an early stage and creating a joint responsibility for the KPI's will produce better results.
If the above is properly implemented the onshore staff will not be able to just point fingers to the offshore provider and issue blame.
By instituting this level of accountability your new outsourcing relationship should be off to a good start.
Staff Turnover When Outsourcing....A Simple Method To Avoid It
One of the biggest battles any user of outsourcing services can attest to is attrition. There is nothing worse than having put resources (=money) into your hires and see them walk out of the door at a rapid clip. They have to be replaced and the new hires have to be retrained. It takes time to bring the new hires up to speed...familiarize them with what is going on. The fact of the matter is that constant attrition is a drag on the quality of the work product.
The problem of staff turnover is true for virtually all BPO centers....no matter if the service offered is IT (Software), Call Center or Service based.
The problem though is not necessarily the same all over the world. Some BPO / Outsourcing providers have fostered a culture and pay environment where the talent stays around. As such it makes sense to review the attrition rates your outsourcing provider has. If they assume a staff turnover rate of 50 % and more (which is not unusual) it does provide a provide a pretty good indication that the center you are dealing with is a "mill" or "body shop". The pay is most probably less than what the local competition offers and no positive culture is fostered.
Some welcome news on this front can be found in the article below. The attrition rates of the BPO industry in the Philippines has now fallen to 20 %. A rather astonishing number considering that the number was 33 % as late as 2011.
Philippines Outsourcing BPO Staff Turnover Rates Down To 20 %
Since the 20 % number represents a blend of the entire industry it signals that you can find outsourcing providers which have reduced staff turnover to levels which are below or close to the turnover rates we are used to see in the US. As a comparison...the table below shows staff turnover rates (voluntary and involuntary) for the US.
Consequently turnover and attrition might not be the problem it used to be, at least not when you pick the right outsourcing / BPO partner....and that is some really good news.
The problem of staff turnover is true for virtually all BPO centers....no matter if the service offered is IT (Software), Call Center or Service based.
The problem though is not necessarily the same all over the world. Some BPO / Outsourcing providers have fostered a culture and pay environment where the talent stays around. As such it makes sense to review the attrition rates your outsourcing provider has. If they assume a staff turnover rate of 50 % and more (which is not unusual) it does provide a provide a pretty good indication that the center you are dealing with is a "mill" or "body shop". The pay is most probably less than what the local competition offers and no positive culture is fostered.
Some welcome news on this front can be found in the article below. The attrition rates of the BPO industry in the Philippines has now fallen to 20 %. A rather astonishing number considering that the number was 33 % as late as 2011.
Philippines Outsourcing BPO Staff Turnover Rates Down To 20 %
Since the 20 % number represents a blend of the entire industry it signals that you can find outsourcing providers which have reduced staff turnover to levels which are below or close to the turnover rates we are used to see in the US. As a comparison...the table below shows staff turnover rates (voluntary and involuntary) for the US.
Source: CompData 2014 Survey
Consequently turnover and attrition might not be the problem it used to be, at least not when you pick the right outsourcing / BPO partner....and that is some really good news.
Agile Project Management...Is Your Software Outsourcer / BPO Firm Using It ?....
One problem I frequently run into when discussing project guidelines for outsourced software development is that most of the clients are well familiar with Gantt charts or Waterfall charts. As such they prefer to look at the project guidelines, timelines and milestones based upon those charts.
Nothing wrong with that of course...but the software development world has moved on and at least the better companies are now mostly using an Agile Software Development set of principles. The concept of an Agile environment is that it is much more "free flowing" and not bound to the traditional milestones and tightly defined guidelines which are being used in a Non-Agile environment.
The challenge is how to provide the accountability to the client (the ones who pay the bill) while harvesting the advantages the Agile environment can deliver.
The Agile Development environment is based upon the following 12 principles:
A practical problem of an Agile development is that there are really no Milestones the teams are working towards. As such there is no firm date which can be given so that the customer can review a an interim work product (milestone).
Nothing wrong with that of course...but the software development world has moved on and at least the better companies are now mostly using an Agile Software Development set of principles. The concept of an Agile environment is that it is much more "free flowing" and not bound to the traditional milestones and tightly defined guidelines which are being used in a Non-Agile environment.
The challenge is how to provide the accountability to the client (the ones who pay the bill) while harvesting the advantages the Agile environment can deliver.
The Agile Development environment is based upon the following 12 principles:
- Customer satisfaction by early and continuous delivery of valuable software
- Welcome changing requirements, even in late development
- Working software is delivered frequently (weeks rather than months)
- Close, daily cooperation between business people and developers
- Projects are built around motivated individuals, who should be trusted
- Face-to-face conversation is the best form of communication (co-location)
- Working software is the principal measure of progress
- Sustainable development, able to maintain a constant pace
- Continuous attention to technical excellence and good design
- Simplicity—the art of maximizing the amount of work not done—is essential
- Best architectures, requirements, and designs emerge from self-organizing teams
- Regularly, the team reflects on how to become more effective, and adjusts accordingly
A practical problem of an Agile development is that there are really no Milestones the teams are working towards. As such there is no firm date which can be given so that the customer can review a an interim work product (milestone).
A practical solution to this dilemma (and one we use internally) is to still provide Gantt charts but use an Agile environment in House. The process has to be of course managed properly...but if done well it is entirely possible to utilize an Agile environment while also providing the form and accountability the client is looking for.
A great article which goes into details as to the way an Agile Development Environment works can be found below.
Why The Valley Loves Outsourcing...and uses it all the time!
It is well known that a lot of tech startups use outsourcing to power their business. They not only outsource software development and design but customer service, sales and order fulfillment. They typically avail themselves to the traditional destinations like India, Philippines , China and Russia. There are a few reasons why outsourcing is being used by tech and service heavy startups....
In my opinion a start up which uses a reputable outsourcing provider who is not just a body shop will always come out ahead. Costs will be dramatically lower and there is huge degree of flexibility to scale development up or down as needed. Another important factor is that the startup gains a degree of technical knowledge it would simply not be able to acquire (or only at significant costs).
An article discussing some of the Pro's and also the Con's is below.
Why Every Startup Should Outsource Software Development...and typically does!
- The timeline from concept to Minimum Viable Product (MVP) is substantially shortened
- Outsourcing companies have a very good grasp of open source, thereby reducing development timeline and costs
- All of the core competencies to run a successful development team are under one roof. The Startup does not have to go out and built a team which covers all aspects needed for a successful application development (Development, Engineering, User Interface Design ....)
- The BPO company, even though it might be located in the Philippines or India, might have significant related experience to the business the start up wants to get off the ground.
In my opinion a start up which uses a reputable outsourcing provider who is not just a body shop will always come out ahead. Costs will be dramatically lower and there is huge degree of flexibility to scale development up or down as needed. Another important factor is that the startup gains a degree of technical knowledge it would simply not be able to acquire (or only at significant costs).
An article discussing some of the Pro's and also the Con's is below.
Why Every Startup Should Outsource Software Development...and typically does!
Does The Cloud Reduce The Demand For Outsourcing..or doesn't it?
One of the effects of the rise of the cloud is that vast parts of roles traditionally filled by outsourcing companies are falling away. Simply put...there is no need (or a diminished one) for DBA and Systems Architects. The hardware side is basically eliminated. The article below makes the point though that there is a partial offset because of the need to develop middle ware which sits between the client and the cloud.
I can attest to that...just among our client we see that the issue of how to manage various cloud solutions and properly integrate them into an enterprise becomes more and more pressing. I also feel that the technical solutions are becoming more ambitious since there is no longer a hardware limitation which would have created a bottleneck in the old, pre-cloud days.
Does the cloud eliminate or create outsourcing/BPO jobs
One of the effects of the rise of the cloud is that vast parts of roles traditionally filled by outsourcing companies are falling away. Simply put...there is no need (or a diminished one) for DBA and Systems Architects. The hardware side is basically eliminated. The article below makes the point though that there is a partial offset because of the need to develop middle ware which sits between the client and the cloud.
I can attest to that...just among our client we see that the issue of how to manage various cloud solutions and properly integrate them into an enterprise becomes more and more pressing. I also feel that the technical solutions are becoming more ambitious since there is no longer a hardware limitation which would have created a bottleneck in the old, pre-cloud days.
Does the cloud eliminate or create outsourcing/BPO jobs
Subscribe to:
Posts (Atom)




