project management concepts lt col l shri harsha, pmp

Download PROJECT MANAGEMENT CONCEPTS Lt Col L Shri Harsha, PMP

Post on 26-Dec-2015

213 views

Category:

Documents

1 download

Embed Size (px)

TRANSCRIPT

  • Slide 1
  • PROJECT MANAGEMENT CONCEPTS Lt Col L Shri Harsha, PMP
  • Slide 2
  • OBJECTIVES Create awareness of the concepts of Project Management and its importance Understand the various tools available to a Project Manager to perform his duties effectively Highlight the areas of the application of these concepts during the execution of projects
  • Slide 3
  • Importance of Project Management Getting things done in the correct manner Planned and prioritized work distribution and accomplishment Identification of key process bottlenecks and suggested preventive actions Project management process improvement Improved risk management Standardized reports, templates, processes and lexicon
  • Slide 4
  • What is a Project ? Has a defined objective Has a deadline Requires integration of knowledge and experience from various organizations When task(s),
  • Slide 5
  • How Temporary? Has a definite beginning and end, not an on-going effort Ceases when objectives have been attained Team is disbanded upon project completionUnique? The product or service is different in some way from other product or services Product characteristics are progressively elaborated What is a Project ?
  • Slide 6
  • Project Characteristics Goal (measurable/verifiable) Oriented Finite duration with a beginning and end Uniqueness to a great extent and related uncertainties Coordinated undertaking of interrelated activities Performing the activities involve resources Resources cost money
  • Slide 7
  • How are Projects different from Operations? Create own charter, organization, and goals Catalyst for change Unique product or service Heterogeneous teams Start and end date Semi-permanent charter, organization, and goals Maintains status quo Standard product or service Homogeneous teams Ongoing Projects Operations
  • Slide 8
  • Poor communication Insufficient resource planning Unrealistic schedules & poor duration estimation Poor project requirements Lack of stakeholder buy-in & no accountability Undefined project success / closure criteria Unrealistic budgets No risk planning Lack of change control process Lack of executive support Resource attrition Lack of synchronization Project Failure
  • Slide 9
  • Executive management support User involvement (optimum) Realistic expectations Clear statement of requirements Proper documentation Public exposure Competitive & Budgetary pressure Project Success
  • Slide 10
  • Project Life Cycle Each phase is marked by one or more tangible verification work product referred to as deliverable The conclusion of a project phase is generally marked by a review The phase reviews are often called phase exits, stage gates, or kill points PROJECT PHASE 1PHASE 2 PHASE 3 PHASE n
  • Slide 11
  • Level Of Activity Initiating Processes Planning Processes Executing Processes Closing Processes Controlling Processes Phase Finish Phase Start Time Typical Life Cycle of Project
  • Slide 12
  • Life Cycle of Project (Time) High Low Cost to make change Opportunity to add Value Characteristics of a Life Cycle
  • Slide 13
  • Balancing SCOPE, COST and TIME within the frame work of QUALITY* * meeting customer requirements Harold Kerzner Risk and customer satisfaction are also factors that often gets included in the perspective. Triple Constraint Theorem
  • Slide 14
  • The application of knowledge, skills, tools, and techniques to project activities in order to meet or exceed stakeholder needs and expectations Project Management
  • Slide 15
  • Project Manager Customer/User Performing Organization Project Team Members Project Management Team Sponsors Influencers Key Stakeholders : Generic Project Manager Customer / User Project Team Members Functional Departments Sales, BSG, Finance Business Partners Subsidiaries & Sister Concerns Vendors and Suppliers Key Stakeholders : X Firm Project Stakeholders Individuals and organizations Involved in or affected by the project outcome
  • Slide 16
  • Program Consists of a group of projects supporting broad, general goals and managed in a coordinated way Project Portfolio Management Collection of projects or programs and other work that are grouped together to facilitate effective management of that work to meet strategic business objectives Subprojects Components of a project that are often contracted out Project Management Office (PMO) A PMO sometimes also referred as Program Management Office is an organization to centralize and coordinate the management of projects under its domain Project Management Concept
  • Slide 17
  • Shared and coordinated resources Identification and development of project management methodology, best practices, and standards Clearinghouse and management for project policies, procedures, templates, and other shared documentation Central office for operation and management of project tools Central coordination of communication management across projects Coordination of overall project quality standards Project Management Office Support
  • Slide 18
  • Project Management Philosophy The Golden Rule of Project Management is three words: -Plan -Organize -Control
  • Slide 19
  • Project Initiation
  • Slide 20
  • Conduct Project Selection Methods Define Scope Document Project Risks, Assumptions, and Constraints Identify and Perform Stakeholder Analysis Develop Project Charter Obtain Project Charter Approval
  • Slide 21
  • Responsibilities Define goals, objective, milestones Determine requirements Determine ground rules and assumptions Identify time, cost and performance constraints Determine operating procedures, administrative policies Identify reporting requirements Project Charter Project Managers
  • Slide 22
  • Goals vs. Objective Goals are broad Objectives are narrow Goals are general intentionsObjectives are precise Goals are intangible Objectives are tangible Goals are abstractObjectives are concrete Goals can't be validated as isObjectives can be validated
  • Slide 23
  • Objectives are SMART S pecific M easurable A ssignable R ealistic T ime related
  • Slide 24
  • ExpectationsStakeholder Shareholder Employee What is my role and the job/task specifications in this project? What learning opportunity/new skill will I get from this project? Organization When can I get the product out? What is the quantum of work involved? How many people would this project need (skill level)? What would be their utilization/availability on this project? How much would the cost/ investment for resources be? When can I get the product? What are the features that exists (that I want eliminated now)? What are the additional feature desired? How much I would have to pay? Customer What is the company doing to minimize overheads & maximize profits? What are the efforts and direction for new avenues of business this year? How does this company compare with and stay ahead of competition? Managing Stakeholder Expectations
  • Slide 25
  • Project Planning
  • Slide 26
  • Develop Project Scope Define Project Phases Develop WBS Define Activity List & Sequence Activities Create Project Network Diagram Perform Critical Path Analysis Perform Cost Estimation Perform Resource Planning Project Planning
  • Slide 27
  • Plan Project Team Organization Create RAM Identify Project Risks and develop Risk Reponses Develop Project Management Plan Baseline the Project Management Plan Setting up Change Control Mechanism Key Tasks
  • Slide 28
  • Plan Do/Undo/Redo Start Complete Plan Execute Start Complete Benefit of Planning
  • Slide 29
  • Project Scope What is the WORK we are supposed to do to deliver the final service / product to the customer?
  • Slide 30
  • Product Scope The features and functionalities that categorize a product or service
  • Slide 31
  • 4 Commandments for Good Project Scope Written Well defined Clearly understood Achievable
  • Slide 32
  • 1.Highest level: refers to the entire project 2.Second level: breaks the project into its major sub- projects/phases 3.Third level: Identify the deliverables for each subproject/phase Identify the activities and tasks that are required to produce each deliverables Lowest level breakup called work packages can be scheduled, cost estimated, monitored and controlled Identifies track able units of work which are assigned to individual members of the project team Create Work Breakdown Structure
  • Slide 33
  • WBS Example
  • Slide 34
  • Schedule Management Create the Activity List State the Activity Relationships State the Resource Requirements Estimate the Activity Duration Create Project Schedule
  • Slide 35
  • Prepare Network Diagram Project schedule network diagrams are schematic displays of the projects schedule activities and the logical relationships among them, also referred to as dependencies.
  • Slide 36
  • Precedence Diagramming Method (PDM) Also known as Activity on Nodes (AON)
  • Slide 37
  • Arrow Diagramming Method (ADM) Also known as