 




<?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; stakeholder</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/tag/stakeholder/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>Ten Ideas to consider Customer Key Users as Major Stakeholders In Software Project</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-ideas-to-consider-customer-key-users-as-major-stakeholders-in-software-project/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-ideas-to-consider-customer-key-users-as-major-stakeholders-in-software-project/#comments</comments>
		<pubDate>Mon, 15 Mar 2010 11:55:35 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[key user]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[stakeholder]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/ten-ideas-to-consider-customer-key-users-as-major-stakeholders-in-software-project/</guid>
		<description><![CDATA[1. Key users are selected based on their organization engagement, knowledge about the business; and their own area expertise. 2. The selection criteria also depend on their openness and acceptance to adaptability, manageability, and their goodwill. 3. Key users play a major role in representing their organization in terms of defining business requirements to the [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-ideas-to-consider-customer-key-users-as-major-stakeholders-in-software-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five Points to do Justice with Your Project Information</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-points-to-do-justice-with-your-project-information/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-points-to-do-justice-with-your-project-information/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 12:13:21 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Development Manager]]></category>
		<category><![CDATA[project information]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[quality manager]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[stakeholder]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-points-to-do-justice-with-your-project-information/</guid>
		<description><![CDATA[You might be a project manager, senior management, customer management, customer project manager, quality manager, development manager, business manager. That makes you an active and responsible stakeholder in the project. Your role is not just to release or collect that piece of information at regular intervals; and dump it. If you do that, you will [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-points-to-do-justice-with-your-project-information/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why hit the people? Hit the process if there is a failure in a software project</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/why-hit-the-people-hit-the-process-if-there-is-a-failure-in-a-software-project/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/why-hit-the-people-hit-the-process-if-there-is-a-failure-in-a-software-project/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 10:00:30 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business analyst]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[development team]]></category>
		<category><![CDATA[HR]]></category>
		<category><![CDATA[implementation team]]></category>
		<category><![CDATA[people management]]></category>
		<category><![CDATA[product]]></category>
		<category><![CDATA[product build]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project team]]></category>
		<category><![CDATA[Q-tag]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[quality building]]></category>
		<category><![CDATA[quality culture]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[stakeholder]]></category>
		<category><![CDATA[testing team]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/why-hit-the-people-hit-the-process-if-there-is-a-failure-in-a-software-project/</guid>
		<description><![CDATA[People are not wrong, processes are. People in an organization do what they are told to do. Organizations who hit on people at the time of failure are not doing the right thing. It is the process that is to be blamed not the person with Q-tag. As long as quality is considered to be the child of people with Q-tag in the organization, and the culture is so around, the non Q-tag people will keep themselves enjoying building a product without quality. Why not blame the developers for developing so many bugs along with the requirements building. Why not blame the analysts who could not understand or translate the requirements correctly. Why not blame the management for not putting the right people and process at right place. This blame game itself is merely a scapegoat in any organization until the focus shifts from people to process enhancement.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/why-hit-the-people-hit-the-process-if-there-is-a-failure-in-a-software-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Who owns the Q-Tag in a software development company?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/who-owns-the-q-tag-in-a-software-development-company/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/who-owns-the-q-tag-in-a-software-development-company/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 10:00:20 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Bug]]></category>
		<category><![CDATA[bugs report]]></category>
		<category><![CDATA[business analyst]]></category>
		<category><![CDATA[development team]]></category>
		<category><![CDATA[implementation team]]></category>
		<category><![CDATA[product approval]]></category>
		<category><![CDATA[project implementation]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project management framework]]></category>
		<category><![CDATA[project methodology]]></category>
		<category><![CDATA[project team]]></category>
		<category><![CDATA[Q-tag]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[Quality-tag]]></category>
		<category><![CDATA[re-testing]]></category>
		<category><![CDATA[software build]]></category>
		<category><![CDATA[software implementation]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[stakeholder]]></category>
		<category><![CDATA[team]]></category>
		<category><![CDATA[test report]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[testing team]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/who-owns-the-q-tag-in-a-software-development-company/</guid>
		<description><![CDATA[Q-tag has to be on each of the stakeholder in a software project. When each and every person wears a Q-tag – the analysis, building, testing and implementation will be more justified. Otherwise there will always be a big question at the time of failure of a product build – that who is responsible? 
]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/who-owns-the-q-tag-in-a-software-development-company/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fifteen Checkpoints for project managers &#8211; if your commitment towards project merely a Pretence?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/fifteen-checkpoints-for-project-managers-if-your-commitment-towards-project-merely-a-pretence/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/fifteen-checkpoints-for-project-managers-if-your-commitment-towards-project-merely-a-pretence/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 10:00:51 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[checkpoints]]></category>
		<category><![CDATA[commitment]]></category>
		<category><![CDATA[pretence]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[stakeholder]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/fifteen-checkpoints-for-project-managers-if-your-commitment-towards-project-merely-a-pretence/</guid>
		<description><![CDATA[
Projects do happen with the beliefs and actions mentioned above. Whether they end up in good or bad state, I am not sure. PMs do exist with these beliefs and actions. But they have to change themselves over a period of time, I am sure.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/fifteen-checkpoints-for-project-managers-if-your-commitment-towards-project-merely-a-pretence/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five Reasons of outsourcing</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-reasons-of-outsourcing/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-reasons-of-outsourcing/#comments</comments>
		<pubDate>Thu, 25 Jun 2009 10:00:46 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[offloading]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project outsourcing]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[stakeholder]]></category>
		<category><![CDATA[third party]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-reasons-of-outsourcing/</guid>
		<description><![CDATA[
Definitely in offloading the vendor-customer chain becomes longer depending on number of components of a project outsourced and the number of vendors involved. Even for a single component of a project there can be more than one vendor. And for a number of components of a project there can be a single vendor. ]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-reasons-of-outsourcing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Role of Vendor and Customer in managing User Manuals</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/role-of-vendor-and-customer-in-managing-user-manuals/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/role-of-vendor-and-customer-in-managing-user-manuals/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 10:00:11 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[build phase]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[project quality]]></category>
		<category><![CDATA[project team]]></category>
		<category><![CDATA[project walkthrough]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[stakeholder]]></category>
		<category><![CDATA[User Manual]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/role-of-vendor-and-customer-in-managing-user-manuals/</guid>
		<description><![CDATA[As already has been discussed, User Manuals play a crucial role in any software project and are the solid bonding between product, users, customer management and vendor project team. The stronger this bond is the more comfortable and happy each stakeholder will be. Each player has to play a crucial role during the game of building of User Manuals. Both Project Management teams have to work hand in hand for that.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/role-of-vendor-and-customer-in-managing-user-manuals/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why User Manuals are so important in Software Project Management</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/why-user-manuals-are-so-important-in-software-project-management/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/why-user-manuals-are-so-important-in-software-project-management/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 10:00:08 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[analytic]]></category>
		<category><![CDATA[business scenario]]></category>
		<category><![CDATA[durability]]></category>
		<category><![CDATA[feel and look]]></category>
		<category><![CDATA[implementation team]]></category>
		<category><![CDATA[key user]]></category>
		<category><![CDATA[live run]]></category>
		<category><![CDATA[post implementation]]></category>
		<category><![CDATA[product support]]></category>
		<category><![CDATA[product training]]></category>
		<category><![CDATA[project implementation]]></category>
		<category><![CDATA[project sign-off]]></category>
		<category><![CDATA[project support]]></category>
		<category><![CDATA[project team]]></category>
		<category><![CDATA[reliability]]></category>
		<category><![CDATA[report]]></category>
		<category><![CDATA[sign-off]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software project management]]></category>
		<category><![CDATA[software training]]></category>
		<category><![CDATA[stability]]></category>
		<category><![CDATA[stakeholder]]></category>
		<category><![CDATA[training team]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[user feedback]]></category>
		<category><![CDATA[User Manual]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/why-user-manuals-are-so-important-in-software-project-management/</guid>
		<description><![CDATA[The product owners or stakeholders might be many in a software project, but the real frontrunners who drive, run and use the software product post implementation are the key users and other users. It is their feedback that matters most. They must be the most comfortable lot on usability, functionality, reliability, stability, durability, resultant outputs in terms of reports and analytics, feel and look of the product. They are the one who are going to matter most in the success or failure of a product during and post implementation. The best tool to give them comfort, satisfaction, confidence and support is the User Manuals that they refer to most of the time during post implementation live run. ]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/why-user-manuals-are-so-important-in-software-project-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Application developed, tested and built well does not ensure successful implementation</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/application-developed-tested-and-built-well-does-not-ensure-successful-implementation/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/application-developed-tested-and-built-well-does-not-ensure-successful-implementation/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 09:59:13 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Application development]]></category>
		<category><![CDATA[application implementation]]></category>
		<category><![CDATA[application readiness]]></category>
		<category><![CDATA[post implementation]]></category>
		<category><![CDATA[project director]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project sponsor]]></category>
		<category><![CDATA[project vision]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software implementation]]></category>
		<category><![CDATA[software project manager]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[stakeholder]]></category>
		<category><![CDATA[successful implementation]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/application-developed-tested-and-built-well-does-not-ensure-successful-implementation/</guid>
		<description><![CDATA[The product may have been developed well, tested well and built well to launch, but what happens if some soft issues that may arise during implementation or even post implementation period are overlooked. It could lead to a disaster…]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/application-developed-tested-and-built-well-does-not-ensure-successful-implementation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
