<?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; project phase</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/quality-assurance/tag/project-phase/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>Mon, 17 Jun 2013 16:21:04 +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>Various Tangential Impacts of Project Management</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/various-tangential-impacts-of-project-management/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/various-tangential-impacts-of-project-management/#comments</comments>
		<pubDate>Wed, 11 Jan 2012 17:45:55 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[project execution]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project phase]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/various-tangential-impacts-of-project-management/</guid>
		<description><![CDATA[Probably it is quite uncertain to predict that a project will run smooth throughout and will face no troubles of any kind during its any of the phases. It is practically impossible to believe it and claim at all about any kind of project sizing from very small to any big size. Troubles and hiccups [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/various-tangential-impacts-of-project-management/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Most Of Software Delays Are Because Of No Proper Requirements Gathered</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/most-of-software-delays-are-because-of-no-proper-requirements-gathered/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/most-of-software-delays-are-because-of-no-proper-requirements-gathered/#comments</comments>
		<pubDate>Sat, 16 Apr 2011 09:22:50 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[development phase]]></category>
		<category><![CDATA[implementation phase]]></category>
		<category><![CDATA[project gap]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[Project Risk]]></category>
		<category><![CDATA[requirement gathering]]></category>
		<category><![CDATA[requirement phase]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[testing phase]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/most-of-software-delays-are-because-of-no-proper-requirements-gathered/</guid>
		<description><![CDATA[Most of the times the software delays are because of no proper requirements are gathered. Reasons of this could be many like lack of business knowledge of Requirement Gathering Team leaders, lack of experience, inappropriate allocation of time, wrong choice of customer representatives for understanding of business process and requirements and so on. In such [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/most-of-software-delays-are-because-of-no-proper-requirements-gathered/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Five Operational Tactics Project Manager Needs to Understand</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/five-operational-tactics-project-manager-needs-to-understand/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/five-operational-tactics-project-manager-needs-to-understand/#comments</comments>
		<pubDate>Fri, 19 Mar 2010 12:07:02 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[milestone]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[project stage]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/five-operational-tactics-project-manager-needs-to-understand/</guid>
		<description><![CDATA[1. During all the project management phases, each process should be clearly having operational key indicator metrics to measure the health of the project at any stage. 2. Approvals, decisions, milestones, tasks, micro tasks should not become a hurdle for the project. 3. People driven project has less chances of growth as compared to a [...]]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/five-operational-tactics-project-manager-needs-to-understand/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Requirements evolve during a Software Project?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/how-requirements-evolve-during-a-software-project/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/how-requirements-evolve-during-a-software-project/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 10:00:04 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[change management]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/how-requirements-evolve-during-a-software-project/</guid>
		<description><![CDATA[New requirements or change in existing requirements is an inevitable process in any software project. As a project manager you encounter it during every phase of a project. Some requirements emerge internally by your own team and some come from the customer.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/how-requirements-evolve-during-a-software-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Project Lifecycle – 2012</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/project-lifecycle-%e2%80%93-2012/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/project-lifecycle-%e2%80%93-2012/#comments</comments>
		<pubDate>Fri, 09 Oct 2009 06:29:44 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[developer]]></category>
		<category><![CDATA[implementation]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[project team]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[software product]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[tester]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/project-lifecycle-%e2%80%93-2012/</guid>
		<description><![CDATA[Phase I: There is nothing called ‘off the shelf” product. It is all ‘made-to-fit’ technique. You specify your requirements and that too at a broader level. For micro level leave a red-mark at areas that need to be looked into at the time of building of software. The more red-marks will mean less precise plan and deadlines. The sooner we are able to convert these red-marks (not clearly known ones) to the clearly defied requirements, the better plan we can submit...]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/project-lifecycle-%e2%80%93-2012/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What is the ‘unit to measure’ your project progress?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-the-%e2%80%98unit-to-measure%e2%80%99-your-project-progress/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-the-%e2%80%98unit-to-measure%e2%80%99-your-project-progress/#comments</comments>
		<pubDate>Fri, 25 Sep 2009 10:00:16 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[implementation]]></category>
		<category><![CDATA[live run]]></category>
		<category><![CDATA[project closure]]></category>
		<category><![CDATA[project execution]]></category>
		<category><![CDATA[project feedback]]></category>
		<category><![CDATA[project initiation]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project milestone]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[project progress]]></category>
		<category><![CDATA[project task]]></category>
		<category><![CDATA[project team]]></category>
		<category><![CDATA[QC]]></category>
		<category><![CDATA[sign-off]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[test report]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[UAT]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-the-%e2%80%98unit-to-measure%e2%80%99-your-project-progress/</guid>
		<description><![CDATA[A project starts with initiation phase and ends up with project closure report. Then afterwards there is post project feedback (after a considerable amount of time given to the customer to get conversant with the product) and warranty support followed by support contracts over a period of time.  Let us begin our story with the project initiation and proposal approval from customer. The real ball-game starts from here.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/what-is-the-%e2%80%98unit-to-measure%e2%80%99-your-project-progress/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Seven Questions on ‘Average Cycle Time’ of your projects?</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/seven-questions-on-%e2%80%98average-cycle-time%e2%80%99-of-your-projects/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/seven-questions-on-%e2%80%98average-cycle-time%e2%80%99-of-your-projects/#comments</comments>
		<pubDate>Wed, 12 Aug 2009 10:00:33 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[Project]]></category>
		<category><![CDATA[project execution]]></category>
		<category><![CDATA[Project Lifecycle]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[Software Project]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/seven-questions-on-%e2%80%98average-cycle-time%e2%80%99-of-your-projects/</guid>
		<description><![CDATA[Do you know average game is successful for similar types?
An average cycle time worked out for similar set of projects falling in one category will work best for you for your future estimations and meeting those estimations. Else average may not work well and estimations may go haywired.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/seven-questions-on-%e2%80%98average-cycle-time%e2%80%99-of-your-projects/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>If you don’t change with the ‘Change’ you get [ex][change]d</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/if-you-don%e2%80%99t-change-with-the-%e2%80%98change%e2%80%99-you-get-exchanged/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/if-you-don%e2%80%99t-change-with-the-%e2%80%98change%e2%80%99-you-get-exchanged/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 10:00:17 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business requirement]]></category>
		<category><![CDATA[change management]]></category>
		<category><![CDATA[customer requirement]]></category>
		<category><![CDATA[development phase]]></category>
		<category><![CDATA[product delay]]></category>
		<category><![CDATA[product launch]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[project timelines]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[software build]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[test phase]]></category>
		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/if-you-don%e2%80%99t-change-with-the-%e2%80%98change%e2%80%99-you-get-exchanged/</guid>
		<description><![CDATA[The requirements keep changing, as the business. Only thing that varies is the pace of change in requirements. Overlooking changes happening in the business process at customer end after freezing requirements will result only in undesirable product. Both customer and vendor have to understand this and keep overseeing the changes rather than overlooking.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/if-you-don%e2%80%99t-change-with-the-%e2%80%98change%e2%80%99-you-get-exchanged/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Outsource in a software project without losing control over it</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/outsource-in-a-software-project-without-losing-control-over-it/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/outsource-in-a-software-project-without-losing-control-over-it/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 10:00:33 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[documentation]]></category>
		<category><![CDATA[handholding]]></category>
		<category><![CDATA[outsourcing]]></category>
		<category><![CDATA[post implementation]]></category>
		<category><![CDATA[project component]]></category>
		<category><![CDATA[project control]]></category>
		<category><![CDATA[project execution]]></category>
		<category><![CDATA[project implementation]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project offload]]></category>
		<category><![CDATA[project outsource]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[requirement analysis]]></category>
		<category><![CDATA[requirement freezing]]></category>
		<category><![CDATA[requirement gathering]]></category>
		<category><![CDATA[software design]]></category>
		<category><![CDATA[software development]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[training]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/outsource-in-a-software-project-without-losing-control-over-it/</guid>
		<description><![CDATA[
We are talking about outsourcing an activity of a software project. The most important components of a software project can be listed as:
Requirement analysis, gathering and freezing
Design, development and testing
Documentation
Implementation, training and hand-holding
Post implementation support
]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/outsource-in-a-software-project-without-losing-control-over-it/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>Ten Reasons of getting into pitfall of leaving a scope of software development at customer site</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-reasons-of-getting-into-pitfall-of-leaving-a-scope-of-software-development-at-customer-site/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-reasons-of-getting-into-pitfall-of-leaving-a-scope-of-software-development-at-customer-site/#comments</comments>
		<pubDate>Wed, 10 Jun 2009 10:00:54 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business analysis]]></category>
		<category><![CDATA[business analyst]]></category>
		<category><![CDATA[business requirement study]]></category>
		<category><![CDATA[change management]]></category>
		<category><![CDATA[developer]]></category>
		<category><![CDATA[implementation phase]]></category>
		<category><![CDATA[implementer]]></category>
		<category><![CDATA[key user]]></category>
		<category><![CDATA[project director]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project manager]]></category>
		<category><![CDATA[project organization]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[project sponsor]]></category>
		<category><![CDATA[requirement analysis]]></category>
		<category><![CDATA[requirement gathering]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[technical lead]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/ten-reasons-of-getting-into-pitfall-of-leaving-a-scope-of-software-development-at-customer-site/</guid>
		<description><![CDATA[In the previous post we learnt what all could a software project could lead to in presence of higher scope of software development at customer site during implementation phase. Let us see what all factors are responsible of insufficient requirement gathering during business study phase of a project.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/ten-reasons-of-getting-into-pitfall-of-leaving-a-scope-of-software-development-at-customer-site/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 reasons of top level customer expectations missing in requirement study document</title>
		<link>http://itknowledgeexchange.techtarget.com/quality-assurance/5-reasons-of-top-level-customer-expectations-missing-in-requirement-study-document/</link>
		<comments>http://itknowledgeexchange.techtarget.com/quality-assurance/5-reasons-of-top-level-customer-expectations-missing-in-requirement-study-document/#comments</comments>
		<pubDate>Fri, 22 May 2009 10:00:03 +0000</pubDate>
		<dc:creator>Jaideep Khanduja</dc:creator>
				<category><![CDATA[business requirement]]></category>
		<category><![CDATA[organization level requirement]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project phase]]></category>
		<category><![CDATA[requirement study]]></category>
		<category><![CDATA[requirement study document]]></category>
		<category><![CDATA[Software Project]]></category>
		<category><![CDATA[Top level expectations]]></category>
		<category><![CDATA[top management]]></category>
		<category><![CDATA[user level requirement]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/quality-assurance/5-reasons-of-top-level-customer-expectations-missing-in-requirement-study-document/</guid>
		<description><![CDATA[

As stated in previous two blogs, top level expectations gathering is very crucial during the business study and requirement gathering phase. And respectively I mentioned how vendor and customer can be careful (and should be) about that. Although it is rare and unexpected, but there are instances where customer organization top level management may not involve in a new software development project. This could have various reasons but could lead to only a single road – where the end is DISASTER.]]></description>
		<wfw:commentRss>http://itknowledgeexchange.techtarget.com/quality-assurance/5-reasons-of-top-level-customer-expectations-missing-in-requirement-study-document/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
