Babson College
Department of Math and Science
Spring Semester, 1999

MIS-7500 — Information Systems Management

Posted: January 18, 1999




Instructor: Dr. Robert H. Reck
Office Address: Babson Hall, 216E or
Kendall Consulting Group
268 Highland Road
Andover, MA 01810
(Best Phone) = 978-474-9109 or 941-366-1774
Fax 978-470-1490
E-mail: reck@babson.edu
Bio: See web site


Class Meets: Tuesdays, 6:30 pm-9:00 p.m., Room TBD


Course Web Site http://faculty.babson.edu/reck/mis7500


Course Summary and Objectives

This course is about the management of information technology (IT) within complex organizations. It will study a company’s technology decisions through the lens of both general managers and Information Systems managers. How technology is used to facilitate or inhibit the goals of a corporation will be studied. Classes are structured to address key topics in systems management, including techniques, issues and contemporary and best practice.


Audience

The course is aimed at those graduate students who need to understand the fundamentals of technology deployment, management information systems and related issues. The course is introductory in nature and presumes little depth or familiarity with information systems, computers, software, or networks. Students should, however, have facility and access to e-mail and the Internet so that they can communicate with the instructor and have access to changes in the syllabus, assignments and readings [if this is an issue for any student, please see the instructor].


Class Approach and Student Evaluation

Classroom participation, three short papers and a final paper/presentation are the basis for the course grade, in proportions 45%, 10% each, and 25% of the final grade.

Participation will be evaluated on the basis of understanding and using assigned readings and study findings, contributing to insights on analysis and action recommendations for the case or topic being discussed, and taking into account others’ inputs.

Papers are to be an analysis and recommendations for a class or class topic(s). The papers are to take into account not only the assignment materials for the classes to that point, but also the class discussions and insights reached after the class. Students are encouraged to discuss material for classes and papers, but are individually responsible for the final products. Class participation will be 45% of the final grade, each of three short papers 10%, and the team final paper and presentation 25%. Papers will be marked down a full letter grade for each calendar day they are late!! If you have an emergency, you should contact the instructor ahead of time with a very good excuse.

We recognize that some students may need to miss an occasional class due to personal, job or CCD activities. This will put them at a disadvantage in terms of class participation. In lieu of being in class, those students that have to miss class are encouraged to write and submit to the instructor a brief memo addressed to the person or character of their choice (including persons in the case study or the instructor) on the subject of the missed class. These papers will receive recognition towards your participation grade by the instructor. Papers are due at the class after the one you miss.

The team project/final paper will be due concurrent with your team's presentation on one of the last two days of class. The team will receive a single grade for the paper and presentation, and all team members will share this grade.


Course Materials

In addition to the course packet (available at the Babson Bookstore), there is one textbook for this course:

[G&G] = S. Gordon and J. Gordon, Information Systems: A Management Approach (Second Edition), Dryden Press, New York, 1999. [ISBN-0-03-022469-1]

Note that this book contains a number of caselets, activities and other readings at the end of each chapter. These ancillary readings are usually not required readings unless explicitly assigned; in any case, actions assigned in these activities need not always be completed as indicated, especially if they involve others.

The instructor will also assign case and reading questions and other readings during the semester. Some of these readings may be on the Internet - most likely available via links from the course web site.


Handouts

Slides used in class will be available the day following the class on the K: drive under the course number - MIS7500. These will be Office 97 Powerpoint or Mac Office 98 Powerpoint slides (these are mutually compatible). Often slides not used in class will also be included in the package to help clarify or expand on materials presented in class. Please contact the instructor if you have trouble accessing the drive or slides.


Detailed Syllabus by Class

Module 1 - Overview of Information Management

1. January 26, 1999 - Introduction

Introduction to this survey course, faculty and other students. Discussion of assignments and readings, as well as course grading criteria. Review of computer and network basics to get us started. Views managers/executives have about technology. Eras of IT and how IT adds value (benefits and beneficiaries). Basics about change, technology and value.

Readings:

G&G: Chapters 1 to 2

2. February 2, 1999 - Information and Its Management

Using information and information management. How information is handled. Information needs of businesses, managers and individuals. Managerial perspectives on management, planning, control and monitoring. Functional needs overview. Role of technology.

Readings:

G&G: Chapters 1 to 2

3. February 9, 1999 - Competitive Systems

Using technology for competitive advantage. Important stories about how technology was used to change the basis of competition. Why it worked and didn't for others. Customer and market driven look at information and information management. Customer resource life cycle. Reengineering introduction.

Readings and Cases:

G&G: Chapter 11

Case: "Otisline," by D. Stoddard, Harvard Business School Publishing, #9-186-304, 1986 (or more recent revision).

Project plan due from teams for semester project.

Module 2 - Information Technology

4. February 16, 1999 - Hardware, Software and Internal Networks

Discussion of types of hardware and software. Network technologies and vocabulary. Build versus buy decisions. Languages - level and syntax. CASE tools. Elements of an IT assessment and review. First steps in an IT architecture. Office automation.

Readings and Cases:

G&G: Chapters 3, 4 and 6

Note: Paper #1 on Module 1 is due today.

5. February 23, 1999 - Database Management Systems

The concept of database management systems will be introduced. Hierarchical and relational technologies. Architecture (start). Data models. Demonstration of a database build and data entry. Data design and structured analysis. Relation of DBMS to corporate management information systems. Enterprise Resource Planning (ERP) systems will be introduced and implementation hurdles discussed.

Readings and Cases:

G&G: Chapter 5

G&G: Activities 5-1to 5-5.

Davenport, T., "Enterprise Resource Planning Systems," Harvard Business Review, June 1997

Reck, "Rapid Software Selection," Innovations (Handout)

Case studies: "Dow Corning Corporation (A and B): Business Processes and Information Technology," by J. Ross, Center for Information Systems Research, Sloan School of Management, Massachusetts Institute of Technology, 1997.

Module 3 - Information Systems

6. March 2, 1999 - Transaction Systems and Nature of Work

Automation and transaction processing systems. Expert systems and neural networks. Mission-critical systems. Changing nature of work and the relationship to technology.

Readings and Cases:

G&G: Chapters 8 and 9

G&G: Activities 8-1 to 8-5

Case: "State Street Boston Corporation: Leading With Information Technology," by D. Stoddard, Harvard Business School Publishing, #9-195-135, June, 1995.

Note: Paper #2 on Module 2 is due today.

7. March 9, 1999 - Management Support Systems/Reengineering

Management and executive information systems. Decision support. Critical success factors. Vertical systems. Relation to value chain. Groupware. Reengineering and change management. Knowledge management.

Readings and Cases:

G&G: Chapters 10

G&G: Activities 10-1 to 10-5

Reck, R., "Business Change," Innovations, Kendall Consulting Group, 1996.

Case: "Knowledge Management at Ernst & Young," by Ann Marie Chard, Graduate School of Business, Stanford University #M-291, September 1997.

Case: "Pacific Bell: Centrex Reengineering," by D. Stoddard, Harvard Business School Publishing, #N9-195-098, 1994 (or more recent version)

Status Report due from teams on semester project.

8. March 23, 1999 - Reengineering/Systems Development

Finish up Reengineering and change management. Systems development life cycle and development processes. SDLC, JAD, RAD, and developing systems on Internet time. Prototypes and pilots. Project management approaches. Teams and team structures.

Readings and Cases:

G&G: Chapter 12

G&G: Activity 12-1 to 12-3

KCG: Project Management, Innovations, Kendall Consulting Group, 1996.

Case: "The New England: Rapid Application Development," Babson College Case Study, November 18, 1997.

9. March 31, 1999 - Electronic Commerce and the Internet

Business strategies and Electronic Commerce. World Wide Web and the Internet. FTP. E-mail. Trends. Hardware and software (e.g., Browser wars). Customer relationships. Internet Time. HTML, Java, etc. Knowledge management.

Readings and Cases:

G&G: Chapter 7

G&G: Activities 7-1 to 7-5

Case: Air Products Internet Strategy, Technology, by M Dailey, Harvard Business School Publishing, #9-397-008, October 21, 1996.

Other readings TBA on the Internet

Module 4 - Planning and Management Issues

10. April 6, 1999 - Architecture/Managing Technology Deployment

Architecture and IT Principles. Bridging the gap between technology and business. Standards and guidelines. Management of the IT function. IS-Business partnerships.

Readings and Cases:

KCG: Principles, Innovations, Kendall Consulting Group, 1996.

Henderson, J., "Plugging Into Strategic Partnerships: The Critical IS Connection," Sloan Management Review, Spring 1990.

11. April 13, 1999 - IS Function and Organization

The IS function, roles and responsibilities. Jobs and competencies. Organizational structures. Pressures to centralize and decentralize. Global structures and impacts. Outsourcing issues.

Readings and Cases:

G&G: Chapter 13

Reck, R., "Globalization," Datamation, October 1, 1988.

Case: "Xerox: Outsourcing Global Information Technology Resources," by K. Davis, Harvard Business School Publishing, #9-195-158, September 30, 1995.

Status Report due from teams on semester project.

12. April 20, 1999 - IS Planning and IS Management Issues

Other issues in IS management. Business-IT alignment and IS planning summary. Technology-driven business planning. Virtual organizations. Implementation problems and issues. Issues facing IT managers: Y2K, e-Comm, big system failures, other.

Readings and Cases:

Case: "Concordia Casting Company," Harvard Business School Publishing, #9-192-151, March 30, 1993.

Note: Paper #3 on Module 3 is due today.

13. April 27, 1999 - Project Presentations and Discussion

Presentations of Class Projects per lottery drawings earlier in semester.

Readings and Cases: TBA

14. May 4, 1999 - Project Presentations and Discussion, and Wrap-Up

Presentations of Class Projects per lottery drawings earlier in semester, PLUS a final wrap-up of the course material and topics.

Readings and Cases: TBA




Short Papers

During the class each student will write three short papers, one on each of the three Modules in the class.

Module 1 - Overview of Information Management - Paper due February 16th
Module 2 - Information Technology - Paper due March 2nd
Module 3 - Information Systems (through class #10) - Paper due April 6th

Papers are to be double-spaced, 1+" margins, 10 or 12 point type font, well written, spell checked, and grammar proofed. They should not exceed five pages excluding any references, exhibits or attachments. A complete reference and/or bibliography section should be included. Papers are to address a topic raised in the module in a way that extends the readings or class discussion in a meaningful way. One approach is to write a memo to a colleague, case character, or (as a last resort) the instructor, trying to persuade that person to take a particular course of action. Papers should be coherent and stand alone from other readings or class work. You may reference frameworks used in class without repeating them in your paper, however, be sure the reference is clear. Do not simply "parrot back" how a framework is used; this is one way to get a low grade. Glitz and pizzaz should be used to encourage reading and to get your message across.


Class Project

You (and up to three teammates) may selection Option 1 or Option 2 as a class project. Teams are required to write a paper and present their findings in class during the last two classes of the semester.

Option 1: Prepare a case study of a critical information technology issue within your organization or department. Use secondary sources (e.g., articles, annual reports, company documents/fliers, and newspapers) as well as primary sources (e.g., interviews with key managers or staff members) for your study. (Harvard case materials from this course should serve as a template for your case write-up.) In addition to describing the sequence of events and presenting the dilemma facing the organization, you should analyze the business and technology situation and make recommendations (including a plan of action) as if you were consulting to the firm or department. You should use a minimum of five relevant practitioner and/or academic journal or book chapter references beyond what you are required to read for this course. The length of the case situation description should be at least 15 (excluding any exhibits). A teaching note is also required (minimum of three pages).

Option 2: Prepare a research report on an interesting area of information technology. The focus of your paper can be on an issue facing IT managers or end users. You can choose a specific information technology from a hardware, software or network vendor and write about that topic and its application in a business context. You should use a minimum of 15 relevant practitioner and/or academic journal references or book chapters beyond what you are required to read for this course should be used in the construct of your paper. This report should be a minimum of 20 pages (excluding any exhibits).

Papers, Etc.: Each team will submit a single written report to the instructor. Papers are to be double-spaced, 1+" margins, 10 or 12 point type font, well written, spell checked, and grammar proofed. Exhibits may be run in text or aggregated at the end. A complete reference and/or bibliography section should be included. Ancillary materials such as videos, CDs, web sites, programs, mock-ups, handouts, should also accompany the paper when handed in. Papers are due on the day of your team's presentation. Be sure to list all team members on the front cover of the report.

Final Presentations: Each team is to make a final presentation in which all team members will participate. These will contribute towards the final project grade as well as the written papers you submit. Papers and other relevant materials (e.g., web sites) are due at your team's presentation. These presentations will be graded as both content and form (pizzaz!!). In the past, students have created videos, presented skits, conducted a talk show and debated key topics. Do whatever makes your topic come to life. You are presenting as much to your colleagues as to the instructor.

Key Activity Dates for Semester Project:

Class 1 and 2 - Divide into teams by options and kick around possible ideas.

Class 3 - Project Plan Due. Submit a one-page report from your team to inform the instructor of your option, topic, thesis or hypothesis, management plan (who will do what by when?), and any issues you see.

Class 7 - Status Report Due. Submit a one-page report from your team to inform the instructor of your progress on your topic. Include a discussion of any major issues facing the team.

Class 10 - Status Report Due.

Class 13 or 14 - Presentations and Reports Due. Note that written reports are due concurrently with your presentation and not automatically on the last class day.



Bookstore Course Pack

This course pack has been requested from the Babson Bookstore. Please contact them for copies of the cases and articles below.

Harvard Business School Case Studies

• "Otisline," by D. Stoddard, Harvard Business School Publishing, #9-186-304, 1986 (or more recent revision).

• "State Street Boston Corporation: Leading With Information Technology," by D. Stoddard, Harvard Business School Publishing, #9-195-135, June, 1995.

• "Knowledge Management at Ernst & Young," by Ann Marie Chard, Graduate School of Business, Stanford University #M-291, September 1997.

• "Pacific Bell: Centrex Reengineering," by D. Stoddard, Harvard Business School Publishing, #N9-195-098, 1994.

• "Xerox: Outsourcing Global Information Technology Resources," by K. Davis, Harvard Business School Publishing, #9-195-158, September 30, 1995.

• Air Products Internet Strategy, Technology, by M Dailey, Harvard Business School Publishing, #9-397-008, October 21, 1996.

• "Concordia Casting Company," Harvard Business School Publishing, #9-192-151, March 30, 1993.

Harvard Business Review Articles

• Davenport, T., "Putting the Enterprise Into the Enterprise System," HBR, July-August 1998.

Kendall Consulting Group Articles

• Rapid Software Selection

• Change Management

• Project Management

• Principles

Other Articles and Cases

• Henderson, J., "Plugging Into Strategic Partnerships: The Critical IS Connection," Sloan Management Review, Spring 1990

• Reck, R., "Globalization," Datamation, October 1, 1988.

• "Dow Corning Corporation (A): Business Processes and Information Technology, " by J. Ross, Center for Information Systems Research, Sloan School of Management, Massachusetts Institute of Technology, 1997

• "Dow Corning Corporation (B): reengineering Global Processes," by J. Ross, Center for Information Systems Research, Sloan School of Management, Massachusetts Institute of Technology, 1997

• "The New England: Rapid Application Development," Babson College Case Study, November 18, 1997






Please use the BACK key to return to your previous page.