1. ELC 347 DAY 2

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

3. Intro to MS Project 2003  4 phases Preliminaries Planning Managing Reporting including post action review

4. Project 2003 Parts and Pieces Calendar Gnatt chart Network diagrams Resource sheet Tasks

5. Gnatt View

6. Network view

7. Resource Sheet

8. Task View

9. Project Guides

10. Options

11. Making a PB &J Define Define resources Define tasks  Duration  Sequence (predecessors)  Assign resource Define Milestones

12. Whats a PB & J? Acceptance criteria S.M.A.R.T.  Specific  Measurable  Acceptable  Realistic  Time

13. What are the steps?? Resources? Materials Order of activities Any milestones?

14. 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

15. 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)

16. Creating a Work Breakdown Structure (WBS) Project A Phase 1 Task 1.1 Task 1.1.1 Task 1.2 Phase 2 Task 2.1 Task 2.2 Phase 3 Task 3.1 Task 3.2 Task 3.2.1 Task 3.2.2

17. 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

19. Editing tasks Several methods  Task List changes Insert, delete, clearing Moving and copying  Use Task information Dialog Box

20. Creating Milestones Two methods  Set duration top 0 units  Mark tasks as a milestone in the Task Dialog box

21. Recurring tasks Tasks that are repeated at regular intervals during Life of project Menu>Insert>Recurring Task

22. Adding Notes to tasks Use task Dialog box Notes tab

23. Scheduling Projects either  Start on a fixed date or  End of a fixed date

24. Schedules depend on Duration estimates for tasks Sequencing of tasks Constraints  Time  Resources

25. Dependency Links Some tasks can’t start till another is finished  Successor task  Predecessor task Show ups as arrows in Project

26. Creating dependencies Easy way is to use the Task dialog box predecessors tab

27. Creating dependencies You can also use task fields  More cumbersome You can click and drag in the Gantt view  Easy to screw up

28. 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

29. Setting Delays and overlaps Use task dialog box, predecessors tab, lag field - is overlap + is delay

30. 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

31. Dependency examples

32. 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

33. 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

34. 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

35. Calender view

36. Network view

37. 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 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