




























Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
software planning management Network diagram
Typology: Slides
1 / 36
This page cannot be seen from the preview
Don't miss anything!
Project Formation Early Phases Middle Phases End Phases Conflict Intensity Schedules Priorities Manpower Technical opinions Procedures Cost Personality conflicts Average Total Conflict
Individual Work Styles and Cultural Differences Cause Schedule Conflicts (^) Some people prefer to follow schedules and meet deadlines while others do not. (^) Different cultures and even entire countries have different attitudes about schedules.
(^) An activity or task is an element of work normally found on the WBS that has an expected duration, a cost, and resource requirements. (^) Project schedules grow out of the basic documents that initiate a project. (^) The project charter includes start and end dates and budget information. (^) The scope statement and WBS help define what will be done. (^) Activity definition involves developing a more detailed WBS and supporting explanations to understand all the work to be done, so you can develop realistic cost and duration estimates.
(^) An activity list is a tabulation of activities to be included on a project schedule. The list should include: (^) The activity name (^) An activity identifier or number (^) A brief description of the activity (^) Activity attributes provide more information about each activity, such as predecessors, successors, logical relationships, leads and lags, resource requirements, constraints, imposed dates, and assumptions related to the activity.
(^) Involves reviewing activities and determining dependencies. (^) A dependency or relationship relates to the sequencing of project activities or tasks. (^) You must determine dependencies in order to use critical path analysis.
(^) Mandatory dependencies : Inherent in the nature of the work being performed on a project; sometimes referred to as hard logic. (^) Discretionary dependencies : Defined by the project team; sometimes referred to as soft logic and should be used with care because they may limit later scheduling options. (^) External dependencies : Involve relationships between project and non-project activities.
Figure 6-2. Sample Activity-on- Arrow (AOA) Network Diagram for Project X
(^) Also called activity-on-arrow (AOA) network diagram. (^) Activities are represented by arrows. (^) Nodes or circles are the starting and ending points of activities. (^) Can only show finish-to-start dependencies.
Figure 6-3. Task Dependency Types
Figure 6-4. Sample PDM Network Diagram
(^) Uses results of the other time management processes to determine the start and end dates of the project. (^) Ultimate goal is to create a realistic project schedule that provides a basis for monitoring project progress for the time dimension of the project. (^) Important tools and techniques include Gantt charts, critical path analysis, and PERT analysis.
(^) Gantt charts provide a standard format for displaying project schedule information by listing project activities and their corresponding start and finish dates in a calendar format. (^) Symbols include: (^) Black diamonds : Milestones (^) Thick black bars : Summary tasks (^) Lighter horizontal bars : Durations of tasks (^) Arrows : Dependencies between tasks