<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Offshore Software Success</title>
	<atom:link href="http://www.offshoresoftwaresuccess.com/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.offshoresoftwaresuccess.com</link>
	<description>Learn to outsource with freelance software developers</description>
	<lastBuildDate>Wed, 10 Aug 2011 01:44:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Effective Offshore Staff Management Essential for Successful Outsourcing by offshore staff philippines</title>
		<link>http://www.offshoresoftwaresuccess.com/project-management/effective-offshore-staff-management#comment-9</link>
		<dc:creator>offshore staff philippines</dc:creator>
		<pubDate>Wed, 10 Aug 2011 01:44:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshoresoftwaresuccess.com/uncategorized/effective-offshore-staff-management-essential-for-successful-outsourcing#comment-9</guid>
		<description>This is the right blog for anyone who wants to find out about this topic and thanks for the post. It was a great and informative post. Looking forward to read more informative and interesting post from you :)</description>
		<content:encoded><![CDATA[<p>This is the right blog for anyone who wants to find out about this topic and thanks for the post. It was a great and informative post. Looking forward to read more informative and interesting post from you <img src='http://www.offshoresoftwaresuccess.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Freelance Software Development Mistake # 4 &#8211; No Shared Vision with the Programmer by Jon</title>
		<link>http://www.offshoresoftwaresuccess.com/hire-freelance-programmers/mistake-4-no-shared-vision-with-programmer#comment-5</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 09 Mar 2011 02:58:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshoresoftwaresuccess.com/uncategorized/freelance-software-development-mistake-4-no-shared-vision-with-the-developer#comment-5</guid>
		<description>To write instructions for a programmer to understand and be able to code, you need to use 4 basic elements:
1) Write instructions in a logical format.  This includes using numbered bulleted format.  Your description should be logical and step-by-step, in that anyone should read what you say and reach the same destination.  Just like if you were to give directions to your house.  Anyone who follows your instructions 100% should reach the same destination.
2) Visual examples.  Screenshots, powerpoint, video screen capture or recording of your ideas.  Snagit is a great screenshot program where you can quickly mark-up photos to callout or write comments on exactly what you want the programmer to do or what feature you have.
If there is something in nature or another product that already does what you want to do, no need to re-invent the wheel.  Find a way to capture visually what someone else has done and reference that software or action and say &quot;this is similar/exactly/opposite of what I want in this project requirement&quot;
In some cases yourself or the programmer can create &quot;sub programs&quot; or &quot;mini programs&quot; can be built to display specific functionality to see if
it is what you want included in the main program.
3) Milestones or stopping points.  Because of the nature of programming, one of the benefits of working from scratch is that once the foundation is coded, you can test each feature or set of features before getting too far in the project.
This helps the programmer not get to far ahead before making sure the program is up to spec.  This also ensures that your project is on a schedule and you can test different functionality to make sure your requirements are met.
The ideal program will be coded in a way that it can be scaled (features can be easily added to it at a later point).
4) Continuous communication.  Thorough discussion before, during and after project is completed. Be specific in your feedback.  Use screenshots and detailed (yet concise) explanations of what you want to see happen, and why the current program is not working.
Also, it&#039;s not uncommon to come up with additional requirements as the project progresses.  For whatever reasons, you want to add or delete features.  Communication is the best way to see this through.
Great article.  Communication is the key.
</description>
		<content:encoded><![CDATA[<p>To write instructions for a programmer to understand and be able to code, you need to use 4 basic elements:<br />
1) Write instructions in a logical format.  This includes using numbered bulleted format.  Your description should be logical and step-by-step, in that anyone should read what you say and reach the same destination.  Just like if you were to give directions to your house.  Anyone who follows your instructions 100% should reach the same destination.<br />
2) Visual examples.  Screenshots, powerpoint, video screen capture or recording of your ideas.  Snagit is a great screenshot program where you can quickly mark-up photos to callout or write comments on exactly what you want the programmer to do or what feature you have.<br />
If there is something in nature or another product that already does what you want to do, no need to re-invent the wheel.  Find a way to capture visually what someone else has done and reference that software or action and say &#8220;this is similar/exactly/opposite of what I want in this project requirement&#8221;<br />
In some cases yourself or the programmer can create &#8220;sub programs&#8221; or &#8220;mini programs&#8221; can be built to display specific functionality to see if<br />
it is what you want included in the main program.<br />
3) Milestones or stopping points.  Because of the nature of programming, one of the benefits of working from scratch is that once the foundation is coded, you can test each feature or set of features before getting too far in the project.<br />
This helps the programmer not get to far ahead before making sure the program is up to spec.  This also ensures that your project is on a schedule and you can test different functionality to make sure your requirements are met.<br />
The ideal program will be coded in a way that it can be scaled (features can be easily added to it at a later point).<br />
4) Continuous communication.  Thorough discussion before, during and after project is completed. Be specific in your feedback.  Use screenshots and detailed (yet concise) explanations of what you want to see happen, and why the current program is not working.<br />
Also, it&#8217;s not uncommon to come up with additional requirements as the project progresses.  For whatever reasons, you want to add or delete features.  Communication is the best way to see this through.<br />
Great article.  Communication is the key.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interesting Comments on the Seven Mistakes when Hiring a Programmer by John Chris</title>
		<link>http://www.offshoresoftwaresuccess.com/hire-freelance-programmers/comments-on-mistakes-hiring-programmer#comment-8</link>
		<dc:creator>John Chris</dc:creator>
		<pubDate>Tue, 15 Feb 2011 01:09:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshoresoftwaresuccess.com/uncategorized/interesting-comments-on-the-seven-mistakes-when-hiring-a-programmer#comment-8</guid>
		<description>Very nice information shared. In my views the most common mistake in hiring a developer is not estimating the time for project and it can be very dangerous in the final stage of any project. So while hiring any developer first think about the time period in which you have to deliver the project to client .
</description>
		<content:encoded><![CDATA[<p>Very nice information shared. In my views the most common mistake in hiring a developer is not estimating the time for project and it can be very dangerous in the final stage of any project. So while hiring any developer first think about the time period in which you have to deliver the project to client .</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interesting Comments on the Seven Mistakes when Hiring a Programmer by Alex</title>
		<link>http://www.offshoresoftwaresuccess.com/hire-freelance-programmers/comments-on-mistakes-hiring-programmer#comment-7</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Wed, 13 Oct 2010 04:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshoresoftwaresuccess.com/uncategorized/interesting-comments-on-the-seven-mistakes-when-hiring-a-programmer#comment-7</guid>
		<description>Thanks a lot for this material! It&#039;s really vital to understand and avoid all 7 mistakes.
</description>
		<content:encoded><![CDATA[<p>Thanks a lot for this material! It&#8217;s really vital to understand and avoid all 7 mistakes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Freelance Software Development Mistake # 1 &#8211; Not Understanding The User&#8217;s Needs by Bharti Pamnani</title>
		<link>http://www.offshoresoftwaresuccess.com/hire-freelance-programmers/mistake-1-not-understanding-user-needs#comment-4</link>
		<dc:creator>Bharti Pamnani</dc:creator>
		<pubDate>Mon, 29 Dec 2008 00:28:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshoresoftwaresuccess.com/uncategorized/freelance-software-development-mistake-1-not-understanding-the-users-needs#comment-4</guid>
		<description>Hey Richard. You have shown really good thing. Mostly free-lancer&#039;s do this mistake. If they are not able to understand the need of the user, they won&#039;t be able to develop the correct product for them. Than the work done will be considered as auto pilot work.
</description>
		<content:encoded><![CDATA[<p>Hey Richard. You have shown really good thing. Mostly free-lancer&#8217;s do this mistake. If they are not able to understand the need of the user, they won&#8217;t be able to develop the correct product for them. Than the work done will be considered as auto pilot work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Freelance Software Development Mistake # 1 &#8211; Not Understanding The User&#8217;s Needs by smithkarl</title>
		<link>http://www.offshoresoftwaresuccess.com/hire-freelance-programmers/mistake-1-not-understanding-user-needs#comment-3</link>
		<dc:creator>smithkarl</dc:creator>
		<pubDate>Wed, 27 Dec 2006 08:11:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshoresoftwaresuccess.com/uncategorized/freelance-software-development-mistake-1-not-understanding-the-users-needs#comment-3</guid>
		<description>Hi,
I found these articles and bookmarked your site instantly. I am soon going to develop a new software, and these 7 articles cost as much as the software itself:)
Thanks for sharing these valuable tips specially for new webmasters with no experience.
Karl
</description>
		<content:encoded><![CDATA[<p>Hi,<br />
I found these articles and bookmarked your site instantly. I am soon going to develop a new software, and these 7 articles cost as much as the software itself:)<br />
Thanks for sharing these valuable tips specially for new webmasters with no experience.<br />
Karl</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Interesting Comments on the Seven Mistakes when Hiring a Programmer by Poornendulal</title>
		<link>http://www.offshoresoftwaresuccess.com/hire-freelance-programmers/comments-on-mistakes-hiring-programmer#comment-6</link>
		<dc:creator>Poornendulal</dc:creator>
		<pubDate>Fri, 15 Dec 2006 11:38:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshoresoftwaresuccess.com/uncategorized/interesting-comments-on-the-seven-mistakes-when-hiring-a-programmer#comment-6</guid>
		<description>All these 7 were the perfectly identified. I must really appreciate your effort in identifying in them.
Well my comment at time point is that an offshore outsourcing company if it has all there they can&#039;t flourish in offshore outsourcing.
Usually companies are very smart in looking unto it and outsource accordingly. A typical example is Health Domino project that has been very closely evaluated before it was finalized with Benchmark Softec Limited, Offshore Outsourcing company.
Most people apply all the above 7 thinking before they oursource. Perhaps Offshore Outsourcing secret is purely based on all the 7 points.
Your effort is the ever made best effort on the Internet I have seen till now.
Thank you for the nice archive
</description>
		<content:encoded><![CDATA[<p>All these 7 were the perfectly identified. I must really appreciate your effort in identifying in them.<br />
Well my comment at time point is that an offshore outsourcing company if it has all there they can&#8217;t flourish in offshore outsourcing.<br />
Usually companies are very smart in looking unto it and outsource accordingly. A typical example is Health Domino project that has been very closely evaluated before it was finalized with Benchmark Softec Limited, Offshore Outsourcing company.<br />
Most people apply all the above 7 thinking before they oursource. Perhaps Offshore Outsourcing secret is purely based on all the 7 points.<br />
Your effort is the ever made best effort on the Internet I have seen till now.<br />
Thank you for the nice archive</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Freelance Software Development Mistake # 1 &#8211; Not Understanding The User&#8217;s Needs by bidfreelancers</title>
		<link>http://www.offshoresoftwaresuccess.com/hire-freelance-programmers/mistake-1-not-understanding-user-needs#comment-2</link>
		<dc:creator>bidfreelancers</dc:creator>
		<pubDate>Sun, 30 Jul 2006 03:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.offshoresoftwaresuccess.com/uncategorized/freelance-software-development-mistake-1-not-understanding-the-users-needs#comment-2</guid>
		<description>Hi,
You have great collection of articles. and its real worth reading them all. I will ask all my bidfreelancers.com users to read them.
Keep it up!
Regards
Ajwani
www.Bidfreelancers.com
</description>
		<content:encoded><![CDATA[<p>Hi,<br />
You have great collection of articles. and its real worth reading them all. I will ask all my bidfreelancers.com users to read them.<br />
Keep it up!<br />
Regards<br />
Ajwani<br />
<a href="http://www.Bidfreelancers.com">http://www.Bidfreelancers.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

