Instructor: Ed Quigley
Up To Date
- some papers to return
- questions on midterm
Opportunity/ Solutions: Why do we have IS Departments, but not Copy Depts or Vehicle depts?
Info Systems: Architecture AND/OR Management
p.272, Architecture (know advantages and disadvantages of each):
- Figure 9.4A, TradeOffs
- You should be able to compare/contrast downsizing and re-engineering
p.279, IS Manaqement
p.282: Role of Corporate IS Dept in Function (distributed) Org:
IS/HR, Training, Hiring, SECURITY, Policy (email, web, porn), Standardization (platforms, etc.)
- Central IS Mgmt
- Functional IS Mgmt (LoB, BU)
Some issues from p.282:
- service-level agreements
- QoS agreements
- cost center vs profit center
P.282: A Brief Diversion into Project Management
Every project has a purpose, a change, a scope, and (gasp) and End.
We manage projects based on a triad of:
So, where do we compromise once all goals aren't going to be met?
- Time (schedule)
- Cost (budget)
IS Project dilemma: the Mythic Man Month
- Compromise on Cost, consuming profitability but not losing
- Check (hope) that there's a client-happy compromise on Scope
- Compromise on schedule just up to (but not at) client pain
- Compromise on Cost, incurring loss
- never compromise quality
p.284, The Info Center
Help Desks as Profit Centers: (ex: banks and bad-check fees).
Do we bill on trouble tickets, hours, # of calls? Profitability?
New trends: QoS, #first-call fixes.
ChargeBack (notion: nothing is free).
Goal: IS expense
Chargeback Issues: making costs overt opens door to Contracting Out. (Competitive Pressure). IS may become an "inside vendor". Strategic Value of inside shop? 20% ?
- p.288 Change Agent
- Project Leader
- p.289 DbA: DataBase Administrator
- TeleComm Manager
- p.292: Webmaster < Webster ?>
- unmentioned: corporate librarian
- information engineer
For Next Week: