<?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: The Top Five Software Project Risks</title>
	<atom:link href="http://www.pmhut.com/the-top-five-software-project-risks/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/the-top-five-software-project-risks</link>
	<description></description>
	<pubDate>Thu, 24 May 2012 22:04:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Magesh Puvananthiran</title>
		<link>http://www.pmhut.com/the-top-five-software-project-risks/comment-page-1#comment-32</link>
		<dc:creator>Magesh Puvananthiran</dc:creator>
		<pubDate>Mon, 27 Aug 2007 07:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/the-top-five-software-project-risks#comment-32</guid>
		<description>Some comments on item #3: Employee turnover

In my opinion, keeping the project information distributed throughout the team is the responsibility of the project manager or the management in general. Because, in my previous project, we had a contractor working on a key project for quite a long time. We have asked for some additional resources(people) for backup but of no avail. One point in time, he really had to leave the company because of long contract durations. He ended up documenting what he knows well in paper. The person who took over still had to go over a lot of things to really catch-up but the documentation really helped.

On the other front, in another project, we had a strategy where the developer has to prepare a design document describing briefly the following and reviewed by a subject matter expert before he starts development:

1. What is the problem reported?
2. What is the suggested solution approach?
3. What are all the things that need to be modified?

This document really helped any new team member who comes on board.</description>
		<content:encoded><![CDATA[<p>Some comments on item #3: Employee turnover</p>
<p>In my opinion, keeping the project information distributed throughout the team is the responsibility of the project manager or the management in general. Because, in my previous project, we had a contractor working on a key project for quite a long time. We have asked for some additional resources(people) for backup but of no avail. One point in time, he really had to leave the company because of long contract durations. He ended up documenting what he knows well in paper. The person who took over still had to go over a lot of things to really catch-up but the documentation really helped.</p>
<p>On the other front, in another project, we had a strategy where the developer has to prepare a design document describing briefly the following and reviewed by a subject matter expert before he starts development:</p>
<p>1. What is the problem reported?<br />
2. What is the suggested solution approach?<br />
3. What are all the things that need to be modified?</p>
<p>This document really helped any new team member who comes on board.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

