<?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: Real Web Project Management: Case Studies and Best Practices from the Trenches</title>
	<atom:link href="http://www.clementfaria.com/blog/real-web-project-management-case-studies-and-best-practices-from-the-trenches/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.clementfaria.com/blog/real-web-project-management-case-studies-and-best-practices-from-the-trenches/</link>
	<description>A Web Developer&#039;s Journal</description>
	<lastBuildDate>Sat, 30 Jul 2011 06:30:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Raymond Brigleb</title>
		<link>http://www.clementfaria.com/blog/real-web-project-management-case-studies-and-best-practices-from-the-trenches/comment-page-1/#comment-1563</link>
		<dc:creator>Raymond Brigleb</dc:creator>
		<pubDate>Thu, 19 Nov 2009 15:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.clementfaria.com/blog/?p=385#comment-1563</guid>
		<description>I liked this book, really I did. But half the reason I bought it was in hopes that I could find the stuff on the CD useful. Unfortunately, half the stuff on the CD was windows-only, which excludes UNIX and, more importantly, the majority of graphic designers who use Mac computers, such as myself. This flaw is also obvious in the book - anyone unwilling to purchase a windows system and Microsoft Project is SOL. Frustrating.&lt;p&gt;I should say that I also felt the book could be a little bit more specific about invoicing and billing clients. The interview on Extreme Programming (?) was more topical here! Overall, though, it&#039;s a pretty good book, but probably not warranting all the five stars!
Rating: 3 / 5</description>
		<content:encoded><![CDATA[<p>I liked this book, really I did. But half the reason I bought it was in hopes that I could find the stuff on the CD useful. Unfortunately, half the stuff on the CD was windows-only, which excludes UNIX and, more importantly, the majority of graphic designers who use Mac computers, such as myself. This flaw is also obvious in the book &#8211; anyone unwilling to purchase a windows system and Microsoft Project is SOL. Frustrating.
<p>I should say that I also felt the book could be a little bit more specific about invoicing and billing clients. The interview on Extreme Programming (?) was more topical here! Overall, though, it&#8217;s a pretty good book, but probably not warranting all the five stars!<br />
Rating: 3 / 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: S. Harrison</title>
		<link>http://www.clementfaria.com/blog/real-web-project-management-case-studies-and-best-practices-from-the-trenches/comment-page-1/#comment-1562</link>
		<dc:creator>S. Harrison</dc:creator>
		<pubDate>Thu, 19 Nov 2009 12:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.clementfaria.com/blog/?p=385#comment-1562</guid>
		<description>As someone who has been running web projects for quite some time, I found this book to be a bit basic.  On the other hand, I wish that I had this book when I first started being responsible for web projects.  Some of the information in this book is just plain good old fashioned advice on project management in general.  It has very specific information regarding the people you need on your project - the information architect, the visual designer, the database person, etc.  More importantly, it has information on how to work with these people successfully, and what you can do to make sure that you deliver the product to the customer&#039;s satisfaction.  Even as someone with web project experience, I am not disappointed in this book at all.  It never hurts to go back and revisit the basics, especially when things start going sideways in a project.
Rating: 4 / 5</description>
		<content:encoded><![CDATA[<p>As someone who has been running web projects for quite some time, I found this book to be a bit basic.  On the other hand, I wish that I had this book when I first started being responsible for web projects.  Some of the information in this book is just plain good old fashioned advice on project management in general.  It has very specific information regarding the people you need on your project &#8211; the information architect, the visual designer, the database person, etc.  More importantly, it has information on how to work with these people successfully, and what you can do to make sure that you deliver the product to the customer&#8217;s satisfaction.  Even as someone with web project experience, I am not disappointed in this book at all.  It never hurts to go back and revisit the basics, especially when things start going sideways in a project.<br />
Rating: 4 / 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mihail Najdenov</title>
		<link>http://www.clementfaria.com/blog/real-web-project-management-case-studies-and-best-practices-from-the-trenches/comment-page-1/#comment-1561</link>
		<dc:creator>Mihail Najdenov</dc:creator>
		<pubDate>Thu, 19 Nov 2009 10:34:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.clementfaria.com/blog/?p=385#comment-1561</guid>
		<description>It is true.
&lt;br /&gt;
&lt;br /&gt;I was wondering: Why, given clints and good &quot;implementors&quot;-developers and designers (we are a small team), things go ugly every time?
&lt;br /&gt;This book gave me the answer - Poor management!
&lt;br /&gt;
&lt;br /&gt;P.S This is my first book review ever.
&lt;br /&gt;
&lt;br /&gt;-----------
&lt;br /&gt;sorry for my English
Rating: 5 / 5</description>
		<content:encoded><![CDATA[<p>It is true.</p>
<p>I was wondering: Why, given clints and good &#8220;implementors&#8221;-developers and designers (we are a small team), things go ugly every time?<br />
<br />This book gave me the answer &#8211; Poor management!</p>
<p>P.S This is my first book review ever.</p>
<p>&#8212;&#8212;&#8212;&#8211;<br />
<br />sorry for my English<br />
Rating: 5 / 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: barbaros ozdogan</title>
		<link>http://www.clementfaria.com/blog/real-web-project-management-case-studies-and-best-practices-from-the-trenches/comment-page-1/#comment-1560</link>
		<dc:creator>barbaros ozdogan</dc:creator>
		<pubDate>Thu, 19 Nov 2009 07:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.clementfaria.com/blog/?p=385#comment-1560</guid>
		<description>I use this book for my Web project management class at Mercy College&#039;s MS in Internet Business Systems program. It covers all the details of a web project life cycle. Students find the book very informative.
Rating: 5 / 5</description>
		<content:encoded><![CDATA[<p>I use this book for my Web project management class at Mercy College&#8217;s MS in Internet Business Systems program. It covers all the details of a web project life cycle. Students find the book very informative.<br />
Rating: 5 / 5</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jain Dow</title>
		<link>http://www.clementfaria.com/blog/real-web-project-management-case-studies-and-best-practices-from-the-trenches/comment-page-1/#comment-1559</link>
		<dc:creator>Jain Dow</dc:creator>
		<pubDate>Thu, 19 Nov 2009 05:43:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.clementfaria.com/blog/?p=385#comment-1559</guid>
		<description>This book is a great book about project management for the web.  It is insightful and provides very useful information.  I especially liked Chapter 5 - Managing Change - and how the authors addressed common problems by providing a bulleted list of the symptoms and solutions to each type of problem.  The authors&#039; use of bulleted lists throughout the book work well and assist the reader with identifying key issues and/or things to think about.  They also make it easy for the reader to quickly refer back to things and skim.       
&lt;br /&gt;
&lt;br /&gt;However, with that said, there is a minor editoral issue with this book.    Everytime a bulleted list is presented the text leading into the list ends in a period (.) rather than a colon (:).
&lt;br /&gt;
&lt;br /&gt;To illustrate: 
&lt;br /&gt;- on pg 66, &quot;Here are some tips for conducting a needs assessment.&quot; And the bulleted list follows.
&lt;br /&gt;- on pg 186, &quot;...and they will be testing for bugs or defects in some or all of the following areas.&quot;  And the bulleted list follows.
&lt;br /&gt;- on pg 268, &quot;Here are some examples of successful Open Source products that are in widespread commercial use.&quot;  And the bulleted list follows.
&lt;br /&gt;
&lt;br /&gt;Having served as an Editor for several professional academic journals, this drove me absolutely mad every time I saw it.  If the authors/editors of this book are going to be wrong, at least they are consistently wrong 100% of the time... which I believe is actually less maddenning then if they had gotten it right only some of the time.
&lt;br /&gt;
&lt;br /&gt;If you can get past this minor editorial glitch that appears rather frequently, then definitely buy the book!
Rating: 3 / 5</description>
		<content:encoded><![CDATA[<p>This book is a great book about project management for the web.  It is insightful and provides very useful information.  I especially liked Chapter 5 &#8211; Managing Change &#8211; and how the authors addressed common problems by providing a bulleted list of the symptoms and solutions to each type of problem.  The authors&#8217; use of bulleted lists throughout the book work well and assist the reader with identifying key issues and/or things to think about.  They also make it easy for the reader to quickly refer back to things and skim.       </p>
<p>However, with that said, there is a minor editoral issue with this book.    Everytime a bulleted list is presented the text leading into the list ends in a period (.) rather than a colon (:).</p>
<p>To illustrate:<br />
<br />- on pg 66, &#8220;Here are some tips for conducting a needs assessment.&#8221; And the bulleted list follows.<br />
<br />- on pg 186, &#8220;&#8230;and they will be testing for bugs or defects in some or all of the following areas.&#8221;  And the bulleted list follows.<br />
<br />- on pg 268, &#8220;Here are some examples of successful Open Source products that are in widespread commercial use.&#8221;  And the bulleted list follows.</p>
<p>Having served as an Editor for several professional academic journals, this drove me absolutely mad every time I saw it.  If the authors/editors of this book are going to be wrong, at least they are consistently wrong 100% of the time&#8230; which I believe is actually less maddenning then if they had gotten it right only some of the time.</p>
<p>If you can get past this minor editorial glitch that appears rather frequently, then definitely buy the book!<br />
Rating: 3 / 5</p>
]]></content:encoded>
	</item>
</channel>
</rss>

