Вы находитесь на странице: 1из 5

Chapter 3

Feasibility Analysis & Systems Project Management

Overview
Determining Feasibility,
Managing Analysis and ‰ project initiation
Design Activities ‰ determining
project feasibility
Professor Merrill Warkentin
‰ project scheduling
Mississippi State University
‰ managing project activities
‰ managingsystems analysis
team members
2 © Copyright 2005, Merrill Warkentin

Reasons for initiating projects Improvement possibilities


‰ Problems that lend themselves ‰ speeding up a process ‰ reducing redundant
to systems solutions ‰ streamlining a process storage
‰ combining processes ‰ reducing redundant
‰ Opportunities for improvement through
output
ƒ upgrading systems ‰ reducing errors
in input ‰ improving system and
ƒ altering systems subsystem integration
ƒ installing new systems

3 © Copyright 2005, Merrill Warkentin 4 © Copyright 2005, Merrill Warkentin

Managing Design Activities Managing analysis & design


‰ teams and tension ‰ promote
communication between
members
‰ develop common norms
ƒ utilize feedback to minimize tension
‰ enhance communication/team-building ƒ create explicit norms

‰ agree on productivity goals ‰ set productivity goals


ƒ based on member expertise,
‰ motivate team members past performance,
nature of the specific project

5 © Copyright 2005, Merrill Warkentin 6 © Copyright 2005, Merrill Warkentin

Copyright 2004, Merrill Warkentin page 1


Chapter 3
Feasibility Analysis & Systems Project Management

Managing analysis & design Project selection criteria


‰ motivate project team members ‰ backed by management
ƒ affiliation, control, ‰ timed appropriately for
independence, creativity commitment of resources
‰ avoid project failures ‰ moves the business toward
ƒ take advantage of training, attainment of its goals
experience, project analysis
‰ practicable
‰ important enough to be considered
over other projects

7 © Copyright 2005, Merrill Warkentin 8 © Copyright 2005, Merrill Warkentin

Feasibility Technical Feasibility


‰ feasibilitystudy assesses the ‰ Can we do it? - Is technology available?
operational, technical, and economic ‰ are current technical resources sufficient
merits of the proposed project to build the new system?
‰ can resources be upgraded to provide the level of
‰ three type
technology necessary for the new system?
ƒ technical feasibility
ƒ economic feasibility
ƒ operational feasibility
ƒ schedule, legal, ethical

9 © Copyright 2005, Merrill Warkentin 10 © Copyright 2005, Merrill Warkentin

Economic Feasibility Economic Feasibility Analysis


‰ Can we afford it? Will it pay for itself? ‰ Costs
‰ whether the time and money are ƒ development costs
available to develop the system ƒ operating costs
‰ includes the purchase of
‰ Benefits
ƒ new equipment
ƒ hardware ƒ tangible (quantifiable)
ƒ software ƒ intangible - important!
‰ How do we decide?

11 © Copyright 2005, Merrill Warkentin 12 © Copyright 2005, Merrill Warkentin

Copyright 2004, Merrill Warkentin page 2


Chapter 3
Feasibility Analysis & Systems Project Management

Operational feasibility Other Feasibility Factors


‰ Should we do it? Can we make it work? ‰ schedule feasibility
‰ determines if the human resources are ƒ can it be completed on time?
available to operate the system
‰ legal feasibility
once it has been installed
‰ users that do not want a new system ƒ does it violate any laws?
may prevent it from becoming ‰ social and ethical feasibility
operationally feasible
ƒ is it right?

13 © Copyright 2005, Merrill Warkentin 14 © Copyright 2005, Merrill Warkentin

Feasibility Analysis Feasibility Study


‰ define project objectives ‰ define problem, objectives, scope
ƒ determine organizational objectives
‰ identify constraints and limitations
ƒ verify that objectives are acceptable
‰ develop alternative solutions
‰ determine resources
‰ estimate costs & benefits
‰ judge feasibility
ƒ decision is made by management ‰ prepare feasibility report
ƒ systems analyst provides expert advice ‰ system proposal for senior mgt.

15 © Copyright 2005, Merrill Warkentin 16 © Copyright 2005, Merrill Warkentin

Feasibility Impact Grid (FIG) Activity planning


‰ used to assess the impact of any ‰ design team selection & assignment
improvements to the existing system
‰ estimate task time
‰ can increase awareness of the impacts
made on the achievement of ‰ schedule project / task
corporate objectives
‰ current or proposed systems on the left
‰ objectives listed on the top
‰ red arrows indicate a positive impact
‰ green arrows indicate implementation

17 © Copyright 2005, Merrill Warkentin 18 © Copyright 2005, Merrill Warkentin

Copyright 2004, Merrill Warkentin page 3


Chapter 3
Feasibility Analysis & Systems Project Management

Activity control Activity planning & control


‰ estimate time required
‰ monitoring using feedback
ƒ major phases
‰ expediting or rescheduling ƒ individual tasks
ƒ time for each task
‰ motivating teams
‰ scheduling
ƒ Gantt charts
ƒ PERT diagrams
‰ expediting
ƒ constantly review schedules and
costs over life of project
19 © Copyright 2005, Merrill Warkentin 20 © Copyright 2005, Merrill Warkentin

Scheduling tools Computer-based project scheduling


‰ benefits
Gantt Charts PERT Diagrams
ƒ low cost
ƒ simple, intuitive, GUI
ƒ variety of display options

‰ programs
ƒ Microsoft Project
ƒ Symantec’s Timeline
ƒ CA-Super Project

‰ personal information managers (PIMS)


ƒ ECCO
ƒ Organizer

21 © Copyright 2005, Merrill Warkentin 22 © Copyright 2005, Merrill Warkentin

GANTT charts PERT charts


‰ project scheduling technique ‰ nodes = events
‰ each bar represents a task ‰ establishes critical path
‰ length of bars = relative length of task (longest, no slack time)

‰ visual, simple ‰ portrays order of precedence


A

‰ enhances
B ‰ helps identify critical activities
C

communication D and slack time A,4


20
C,5

E 10 40 E,6 50

B,2 D,3
30

23 © Copyright 2005, Merrill Warkentin 24 © Copyright 2005, Merrill Warkentin

Copyright 2004, Merrill Warkentin page 4


Chapter 3
Feasibility Analysis & Systems Project Management

PERT diagram advantages Team management


‰ easy identification of the ‰ teams often have two leaders:
order of precedence ƒ one who leads members to accomplish tasks
‰ easy identification of the critical path ƒ one concerned with social relationships
and thus critical activities ‰ the systems analyst must manage
‰ easy determination of slack time, ƒ team members
the leeway to fall behind on ƒ their activities
non-critical paths ƒ their time, and resources

25 © Copyright 2005, Merrill Warkentin 26 © Copyright 2005, Merrill Warkentin

Goal setting
‰ set for tangible outputs and Copyright Notice
process activities This document may not, in whole or part,
be copied, photocopied, reproduced, translated, transmitted,
‰ must be reasonable
or reduced to any electronic medium or machine readable form
‰ help to motivate without explicit permission and written authorization
from Dr. Merrill Warkentin.
team members mwarkentin@acm.org
MISProfessor.com

27 © Copyright 2005, Merrill Warkentin 28 © Copyright 2005, Merrill Warkentin

Copyright 2004, Merrill Warkentin page 5

Вам также может понравиться