ich war hier: PmTimeCostQuality

Version [18216]

Dies ist eine alte Version von PmTimeCostQuality erstellt von RonnyGertler am 2012-12-12 17:47:42.

 

 (image: http://wdb.fh-sm.de/uploads/QualipaktLehre/BMBF_Logo_klein.jpg)

Time, Cost & Quality Management


Inhalte von Prof. Dr. Kurt Englmeier

Project Time Management


Projects are temporary undertakings to create a unique product or service. The idea of time is inherent to the very definition of a project in that all projects are temporary. Even though they may seem to last forever, sooner or later they must end. Adequate planning of the temporary project can predict when a project will end. Within this short, limited time, the project manager must create something: a product or a service. The creation is about change—and change, as you may have guessed, takes time.

Project TimeManagement

Time management relies on several inputs to monitor and control the project schedule.

Creation of the product or service comes about due to the work the project team completes. The sum of the time of the work equates to when the project is completed. In addition to the duration of activities, there are other factors of time to consider, such as the following:

● Project management activities
● Planning processes
● The sequence of activities
● Procurement
● Reliance on internal and external events
● Known and unknown events affecting the project


Sequencing Project Activities


Now that the activity list has been created, the activities must be arranged in a logical sequence. This process calls on the project manager and the project team to identify the logical relationships between activities and the preferred relationship between those activities. This can be accomplished in a few different ways.

The precedence diagramming method (PDM) is the most common method of arranging the project work visually. The PDM puts the activities in boxes, called nodes, and connects the boxes with arrows. The arrows represent the relationship and the dependencies of the work packages. The following illustration shows a simple network diagram using PDM.

Sequencing Project Activities

Relationships between activities in a PDM constitute one of four different types:

Finish-to-start (FS) This relationship means Task A must be completed before Task B can begin.
Start-to-start (SS) This relationship means Task A must start before Task B can start. This relationship allows both activities to happen in tandem.
Finish-to-finish (FF) This relationship means Task A must complete before Task B does. Ideally, two tasks must finish at exactly the same time, but this is not always the case.
Start-to-finish (SF) This relationship is unusual and is rarely used. It requires that Task A start so that Task B may finish.

Sequencing Project Activity Types

Considering Leads and Lags
Leads and lags are values added to work packages to slightly alter the relationship between two or more work packages. Lead time is considered a negative value because time is subtracted from the downstream activity to bring successor activities closer to the start of the project.

Leads & Lags

Examining the Sequencing Outputs


There are many approaches to using activity sequencing: a project manager and the project team can use software programs, the approach can be done manually, or the team can manually do the scheduling and then transfer the schedule into a PMIS. Whichever method is selected, the project manager must remember four things.

● Only the required work should be scheduled.
● Finish-to-start relationships are the most common and preferred.
● Activity sequencing is not the same as a schedule.
● Scheduling comes after activity sequencing.

A project network diagram (PND) illustrates the flow of the project work and the relationship between the work packages. PNDs are typically "activity on node" (AON), and most PMIS packages use the PDM method. The following illustration is a typical example of a network diagram.

Examining the Sequencing Outputs

Considering the Resource Requirements


The identified resource requirements will affect the project schedule. Remember the difference between duration and effort? Duration is how long the activity will take, while effort is the labor applied to the task.

Considering the Resource Requirements

Estimating Activity Durations


Activity duration estimates, like the activity list and the WBS, don't come from the project manager—they come from the people completing the work. They may also undergo progressive elaboration. In this section, we'll examine the approach to completing activity duration estimates, the basis of estimates, and the allowance for activity list updates.

How confident can a project manager be when it comes to estimating? If the project work has been done before in past projects, the level of confidence in the duration estimate is probably high. But if the work has never been done before, there are lots of unknowns—and with that comes risk. To mitigate the risk, the project manager
can use a three-point estimate. A three-point estimate requires that for each activity, optimistic, most likely, and pessimistic time estimates be created.

(Optimistic time + (4 × Most likely time) + Pessimistic time)/6

Estimating Activity Durations

CategoryPmMa
Diese Seite wurde noch nicht kommentiert.
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki