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.  Use project plans to coordinate rather than to control.  Make use of different personalities within the project environment.  Preschedule frequent revisions to project plans.  Empower workers to estimate their own work.  Describe value-creating tasks rather than activities.  Define specific and tangible milestones.  Use check lists, matrices, and other supplements to project plans. Internal Factors          Infrastructure Project scope Labor relations Project location Project leadership Organizational goal Management approach Technical manpower supply Resource and capital availability External Factors        Public needs Market needs National goals Industry stability State of technology Industrial competitors Government regulations Components of Project Plan           Summary of Project Plan Objectives Approach Policies and Procedures Contractural Requirements (document problematic areas) Project Schedule Resource Requirements Performance Measures Contingency Plans Tracking, Reporting, and Auditing Project Development Lifecycle Planning Phase  Define problem  Confirm project feasibility  Produce project schedule  Staff the project  Launch the project Analysis Phase  Gather information    Define system requirements Build prototypes for discovery of requirements    Problem Domain  Application 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 Organization Organizational Objective Organization Organizational Use of Technology 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  Tests of feasibility     Technical feasibility Operational feasibility Schedule Feasibility Economic feasibility Scope of Feasibility Analysis        Need Analysis Process Work Engineering & Design Cost Estimate Financial Analysis Project Impacts Conclusions and Recommendations Feasibility Dangers   A project that was once feasible may not remain so - why not? Feasibilities can often conflict!     Best solution can often be the most expensive good operational feasibility poor economic feasibility 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 Schedule Scope / Quality Managing Expectations  Columns in matrix are the priorities:      Max or Min: most important Constrain: median importance Accept: lowest importance Impossible to optimize all simultaneously! Rule: 1 check per row & column Expectation Management Priorities Max or Min Constrain X Cost: $20B Schedule: Deadline 12/1969 Scope / Quality: Man on the moon, return safely Accept X X Frequent Causes of Failures  Taking shortcuts with methodology   when/why do these occur? Cost of fixing errors, finding an error in:      Requirements: $1,000 Design: $2,500 Coding: $6,000 Testing: $25,000 Implementation: $75,000 Frequent Causes of Failures  Scope & Feature Creep   can be both good and bad, how? are mgmt intentions clear? Tests of Feasibility • 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 • Schedule Feasibility  How reasonable is the project timetable? • Economic Feasibility How cost-effective solution? Cost-benefit analysis  is the project or Operational 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? Technical 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? Economic 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? Project Budget Template Author's Name Cost Analysis 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$$) --Annual expense increase --Benefits and indirect costs changes per year --Benefits (as a percentage of wages) Expenses 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 Publication costs Total Administrative Costs Total Direct Cost Indirect Costs (at 54.5%) Yearly Project Costs $75,000 3% 0% 32% Year 1 Year 2 Year 3 Year 4 Year 5 Benefit Analysis •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 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 Economic Feasibility • Payback analysis How long will it take to recoup the costs of this project? Return on investment (ROI) analysis Net present value analysis Feasibility Analysis • Compare candidate systems on basis of several characteristics Better analysts always consider multiple solutions Candidate Systems Matrix Candida te Syste ms Ma trix Characte ristics Portion of System Computerize d Brief description of portion of system that would be computerized in this candidate. Ca ndida te 1 COTS package Platinum Plus from Entertainment Solutions, Inc. Be ne fits Brief description of business benefits that would be realized for this candidate Solution can be implemented quickly. Se rve rs a nd W orksta tions Description of the servers and workstations needed to support this candidate. PIV, MS Windows 2000 c lass servers and workstations Softw a re Tools Ne e de d Software tools needed to design and build the candidate solution (e.g., DBMS, operating systems, languages) Applica tion Softw a re Description of software to be built, purchased, accessed or some combination of the above. Me thod of Data Proce ssing On-line, batch, deferred batch, real-time Output Device s a nd Implica tions Output devices that would be used (e.g., network, preprinted forms, etc.) as well as output considerations (timing constraints) Input De vices a nd Implica tions Description of input methods to be used (e.g., keyboard, mouse, etc.), special input requirements (new or revised forms), input considerations (timing of actual inputs) Stora ge De vices a nd Implica tions Description of what data would be stored, what data would be accessed from existing stores, what storage media would be used, how much storage capacity needed, how that data would be organized. MS Visual C++ MS Access for customization of package for report writing. Package solution Client-server HP4MV dept laser printers keyboard & mouse MS SQL DBMS with 100G arrayed capability 10.13.01 Ca ndidate 2 Ca ndida te 3 Feasibility Analysis Matrix Feasibility Analysis Feasibility Criteria Weight Operational Feasibility Functionality: To what degree does the candidate solution benefit the organization? Political: How well will the solution be received by users? Management? 30% Technical Feasibility Technology: Assessment of maturity, availability, ability to acquire, and desirability of computer technology needed to support the candidate. Expertise: Assessment of the technical expertise needed to develop, operate, and maintain the candidate system 30% Economic Feasibility Cost to Develop Payback period (discounted) Net Present Value Detailed Calculations 30% Candidate 1 Ranking Candidate 2 Only supports Fully supports Members Services required requirements and functionality current business processes would have to be modified Score: 60 Score: 100 Candidate 3 Same as Candidate #2 Score: 100 Current release of Current technical Platinum Plus is staff only has 1.0; only on market Powerbuilder 6 weeks experience. Staff thinks Access app is simple. Score: 50 Score: 95 Score: 60 $350,000 $418,040 $400,000 4.5 years 3.5 years 3.3 years $210,000 $306,748 $325,500 See attachment A See Attachment A See Attachment A Score: 60 Schedule Feasibility Assessment of how long the solution will take to design and implement. 10.13.01 Score: 85 Score: 90 10% Less than 3 months 9-12 months 9 months Score: 95 Score: 80 Score: 85 60.5 92 83.5 [...]... 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  Tests of feasibility     Technical feasibility Operational feasibility Schedule Feasibility Economic feasibility Scope of Feasibility Analysis   ... Tests of Feasibility • 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 • Schedule Feasibility  How reasonable is the project timetable? • Economic Feasibility How cost-effective solution? Cost-benefit analysis  is the project. .. Project Impacts Conclusions and Recommendations Feasibility Dangers   A project that was once feasible may not remain so - why not? Feasibilities can often conflict!     Best solution can often be the most expensive good operational feasibility poor economic feasibility What can you do if the project is not feasible on all levels? Managing Expectations    Often most difficult aspect of a project. .. Feasibility How cost-effective solution? Cost-benefit analysis  is the project or Operational 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? Technical Feasibility • Questions to Ask Is the proposed solution practical? Do we possess the necessary... economic feasibility 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 Schedule Scope / Quality Managing Expectations  Columns in matrix are the priorities:      Max or Min: most important Constrain: median importance Accept: lowest importance ... Reporting, and Auditing Project Development Lifecycle Planning Phase  Define problem  Confirm project feasibility  Produce project schedule  Staff the project  Launch the project Analysis Phase... Continuing process of feasibility assessment  Tests of feasibility     Technical feasibility Operational feasibility Schedule Feasibility Economic feasibility Scope of Feasibility Analysis... of Feasibility • Schedule Feasibility  How reasonable is the project timetable? • Economic Feasibility How cost-effective solution? Cost-benefit analysis  is the project or Operational Feasibility