Amacom - Modern Project Management (Ocr) - 2001 ! - (By Laxxuss)

They also cause the amount of resources needed from

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: e project management system, it is not reasonable to assume these dates are the ones you really want to time phase the control budget. Therefore, they usually reject this operational policy, since most project managers believe that the maintenance of schedule dates takes an individual Page 203 periodic review of each of the start and end date pairs for each task. However, even if this policy is rejected, most project managers do not mind using an automated interface to make the initial bulk move of schedule dates over to the project management systems at the beginning of a project, because it saves a lot of time and effort in the beginning, and they know that all of these dates are going to be periodically reviewed (and possibly updated) anyway. The second operational policy that might allow automated transfer of schedule dates from the scheduling system to the project management system is to maintain a separate schedule for each budget and for the forecast . In this way, each of the individual schedules can be tuned to the budget that it is used to time phase, rather than having a single schedule for all purposes. This option is universally unpopular with project managers because it requires increasing the scheduling effort by approximately 300%. Change orders and quantity variances often cause dependencies among tasks to change. They also cause the amount of resources needed from the resource pools to change. So even if all the schedules had the same tasks, they would still be intrinsically different schedules. Also, change orders often create new tasks and eliminate old tasks, so these individual schedules will probably not contain the same tasks. The effort required to maintain four schedules (or even two or three) makes this policy unworkable. Furthermore, all the objections to moving dates automatically from the scheduling system to the project management system without individual review still hold to some degree for this second policy as for the first. We will allocate a significant amount of space in the following section explaining how the automated interface between Microsoft Project and Modern Project works. Our recommendation, however, is to use it only to move the initial set of dates from the scheduling system during the project planning phase into the project management system. Thereafter, Page 204 you can make manual changes to the dates on the basis of the current schedule, the nature of the variances that cause the schedule changes, and project management judgment. It is also recommended that the schedule that is maintained by the scheduling system correspond to the control budget. This way the resources needed for the tasks will be the same in the scheduling system as in the project management system. This, of course, necessitates a strict separation of variances between quantification variances and productivity variances, because productivity variances cause changes in the timing of a project that in turn cause changes in the time phasing of the...
View Full Document

This note was uploaded on 01/11/2011 for the course ACC 9 taught by Professor Yeetan during the Spring '10 term at Sunway University College.

Ask a homework question - tutors are online