1 / 18

Chapters 4 & 5 Getting Started with an IS Project

Chapters 4 & 5 Getting Started with an IS Project. Ch. 4: Project Identification & Selection Ch. 5: Project Initiation & Planning. Agenda. Chapter 4 Topics Where Do Projects Come From? Role of IS Architecture and Planning Projects from Re-engineering BSP Information Cross

nellis
Télécharger la présentation

Chapters 4 & 5 Getting Started with an IS Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapters 4 & 5Getting Started with an IS Project Ch. 4: Project Identification & Selection Ch. 5: Project Initiation & Planning

  2. Agenda • Chapter 4 Topics • Where Do Projects Come From? • Role of IS Architecture and Planning • Projects from Re-engineering • BSP Information Cross • Project Selection Exercise

  3. Chapter 4 Learning Objectives • Describe the processes for project identification and selection • Describe IS planning and relationship to corporate planning • Describe how IS planning assists project identification and selection • Understand affinity matrices and their use in IS and project planning • Describe internet EC applications: internet, intranet, extranet

  4. and Figure 1-6 SDLC-based guide to this book Chapters 4-5 Chapter 16 Chapters 6-9 Chapter 15 Chapters 10-14

  5. So, Where Do Projects Come From? • IS Planning • Top management, strategic, large, long • Steering Committee • Integration, great change, formal CBA, large and risky • User department/manager • Specific business need, need soon, fewer users and layers and functions • Development group • New platform, improvements/integration, CBA not done or unclear

  6. Zachmann, J. A. (1987). A framework for information systems architecture. IBM Systems Journal 26 (3), 276-292.

  7. Hay, D. C. (1997). The Zachman framework: an introduction. The Data Administration Newsletter (1). Available at: http://www.tdan.com/i001fe01.htm

  8. What Roles Does IS Architecture Play in Project Generation? • Shows important components of enterprise-wide picture of systems, about which projects can be defined: • Data -- What • Process -- How • Network -- Where • People -- Who • Events -- When • Objectives -- Why (Zachmann) • AS-IS vs. TO-BE (over time) • Projects are the means for transition

  9. IS Architecture: A Way to Place a Project in Context • Need to relate work in a project to business scope, business model, information systems model, technology model, technology definition, and information system in all dimensions • A way to show relationship between projects and the level at which a project affects architecture • A way to show IS plan -- what is changing through all projects

  10. Other Reasons for an IS Architecture • Shared understanding • Way to communicate the future • Help make decisions (e.g., which projects to select) • Communicate to vendors • Way to find opportunities to integrate

  11. Question: “Architecture” sounds good on paper—what issues (technical, organizational, etc.) inhibit your ability to create the IS plan or architecture you want?

  12. BSP Information Cross Provide data and services to - re-engineer Responsibility to perform - reorganize and re-engineer Processes Systems Units Provide procedures to collect, organize, maintain data - IS design Responsibility to provide integrity - stewardship Databases

  13. Projects from Re-engineering • Planning matrices • Location, function, unit, objective, process, data entity, information system, ... • Affinity clustering • Look for strong relationships between elements • Share data • Redesign or relocate processes • Prioritize processes, data, systems, etc.

  14. Organizational Change Process “AS IS” “TO BE” Transform IS Projects

  15. “Racking and Stacking” Projects Sources of Potential Projects Project ID and Selection Project Initiation and Planning Top Down Schedule of Projects: 1. 2. 3. Evaluate, prioritize, schedule Bottom Up

  16. Opinion: Generally speaking, which is “better”: top down or bottom up planning processes?

  17. Project Selection -- Making the Case • UD IS Steering Committee representing Admin. & Finance, Provost, Student Services, UDRI -- develop how you will decide to pick only one proposal --all funds come from central budget for development and are therefore limited! • Three proposals: • Provost Council & Admissions: Electronic application submission– system enhancement • Rudy’s Fly Buy: Frequent purchaser promotional program--new system • UDRI: Faculty skills inventory to direct research opportunities to appropriate faculty--major system enhancement

  18. Chapter 4 Summary • Project Identification and Selection

More Related