Presentation is loading. Please wait.

Presentation is loading. Please wait.

IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-1 IntroductionFramework&PrinciplesRational Unified.

Similar presentations


Presentation on theme: "IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-1 IntroductionFramework&PrinciplesRational Unified."— Presentation transcript:

1 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-1 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement IS Project Management

2 Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-2 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Introduction What is a Project ? A project is a temporary endeavour undertaken to create a unique product or service  The end is reached : Project objectives are achieved, or Project is terminated  Temporary does not mean short in duration  Temporary does not apply project`s products or services  All temporary tasks are not projects  Temporary nature of projects may apply to other aspects : The opportunity is temporary and – The project team is temporary  Doing something which has not been done before  The project might have repetitive elements  The characteristics must be progressively elaborated : Elaboration of product characteristics must be coordinated with project scope definition Ideally the scope of the project should remain constant as the product characteristics change. Examples: Developing a new product Changing the structure of organization Implementing a new design process Operations are not projects: Operations are ongoing and repetitive Project always begin with Problem (John J. Rakos)

3 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-3 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Introduction Progressive Elaboration  Integrates concepts of temporary and unique As the product is unique it should be progressively elaborated.  The scope of the project should remain constant even as the product scope is progressively elaborated.  Example: Problem analysis Requirements specification Software design Coding Testing

4 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-4 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Introduction Rich picture of a general software-development process (Mireles and Jacobo)

5 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-5 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Introduction What is a Project Management ? Project management is the application of knowledge, skills, tools, and techniques to project activities in order to meet project requirements Requires to balance: Scope, time, cost and quality: Scope/quality Cost Time  Involves stakeholders with different needs and expectations  Involves identified requirements  Management by projects is not project management.

6 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-6 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Relationship to Other Disciplines Project Management Knowledge and Practice Management Knowledge and Practises Application Area Knowledge And Practises Software estimation Life cycles Quality models Significance of problem domain knowledge Operations: Planning Organizing Staffing Executing Controlling Introduction

7 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-7 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Introduction Why The Project Fail ? – John J. Rakos Failure at The Start Do not get off the ground (without a plan) Unrealistic deadline and budget Failure in The Development stages Analysis and design are not documented The responsibilities are not clear assigned to spesific individuals Design, testing, and implementation methods are invaluable Lack of walk-through’s and review Many project failures are blamed on turnover Lack of development standard Brute force techniques such as add more manpower don’t work Failure at The End Delivery without thorough debugging Do not deliver the promised performance Maintenance cost is too high Overrun in expense and schedule, unhappy users, damaged reputation, waste expensive talent, etc

8 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-8 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Framework&Principles Project Management Framework Scope Mgt Time Mgt Cost Mgt Quality Mgt Project Integration Management HR Mgt Comm Mgt Risk Mgt Procure Mgt Tools and Techniques Stakeholders needs and expectations Core Function Facilitating Function

9 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-9 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Project Management Framework Integration Management  Plan development  Project plan execution  Overall change control Scope Management  Initiation  Scope planning  Scope definition  Scope verification  Scope change control Time Management  Activity definition  Activity sequencing  Activity durationestimating  Schedule development  Schedule control Cost Management  Resources Planning  Cost estimating  Cost budgeting  Cost control Quality Management  Quality planning  Quality assurance  Quality control HR Management  Organizational planning  Staff acquisition  Team development Comm. Management  Communications Planning  Information distribution  Performance reporting  Administrative closure Risk Management  Risk identification  Risk quantification  Risk response development  Risk response control Risk Management  Procurement planning  Solicitation planning  Solicitation  Source selection  Contract administration  Contract close-out Framework&Principles

10 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-10 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Framework&Principles DefinitionAnalysisDesignProgrammingSystem TestAcceptanceOperation Requirements Go/no Go decision Proposal Requirement Document (*) (userS.O.) Analysis ProposalProposal (User buys) Preliminary project plan (resource provider S.O) Functional specification Development Proposal Re-estimate Functional Spesification (user S.O) Estimates and Project plan (re-done) Top level design System Design ATP Re-estimate Design specifica. (walked thru.) Acceptance test Plan (user s.o) Revised estimates (done) Module Design Coding Module Design (walked thru) System test Plan (Done) User Documen- Tation (started) Programs (tested) Project leader (S.O) Integration Testing Working/ Debugged System (Proj.Mgr S.O.) Acceptance Test Test Result (user S.O.) User Supported Cutover Warranty Sell next project Post Project Rev. Maintenance New system Operational (user satis.) Proposal for Next project (user buy) ACTIVITIES Project Management Reviews Status Reports DocumentationUser Training DOCUMENTS AND (MILESTONES) Relative Effort (PM) (Total Staff) (*) PROJECT PHASE (*) The requirements Document may or may not be part of the project John J. Rakos

11 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-11 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Framework&Principles The Iterative Model graph shows how the process is structured along two dimensions

12 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-12 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Framework&Principles

13 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-13 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement The principles of modern software management (Royce Walker) Base the process on an architecture-first approach Establish an iterative life-cycle process that confronts risk early Transition design methods to emphasize component-based development Establish a change management environment Enhance change freedom through tools that support round-trip engineering Framework&Principles

14 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-14 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Capture design artifacts in rigorous, model-based notation Instrument the process for objective quality control and progress assessment Use a demonstration-based approach to assess intermediate artifacts Plan intermediate releases in groups of usage scenarios with envolving levels of detail Establish a configurable process that is economically scalable Framework&Principles

15 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-15 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Framework&Principles Work Breakdown Structure  Determine how to organize the work breakdown  Time based, i.e. planning/analysis/design/construct/ test/implement  Deliverable based, i.e. online application/data warehouse/user query tools  Geography based, i.e. Chicago Pilot Test/Midwest Region/Eastern Region  Other …  Any breakdown should end up covering all the work  Sequencing not important for WBS

16 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-16 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Work Breakdown Structure Framework&Principles SIA PROJECT Level 0 Level 1 Level 2 Level 3 0.0 DEFINITION ANALYSIS DESIGN PROGRAMMING SYSTEM TEST ACCEPTANCE OPERATION 1.02.03.04.05.06.07.0 Requirement Document Requirement Document Feasibility Study Feasibility Study Risk Analysis Pre. Project Plan Pre. Project Plan Proposal Negotiate Proposal Negotiate Proposal 1.11.21.31.41.51.6 Interviews Analyse Existing Sys. Analyse Existing Sys. Define New Sys. Function Define New Sys. Function Write Funct. Specification Write Funct. Specification Negotiate Func. Spec. Negotiate Func. Spec. 2.12.22.32.42..5 Office Manager Office Manager Warehouse Supervisor Warehouse Supervisor Registrars CEO Accountant 2.1.12.1.22.1.32.1.42.1.5

17 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-17 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Framework&Principles When Do You Stop? Some person (or group for larger project) can take responsibility for the task, or to accomplish the activities involved You can get rough estimate of the effort (person days) needed to perform the activity (or activities involved) You can schedule the task The task must be small and able to be completed Estimate (person-day)2 2 1 1 3 2 Total 11 days Registration System Registration System Warehouse System Warehouse System CEO’s Business CEO’s Business Accountant’s Business Accountant’s Business Documents Data Flow Data Flow Analyses Existing Sys. Analyses Existing Sys.

18 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-18 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Mind-Mapping Approach

19 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-19 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement

20 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-20 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement

21 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-21 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement 1.0 Concept 1.1 Evaluate current systems 1.2 Define Requirements 1.2.1 Define user requirements 1.2.2 Define content requirements 1.2.3 Define system requirements 1.2.4 Define server owner requirements 1.3 Define specific functionality 1.4 Define risks and risk management approach 1.5 Develop project plan 1.6 Brief Web development team 2.0 Web Site Design 3.0 Web Site Development 4.0 Roll Out 5.0 Support Intranet WBS in Tabular Form

22 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-22 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Intranet WBS and Gantt Chart in Project 2000

23 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-23 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement

24 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-24 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Framework&Principles The person responsible for the plan (probably the project manager for a small to mid sized project) then collate all the estimate and precedent, as follows ACTIVITYEFFORTPRECEDENTS Definition20- Analysis35Definition Design25Analysis Program A (Control)20Design Program B (Registration)30Design Program C (Warehouse)25Design System Test10Program A, B, C Documentation20Design Acceptance5System Test, Documentation Training10Documentation Operation10Acceptance TOTAL210 Note: This example only the progranning had sub-component. If there are any sub- component of any other major activity avaliable, they would also be listed Network Diagram

25 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-25 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Framework&Principles Network Diagram STRT 0 DEF 20 ANAL 35 DES 25 PGMB 30 SYS TST 10 ACC 5 OPER 10 END PGMB 30 PGMB 30 PGMB 30 OPER 10 Precedence Network Another Format ….. Activity on Arrow 0 1 Activity n t

26 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-26 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Critical Path Method 1 2 A 10 day 3 45 67 B C G D E F 5 day 3 day 4 day 6 day 3 day 5 day 0 10 0 + 10 15 10 + 5 13 10 + 3 17 13 + 4 20? 17 + 3 21? 15 + 6 21 26 21 + 5

27 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-27 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Critical Path Method 1 2 A 10 day 3 45 67 B C G D E F 5 day 3 day 4 day 6 day 3 day 5 day 0 10 15 13 17 2126 21 26 - 5 15 21 - 6 18 21 - 3 14 18 - 4 11 ? 14 - 3 10 ? 15 - 5 100 10 - 10

28 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-28 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement Critical Path Method 1 2 A 10 day 3 45 67 B C G D E F 5 day 3 day 4 day 6 day 3 day 5 day 0 10 15 13 17 2126 21 15 18 14 100 Project Duration: 26 day : Critical path

29 IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-29 IntroductionFramework&PrinciplesRational Unified ProcessSPM PlanSuplement


Download ppt "IS Project Management Program Pascasarjana, Universitas Gunadarma, Magister Management, Budi Hermana-1 IntroductionFramework&PrinciplesRational Unified."

Similar presentations


Ads by Google