<?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: Human aspects of Project Management</title>
	<atom:link href="http://evolutionofbpr.com/human-aspects-of-project-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://evolutionofbpr.com/human-aspects-of-project-management/</link>
	<description>A Holistic Approach to Implementating Enterprise Application Software</description>
	<pubDate>Wed, 07 Jan 2009 02:19:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Aditya Gholap</title>
		<link>http://evolutionofbpr.com/human-aspects-of-project-management/comment-page-1/#comment-129</link>
		<dc:creator>Aditya Gholap</dc:creator>
		<pubDate>Fri, 04 Jul 2008 04:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://evolutionofbpr.com/?p=206#comment-129</guid>
		<description>Interesting. A couple of handy insights. I agree particularly with the last point about adoption management. When we started, we created an MIS with Google Docs. That sort of failed because it wasn't enticing enough, interface wasn't great and people didn't see 'trends' wrt their performance and they couldn't see how it contributed to organisational growth so the effect was not as expected. We then moved to a web based project management tool called &lt;a href="http://www.deskaway.com/" rel="nofollow"&gt; Deskaway &lt;/a&gt; - we had an entire day with a training workshop and guidelines with respect to impact on the company and also an understanding of how individual work affects the organisation. At the end we gave our crew members the option to opt out of managing projects using the tool or opt in. They clearly saw the importance of process management and they saw how we didn't want to stifle creativity - they also saw the importance of improved analytics and reporting on the business and this got social collaboration really going. It starts in the mind i guess.</description>
		<content:encoded><![CDATA[<p>Interesting. A couple of handy insights. I agree particularly with the last point about adoption management. When we started, we created an MIS with Google Docs. That sort of failed because it wasn&#8217;t enticing enough, interface wasn&#8217;t great and people didn&#8217;t see &#8216;trends&#8217; wrt their performance and they couldn&#8217;t see how it contributed to organisational growth so the effect was not as expected. We then moved to a web based project management tool called <a href="http://www.deskaway.com/" rel="nofollow"> Deskaway </a> - we had an entire day with a training workshop and guidelines with respect to impact on the company and also an understanding of how individual work affects the organisation. At the end we gave our crew members the option to opt out of managing projects using the tool or opt in. They clearly saw the importance of process management and they saw how we didn&#8217;t want to stifle creativity - they also saw the importance of improved analytics and reporting on the business and this got social collaboration really going. It starts in the mind i guess.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
