Scribd
Upload
4K views2 pages

Sources Project Request

The document discusses the process for identifying, initiating, and planning IT projects within an organization. It describes several key aspects: - Projects can be identified from top-down sources like senior management or from bottom-up sources like user departments. - The planning process involves creating mission and objective statements to define the goals and strategies for a project. - Project initiation establishes teams and plans, including developing a project charter to communicate details to stakeholders. - Risk assessments evaluate the potential economic, technical, operational, schedule, legal, political, and maintenance risks of a project. - Structured walkthroughs involve peer reviews at different stages using roles like presenter, user, secretary, and standard-bearer.

Uploaded by

雪山飛狐
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4K views2 pages

Sources Project Request

The document discusses the process for identifying, initiating, and planning IT projects within an organization. It describes several key aspects: - Projects can be identified from top-down sources like senior management or from bottom-up sources like user departments. - The planning process involves creating mission and objective statements to define the goals and strategies for a project. - Project initiation establishes teams and plans, including developing a project charter to communicate details to stakeholders. - Risk assessments evaluate the potential economic, technical, operational, schedule, legal, political, and maintenance risks of a project. - Structured walkthroughs involve peer reviews at different stages using roles like presenter, user, secretary, and standard-bearer.

Uploaded by

雪山飛狐
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Sources project request

Management and business unit-for replacing and extending an existing


system to gain needed information or to provide new service to customer
IS managers-who want make system,less costly, more efficient, move to new
operating enviroment
Formal planning group-identify project for improvement to help organization
meet coperate objective
Project identify
Top management-CEO of small and medium organization or Senior Executive
of large organization
Steering committee-composed of cross section of managers with an interest
in system
User departments-head or committee of requesting deparments decides
which projects to submit
Development group or Is senior-project identified with existing hardware and
system will intergrate to proposed project
Project identify source
Top-down source-top management and steering committe,focus broader
needs of organization
Bottom-up source-user departments and IS development group,focus business
needs of organization
Planning Results
Mission statement-a statement that makes it clear what business company is
it in
Objective statement-a series of statement express an qualitative goal and
quantitative goals for reaching a desired future position
Competitive strategy-the method of organization to achieve mission and
objective
Project Initiation
-establishing project initiation team
-establishing project initiation plan
-developing project charter
Project charter
-high level overview of the project
-short document for internal and external stakeholder
-useful communication tools to assure organizations
understand initiation planning

and

stakeholder

Economic- a process of identifying the financial benefits and costs associated


with a development project
Technical- a process of assessing the development organizations ability to
construct a proposed system
Operational- Process of assessing the degree to which a proposed system
solves business problems or takes advantage of business opportunities
outlined in the System Service Request or project
identification study.
Schedule- Process of assessing the degree to which the potential time frame
and completion dates for all major activities within a project meet
organizational deadlines and constraints for affecting change.
Legal and contractual- Process assessing potential legal and contractual

ramifications due to the construction of a system.


Political- Process of evaluating how key stakeholders within the organization
view the proposed
system
Structured Walkthroughs: a peer-group review of any product created during
the system development process and are widely used by professional
development organizations.
Coordinator person plans the meeting and facilitates a smooth meeting
process.
Presenter person describes the work product to the group such as System
Analyst.
User person to make sure that the work product meet the needs of the
projects customers.
Secretary person takes notes and records decisions or recommendations
made by the group.
Standard-Bearer person to ensure that the work product adheres to
organizational technical
standards such as standard procedures, methods and documentation formats.
Maintenance Oracle person reviews the work product in terms of future
maintenance activities.
Characteristics System Analyst
Impertinence-question everything
Impartially-consider all issue and find the best organizational solution
Attention to detail-every fact must fit with other fact
Reframing-challenge to look at the organization in new ways
Interview
advantages
-personal contact allows the interviewer to respond adaptively to what is said.
-it is possible to probe in greater depth.
-if the interviewee has little or nothing to say, the interview can be
terminated.
dis advantages
-can be time-consuming and costly notes must be written up or tapes
transcribed after the interview
-can be subject to bias
-if interviewees provide conflicting information this can be difficult to resolve
later
Questionnaires
-economical way of gathering information from a large number of people.
-effective way of gathering information from people who are geographically
dispersed.
-results are less biased due to standardization.
-good questionnaires are difficult to design.
-no automatic way of following up or probing more deeply.
-postal questionnaires suffer from low response rates.

You might also like