fallsem2014-15_cp2496_08-aug-2014_rm01_unit-ii

Upload: saurabh-tripathi

Post on 02-Jun-2018

217 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/11/2019 FALLSEM2014-15_CP2496_08-Aug-2014_RM01_unit-II

    1/3

    UNIT - II

    Planning phase

    Project Initiation :Introduction

    Here the organization creates and assess the original goals and expectations for a newsystem.

    First step is to identify the project-that will deliver the value of business

    Second step the analyst performs a feasibility analysis to determine technical, economic,

    and organizational feasibility analysis.hirdly the appropriate project is selected and the development of the project begins

    Objectives of project initiation!nderstand the importance of lin"ing the information system to business needs.

    #e able to create system re$uirements!nderstand how to assess technical, economic and organizational feasibility

    #e able to perform feasibility analysis

    !nderstand how projects are selected in some organization.Feasibility %nalysis

    Feasibility analysis guides the organization in determining whether to proceed with the

    project

    &t identifies the important ris" associated with the project that must be addressed if theproject is approved.

    he most common feasibilities are echnical, 'conomic, (rganizational.echnical FeasibilityFamiliarity with application) *ess familiarity generates more ris".

    Familiarity with technology.

    +roject size) *arge projects have more ris".ompatibility) he harder it is to integrate the system with company existing technology

    the higher the ris".

    'conomic Feasibility

    evelopment cost,%nnual operating cost,

    %nnual benefits cost saving and revenue/

    &ntangible costs and benefits.(rganizational Feasibility

    +roject champions

    Senior management!sers

    (ther sta"e holders

    &s the project strategically aligned with the business.

    +roject 0anagement -&ntroduction

  • 8/11/2019 FALLSEM2014-15_CP2496_08-Aug-2014_RM01_unit-II

    2/3

    &t describes the important step of the project management

    &t begins with planning phase, and continuous throughout the S*.

    &t estimates the size of the project and identifies the tas" that need to be performed.Staffs the project and puts several activities in place to help co-ordinate project activities.

    &t includes wor" plan, staffing plan, and standards list.

    &t is the process of planning and controling the development of a system.&t is an actual profession, and analyst spend years wor"ing on projects prior to tac"ling

    the management of them.

    Identifying the project size

    +roject management is in ma"ing trade offs and 1 important concepts) he size of the

    system interms of what it does/ the time to complete the project when the project will

    be finished / and the cost of the project.hese 1 things are interdependent lever that the project manager controls throughout the

    S*

    2henever one lever is pulled the other lever are affected in someway.

    here are two basic ways to estimate the time re$uired to build a system.he simplest method uses the amount of time spent in the planning phase to predict the

    time re$uired for entire project. he idea is that a simple project will re$uire littleplanning and complex project will re$uire more planning.

    Typical business application system spend !" of its effort in planning# $%" in

    analysis# &!" in design phase and &%" in implementation phase3

    Function +oint %pproach

    he second approach to estimation is called function point approach.

    &t is more complex, and it is hoped more reliable three step process.First the project manager estimates the size of the project in terms of *ines of code.

    he size estimate is then converted into the amount of effort re$uired to develop the

    system.

    he estimated effort is then converted into an estimated schedule time in terms of the

    number of months from start to finish.((0( 0odel

    &t is one of the most common algorithm.

    ((0( model vary based on the complexity of the software, size of the system the

    experience of the developers and the type of software you are developingreating and managing wor" plan

    he project manager has a general idea of the size and approximate schedule for the

    project and he or she creates a wor" plan.

    &t is a dynamic schedule that records and "eeps trac" of all the tas"s that need to be

    accomplished over the course of the project.

    The 'or( plan lists each tas( along 'ith important information captured by the

    'or( plan)

    *i"e name of the tas"

  • 8/11/2019 FALLSEM2014-15_CP2496_08-Aug-2014_RM01_unit-II

    3/3

    Start date

    ompletion date

    +ersons assignedeliverables

    ompletion status

    *taffing of the Project

    How many people must be assigned to the project

    &t determines average number of staffs needed for the project&t describes number of people who will wor" on the project

    o calculate this figure divide the total person-months of effort by the optimal schedule.

    oordinating the project activities

    *i"e all project management responsibilities the act of coordinating the project activities

    continuous through out the entire project until a system is delivered to the project sponsor

    and end users.