<?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/"
	>

<channel>
	<title>Frampton Consulting Services &#187; Matt</title>
	<atom:link href="http://www.framptonconsulting.com/author/SQUINTZ76/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.framptonconsulting.com</link>
	<description>Business Services Experts</description>
	<lastBuildDate>Wed, 27 Jan 2010 21:06:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
		<item>
		<title>Client &#8211; Vendor Relationship &amp; Program Mangement: Part 1</title>
		<link>http://www.framptonconsulting.com/client-vendor-relationship-part-1/</link>
		<comments>http://www.framptonconsulting.com/client-vendor-relationship-part-1/#comments</comments>
		<pubDate>Sat, 21 Nov 2009 18:30:06 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[Consulting]]></category>
		<category><![CDATA[client and vendor relationship]]></category>
		<category><![CDATA[it management]]></category>
		<category><![CDATA[it vendor]]></category>
		<category><![CDATA[program management]]></category>
		<category><![CDATA[Project Management]]></category>

		<guid isPermaLink="false">http://www.framptonconsulting.com/?p=100</guid>
		<description><![CDATA[I&#8217;ve been reflecting quite a bit lately on how to help improve the inner workings between client and vendor in the IT arena.  I will add my thoughts and discovery as it comes in, but for now I have enough for a good start. Since recently stepping in as a consultant / sr. program manager [...]]]></description>
		<wfw:commentRss>http://www.framptonconsulting.com/client-vendor-relationship-part-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test Cycle Execution Strategy &#8211; For Major Software Upgrades by Vendor</title>
		<link>http://www.framptonconsulting.com/test-cycle-execution-strategy-for-major-software-upgrades-by-vendor/</link>
		<comments>http://www.framptonconsulting.com/test-cycle-execution-strategy-for-major-software-upgrades-by-vendor/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 18:32:37 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[Consulting]]></category>
		<category><![CDATA[major upgrades]]></category>
		<category><![CDATA[QA test cycles]]></category>
		<category><![CDATA[regression testing]]></category>
		<category><![CDATA[software testing]]></category>
		<category><![CDATA[test efforts]]></category>
		<category><![CDATA[test strategy]]></category>
		<category><![CDATA[testing]]></category>
		<category><![CDATA[testing execution]]></category>

		<guid isPermaLink="false">http://www.framptonconsulting.com/?p=79</guid>
		<description><![CDATA[I recently visited a client to discuss many topics surrounding their software testing and deployment project process.  Though there were many outputs from these meetings, there was a very obvious bottleneck in their QA area of the processes.  Due to this we spent a good deal of time on this and I felt it would [...]]]></description>
		<wfw:commentRss>http://www.framptonconsulting.com/test-cycle-execution-strategy-for-major-software-upgrades-by-vendor/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Standardize your businesses Project Milestones.</title>
		<link>http://www.framptonconsulting.com/standardize-your-businesses-project-milestones/</link>
		<comments>http://www.framptonconsulting.com/standardize-your-businesses-project-milestones/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 15:25:17 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[milestones]]></category>
		<category><![CDATA[project execution]]></category>
		<category><![CDATA[project milestones]]></category>
		<category><![CDATA[project planning]]></category>
		<category><![CDATA[project statuses]]></category>
		<category><![CDATA[standard project status]]></category>

		<guid isPermaLink="false">http://squintz76.fatcow.com/framptonconsulting/?p=69</guid>
		<description><![CDATA[One thing I&#8217;ve seen often is a lack of clear milestone standardization and understanding.  It&#8217;s crucial to all those involved who are part of any project within an organization or who receive updates regarding these projects to know what each milestone may mean. There are many “basic” statuses or milestones for every project within an organization and/or [...]]]></description>
		<wfw:commentRss>http://www.framptonconsulting.com/standardize-your-businesses-project-milestones/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Merger: Processes can evolve!</title>
		<link>http://www.framptonconsulting.com/merger-processes-can-evolve/</link>
		<comments>http://www.framptonconsulting.com/merger-processes-can-evolve/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 03:26:37 +0000</pubDate>
		<dc:creator>Matt</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[merger process]]></category>
		<category><![CDATA[process]]></category>
		<category><![CDATA[project processes]]></category>

		<guid isPermaLink="false">http://mattframpton.wordpress.com/?p=8</guid>
		<description><![CDATA[In 2007, while working for a vendor in banking operations &#8211; lockbox processing to be specific &#8211; we went through a merger with one of our stiffest competitors.  It was one of the most challenging processes I have ever encountered, as most mergers are.  Our company had been growing, our leaders were young and dynamic and [...]]]></description>
		<wfw:commentRss>http://www.framptonconsulting.com/merger-processes-can-evolve/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

