ELC 347 DAY 2. Agenda Questions Working with MS Project 2003 Making a PB & J Sandwich.

37
ELC 347 DAY 2
  • date post

    19-Dec-2015
  • Category

    Documents

  • view

    214
  • download

    0

Transcript of ELC 347 DAY 2. Agenda Questions Working with MS Project 2003 Making a PB & J Sandwich.

ELC 347

DAY 2

Agenda

Questions Working with MS Project 2003 Making a PB & J Sandwich

Intro to MS Project 2003

4 phases Preliminaries Planning Managing Reporting including post action review

Project 2003Parts and Pieces

Calendar Gnatt chart Network diagrams Resource sheet Tasks

Gnatt View

Network view

Resource Sheet

Task View

Project Guides

Options

Making a PB &J

Define Define resources Define tasks

Duration Sequence (predecessors) Assign resource

Define Milestones

Whats a PB & J?

Acceptance criteria S.M.A.R.T.

Specific Measurable Acceptable Realistic Time

What are the steps??

Resources? Materials Order of activities Any milestones?

Different Types of tasks

Normal tasks Activities Atomic?

Milestones Goal is achieved or A deliverable is completed or A decision point is reached

Summary Tasks Groups of related tasks Not atomic

Creating Task Lists

Two methods Top down

List major phases (Summary Task) Add detail tasks (subtasks)

Bottom up List all task details (subtasks) Aggregate tasks into similar groups (sunnary

tasks)

Creating a Work Breakdown Structure (WBS)

Project A

Phase 1 Phase 2 Phase 3

Task 1.1

Task 1.2

Task 2.1

Task 2.2Task 1.1.1

Task 3.1

Task 3.2

Task 3.2.1

Task 3.2.2

Entering Tasks into Project

Use Gantt view ID field – (auto set) Task name field Duration field Start and finish field Predecessors field Resouce names field

Editing tasks

Several methods Task List changes

Insert, delete, clearing Moving and copying

Use Task information Dialog Box

Creating Milestones

Two methods Set duration top 0 units Mark tasks as a milestone in the Task

Dialog box

Recurring tasks

Tasks that are repeated at regular intervals during Life of project

Menu>Insert>Recurring Task

Adding Notes to tasks

Use task Dialog box Notes tab

Scheduling

Projects either Start on a fixed date or End of a fixed date

Schedules depend on

Duration estimates for tasks Sequencing of tasks Constraints

Time Resources

Dependency Links

Some tasks can’t start till another is finished Successor task Predecessor task

Show ups as arrows in Project

Creating dependencies

Easy way is to use the Task dialog box predecessors tab

Creating dependencies

You can also use task fields More cumbersome

You can click and drag in the Gantt view Easy to screw up

Delays and overlaps

Delay Task may lag another task but a certain

amount of time Overlap

Task may lead another task by a certain amount of time

Setting Delays and overlaps

Use task dialog box, predecessors tab, lag field

- is overlap + is delay

Four types of dependencies

FS Finish to start Predecessor must finish before successor can

start SS Start to start

Start of predecessor determines start of successors

FF finish to finish Finish of predecessor determines finish of

successor SF Start to finish

Predecessor start determines successor finish

Dependency examples

Using task constraints

Fixes task performance dates Limits scheduling opportunities Some are flexible some are not

Nonflexible constraints show up in indicator field

Use task Dialog

8 Constraint types

ASAP As soon as possible (default) Flexible

ALAP As late as possible Flexible

SNET Start no earlier than Inflexible for fixed finish date

SNLT Start no later than Inflexible for fixed start date

8 Constraint types (con;t)

FNET Finish no earlier than Inflexible for fixed finish date

FNLT Finish no later than Inflexible for fixed start date

MSO Must start on inflexible

MFO Must finish on inflexible

Calender view

Network view

Group Work

Lets build a MS project Plan for field hardware rollout using the following template http://www.timkress.net/Articles/Field%20Hardware%20R

ollout.html Set project start date to September 13 and ignore other

dates Make assumptions about phase scheduling

Document assumptions Let project do the scheduling for everything else

WE WILL REVISE AFTER Save project we will use again later