Project Management – PTM721S

Slides:



Advertisements
Similar presentations
Project Selection (Ch 4)
Advertisements

Chapter 4: Project Integration Management
Chapter 5: Project Scope Management
Chapter Four Project Initiation and Integration. Learning Objectives  Discuss the strategic planning process and apply different project selection methods/Select.
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
This work is licensed under a Creative Commons Attribution 3.0 Unported LicenseCreative Commons Attribution 3.0 Unported License (CC-BY). Project Management.
Project Integration Management
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
Copyright 2009  Develop the project charter: working with stakeholders to create the document that formally authorizes a project—the charter  Develop.
Project Management Project Initiation & Selecting
Project Scope Management
Chapter 4: Project Scope Management
HIT241 - Project Scope Management Introduction
Chapter 4: Project Integration Management
HIT241 - Management and Information Systems Management & Project Management Running an information systems project calls for ability in all management.
Project Management CIS 486 Fall 2005 Week 3 Lecture Dr. David Gadish
The Analyst as a Project Manager
Chapter 3: The Project Management Process Groups
Chapter 5: Project Scope Management
Chapter 4: Project Initiation
Chapter 5: Project Scope Management
Learning Objectives Describe an overall framework for project integration management as it relates to the other PM knowledge areas and the project life.
Project Scope Management
Lecture 2_3: Project Integration Management
Introduction ► This slide deck provides a suggested framework for the financial evaluation of an investment project. When evaluating any such project,
Project Integration Management Chapter 4. Copyright 2014 The Key to Overall Project Success: Good Project Integration Management Project managers must.
Information Technology Project Management, Sixth Edition Note: See the text itself for full citations.
Week5: Project Scope Management
Lecturer -Raja Natarajan Jul Project Integration and Scope Management Identifying, Selecting and Defining a Project ……….
IT Project Management, Third Edition Chapter 5 1 Chapter 2: Project Scope Management.
Copyright 2008  Most organizations cannot undertake most of the potential projects identified because of resource limitations and other constraints.
Project Scope Management Project management Digital Media Department Unit Credit Value : 4 Essential Learning time : 120 hours.
Project Scope Management Mohammad A. Rob. Importance of Good Project Scope Management Studies found that user involvement, a clear project mission, a.
Chapter 03 Project Scope Management
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
Copyright 2008  Project management process groups progress from initiating activities to planning activities, executing activities, monitoring and controlling.
Develop Project Charter
Chapter 4: Project Integration Management
Project Initiation and Integration
Project Scope Management 1. 2 Learning Objectives Understand the elements that make good project scope management important. Explain the scope planning.
PROJECT MANAGEMENT PLAN - EXECUTIVE SUMMARY
SCOPE DEFINITION,VERIFICATION AND CONTROL Ashima Wadhwa.
Information Technology Project Management, Seventh Edition.
Chapter 4: Project Integration Management Information Technology Project Management, Fourth Edition.
The Project Management Process Groups
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
Module Four, Session One Develop Project Charter.
Project Management PTM721S
Project Management PTM721S
Project Management – PTM712S
Project Management PTM721S
Mr. Joshua Mario Project Management
Project Management – PTM721S
Factors to consider System component costs Methods
Project Planning: Scope and the Work Breakdown Structure
Project Management – PTM712S
Software Project Management
Project Management – PTM712S
IF 3507 Manajemen Proyek Perangkat Lunak
Project Management PTM721S
Systems Analysis and Design in a Changing World, 4th Edition
Project Initiation.
Project Integration Management
Chapter 4: Project Integration Management
IF 3507 Manajemen Proyek Perangkat Lunak
Project Management PTM721S
Chapter 5: Project Scope Management
PROJECT SCOPE MANAGEMENT
Project Management Process Groups
PROJECT SCOPE MANAGEMENT
Presentation transcript:

Project Management – PTM721S Faculty of Computing and Informatics 7 August2017 Project Management – PTM721S Lesson 5 – Project scope management

Project scope management Faculty of Computing and Informatics Project scope management Why organisations invest in IT projects Definition of project scope management Project scope management processes Project initiation – techniques for selecting projects Scope planning and scope statement Scope definition and WBS Scope verification and scope change control

Why organisations invest in IT projects? Faculty of Computing and Informatics Why organisations invest in IT projects? Support explicit business objectives Has good Internal Rate of Return (IRR) Supports implicit business objectives Has good Net Present Value (NPV) Has reasonable payback period Used in response to competitive systems Supports management decision making

Why organisations invest in IT projects? Faculty of Computing and Informatics Why organisations invest in IT projects? Meets budgetary constraints High probability of achieving benefits Good accounting rate of return High probability of completing projects Meets technical/system requirements Supports legal/government requirements Good profitability index Introduces new technology

Definition of project scope management Faculty of Computing and Informatics Definition of project scope management Scope refers to all work involved in creating the products of a project and all processes used to create them A deliverable is a product produced as part of the project Deliverables can be project-related such as pieces of hardware or software or process-related such as a planning document or minutes of meeting

5 Project scope management processes Faculty of Computing and Informatics 5 Project scope management processes Initiation – committing organisation to begin a project or continue to next phase – PROJECT CHARTER Scope planning – developing documents to provide basis for future project decision – CRITERIA FOR COMPLETION Scope definition – subdividing major project deliverables – WORK BREAKDOWN STRUCTURE Scope verification – formalizing acceptance of project scope Scope change control – controlling changes to project scope – SCOPE CHANGES, CORRECTIVE ACTION, LESSONS LEARNT

Initiation – Identifying potential projects – SWOT Analysis Faculty of Computing and Informatics Initiation – Identifying potential projects – SWOT Analysis

Initiation – 5 techniques for selecting projects Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects Focusing on broad organisational needs Categorising information technology projects Performing Net Present Value (NPV) analysis, present value or other financial analyses Using a weighted scoring model Implementing a balanced scorecard

Does the project meet need? Does the project meet funding? Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects - Focusing on broad organisational needs Organisational needs, e.g., improve safety, increase moral, provide better communications, improve customer service Three criteria: Does the project meet need? Does the project meet funding? Does the project meet will?

Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – categorizing IT projects Problems – undesirable situations that prevent an organisation from achieving its goals, e.g. getting information in a timely manner Opportunities – chances to improve organisation, e.g. enhance sales by selling products directly to customer Directives – requirements imposed by management, government or external vendors Time it will take to complete project, e.g., customer requires vendor to use EDI to do business with them Overall priority of project

Initiation – 5 techniques for selecting projects – Net Present Value Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Net Present Value Net Present Value (NPV) is a method of calculating the expected net monetary gain or loss from a project by discounting all expected future cash inflows and outflows Estimated costs and benefits of project and products Determine discount rate – minimum acceptable rate of return on investment - what organisation would expect to receive elsewhere for investment of similar nature

Initiation – 5 techniques for selecting projects – Net Present Value Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Net Present Value

The higher the ROI, the better Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Return on Investment (ROI) (see next slide for example) Return on investment (ROI) are results of subtracting project costs from benefits and then dividing by costs ROI = (total discounted benefits – total discounted costs) / discounted costs ROI = (516, 000 – 243,200) / 243, 200 = 112% The higher the ROI, the better

Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Return on Investment

Initiation – 5 techniques for selecting projects – Payback analysis Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Payback analysis Payback period is the amount of time it will take to recoup, in the form of net cash inflows, the net dollars invested in a project

Initiation – 5 techniques for selecting projects – Payback Analysis Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Payback Analysis

Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Weighted scoring model A weighted scoring model is a tool that provides a systematic process for selecting projects based on many criteria Identify criteria important to the project selection process Assign weights (percentages) to each criterion so they add up to 100% Assign scores to each criterion for each project Multiply the scores by the weights and get the total weighted scores The higher the weighted score, the better

Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Weighted scoring model

Initiation – 5 techniques for selecting projects – Balanced scorecard Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Balanced scorecard A balanced scorecard is a methodology that converts and organisation’s value drivers such as customer service, innovation, operational efficiency and financial performance to a series of defined metrics www.balancedscorecard.org

Faculty of Computing and Informatics Initiation – 5 techniques for selecting projects – Balanced scorecard example

Faculty of Computing and Informatics Project Charter A project charter is a document that formally recognizes the existence of a project and provides direction on the project’s objectives and management Key project stakeholders should sign a project charter to acknowledge agreement on the need and intent of the project; a signed charter is a key output of project integration management

Parts of the Project Charter Faculty of Computing and Informatics Parts of the Project Charter Project title and date of authorization Project manager’s name and contract information A brief description of project objectives A summary of planned approach for managing project A roles and responsibilities matrix A sign-off section for signatures of key project stakeholders A comments section in which stakeholders can provide important comments related to project

Scope planning and scope statement Faculty of Computing and Informatics Scope planning and scope statement Project scope planning is developing documents to provide the basis for future decisions including the criteria for determining if a project or project phase has been completed successfully The output of project scope planning: Witten scope statement Project scope management plan

Scope planning and scope statement – scope statement Faculty of Computing and Informatics Scope planning and scope statement – scope statement Scope statement is a document used to develop and confirm a common understanding of the project scope Project justification – business need for project Brief description of project’s products – characteristics of products or services the project will produce Summary of project deliverables – e.g. problem plan, WBS, cost estimate, communications management plan, performance reports Quantifiable criteria for project success, e.g. cost, schedule, quality measures References to supporting documents, e.g. org. charts,

Scope planning and scope statement – project scope management plan Faculty of Computing and Informatics Scope planning and scope statement – project scope management plan A project management plan is a document used to coordinate all project planning documents and help guide a project’s execution and control The components of a project management plan Introduction or overview of the project Description of how the project is organized Management and technical processes used on the project Work to be done, schedule, and budget information

Scope planning and scope statement – sample project management plan Faculty of Computing and Informatics Scope planning and scope statement – sample project management plan

Scope definition and work breakdown structure (WBS) Faculty of Computing and Informatics Scope definition and work breakdown structure (WBS) WBS is a deliverable-oriented grouping of work involved in a project that defines the total scope of the project. For example: Evaluate current systems Define requirements Define specific functionality Define risk and risk management approach Develop project plan Brief project team Design and develop prototype Roll out Support

Scope verification and scope change control Faculty of Computing and Informatics Scope verification and scope change control Scope verification involves formal acceptance of project scope by the stakeholders Factors causing IT project problems: Lack of user input Incomplete requirements and specifications Lack of executive support Technology incompetence Lack of resources Unrealistic expectations Unclear objectives Unrealistic time frames New technology

Thank You. Faculty of Computing and Informatics 13 Storch Street Private Bag 13388 Windhoek NAMIBIA T: +264 61 207 2258 F: +264 61 207 9258 E: fci@nust.na W: www.nust.na Faculty of Computing and Informatics Thank You.