 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Quality Assurance and Project Management &#187; coder</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/tag/coder/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/quality-assurance</link>
	<description>Improvement in Quality never ends. There is always a scope of improvement in life...</description>
	<lastBuildDate>Thu, 16 May 2013 18:52:46 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<copyright>2006-2007 </copyright>
	<managingEditor>jaideepkhanduja@gmail.com (Quality Assurance and Project Management)</managingEditor>
	<webMaster>jaideepkhanduja@gmail.com (Quality Assurance and Project Management)</webMaster>
	<image>
		<url>http://itknowledgeexchange.techtarget.com/quality-assurance/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url>
		<title>Quality Assurance and Project Management</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance</link>
		<width>144</width>
		<height>144</height>
	</image>
	<itunes:subtitle></itunes:subtitle>
	<itunes:summary>Improvement in Quality never ends. There is always a scope of improvement in life...</itunes:summary>
	<itunes:keywords></itunes:keywords>
	<itunes:category text="Society &#38; Culture" />
	<itunes:author>Quality Assurance and Project Management</itunes:author>
	<itunes:owner>
		<itunes:name>Quality Assurance and Project Management</itunes:name>
		<itunes:email>jaideepkhanduja@gmail.com</itunes:email>
	</itunes:owner>
	<itunes:block>no</itunes:block>
	<itunes:explicit>no</itunes:explicit>
	<itunes:image href="http://itknowledgeexchange.techtarget.com/quality-assurance/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" />
		<item>
		<title>Can a Tester be Called Anti Coder</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/can-a-tester-be-called-anti-coder/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/can-a-tester-be-called-anti-coder/#comments</comments>
		<pubDate>Mon, 26 Dec 2011 19:15:55 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[code]]></category>
		<category><![CDATA[coder]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[programmer]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/can-a-tester-be-called-anti-coder/</guid>
		<description><![CDATA[Shall we treat tester as a code destroyer? If on one hand a developer develops a code, a tester always tries to find out the holes in the pot. That is where a conflict on personal level originates when a programmer or coder takes it too personal by getting faults being found out in the [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/can-a-tester-be-called-anti-coder/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An orthodox software project scenario</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/an-orthodox-software-project-scenario/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/an-orthodox-software-project-scenario/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 12:08:12 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[coder]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/an-orthodox-software-project-scenario/</guid>
		<description><![CDATA[In most of the orthodox software project scenarios software testing is a late entry. Mostly testing starts when the coding is finished. The concept of complete code testing prevails where the testers are assumed to conduct testing on the product once it is declared as complete. A whole lot of time has already been consumed [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/an-orthodox-software-project-scenario/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Eight Goal Settings for Software Developers</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/eight-goal-settings-for-software-developers/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/eight-goal-settings-for-software-developers/#comments</comments>
		<pubDate>Mon, 07 Dec 2009 10:00:21 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[coder]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[goal setting]]></category>
		<category><![CDATA[Project]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/eight-goal-settings-for-software-developers/</guid>
		<description><![CDATA[As discussed in previous post, goal setting is a chain reaction. Goal setting by one will definitely force another to set their goal as it is obvious to happen in a team. Project management is a team effort. Like in football, a pass by center to forward enables him to shoot a goal. Let us see how a developer can set some meaningful goals for himself during his role in software development]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/eight-goal-settings-for-software-developers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>20 gems for project managers</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/20-gems-for-project-managers/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/20-gems-for-project-managers/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 10:00:37 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[bug report]]></category>
		<category><![CDATA[coder]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[programmer]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[technical knowledge]]></category>
		<category><![CDATA[tester]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/20-gems-for-project-managers/</guid>
		<description><![CDATA[1.	A project manager is always right
2.	Quality is seriously maintained by developers while developing software
3.	A separate set of people (quality control or testers) is not required to take care of the software produced or developed]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/20-gems-for-project-managers/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Quality of documents says it all about the health of the project</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/quality-of-documents-says-it-all-about-the-health-of-the-project/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/quality-of-documents-says-it-all-about-the-health-of-the-project/#comments</comments>
		<pubDate>Wed, 23 Sep 2009 10:00:52 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business analyst]]></category>
		<category><![CDATA[coder]]></category>
		<category><![CDATA[programmer]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/quality-of-documents-says-it-all-about-the-health-of-the-project/</guid>
		<description><![CDATA[A software project has to undergo various stages before reaching the final stage of customer sign off. At each stage of the project there are certain set of documents that are maintained by the project team for internal or external purposes...]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/quality-of-documents-says-it-all-about-the-health-of-the-project/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Why is Change opposed?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/why-is-change-opposed/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/why-is-change-opposed/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 10:00:52 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[change management]]></category>
		<category><![CDATA[coder]]></category>
		<category><![CDATA[programmer]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/why-is-change-opposed/</guid>
		<description><![CDATA[Change is powerful.
Change is inevitable.
Change does not challenge your knowledge.
Change does not indicate that you are incapable. Rather when one is being told to change, someone has confidence in his capability to CHANGE and PERFORM better.
Change does not mean that you are wrong, it means that there is a scope of improvement.

But...]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/why-is-change-opposed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Project Management – Tasks vs. Milestones</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/project-management-%e2%80%93-tasks-vs-milestones/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/project-management-%e2%80%93-tasks-vs-milestones/#comments</comments>
		<pubDate>Wed, 11 Feb 2009 11:04:04 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[coder]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[programmer]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[project completion]]></category>
		<category><![CDATA[Project Development]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project milestone]]></category>
		<category><![CDATA[project progress]]></category>
		<category><![CDATA[project task]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software team]]></category>
		<category><![CDATA[technical]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/?p=103</guid>
		<description><![CDATA[A new project is always divided into small tasks and based on the resources available, the task(s) are allocated to individuals by the project manager (PM). A simple metrics is important to follow to monitor (and manger) the completion of tasks and thereby figuring out at any moment of time – the progress of the [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/project-management-%e2%80%93-tasks-vs-milestones/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mr. PM, what metrics you use for measuring “Task Completion”</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/mr-pm-what-metrics-you-use-for-measuring-%e2%80%9ctask-completion%e2%80%9d/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/mr-pm-what-metrics-you-use-for-measuring-%e2%80%9ctask-completion%e2%80%9d/#comments</comments>
		<pubDate>Mon, 09 Feb 2009 09:55:41 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[coder]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[PM]]></category>
		<category><![CDATA[programmer]]></category>
		<category><![CDATA[programming]]></category>
		<category><![CDATA[project completion]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project metrics]]></category>
		<category><![CDATA[project progress]]></category>
		<category><![CDATA[Project Status]]></category>
		<category><![CDATA[project task]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/?p=101</guid>
		<description><![CDATA[It is not important what metrics you (the project manager) use, because unless and until you understand the meaning of “task” and “task completion”, you can’t get into the mode of monitoring and measuring it. The progress (or completion) project as a whole is measurable only if it is broken into pieces termed as “tasks”. [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/mr-pm-what-metrics-you-use-for-measuring-%e2%80%9ctask-completion%e2%80%9d/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
