Ch04-Selecting and Planning Projects.pdf

Object oriented system analysis and design

1. 4-1
© Prentice Hall, 2007
Chapter 4: Chapter 4: Selecting and Planning  Selecting and Planning  Projects Projects Object-Oriented Systems Analysis and
Design
Joey F. George, Dinesh Batra,
Joseph S. Valacich, Jeffrey A. Hoffer
4-2
© Prentice Hall, 2007
Chapter Objectives Chapter Objectives
C
Describe the steps involved for identifying
and selecting, initiating, planning, and
executing projects.
C
Describe several methods for feasibility
assessment.
C
Describe tangible vs. intangible benefits
and costs, and one-time vs. recurring costs.
4-3
© Prentice Hall, 2007
Chapter Objectives (Continued) Chapter Objectives (Continued)
C
Perform cost-benefit analysis by performing
net present value (NPV), return on
investment (ROI), and breakeven analysis.
C
Explain Project Scope Statement and
Baseline Project Plan (BPP).
C
Describe the activities and roles in a
structured walkthrough.
4-4
© Prentice Hall, 2007

2. 4-5
© Prentice Hall, 2007
Identifying and Selecting   Identifying and Selecting   OOSAD Projects OOSAD Projects h
Top-down approaches C
Top management
C
Steering committees
h
Bottom-up approaches C
User departments
C
Development group
4-6
© Prentice Hall, 2007
4-7
© Prentice Hall, 2007
Each stakeholder group brings their own perspective
and motivation to the IS decision
4-8
© Prentice Hall, 2007

3. 4-9
© Prentice Hall, 2007
4-10
© Prentice Hall, 2007
4-11
© Prentice Hall, 2007
The project charter is a
short document that
formally announces
project and briefly
describes its objectives,
assumptions, and
stakeholders
4-12
© Prentice Hall, 2007
Managing the Project: Managing the Project: Initiation Tasks Initiation Tasks 1.Establishing the project initiation team
2.Establishing a relationship with the
customer
3.Establishing the project initiation plan
4.Establishing management procedures
5.Establishing the project management
environment and the project workbook
6.Developing the project charter

4. 4-13
© Prentice Hall, 2007
Managing the Project: Managing the Project: Planning Tasks Planning Tasks 1.Describing project scope, alternatives, and
feasibility
2.Dividing the project into manageable tasks
3.Estimating resources and creating a
resource plan
4.Developing a preliminary schedule
5.Developing a communication plan
4-14
© Prentice Hall, 2007
Managing the Project: Managing the Project: Planning Tasks (cont.) Planning Tasks (cont.) 6.Determining project standards and
procedures
7.Identifying and assessing risk
8.Creating a preliminary budget
9.Developing a project scope statement
10.Setting a baseline project plan
4-15
© Prentice Hall, 2007
System Service Request
(SSR) is a form requesting
development or
maintenance of an
information system. It
includes the contact
person, a problem
statement, a service
request statement, and
liaison contact
information.
4-16
© Prentice Hall, 2007
Feasibility Assessment Feasibility Assessment h
Economic feasibility
h
Technical feasibility
h
Operational feasibility
h
Schedule feasibility
h
Legal and contractual feasibility
h
Political feasibility

5. 4-17
© Prentice Hall, 2007
Economic Feasibility Economic Feasibility h
Cost-benefit analysis – identify all the
financial benefits and costs associated with a
project
h
Tangible vs. intangible benefits
h
Tangible vs. intangible costs
h
One-time vs. recurring costs
4-18
© Prentice Hall, 2007
Three financial measures for cost-benefit analysis
4-19
© Prentice Hall, 2007
Net Present Value Net Present Value
PV
n
= present value of
Y
dollars
n
years from now
based on a discount rate of
i
.
NPV
= sum of PVs across years.
Calculates time value of money.
4-20
© Prentice Hall, 2007
BEA determines the
time at which benefits
begin to exceed costs

6. 4-21
© Prentice Hall, 2007
Technical Feasibility Technical Feasibility h
Assessing the organization’s ability to
construct the proposed system
h
Takes into account various project risk
factors
4-22
© Prentice Hall, 2007
4-23
© Prentice Hall, 2007
High technical familiarity mitigates risk due to pr oject
size and structure. Low familiarity increases risk.
4-24
© Prentice Hall, 2007
Other Feasibility Concerns Other Feasibility Concerns
h
Operational C
Will the system achieve the objectives of the project?
h
Schedule C
Can the project be accomplished in a reasonable time fr ame?
C
Project management critical path scheduling can help answ er
this concern.
h
Legal/Contractual C
Are there regulations or legal obligations that affect the
success of the project?
h
Political C
Will the project have user and management support?
C
Will there be resistance?

7. 4-25
© Prentice Hall, 2007
Baseline Project Plan
(BPP) is a document
intended primarily to
guide the development
team, containing an
overview of the project, a
detailed description of
the system, a complete
feasibility assessment,
and a list of management
issues.
4-26
© Prentice Hall, 2007
Project Scope
statement is part of
the BPP, and
identifies the
problem or
opportunity, the
project objectives,
description, benefits,
deliverables, and
expected duration.
4-27
© Prentice Hall, 2007
What is a Structured Walkthrough? What is a Structured Walkthrough?
h
A peer-group review of any product created
during the system development process h
- Individuals attending can have the following
h
roles: coordinator, presenter, user, secretary,
h
standard-bearer, maintenance oracle
h
- Can be applied to BPP, system specifications,
h
logical and physical designs, program code,
test
h
procedures, manuals and documentation
4-28
© Prentice Hall, 2007
Structured
walkthrough form