Project planning feasibility study

Project planning feasibility study tài liệu, giáo án, bài giảng , luận văn, luận án, đồ án, bài tập lớn về tất cả các lĩ...

Project Planning &

Feasibility Study

R Ramesh Babu Senior Lecturer/SMBS

VIT

Project Planning

Guidelines for Project Plans

control

environment

project plans

Components of Project Plan

 Summary of Project Plan

 Objectives

 Approach

 Policies and Procedures

 Contractural Requirements (document

Project Development Lifecycle

Planning Phase

 Define problem

 Confirm project feasibility

 Produce project schedule

 Staff the project

 Launch the project

Analysis Phase

 Gather information

 Problem Domain

 Application

 Define system requirements

 Build prototypes for discovery of

requirements

 Prioritize requirements

 Generate and evaluate alternatives

 Review recommendations with management

Design Phase

 Design and integrate the network

 Design the application architecture

 Design the user interfaces

 Design the system interfaces

 Design and integrate the database

 Prototype for design details

 Design and integrate the system controls

Implementation Phase

 Construct software components

 Verify and test

 Convert data

 Train users and document the system

 Install the system

Support Phase

 Maintain the system

 Enhance the system

 Support the users

 Help desk

Technology Development

Obsolescence of today’s products

Organization

Organizational

Objective

Another Illustrated Example…

Preventing of

Failures

Project Feasibility

 Measure of how beneficial or practical the development of an information system will be to an organization.

 Process by which feasibility is measured

 Continuing process of feasibility assessment

Scope of Feasibility Analysis

Feasibility Dangers

 A project that was once feasible may not

remain so - why not?

 Feasibilities can often conflict!

 What can you do if the project is not feasible

on all levels?

Managing Expectations

 Often most difficult aspect of a project

 Tool for balancing priorities

 Rows in matrix are project dimensions:

 Cost

Managing Expectations

 Columns in matrix are the priorities:

 Impossible to optimize all simultaneously!

 Rule: 1 check per row & column

Frequent Causes of Failures

 Taking shortcuts with methodology

 Cost of fixing errors, finding an error in:

Frequent Causes of Failures

 Scope & Feature Creep

• Operational Feasibility

 How well will the solution work in the organization?

• Technical Feasibility

 How practical is the technical solution?

 How available are technical resources and expertise?

Tests of Feasibility

• Questions to Ask

 Is the problem worth solving?

 Will the solution to the problem work?

 How do end users and management feel about the solution?

 Has a usability analysis been conducted?

Operational Feasibility

• Questions to Ask

 Is the proposed solution practical?

 Do we possess the necessary technology?

 Do we possess the necessary technical

expertise?

 Is the schedule reasonable?

Technical Feasibility

• Cost-benefit analyses

 How much will the system cost?

 Development costs

 Operation costs

 Maintenance and support costs

 Do we possess the necessary technology?

 Do we possess the necessary technical

expertise?

 Is the schedule reasonable?

Economic Feasibility

Cost Analysis

Project Budget Template

Author's Name Organization Name, Date Assumptions

Personnel/Infrastructure assumptions Infrastructure assumptions

Initial network and remote access upgrades covered in ZYX project

Programmatic assumptions

Budget currently contains expenses only Revenues to be estimated upon completion of market survey

Worksheet and expense assumptions

Average manager salary (2002$$) $75,000

Benefits and indirect costs changes per year 0%

Benefits (as a percentage of wages) 32% Expenses Year 1 Year 2 Year 3 Year 4 Year 5 Personnel

Benefits (at 32%) Hardware Software Computer Usage Costs Training Costs Library Resources

Program Maintenance and Upgrade Costs Travel Costs

Administrative Costs

Administration Postage, Fedex Communications

Total Administrative Costs Total Direct Cost Indirect Costs (at 54.5%) Yearly Project Costs

•Benefit analyses

 Tangible benefits can be easily quantified.

 Measured in terms of monthly or annual

savings, or of profit to organization

 Intangible benefits more difficult to quantify.

Benefit Analysis

Benefit Analysis

Tangible Benefits

• Fewer processing errors

• Increased throughput

• Decreased response time

• Elimination of job steps

• Increased sales

• Reduced credit losses

• Reduced expenses

Intangible Benefits

• Improved customer goodwill

• Improved employee morale

• Better service to community

• Better decision-making

• Payback analysis

 How long will it take to recoup the costs of this project?

 Return on investment (ROI) analysis

 Net present value analysis

Economic Feasibility

• Compare candidate systems on basis of several characteristics

 Better analysts always consider multiple solutions

Feasibility Analysis

Candidate Systems Matrix

Candidate Systems Matrix 10.13.01

Characteristics Candida te 1 Candidate 2 Candida te 3 Portion of System Computerized

Solutions, Inc

Be ne fits

Se rvers and W orkstations

Softw are Tools Needed

report writing

Application Softw are

purchased, accessed or some

combination of the above

Method of Data Processing

Output Devices and Implications

as output considerations (timing constraints)

Input Devices and Implications

(e.g., keyboard, mouse, etc.), special

input requirements (new or revised forms),

input considerations (timing of actual inputs)

Stora ge Devices and Implications

how much storage capacity needed, how

that data would be organized

Feasibility Analysis Matrix

Feasibility Analysis 10.13.01

Feasibility Criteria Weight Candidate 1 Candidate 2 Candidate 3 Operational Feasibility 30%

Functionality: To what degree does the Only supports Fully supports Same as

processes would have to be modified

Score: 60 Score: 100 Score: 100 Technical Feasibility 30%

Economic Feasibility 30%

Payback period (discounted) 4.5 years 3.5 years 3.3 years

Detailed Calculations See attachment A See Attachment A See Attachment A

Score: 60 Score: 85 Score: 90 Schedule Feasibility 10%

take to design and implement.

Score: 95 Score: 80 Score: 85