<?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 on: Mullets and Drawing Phases	</title>
	<atom:link href="https://wemberinc.com/mullets-and-drawing-phases/feed/" rel="self" type="application/rss+xml" />
	<link>https://wemberinc.com/mullets-and-drawing-phases/</link>
	<description>Owner&#039;s Representation</description>
	<lastBuildDate>Wed, 27 Sep 2023 15:56:15 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.5</generator>
	<item>
		<title>
		By: Leanne K. Travis		</title>
		<link>https://wemberinc.com/mullets-and-drawing-phases/#comment-32</link>

		<dc:creator><![CDATA[Leanne K. Travis]]></dc:creator>
		<pubDate>Fri, 07 Feb 2014 21:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.wemberinc.com/?p=4582#comment-32</guid>

					<description><![CDATA[The whole essence of QA entails that the requirements are met and the project&#039;s needs are being matched to what the client desires. When the requirements are documented during the beginning of the project, the QA team tries to anticipate any issues that may arise, according what the client wants. This is one reason why QA should closely follow the client&#039;s mindset. Project management, development and business analyst biases should not have a bearing on the process of meeting the requirements. But many times the QA team is controlled, in one way or another, by a timeline, politics or departmental change. When that happens, the project is prone to defects. Of course, defects increase the project&#039;s delivery time and therefore decrease customer satisfaction, ROI for all parties involved, and overall quality.]]></description>
			<content:encoded><![CDATA[<p>The whole essence of QA entails that the requirements are met and the project&#8217;s needs are being matched to what the client desires. When the requirements are documented during the beginning of the project, the QA team tries to anticipate any issues that may arise, according what the client wants. This is one reason why QA should closely follow the client&#8217;s mindset. Project management, development and business analyst biases should not have a bearing on the process of meeting the requirements. But many times the QA team is controlled, in one way or another, by a timeline, politics or departmental change. When that happens, the project is prone to defects. Of course, defects increase the project&#8217;s delivery time and therefore decrease customer satisfaction, ROI for all parties involved, and overall quality.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 

Served from: wemberinc.com @ 2026-04-26 02:30:34 by W3 Total Cache
-->