Managing Information Systems (sort of)

1. Managing Information Systems (sort of)

2. Course Overview • Introduction • Teaching philosophy • Class objectives • Administrivia (expectations, assignments, grades) • Challenges of Teaching/Learning IT Mgmt • Thinking about what you “want to be when you grow up” • IT mgmt -- an overview • Recurring themes(organizational culture & its influence on organization & individual behavior, and personal ethics)

3. Course Objectives • Develop a useful way of thinking about the roles that information systems and technology can play in organizations and the criticality of aligning business/organizational and IS/IT strategies. • Develop a fundamental understanding of IT management structures, policies and functions. • Introduce the processes of selecting and operating information technology at the enterprise level. • Develop an appreciation for some of the non-rational ways in which organizations and individuals function that will (hopefully) help you survive, perhaps even thrive, in the “real world.” 

4. Teaching Philosophy • Learning, and work in general, should be fun (not necessarily easy). • Emphasize practice-informed theory. • Preparation, participation, writing and oral communications are important. • Balance technical skills vs. mgmt knowledge • Tacit vs. explicit knowledge and the challenges of teaching and learning mgmt (an issue representing the most fundamental challenge of this course.)

5. Assignments and Grading

6. Relationship between course objectives and course assignments • Develop a useful way of thinking about the roles that information systems and technology can play in organizations and the criticality of aligning business/organizational and IS/IT strategies (class readings, lectures and discussion) • Develop a fundamental understanding of IT management structures, policies and functions (class readings, class-led discussion and IT Mgr interviews) • Introduce the processes of selecting and operating information technology at the enterprise-level (technical evaluation projects and presentations) • Develop an appreciation for some of the non-rational ways in which organizations and individuals function that will (hopefully) help you survive and perhaps thrive in the “real world” (class readings, class-led discussion and IT Mgr interviews)

7. Group Participation: Topic Leader • For selected topic, the group is to: • Analyze reading assignment • Conduct outside research (from at least four sources per team member) • Prepare executive summary of topic (500-750) words and provide annotated bibliography of sources used • Be prepared to help lead discussion with instructor and class • Bonus points. Developing in-class exercise to reinforce key points and generate class discussion

8. Discussion Topics • CIO/IT Mgmt Roles & Challenges (4 Feb) • IT Mgmt Organization & Processes (11 Feb) • Systems Mgmt, SLAs and IT Metrics (18 Feb) • Security Mgt and mitigation (25 Feb) • Architecture, Infrastructure & B Strategy (3 Mar) • IT and change management (10 Mar) • Building world-class infrastructure (24 Mar) • IT & International Business (31 Mar) • Justifying/Evaluating IT Investments (14 Apr)

9. IT Manager Interview • Contact IT manager(top IT mgr in local organization preferred—but not absolutely required) • Complete interview (interview form avail on web) • Encourage IT manager to identify and discuss key IT management issues within his or her organization • Ask IT manager to provide personal insights relevant to your group’s discussion topic • Turn in electronic copy of completed interview form • Provide 15 minute presentation to class reporting on interview findings and emphasizing any particular insights gained.

10. Technical Evaluation • Each group will select from the following list of system applications and: • Develop an understanding of the broad market category • Identify at least 2 products for evaluation • Conduct an evaluation – review literature and perform hands-on analysis • Three products • In-class technical tutorial on the investigated products. • Group paper presenting technical evaluation • Individual paper providing and justifying your recommendation

11. Technical Evaluation Topics • Network Firewalls or IDSs (software-based) • Host/Workstation Firewalls • Network Management Applications • Server Management Applications (Unix, Linux, Windows, or multi-platform support) • Security Scanning Software • Configuration Management Applications • Third-party directory services • Network sniffer/diagnostic software • Others??

12. Individual Assignments & Participation • Independent Readings (minimum 3 articles from professional/trade press on IT topics of primary interest to you) • Assigned Readings (be prepared to discuss, there will be quizzes) • Case write-ups and discussion • Tech evaluation recommendation • Final case (or exam)

13. It isn’t what we don’t know that gives us trouble, it’s what we do know that ain’t so. ~Will Rogers

15. Questions???

16. ITM, ISM, IM & IRM:What’s the difference?

17. Confusing terms • EDP, DP, IS, MIS, IT, IM & IRM – acronym heaven (or hell) • Proliferation of terminology can lead to confusion – particularly with interest in the field expanding beyond the geeks Source: Boaden & Locket (1991) IT, IS, and IM: Definition and development, European Journal of Information Systems, 1(1):23-32.

18. Terminology Evolves with Practice • Data Processing (DP) and Electronic Data Processing (EDP): terms associated with mainframe computers, batch-oriented processing primarily supporting accounting functions. Terms rarely used now. • Information Systems (IS) and Management Information Systems (MIS): terms introduced in mainframe era reflecting that as computers became more capable and supported additional types of information, the focus grew beyond technology to include people and their use of information. Emphasis on centralized corporate applications.

19. Terminology Evolves with Practice • Information Technology (IT): imprecise term generally emphasizing technology and recognizing that more than computers are involved (e.g., telecommunications). • Information Management (IM) and Information Resources Management (IRM): term originated generally in information and library science field. Usage within the broader field traced back to Federal Paperwork Reduction Act (PRA) of 1980. The PRA emphasizes that in addition to technology, information should be managed as a valuable asset or resource. In a manner of speaking, combining the notions of IT and IS.

20. Conclusions • Usage of the terms remains confusing. Academics typically try to add precision but may actually contribute to confusion by providing multiple definitions for each term. • Federal government was primary user of the term IRM but some policies now refer to ITM. • While the terms ITM, IM, IRM may be used inter-changeably – those using ITM may tend to take more of a technology focus, while those using the terms IM or IRM generally include technology but are emphasizing the management of information, people and processes as well. • Bottom line: it does not hurt and it may help to clarify what is meant. In this class, we will generally use the term ITM – in the broader sense implied by IRM.

21. Questions???