| A | B |
|---|
| 3 people that general initiate a new system request | upper management, user groups, the IT department |
| Type of system upper management will request | large, lengthy projects geared toward strategy, organizational change, or managerial information |
| type of system user groups will request | transaction-oriented and are usually geared toward saving time or expense |
| Type of system the IT department will request | designed to support the IT infrastructure, integrate existing systems, etc. |
| Feasibility analysis | used to aid in the decision of whether or not to proceed with the IS project. Looks at technical, economic, and organizational feasibility. Can and should be conducted several time throughout a project |
| project | identified when someone sees an opportunity to create business value from using IT |
| project sponsor | a key person proposing the development or adoption of the new IT |
| approval committee | review proposals from various groups and units in the organization and decides which to commit to developing |
| 3 Primary Activities of identification and selection | 1. Identifying potential development projects 2. classifying and ranking projects 3. selecting projects for development |
| Technical Feasibility | Answers questions such as: can it be built, do we know how, can we learn how, how difficult will it be to build, and how difficult will it be to learn? |
| Economic Feasibility | How much will it cost, how much will the client get out of it, and is it even worth it? |
| Organizational Feasibility | Do the organizations' power people support it, does it fir the strategy and long-term plans of the organization (strategic alignment), do the potential users like the idea, and will the users actually use it if it is implemented? |
| 3 primary stakeholder groups | Champion, organizational management, and system users |
| Champion | initiates and promotes the project, allocates his time to the project, and provides resources to the project |
| Organizational Management | knows about the project, budgets enough money for it, and encourages users to accept and use the system |
| System Users | Make decisions that influence the project, perform hands-on activities for the project. Ultimately determine whether the project is successful by using or not using the program |
| Improve with Champions | Make a presentation about the objectives of the project and the proposed benefits to those executives who will benefit directly from the system. Create a prototype of the system to demonstrate its potential value |
| Improve with Organizational Management | Make a presentation to management about the objectives of the project and the proposed benefits. Market the benefits of the system using memos and organizational newsletters. Encourage the champion to talk about the project with his or her peers |
| Improve with Users | Assign users official roles on the project team, assign users specific tasks to perform with clear deadlines, ask for feedback from users regularly |
| a high-level, noninformation systems executive who is usually, but not always, the project sponsor who created the system request | Where does the project champion come from? |
| Project Portfolio Management | a process that optimizes project selection and sequencing in order to best support business goals. |
| Business goals | expressed in terms of quantitative economic measures, business strategy goals, IT strategy goals |
| System Request | a document that describes the business reasons for building a system and the value the system is expected to provide. Generally filled out by whoever wants the system |
| Key elements of the system request | project name; project sponsor; business need; business requirements(functionality); expected business value; and special issues or constraints |
| Project Sponsor | The person who initiates the project and who serves as the SPOC for the project on the business side |
| Examples of a project sponsor | members of FINA dept, VP of MKT, IT MGR, steering committee, CIO, CEO |
| Business Need | the business-related reason for initiating the system |
| Examples of business needs | increase sales, improve market share, improve access to information, improve customer service, decrease product defects, streamline supply chain |
| Business Requirements | the business capabilities that the system will provide |
| Examples of business requirements | Provide online access to information, capture customer demographic info, include product search capabilities, produce mgmt reports, include online user support |
| Examples of business value | 3% increase in sales, 1% increase in market share, reduction in headcount by 5, 200k supply cost savings |
| business value | the benefits that the system will create for the organization |
| Special Issues or constraints | issues that are relevant to the implementation of the system and decisions made by the committee about the project |
| Examples of special issues or constraints | Gov't-mandated deadline for may 30, system needed by xmas, security clearance needed to work with data |
| Tangible business value | quantified and easily measured. Ex: 2% cost reduction |
| Intangible business value | important, but hard to measure benefits to the organization. Ex: improved customer service or a better comparative position |
