The purpose of this chapter is to introduce the first phase of the systems
development life cycle-identifying and selecting systems development projects.
The chapter takes the position that organizations can benefit from following a formal process
for identifying and selecting projects. To do this, the chapter first overviews the
corporate strategic planning process and then links this process to information systems
planning. Both are presented as a three-step process. For information systems planning,
the first step is described as a process in which a senior manager, a business group,
an IS manager, or a steering committee identify all possible systems development projects
that an organization unit could undertake. Next, projects are classified and ranked
according to some criteria that are important to the organization. Finally, those
projects deemed most likely to yield significant organizational benefits, given available
resources, are selected for subsequent development activities.


Introduction.

Identifying and Selecting Systems Development Projects.
focus) -
can be performed by :| Characteristics of alternative Methods for Making IS Identification and Selection Decisions | ||
|---|---|---|
| Selection Method | Characteristics | |
| Top Management | Greater Strategic Focus, Largest project Size, Longest Project Duration | |
| Steering Committee | Cross-Function Focus, Greater Organizational Change, Formal Cost-Benefit Analysis, Larger & Riskier Project | |
| User Department | Narrow, non-strategic Focus, Faster Development, Fewer users, Management Layers, and Business Functions | |
| Development Group | Integration with existing systems focus, Fewer Development Delays, Less Concern on Cost-Benefit Analysis | |
| Possible Evaluation Criteria When Classifying & Ranking Projects | |
|---|---|
| Evaluation Criteria | Description |
| Value Chain Analysis | Extent to which activities add value and costs when developing products and/or services |
| Strategic Alignment | Extent to which the project is viewed as helping the organization activities and long-term goals |
| Potential Benifits | Extent to which the project is viewed as improving profits, customer service, ... etc., and the duration of these benefits |
| Resource Availability | Amount and type of resources the project requires and their availability |
| Project Size/Duration | Number of individuals and the length of time needed to complete the project |
| Technical Difficulty/Risks | Level of technical difficulty to successfully complete the project within given time and resource constraints |

Corporate and Information System Planning.
Although there are numerous motivations for carefully planning the identification and
selection of projects, organizations have not traditionaly used systematic planning process when determining how to
allocate IS resources. Instead, projects have often resulted from attempts to solve isolated
organizational problems. In effect, organizations have asked the question:
What procedure (application program) is required to solve this particular problem as it exists today ?
The difficulty with this approach is that the required organizational procedures are likely to change
over time as the environment changes.
