13
Key Issues in SISP Methodologies

Key Issues in SISP Methodologies 2003

Embed Size (px)

Citation preview

Page 1: Key Issues in SISP Methodologies 2003

Key Issues in SISP Methodologies

Page 2: Key Issues in SISP Methodologies 2003

Problems in implementing SISP methodologies are

classified as

Resource,

Planning process,

Output related problem

Page 3: Key Issues in SISP Methodologies 2003

Output related problem

The most severe problem identified by IS

managers is the failure to secure top

management commitment for carrying out the

final plan.

The second most severe problem identified is

the requirement for substantial further analysis

after the completion of the IS plan.

Page 4: Key Issues in SISP Methodologies 2003

Resource related problem

Six of the next top eight problems are related to

the resources required to carry out the strategic

information systems planning :

Success of the plan depends on the team leader,

difficulty in finding the team leader meeting the

criteria specified in the study.

Methodology lacking computer support.

Planning exercise taking long time.

Page 5: Key Issues in SISP Methodologies 2003

Among the top ten problems encountered while

implementing one of these methodologies three are

common:

Difficulty in obtaining top management commitment

for implementing the outputs,

The requirement of substantial further analysis and

Difficulty in finding a good team leader.

Page 6: Key Issues in SISP Methodologies 2003

Summarizing the difficulties in implementation of SISP

Most organizations find it difficult to undertake it.

Their lack of experience with SISP.

Absence of a comprehensive, structured, easy to use

methodology.

Advances in Information Technology and their

applicability in organizations has outpaced all formal

methodologies evolved in the 70s and 80s or evolved

in 90s as marginally modified versions of the earlier

methodologies.

Page 7: Key Issues in SISP Methodologies 2003

The overall success of an integrated

business/technology architecture depends upon the

organizational structure, the level of IT experience

within the company and the availability of

information resources. Since these factors differ

between firms, there may not be a single best way

to view IT planning.

It is difficult to find a team leader who meets the

criteria specified in SISP methodologies

Page 8: Key Issues in SISP Methodologies 2003

Conceptual Framework for SISP

Page 9: Key Issues in SISP Methodologies 2003

Steps in a typical SISP formulation are:

Page 10: Key Issues in SISP Methodologies 2003

Step Importance Includes

Study Internal Business Environment.

to determining the business ISneeds

mission of the organization, objectives, strategies and plans, business activities, the organizational environment, core competencies, critical success factors and the internal value chain.

Study external business environment.

focus attention on the forces andpressure groups it encounters

industry that organization is in, industry’s critical success factors, competitive position of the organization in industry, relationship with major buyers and suppliers.

Study internal IS/IT environment

current and planned applications portfolio that supports the business , present IS organization, skills and attitudes of people in the organization, IT environment and the IS/IT budgets.

Page 11: Key Issues in SISP Methodologies 2003

Note Either after the completion of the top level model or

even during its completion, some critical vertical flows

can be identified.

Applications can then quickly be developed, tested

and implemented along those critical/competitive flows.

The rest of the model can await completion and

subsequent implementation while the organizational

resources are concentrated on developing applications

demanded by the exigencies of the current situation.

Page 12: Key Issues in SISP Methodologies 2003

Conclusions

Page 13: Key Issues in SISP Methodologies 2003

Information-based enterprises must be planned in an

integrated way whereby all stages of the life cycle are

engaged to bring about agility, quality, and

productivity.

The integration is similar in nature to the integration

of product life cycle for an enterprise.

A needed new approach would tap into enterprise’s

information resources which capture and characterize

the enterprise to allow for integration of the planning

stage with information systems development stages

and support a shortened and adaptive cycle.