1. 3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer

2. Chapter 3 3-2 © Prentice Hall, 2004 Chapter Objectives Af ter studying this chapter you should be able to: – Describe the skills required to be an effective project manager. – Describe the unique characteristics of an OOSAD project.

3. Chapter 3 3-3 © Prentice Hall, 2004 Chapter Objectives (Continued) Af ter studying this chapter you should be able to: – List and describe the skills and activities of a project manager through: Initiation Planning Execution Close-down

4. Chapter 3 3-4 © Prentice Hall, 2004 Chapter Objectives (Continued) Af ter studying this chapter you should be able to: – Explain critical path scheduling, Gantt charts, Network diagrams. – Explain how commercial software packages can help with project management tasks.

5. Chapter 3 3-5 © Prentice Hall, 2004

6. Chapter 3 3-6 © Prentice Hall, 2004 Activities and Skills of a Project Manager Leadership Management Customer relations Technical problem solving Conflict management Team management Risk and change management

7. Chapter 3 3-7 © Prentice Hall, 2004 Project management is as much an art as a science

8. Chapter 3 3-8 © Prentice Hall, 2004 The OOSAD System Development Process In OOSAD, the entire SDC repeats itself over several iterations. Each iteration distributes the focus on its own set of SDC phases, but in each iteration all SDC phases are addressed to some extent.

9. Chapter 3 3-9 © Prentice Hall, 2004

10. Chapter 3 3-10 © Prentice Hall, 2004

11. Chapter 3 3-11 © Prentice Hall, 2004 Each iteration involves a workflow, consisting of SDC steps.

12. Chapter 3 3-12 © Prentice Hall, 2004 SDC applied to iteration 1

13. Chapter 3 3-13 © Prentice Hall, 2004 SDC applied to iteration 1 Mgt and Planning

14. Chapter 3 3-14 © Prentice Hall, 2004 SDC applied to iteration 1 Analysis

15. Chapter 3 3-15 © Prentice Hall, 2004 SDC applied to iteration 1 Design

16. Chapter 3 3-16 © Prentice Hall, 2004 SDC applied to iteration 1 Implementation

17. Chapter 3 3-17 © Prentice Hall, 2004 SDC applied to iteration 2

18. Chapter 3 3-18 © Prentice Hall, 2004 SDC applied to iteration 3

19. Chapter 3 3-19 © Prentice Hall, 2004 SDC applied to iteration 4

20. Chapter 3 3-20 © Prentice Hall, 2004 SDC applied to iteration 5

21. Chapter 3 3-21 © Prentice Hall, 2004 Moral: don’t over-plan early in the project. Continue planning activities throughout entire project. Plans improve over the course of the project

22. Chapter 3 3-22 © Prentice Hall, 2004 SDC focus changes from iteration to iteration

23. Chapter 3 3-23 © Prentice Hall, 2004

24. Chapter 3 3-24 © Prentice Hall, 2004 Project Management Tasks and Activities Project Phases – Project Initiation – Project Planning – Project Execution – Project Closedown

25. Chapter 3 3-25 © Prentice Hall, 2004 Project Initiation First phase of project management, involves assessment of project scope, size, and complexity and establishment of project procedures

26. Chapter 3 3-26 © Prentice Hall, 2004 Six Project Initiation Activities 1. Establishing the project initiation team 2. Establishing a relationship with the customer 3. Establishing the project initiation plan 4. Establishing management procedures 5. Establishing the project management environment and the project workbook 6. Developing the project charter

27. Chapter 3 3-27 © Prentice Hall, 2004 Project initiation does not include detailed plans for entire project

28. Chapter 3 3-28 © Prentice Hall, 2004 The Project Workbook An online or hardcopy repository of all project correspondence, inputs, outputs, deliverables, procedures, and standards Used as a primary communications medium for the project team

29. Chapter 3 3-29 © Prentice Hall, 2004 The Project Charter A short, high-level document prepared for internal and external stakeholders to formally announce the establshment of the project and to briefly describe its objectives, key assumptions, and stakeholders

30. Chapter 3 3-30 © Prentice Hall, 2004 Project workbook grows and evolves during project activities

31. Chapter 3 3-31 © Prentice Hall, 2004 Project Planning Second phase of project management, focusing on defining clear, discrete activities and the work needed to complete each activity within a single project

32. Chapter 3 3-32 © Prentice Hall, 2004 Ten Project Planning Activities 1. Describing project scope, alternatives, and feasibility 2. Dividing the project into manageable tasks 3. Estimating resources and creating a resource plan 4. Developing a preliminary schedule 5. Developing a communication plan

33. Chapter 3 3-33 © Prentice Hall, 2004 Ten Project Planning Activities (cont.) 6. Determining project standards and procedures 7. Identifying and assessing risk 8. Creating a preliminary budget 9. Developing a project scope statement 10. Setting a baseline project plan

34. Chapter 3 3-34 © Prentice Hall, 2004 The Baseline Project Plan (BPP) The major deliverable from the project initiation and planning phases, this document contains estimates of scope, benefits, schedules, costs, risks, and resource requirements BPP is updated throughout project execution and closedown

35. Chapter 3 3-35 © Prentice Hall, 2004 Gantt: Focus is on time. Two Project Scheduling Diagrams in Microsoft Project These diagrams are important components of the BPP. Network: Focus is on dependencies.

36. Chapter 3 3-36 © Prentice Hall, 2004 Cost- benefit analysis is a key componen t of the BPP

37. Chapter 3 3-37 © Prentice Hall, 2004 Project Execution Third phase of project management, involving putting the plans created in the previous phases into action, and monitoring actual progress against the BPP

38. Chapter 3 3-38 © Prentice Hall, 2004 Five Project Execution Activities 1. Executing the baseline project plan 2. Monitoring project progress agains the baseline project plan 3. Managing changes to the baseline project plan 4. Maintaining the project workbook 5. Communicating the project status

39. Chapter 3 3-39 © Prentice Hall, 2004 Project Closedown Final phase of the project management process, focusing on bringing the project to an end

40. Chapter 3 3-40 © Prentice Hall, 2004

41. Chapter 3 3-41 © Prentice Hall, 2004 Three Project Closedown Activities 1. Closing down the project 2. Conducting post-project reviews 3. Closing the customer contract

42. Chapter 3 3-42 © Prentice Hall, 2004 Project Management Tools Critical path scheduling Network diagrams Gantt diagrams Work breakdown structures (WBS) Software tools

43. Chapter 3 3-43 © Prentice Hall, 2004 Critical Path Scheduling A scheduling technique whose order and duration of a sequence of task activities directly affects the completion date of a project Critical path – the shortest time in which a project can be completed Slack time – the amount of time an activity can be delayed without delaying the project

44. Chapter 3 3-44 © Prentice Hall, 2004 Critical path example Note the durations and precedents (dependencies)

45. Chapter 3 3-45 © Prentice Hall, 2004 Determining the Critical Path Calculate the earliest possible completion time for each activity by summing the activity times in the longest path to the activity. This gives total expected project time. Calculate the latest possible completion time for each activity by subtracting the activity times in the path following the activity from the total expected time. This gives slack time for activities. Critical path – contains no activities with slack time

46. Chapter 3 3-46 © Prentice Hall, 2004 Network diagram shows dependencies. Network diagram with early and late times calculated and critical path determined

47. Chapter 3 3-47 © Prentice Hall, 2004 Work Breakdown Structure (WBS) is a hierarchy of tasks and subtasks. Note: numbering in WBS does not imply chronological order. It is not necessary for all subtasks in 1 to precede all subtasks in 2.

48. Chapter 3 3-48 © Prentice Hall, 2004 Planning detail evolves over time.

49. Chapter 3 3-49 © Prentice Hall, 2004 Recap After studying this chapter we learned to: – Describe effective project management skills through all phases of the systems development process. – Describe OOSAD. – Understand critical path scheduling, Gantt charts, and Network diagrams. – Work with commercial project management software products.