<?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 for PT Designs</title>
	<atom:link href="http://www.pham-tom.com/ptdesigns/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pham-tom.com/ptdesigns</link>
	<description></description>
	<lastBuildDate>Wed, 27 Apr 2011 05:45:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on Comic Style to Explain Process by Michal Pisarek</title>
		<link>http://www.pham-tom.com/ptdesigns/design/226/comment-page-1#comment-43</link>
		<dc:creator>Michal Pisarek</dc:creator>
		<pubDate>Wed, 27 Apr 2011 05:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=226#comment-43</guid>
		<description>Nice work! I really like this idea of communicating to clients!</description>
		<content:encoded><![CDATA[<p>Nice work! I really like this idea of communicating to clients!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Misuse of Visual Continuity by USB 3G</title>
		<link>http://www.pham-tom.com/ptdesigns/design/85/comment-page-1#comment-42</link>
		<dc:creator>USB 3G</dc:creator>
		<pubDate>Thu, 24 Mar 2011 10:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=85#comment-42</guid>
		<description>Nice, that&#039;s helpful for me!</description>
		<content:encoded><![CDATA[<p>Nice, that&#8217;s helpful for me!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SharePoint Out-of-the-Box Solution Approach by Tom Pham</title>
		<link>http://www.pham-tom.com/ptdesigns/sharepoint/210/comment-page-1#comment-41</link>
		<dc:creator>Tom Pham</dc:creator>
		<pubDate>Thu, 02 Dec 2010 23:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=210#comment-41</guid>
		<description>I would have to agree with the OOTB in-house developers.  To be safe, I&#039;d say a little more than 30 hours to provide documentation/training materials and UAT.  The only thing I&#039;d throw caution in the wind about would be for maybe a loss of fidelity in the look &amp; feel but overall it sounds like most of what you&#039;re looking for can be thrown together using look-up tables, filters/views, site columns and permission assignments. 

Best of luck!</description>
		<content:encoded><![CDATA[<p>I would have to agree with the OOTB in-house developers.  To be safe, I&#8217;d say a little more than 30 hours to provide documentation/training materials and UAT.  The only thing I&#8217;d throw caution in the wind about would be for maybe a loss of fidelity in the look &amp; feel but overall it sounds like most of what you&#8217;re looking for can be thrown together using look-up tables, filters/views, site columns and permission assignments. </p>
<p>Best of luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SharePoint Out-of-the-Box Solution Approach by Tom Pham</title>
		<link>http://www.pham-tom.com/ptdesigns/sharepoint/210/comment-page-1#comment-40</link>
		<dc:creator>Tom Pham</dc:creator>
		<pubDate>Thu, 02 Dec 2010 23:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=210#comment-40</guid>
		<description>I would have to agree with the OOTB in-house developers.  To be safe, I&#039;d say a little more than 30 hours to provide documentation/training materials and UAT.  The only thing I&#039;d throw caution in the wind about would be for maybe a loss of fidelity in the look &amp; feel but overall it sounds like most of what you&#039;re looking for can be thrown together using look-up tables, filters/views, site columns and permission assignments. 

Best of luck!</description>
		<content:encoded><![CDATA[<p>I would have to agree with the OOTB in-house developers.  To be safe, I&#8217;d say a little more than 30 hours to provide documentation/training materials and UAT.  The only thing I&#8217;d throw caution in the wind about would be for maybe a loss of fidelity in the look &amp; feel but overall it sounds like most of what you&#8217;re looking for can be thrown together using look-up tables, filters/views, site columns and permission assignments. </p>
<p>Best of luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SharePoint Out-of-the-Box Solution Approach by Estes</title>
		<link>http://www.pham-tom.com/ptdesigns/sharepoint/210/comment-page-1#comment-39</link>
		<dc:creator>Estes</dc:creator>
		<pubDate>Thu, 02 Dec 2010 23:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=210#comment-39</guid>
		<description>Came across your site after having been told that my estimate of hours for developing an Intranet SharePoint solution for Petty Cash was way overblown (minimum of 200 hours). I did not use an Agile methodogy and must confess that my knowledge of SharePoint is quite limited, but knowing that the Director wanted several layers of Automation including look-ups for Dept, Employee, GL accounts from GP, Cyber Signatures and email notifications, I added additional time for UAT reworks and documentation. OOTB in-house developers believe it can be done in a matter of about 30 hours! Am I that far off in estimations of SharePoint solution development?</description>
		<content:encoded><![CDATA[<p>Came across your site after having been told that my estimate of hours for developing an Intranet SharePoint solution for Petty Cash was way overblown (minimum of 200 hours). I did not use an Agile methodogy and must confess that my knowledge of SharePoint is quite limited, but knowing that the Director wanted several layers of Automation including look-ups for Dept, Employee, GL accounts from GP, Cyber Signatures and email notifications, I added additional time for UAT reworks and documentation. OOTB in-house developers believe it can be done in a matter of about 30 hours! Am I that far off in estimations of SharePoint solution development?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Being a SharePoint Business Analyst by Tom Pham</title>
		<link>http://www.pham-tom.com/ptdesigns/client-projects/92/comment-page-1#comment-38</link>
		<dc:creator>Tom Pham</dc:creator>
		<pubDate>Tue, 12 Oct 2010 13:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=92#comment-38</guid>
		<description>Instead of creating a new field &quot;Last Updated Date&quot;, there is already a field that does this.  It&#039;s called &quot;Modified&quot;.  But it looks like it all worked out.  :)</description>
		<content:encoded><![CDATA[<p>Instead of creating a new field &#8220;Last Updated Date&#8221;, there is already a field that does this.  It&#8217;s called &#8220;Modified&#8221;.  But it looks like it all worked out.  <img src='http://www.pham-tom.com/ptdesigns/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Being a SharePoint Business Analyst by Ewen1</title>
		<link>http://www.pham-tom.com/ptdesigns/client-projects/92/comment-page-1#comment-37</link>
		<dc:creator>Ewen1</dc:creator>
		<pubDate>Wed, 29 Sep 2010 22:38:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=92#comment-37</guid>
		<description>Thanks Tom! I think I figured out another solution. I made a new field “Last Updated Date.” It is required and the default is the current date. When user updates the comments, the date is automatically populated. So when we export the list, it shows the new comment and date it was updated. </description>
		<content:encoded><![CDATA[<p>Thanks Tom! I think I figured out another solution. I made a new field “Last Updated Date.” It is required and the default is the current date. When user updates the comments, the date is automatically populated. So when we export the list, it shows the new comment and date it was updated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Being a SharePoint Business Analyst by Tom Pham</title>
		<link>http://www.pham-tom.com/ptdesigns/client-projects/92/comment-page-1#comment-36</link>
		<dc:creator>Tom Pham</dc:creator>
		<pubDate>Wed, 29 Sep 2010 16:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=92#comment-36</guid>
		<description>Depending on your rights, you should be able to modify your view to include &quot;modified&quot; or &quot;created&quot;.

Once you do this, and it is displaying all the columns you need it to display, just export it to Excel.

Hope this helps.</description>
		<content:encoded><![CDATA[<p>Depending on your rights, you should be able to modify your view to include &#8220;modified&#8221; or &#8220;created&#8221;.</p>
<p>Once you do this, and it is displaying all the columns you need it to display, just export it to Excel.</p>
<p>Hope this helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Being a SharePoint Business Analyst by Ewen1</title>
		<link>http://www.pham-tom.com/ptdesigns/client-projects/92/comment-page-1#comment-35</link>
		<dc:creator>Ewen1</dc:creator>
		<pubDate>Wed, 29 Sep 2010 16:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=92#comment-35</guid>
		<description>Hi Tom, I am using a list in Share Point to track help desk tickets. I would like to export my list to a spreadsheet so I can print it and take it to meetings. It would be helpful if there was a time/date stamp so I know when the comment was entered. This would help me to discuss the status more accurately. Make sense?
 
I found some freeware, but apparently they don&#039;t allow freeware on production servers. (makes sense) 

Thanks for your help!</description>
		<content:encoded><![CDATA[<p>Hi Tom, I am using a list in Share Point to track help desk tickets. I would like to export my list to a spreadsheet so I can print it and take it to meetings. It would be helpful if there was a time/date stamp so I know when the comment was entered. This would help me to discuss the status more accurately. Make sense?</p>
<p>I found some freeware, but apparently they don&#8217;t allow freeware on production servers. (makes sense) </p>
<p>Thanks for your help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Being a SharePoint Business Analyst by Tom Pham</title>
		<link>http://www.pham-tom.com/ptdesigns/client-projects/92/comment-page-1#comment-34</link>
		<dc:creator>Tom Pham</dc:creator>
		<pubDate>Wed, 29 Sep 2010 16:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.pham-tom.com/ptdesigns/?p=92#comment-34</guid>
		<description>@Ewen1
&lt;br&gt;
&lt;br&gt;The short answer, no.  With OOTB, all you can really do is move it from one location to another.  I am currently researching a similar solution whereby the user wants to migrate an entire blog/wiki while keeping the timestamps.  I believe that DocAve might have some features that allow this.  Will keep you posted.</description>
		<content:encoded><![CDATA[<p>@Ewen1</p>
<p>The short answer, no.  With OOTB, all you can really do is move it from one location to another.  I am currently researching a similar solution whereby the user wants to migrate an entire blog/wiki while keeping the timestamps.  I believe that DocAve might have some features that allow this.  Will keep you posted.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

