<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="https://pm.haifa.ac.il/skins/common/feed.css?207"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>StensonReding882 - Revision history</title>
		<link>https://pm.haifa.ac.il/index.php?title=StensonReding882&amp;action=history</link>
		<description>Revision history for this page on the wiki</description>
		<language>en</language>
		<generator>MediaWiki 1.15.1</generator>
		<lastBuildDate>Thu, 23 Apr 2026 04:03:26 GMT</lastBuildDate>
		<item>
			<title>StensonReding882:&amp;#32;Created page with 'The Advantages of Planning Using Microsoft Project  Microsoft Project has been round in a single type or one other because the early '90s, however its usage amongst skilled missi…'</title>
			<link>https://pm.haifa.ac.il/index.php?title=StensonReding882&amp;diff=4584&amp;oldid=prev</link>
			<description>&lt;p&gt;Created page with &amp;#39;The Advantages of Planning Using Microsoft Project  Microsoft Project has been round in a single type or one other because the early &amp;#39;90s, however its usage amongst skilled missi…&amp;#39;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;The Advantages of Planning Using Microsoft Project&lt;br /&gt;
&lt;br /&gt;
Microsoft Project has been round in a single type or one other because the early '90s, however its usage amongst skilled mission managers remains to be not as widespread as you may think. There are a number of reasons for this, although it is considered by many as being the business commonplace benchmark for undertaking management software.&lt;br /&gt;
&lt;br /&gt;
One of many most important reasons for project managers' obvious reluctance to embrace Microsoft Project is a lack of awareness in respect of how the software program works. It's notoriously tough to successfully self-train MS Project, largely because of a lack of knowledge in respect of defining and linking venture tasks. The issue is that the Job Sheet seems to recommend that one ought to enter process begin and finish dates. That is in actual fact exactly the improper factor to do as amongst other issues, it imposes what MS Project refers to as a 'constraint'. The mistaken kind of constraint reduces flexibility and may prevent MS Project from re-scheduling duties should there be a change to the plan.&lt;br /&gt;
&lt;br /&gt;
The correct strategy to define to tasks is in fact to specify solely durations and allow Microsoft Project to set begin and end dates by way of its system of process linkage. Linkages define a dependent relationship between tasks and allow a fluid schedule to be planned. If as an example a activity is delayed, the effect on any dependent duties shall be displayed on the Gantt chart giving the mission manager forewarning of possible scheduling issues. This is perhaps the least understood aspect of Microsoft Project, particularly for the inexperienced person and really difficult to teach one's self.&lt;br /&gt;
&lt;br /&gt;
Another excuse for venture managers' reticence is a lack of knowledge of the true scope of the software program's capability. In the best palms, Microsoft Project is an immensely highly effective scheduling device, enabling the challenge supervisor to experiment with varied 'what if' scenarios. The Gantt chart is the normal way of representing the challenge's timeline and have lengthy since been thought-about a extremely useful visible tool. Historically Gantt charts can be drawn out by hand and a posh mission could take some considerable time to plan in this manner.&lt;br /&gt;
&lt;br /&gt;
One problem with the hand-drawn plan is the problem of re-scheduling should it turn into necessary. There may be where Microsoft Project scores closely in opposition to conventional methods. With a easy click of the mouse, duties will be re-scheduled and the Gantt chart instantly updated by the software. This can probably be an enormous saving in time and leaves the project supervisor free to do what they do best.&lt;br /&gt;
&lt;br /&gt;
An additional motive for some mission managers' prejudice is maybe a bad expertise with the software program within the past. Project 2010 is a a lot improved device compared with earlier versions and most, if not all the known issues, have been efficiently addressed by Microsoft. As an example, the relatively poor financial reporting capability of Microsoft Project was dramatically improved in 2007 with the appearance of 'Visual Experiences'. These are graphs that are created from data which Project exports to Microsoft Excel. Excel robotically creates a PivotTable based on the info and eventually converts it into PivotChart format. All this is accomplished with out the user requiring any detailed information of PivotTables and PivotCharts but the result is a really comprehensive and user-friendly reporting package.&lt;br /&gt;
&lt;br /&gt;
There are various reasons then why project managers have grown differ of Microsoft Project through the years, but I hope we now have proven in this article that perhaps it's now time to take another look.&lt;br /&gt;
			&lt;br /&gt;
[http://amandustechnologies.com MSP]&lt;/div&gt;</description>
			<pubDate>Tue, 06 Mar 2012 10:21:23 GMT</pubDate>			<dc:creator>StensonReding882</dc:creator>			<comments>https://pm.haifa.ac.il/index.php?title=Talk:StensonReding882</comments>		</item>
	</channel>
</rss>