Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Network diagram software planning management, Slides of Software Engineering

software planning management Network diagram

Typology: Slides

2018/2019

Uploaded on 05/26/2019

lisha-jonwal
lisha-jonwal 🇮🇳

1 document

1 / 36

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Project Time Management
1303KM project Management
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24

Partial preview of the text

Download Network diagram software planning management and more Slides Software Engineering in PDF only on Docsity!

Project Time Management

Learning Objectives

  1. Understand the importance of project schedules and good project time management.
  2. Define activities as the basis for developing project schedules.
  3. Describe how project managers use network diagrams and dependencies to assist in activity sequencing.
  4. Understand the relationship between estimating resources and project schedules.
  5. Explain how various tools and techniques help project managers perform activity duration estimating.
  6. Use a Gantt chart for planning and tracking schedule information, find the Critical-Path for a project, and describe how the Program Evaluation and Review Technique (PERT) affect schedule development.
  7. Controlling and managing changes to the project schedule.

Figure 6-1. Conflict

Intensity Over the Life of a

Project

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.

2 Activity Definition

 (^) 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.

Activity Lists and Attributes

 (^) 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.

Activity Sequencing

 (^) 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.

Three Types of

Dependencies

 (^) 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

Arrow Diagramming

Method (ADM)

 (^) 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

4 Schedule Development

 (^) 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.

5 Gantt Charts

 (^) 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