Professional Documents
Culture Documents
Session13&14 ManagingSystems FULL Updated
Session13&14 ManagingSystems FULL Updated
Reviews and
approves plans for
systems in all
divisions
Overseeing specific
IS projects
Responsible for
individual systems
project
Linking Systems project to business plan
◼Identifies systems projects that will deliver most business value, organizations need to
develop an information systems plan that supports their overall business plan and in
which strategic systems are incorporated into top-level planning.
Purpose of plan, Strategic business plan rationale, Current systems/situation, New
developments, Management strategy, Implementation plan, Budget Requirements
◼Further, the plan contains a statement of corporate goals and specifies how information
technology will support the attainment of those goals.
◼The report shows how general goals will be achieved by specific systems projects and
identifies specific target dates and milestones that can be used later to evaluate the
plan’s progress in terms of how many objectives were actually attained in the time
frame specified in the plan.
◼The plan indicates the key management decisions concerning hardware acquisition;
telecommunications; centralization/ decentralization of authority, data, and hardware;
and required organizational change.
Linking Systems project to business plan
◼An Effective plan should include
Firms will need to inventory and document all of their information system applications and
IT infrastructure components
Managers should try to identify the decision improvements that would provide the greatest
additional value to the firm.
Develop a set of metrics to quantify the value of more timely and precise information on the
outcome of the decision.
The organization must have a clear understanding of both its long- and short-term
information requirements.
◼Key Performance Indicators (KPI)
KPIs are shaped by the industry, the firm, the manager, and the broader environment.
New information systems should focus on providing information that helps firm meet these
goals implied by key performance indicators.
Portfolio Analysis
◼Inventories all of the organization’s information systems projects and assets, including
infrastructure, outsourcing contracts, and licenses.
This portfolio of information systems investments can be described as having a certain
profile of risk and benefit to the firm
Firms would try to improve the return on their portfolios of IT assets by balancing the risk
and return from their systems investments
◼Management can determine optimal mix of investment
risk and reward for their firms, balancing riskier high-
reward projects with safer lower-reward ones.
◼Firms where portfolio analysis is aligned with business
strategy have been found to have a superior return on
their IT assets, better alignment of IT investments with
business objectives, and better organization-wide
coordination of IT investments
Scoring Model
◼Assigns weights to
various features of a
system and then calculates
the weighted totals
◼Often the most important
outcome of a scoring
model is not the score but
agreement on the criteria
used to judge a system
◼Used most commonly to
confirm, to rationalize,
and to support decisions
rather than as the final
arbiters of system
selection.
Information system costs and benefits
◼Major IS Costs – Hardware, Networking, Software, Services, Personnel
◼Tangible benefits: - Can be quantified and assigned monetary value
◼Intangible benefits: - Cannot be immediately quantified but may lead to quantifiable gains in
the long run
Capital budgeting for Information Systems
◼Used to measure the value of investing in long-term capital investment projects.
◼Rely on measures of cash flows into and out of the firm; capital projects generate
those cash flows.
The investment cost for information systems projects is an immediate cash
outflow caused by expenditures for hardware, software, and labor.
Cash inflows take the form of increased sales of more products or reduced
costs in production and operations.
The difference between cash outflows and cash inflows is used for calculating
the financial worth of an investment
◼Various capital budgeting models used for IT projects: Payback method,
accounting rate of return on investment (ROI), net present value, internal rate of
return (IRR)
Assessing the Business Value of IS
◼Real options pricing models (ROPM)
Used when future revenue streams of IT projects are uncertain and up-front costs are high.
Although the costs of this investment can be calculated, not all of the benefits of making
this investment can be established in advance
Use the concept of options valuation borrowed from the financial industry.
An option is essentially the right, but not obligation, to act on some future date.
Gives managers flexibility to stage IT investment or test the waters with small pilot projects
or prototypes to gain more knowledge about risks before investing in entire implementation
But the disadvantages of this model are primarily in estimating all the key variables
affecting option value, including anticipated cash flows from the underlying asset and
changes in the cost of implementation.
◼Limitations of financial models - Do not take into account social and
organizational dimensions that may affect costs and benefits
Dimensions of IS Project Risks
◼Project Size - The larger the project—as indicated by the dollars spent, the size of the
implementation staff, the time allocated for implementation, and the number of organizational
units affected—the greater the risk
The organizational complexity of the system and the technical characteristics also determine
the level of risk
◼Project Structure - Project which relatively undefined, fluid, and constantly changing
requirements; with outputs that cannot be fixed easily because or with users who cannot agree
on what they want carry high risk compered to highly structured IS project
◼Lack of experience with technology - Project team and the IS staff lack the required technical
expertise - unfamiliar with the hardware, system software, application software, or DBMS
proposed for the project
◼Other factors, primarily organizational
Complexity of information requirements, scope of the project, and how many parts of the
organization will be affected by a new information system
Change Management and Implementation
◼Implementation refers to all organizational activities working toward adoption, management,
and routinization of an innovation
◼System Analysts as Change Agents
Redefines the configurations, interactions, job activities, and power relationships of
organizational groups
Catalyst for entire change process and ensures all parties involved accept changes created by new system
Communicates with users, mediates between competing interest groups, and ensures that the
organizational adjustment to such changes is complete.
◼Role of End users
High level user involvement provide them more opportunities to mould the system according to
their priorities and business requirements, and more opportunities to control the outcome.
Users are more likely to react positively to the completed system because they have been active
participants in the change process.
Incorporating user knowledge and expertise leads to better solutions.
User-designer communications gap
◼Users and information systems specialists tend to have different backgrounds, interests, and
priorities leading to divergent organizational loyalties, approaches to problem solving, and
vocabularies.
Communication problems between end users and designers are a major reason why user
requirements are not properly incorporated into information systems and why users are
driven out of the implementation process.
Formal Planning and Control Tools – GANTT Charts
◼Lists project activities and their corresponding start and completion dates.
Visually represents the timing and duration of different tasks in a development project as
well as their human resource requirements
◼Purpose of Gantt chart
To illustrate the relationship between project activities & time.
To show the multiple project activities on one chart
To provide a simple & easy to understand representation of project scheduling
◼Two methods of creating Gantt charts
Forward Schedule: starting with the list of activities and a given start date (6th Sept in
previous example) follow them forwards in time until you hit given deadline.
Backward Schedule: look at the deadline, from that date work in the logical list of
activities.
◼The Gantt Chart does not explain the reasoning behind the chosen duration of each activity and
the charts do not consider project costs or resources
Formal Planning and Control Tools – GANTT Charts
Formal Planning and Control Tools – PERT Charts
◼Program Evaluation and Review Technique (PERT) - Graphically depicts project tasks and
their interrelationships.
Lists the specific activities that make up a project and the activities that must be completed
before a specific activity can start
Portrays a project as a network diagram consisting of numbered nodes (either circles or
rectangles) representing project tasks.
Each node is numbered and shows the task, its duration, the starting date, and the completion date.
The direction of the arrows on the lines indicates the sequence of tasks and shows which activities
must be completed before the commencement of another activity.
◼Incorporates statistical analysis and thereby determines the probabilities concerning the time
by which each activity or entire project would be completed.
◼Developing PERT Charts
List the activities involved in the project. Break your project down into more manageable tasks.
Consider dependencies and place nodes and arrows based on the identified dependencies
Formal Planning and Control Tools – PERT Charts
Managing IS Project Risks
◼Management support and commitment - Effects positive perception by both users and technical
staff - Creates a belief that their participation in the development process will receive higher-level
attention and priority and Ensures sufficient funding and resources.
◼The challenges of innovation and implementation require extensive organizational change and
require replacing old technologies and legacy systems that are deeply rooted in many
interrelated business processes
Led to a very high failure rate among enterprise application and business process reengineering (BPR) projects
Poor implementation and change management practices
Employee’s concerns about change
Resistance by key managers
Changing job functions, career paths, recruitment practices
◼Projects related to mergers and acquisitions are deeply affected by the organizational
characteristics of the merging companies as well as by their IT infrastructures
Merging of systems of two companies requires considerable organizational change and complex systems
projects to manage failing which the merged entity cannot execute its business processes effectively.
Managing IS Project Risks
◼Increasing user involvement - Projects with relatively little structure and many undefined
requirements must involve users fully at all stages.
External integration tools - Ways to link work of implementation team to users at all levels
Implementation strategy needs to address issues of Counter implementation - deliberate
strategy to thwart implementation of a system or innovation in an organization
◼Strategies to overcome user resistance
User participation, user education & training, management edicts and policies, incentives for
cooperation, improvement of end-user interface, resolution of organizational issues prior to
introduction of new system
◼Designing for the organization - IS projects must explicitly address the ways in which the
organization will change when the new system is installed, including installation of mobile
and web applications.
In addition to procedural changes, transformations in job functions, organizational structure,
power relationships, and the work environment should be carefully planned.
Managing IS Project Risks
◼Areas where users interface with the system require special attention, with sensitivity to
ergonomics issues.
Ergonomics refers to the interaction of people and machines in the work environment.
It considers the design of jobs, health issues, and the end-user interface of information systems
◼Thorough organizational impact analysis to be conducted explaining how a proposed system
will affect organizational structure, attitudes, decision making, and operations.
To integrate information systems successfully with the organization, thorough and fully documented
organizational impact assessments must be given more attention in the development effort.
◼Incorporate sociotechnical design to address addressing human and organizational issues
The social design plans explore different workgroup structures, allocation of tasks, and the
design of individual jobs.
Separate sets of technical and social design solutions and selecting solution that best blends
both design leading to technical efficiency with sensitivity to organizational and human
needs, leading to higher job satisfaction and productivity.
PM Software Tools
◼Commercial software tools that automate many aspects of project management facilitate the
project management process.
Typically features capabilities for defining and ordering tasks, assigning resources to tasks,
establishing starting and ending dates to tasks, tracking progress, and facilitating
modifications to tasks and resources.
◼MS Project - PC-based software, with capabilities for producing PERT and Gantt charts and
for supporting critical path analysis, resource allocation, project tracking, and status reporting.
◼Increase in SaaS, open-source software
◼Project portfolio management software - helps organizations manage portfolios of projects and
dependencies among them.
Helps managers compare proposals and projects against budgets and resource capacity
levels to determine the optimal mix and sequencing of projects that best achieves the
organization’s strategic goals
CHANGING ROLE OF CIO IN BUSINESS
• CIO stands for Chief Information Officer,
• CIO reverses all use of information technology in many companies
and brings into alignment with strategic business goals.
• Maintainance of all the computer services, internet technology,
telecommunication services and other IT.
• Job roles of CIO includes overseeing the development of customer
service platforms, approving vendor negotiations and IT architecture,
establishing IT policies, standards, and change in a business.
• Developing and approving technology futures and budgets
TYPES OF CHANGES IN A PROJECT
• Substitution changes: The change in demand for a good as a result of a
change in the relative price of the good compared to that of other
substitute goods.
For example, rebranding the item into a new form, restructuring and
updating the software into a new form so as to meet the business objectives.
TYPES OF CHANGES IN A PROJECT
◼Particularism - at a cultural level, making judgments and taking action on the basis of narrow
or personal characteristics, in all its forms (religious, nationalistic, ethnic, regionalism,
geopolitical position)
Rejects the very concept of a shared global culture
Rejects penetration of domestic markets by foreign goods & services.
◼Differences among cultures produce differences in social expectations, politics, and ultimately
legal rules.
State of the Art
◼Most companies have inherited patchwork international systems from the distant
past, often based on outdated concepts of information processing, with reporting
from independent foreign divisions to corporate headquarters, manual entry of
data from one legacy system to another, and little online control and
communication
◼Other companies have recently built technology platforms for international
systems but have nowhere to go because they lack global strategy.
◼Significant difficulties in building appropriate international architectures:
Planning a system appropriate to firm’s global strategy
Structuring organization of systems and business units
Solving implementation issues
Choosing right technical platform
Global strategies and Business organization