Edit from Article Greenhouse: FORMAT
| ←Older revision | Revision as of 23:52, 17 November 2019 | ||
| Line 1: | Line 1: | ||
| − |
Liquid error: wrong number of arguments (given 1, expected 2)Liquid error: wrong number of arguments (given 1, expected 2)66% of the entrepreneurs nod YES when it comes to software outsourcing. It is the new normal. Pioneers in this business often quote that if you are depriving yourself of outsourcing and your competitors are not, you are losing the competitive edge. And choosing a software development team is a walk in the park. Except, the park is Jurassic park ;-) This article will provide a quick outlook into the points one should keep in mind before outsourcing software development.
|
+ |
Liquid error: wrong number of arguments (given 1, expected 2)66% of the entrepreneurs nod YES when it comes to software outsourcing. It is the new normal. Pioneers in this business often quote that if you are depriving yourself of outsourcing and your competitors are not, you are losing the competitive edge. And choosing a software development team is a walk in the park. Except, the park is Jurassic park ;-) This article will provide a quick outlook into the points one should keep in mind before outsourcing software development.
|
|
[[Category:Articles in Quality Review]]
|
[[Category:Articles in Quality Review]]
|
||
|
== Steps ==
|
== Steps ==
|
||
| − |
|
+ |
# Do your research. Research is the most important part of outsourcing. People who say, let’s make a decision and we will see what happens will outright fail when it comes to software outsourcing. There are tens of thousands of companies that offer similar services and choosing one will need a good amount of old school.[[Image:Owl 47526_1280.png|center]]
|
| − |
|
||
| − |
|
||
| − |
|
||
|
#* '''Run preliminary research to shortlist companies:''' Google your keyword. See who the competent players are. Make a list. Similarly, follow reputed listing directories and take a look there too. Go through their website, their work experience and most importantly, the client testimonials.
|
#* '''Run preliminary research to shortlist companies:''' Google your keyword. See who the competent players are. Make a list. Similarly, follow reputed listing directories and take a look there too. Go through their website, their work experience and most importantly, the client testimonials.
|
||
|
#* '''REMEMBER:''' You will need to know every aspect of your potential vendor to establish its commercial potential. Do some further RnD and restrict your list to a maximum of 4-5 top companies.
|
#* '''REMEMBER:''' You will need to know every aspect of your potential vendor to establish its commercial potential. Do some further RnD and restrict your list to a maximum of 4-5 top companies.
|
||
|
#* '''Make a project spec that will act as a holy grail for the requirements'''. Start with writing your goals in a document. This will provide a vision for the software. Then start writing the software requirements in that spec. Make sure it makes sense. Then you can either approach the potential software development companies and discuss the spec or just simply post the spec on independent freelancing platforms and wait for proposals and bids.
|
#* '''Make a project spec that will act as a holy grail for the requirements'''. Start with writing your goals in a document. This will provide a vision for the software. Then start writing the software requirements in that spec. Make sure it makes sense. Then you can either approach the potential software development companies and discuss the spec or just simply post the spec on independent freelancing platforms and wait for proposals and bids.
|
||
| − |
# '''Freelancing sites are not recommended''' until and unless you have a very tight budget. The number of bids and proposals you will get will be overwhelming and 90% of those will be generic copy paste proposals or automated bots.[[Image:Bad review 2813741_1280.png|center]]
|
+ |
#* '''Freelancing sites are not recommended''' until and unless you have a very tight budget. The number of bids and proposals you will get will be overwhelming and 90% of those will be generic copy paste proposals or automated bots.[[Image:Bad review 2813741_1280.png|center]]
|
| − |
|
+ |
# Review the company’s work experience. Start with writing your goals in a document. This will provide a vision for the software. Then start writing the software requirements in that spec. Make sure it makes sense. Then you can either approach the potential software development companies and discuss the spec or just simply post the spec on independent freelancing platforms and wait for proposals and bids.[[Image:Pixel cells 3702060_1280.png|center]]
|
| − |
|
||
| − |
|
||
| − |
|
||
| − |
|
||
|
#* This is important because someone who has experience in similar technology can easily understand your requirements, suggest better features and functionalities and also solve bugs faster.
|
#* This is important because someone who has experience in similar technology can easily understand your requirements, suggest better features and functionalities and also solve bugs faster.
|
||
| − |
#* If a company cannot show a vivid portfolio, cross them off your list.
|
+ |
#* If a company cannot show a vivid portfolio, cross them off your list.
|
| − |
|
+ |
# Talk to their past and present clients. Testimonials speak volumes. It helps the clients form an idea of the quality of work and encourages them to trust the vendors. Take a look at the testimonials on their website and also third party sites like Clutch, Goodfirms, etc.[[Image:Multi tasking 2840792_1920.jpg|center]]
|
| − |
|
||
| − |
|
||
| − |
|
||
| − |
|
||
|
#* Also, ask them for references and contact details so that you can personally speak to the past and present clients in order to get a detailed view of their technical expertise, communication and project management. This will form a more impartial outlook for you and result in better judgement.
|
#* Also, ask them for references and contact details so that you can personally speak to the past and present clients in order to get a detailed view of their technical expertise, communication and project management. This will form a more impartial outlook for you and result in better judgement.
|
||
| − |
|
+ |
# Check the communicate and inquisitiveness.If the potential software development company doesn’t ask questions, it doesn’t understand anything! If the client is explaining a user-flow, being a software company developing software applications for years, they are bound to have some questions regarding the flow. If they nod yes to everything you say, nod ‘NO” for choosing them.[[Image:Woman 1459220_1280.png|center]]
|
| − |
|
||
| − |
|
||
| − |
|
||
| − |
|
||
|
#* Also, check for their English fluency. This is important as software development is an iterative process and you both need to understand each other in this long road. Find someone who takes effort to constantly better the processes, designs, and user flows.
|
#* Also, check for their English fluency. This is important as software development is an iterative process and you both need to understand each other in this long road. Find someone who takes effort to constantly better the processes, designs, and user flows.
|
||
| − |
|
+ |
# Run through the technology stack. You have to make sure they know their technology better than anyone else in the game. If they can’t write clean and expert-level codes, it really doesn’t make any sense. Technical competency is one of the most important factors when it comes to software development.[[Image:Man 1459246_1280.png|center]]
|
| − |
|
+ |
#* Take a look at their technology stack before proceeding with the company. Make sure they have developers who have skills and expertise to adapt to any new tech stack and are constantly trying to update their knowledge and skills.
|
| − |
|
+ |
# Know more about the company’s transparency. This cannot be stressed upon enough. High-quality applications cannot be developed without high transparency.[[Image:Diamond 158431_1280.png|center]]
|
| − |
|
+ |
#* The first step to this is maintaining a document where every deliverable is listed. The cost and time estimate should be based on this document. This makes the approach straightforward and helps development firms create a transparent environment when negotiating rates, time and application functionalities.
|
| − |
|
||
| − |
#* Take a look at their technology stack before proceeding with the company. Make sure they have developers who have skills and expertise to adapt to any new tech stack and are constantly trying to update their knowledge and skills.
|
||
| − |
|
||
| − |
|
||
| − |
|
||
| − |
|
||
| − |
|
||
| − |
#* The first step to this is maintaining a document where every deliverable is listed. The cost and time estimate should be based on this document. This makes the approach straightforward and helps development firms create a transparent environment when negotiating rates, time and application functionalities.
|
||
| − |
|
||
| − |
|
||
|
==Tips==
|
==Tips==
|
||
| Line 49: | Line 24: | ||
|
* Bigger is not always better. Probably you would be better off with a small company where you get personalized attention and where they can go the extra mile to occasionally entertain your minor deviation from spec or minor extra work.
|
* Bigger is not always better. Probably you would be better off with a small company where you get personalized attention and where they can go the extra mile to occasionally entertain your minor deviation from spec or minor extra work.
|
||
|
* You might think hiring freelancers is easier and cost-effective, but the hassles when you need an upgrade or some additional minor work will account for much higher costs in the long run. So, weigh your options and decide carefully where you should invest your time.
|
* You might think hiring freelancers is easier and cost-effective, but the hassles when you need an upgrade or some additional minor work will account for much higher costs in the long run. So, weigh your options and decide carefully where you should invest your time.
|
||
| − |
|
||
| − |
|
||
|
==Warnings==
|
==Warnings==
|
||
|
* Ever-changing requirement spec - Don’t go to and fro on your team. The ever-changing spec will always result in the client spending more money and the development team investing more time. It’s never a happy outcome.
|
* Ever-changing requirement spec - Don’t go to and fro on your team. The ever-changing spec will always result in the client spending more money and the development team investing more time. It’s never a happy outcome.
|
||
|
* Avoid Micromanaging - Dictating everything makes your software team feel inefficient and incompetent and in turn, keeps them from brainstorming and innovating.
|
* Avoid Micromanaging - Dictating everything makes your software team feel inefficient and incompetent and in turn, keeps them from brainstorming and innovating.
|
||
| − |
|
||
| − |
|
||
|
==Parting words==
|
==Parting words==
|
||
from wikiHow - Recent Changes [en] https://ift.tt/2KwaRjd
via IFTTT
