Project Management Group

Slides:



Advertisements
Similar presentations
Roadmap for Sourcing Decision Review Board (DRB)
Advertisements

PROJECT RISK MANAGEMENT
Root Cause Analysis Procedure (IMSP525) Training
Project Based Risk Management Defusing a potential ticking time bomb
By Saurabh Sardesai October 2014.
10.5 Report Performance The process of collecting and distributing performance information, including status reports, progress measurements and forecasts.
Managing Project Risk.
IS&T Project Management: How to Engage the Customer September 27, 2005.
Runway Safety Teams (RSTs) Description and Processes Session 5 Presentation 1.
PRESENTED BY TRUST THOMAS EROMOSELE STUDENT NO:
Degree and Graduation Seminar Project Management Processes
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
PMP® Exam Preparation Course
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
NIST Special Publication Revision 1
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Software Project Management
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Georgia Institute of Technology CS 4320 Fall 2003.
Project Management Processes for a Project
Develop Project Charter
SOFTWARE PROJECT MANAGEMENT
Project Risk Management Planning Stage
(Project) RISK MANAGEMENT PROCESS SEPTEMBER 5, 2008.
Introduction to Project Management Chapter 9 Managing Project Risk
Project Management Project Integration Management Minder Chen, Ph.D. CSU Channel Islands
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Chapter 6 Internal Control in a Financial Statement Audit McGraw-Hill/IrwinCopyright © 2012 by The McGraw-Hill Companies, Inc. All rights reserved.
CMMI for Services, Version 1.3 Speaker: Business Excellence Date:
MGT 437 OUTLET Become Exceptional/mgt437outlet.com FOR MORE CLASSES VISIT
Project Management PTM721S
Continuous Improvement Project (A Guideline For Sponsors)
Steve Barfoot, President Advantage International Registrar, Inc.
PROJECT MANAGEMENT AND PLANNING
Software Project Configuration Management
Software Quality Control and Quality Assurance: Introduction
EIA approval process, Management plan and Monitoring
Monitoring and Evaluation Systems for NARS organizations in Papua New Guinea Day 4. Session 12. Risk Management.
Data Architecture World Class Operations - Impact Workshop.
12.3 Control Procurements The process of managing procurement relationships, monitoring contract performance and making changes or corrections as needed.
Project Based Risk Management Defusing a potential ticking time bomb
Software Configuration Management
Understanding the Principles and Their Effect on the Audit
Project Integration Management
Project Integration Management
TechStambha PMP Certification Training
CHAPTER11 Project Risk Management
Project Risk Management
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
UNIT-6 SOFTWARE QUALITY ASSURANCE
CMMI – Staged Representation
Engineering Processes
CIS12-3 IT Project Management
Risk Management Process (Revised)
UNIT-6 SOFTWARE QUALITY ASSURANCE
Before During After Follow-up Resolve Review Pre-review Familiarize
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Prepared and Presented By:- Abhishek Rautela
Metrics for process and Projects
Portfolio, Programme and Project
Engineering Processes
Configuration Management
Managing Project Work, Scope, Schedules, and Cost
ISSUE MANAGEMENT PROCESS MONTH DAY, YEAR
Executive Project Kickoff
Project Kick-off <Customer Name> <Project Name>
{Project Name} Organizational Chart, Roles and Responsibilities
Project Name Here Kick-off Date
Presentation transcript:

Project Management Group Prepared and Presented By:-Abhishek Rautela For Internal use only

Project Management Process Areas Project Planning (PP) Project Monitoring and Control (PMC) Integrated Project Management (IPM) Risk Management (RSKM) Decision Analysis and Resolution (DAR) Metric Analysis (MA)

PP & PMC The purpose of this process is to prepare the work plans for carrying out the project’s activities and also to lay down the procedure to monitor and control the project activities. Reference Process(QMS) :Project Management Process. Key Players\Group: Project Managers.

PP & PMC Process Start Stop Roles & Responsibilities: Entry Criteria : Base lined SOW PIN (Emails, Power point presentations etc) Roles & Responsibilities: 1. Project Director -Approve the PMP. 2. Project Manager:- Prepare PMP & Schedules ,Identify Deliverables Plan, organize, lead, and monitor the activities of the project Checks for regular project status and deliverables. Take Actions against NC’s 3.QA:- Certify all of the project deliverables Tasks: Process Tailoring PIN meeting. Preparation of PMP Change request handling Project monitoring and control Planning and managing status reporting Tracking outstanding items. Audit Findings and NC Output: PMP Weekly status Report CR Log Schedule Stop

Integrated Project Management The purpose of Integrated Project Management (IPM) is to establish and manage the project and the involvement of the relevant stakeholders according to an integrated and defined process that is tailored from the organization’s set of standard processes. Reference Process(QMS) :Project Management Process, Client Engagement Process Reference Guidelines: Project Tailoring Guidelines Key Players\Group: Project Managers

Expectations from the PA. Integrated Project Management involves the following: Establishing the project’s defined process at project startup by tailoring the organization’s set of standard processes Managing the project using the project’s defined process Establishing the work environment for the project based on the organization's work environment standards Using and contributing to the organizational process assets Enabling relevant stakeholders’ concerns to be identified, considered, and, when appropriate, addressed during the development of the product Ensuring that the relevant stakeholders perform their tasks in a coordinated and timely manner (1) to address product and product component requirements, plans, objectives, problems, and risks; (2) to fulfill their commitments; and (3) to identify, track, and resolve coordination issues

Risk Management This is to provide a guideline to the project managers for planning, assessing (identifying and analyzing) risk areas, developing risk handling options, monitoring risks and documenting the overall risk management process. Generic Risks : Generic risks are a potential threat to every software project. Hence nature is universal Work Related Risks: These are special characteristics of the product. This type of risk is specific to the project at hand and may vary from project to project Reference Guidelines: Guidelines for Risk Management Key Players\Group: Project Managers

Process Description Risk Management Risk Planning Risk Assessment Risk Handling Risk Monitoring Risk Control Risk Avoidance Risk Assumption Risk Identification Risk Analysis, rating prioritization

Risk Analysis, Rating & prioritization Project / Engagement / Function Name:   Last updated on : Responsible Person for tracking and addressing the risk: Risk ID Risks Discription Probability (1/2/3/4/5) Impact (1/2/3/4) Value Risk Handling Approach Category Mitigation Strategy Contingency Plan Date Iden Date Review Action Taken Status Probability (P) Levels Impact (I) Values Risk Level Values (P x I) 1 - (R)emote 1 - (N)egligible 1 to 2 – Trivial 2 - (U)nlikely 2 - (M)arginal 3 to 4 – Normal 3 - (L)ikely 3 - (C)ritical 5 to 9 – Low 4 - (H)ighly likely 4 - (S)howstopper 9 to 14- Medium 5 - (N)ear certainty 15 to 25- High

DAR The purpose of Decision Analysis and Resolution (DAR) Process is to analyze possible decisions using a formal evaluation process that evaluates identified alternatives against established criteria. Reference Process(QMS) :Project Management Process. Key Players\Group: Project Managers, Designers

DAR Process Start Stop Roles & Responsibilities: Entry Criteria Business or Technical decision impacting organization Selection of Risk handling option: Roles & Responsibilities: 1. Senior Management: Reviews DAR activities. 2. Project Manager: Assigns issue, selects decision team and its facilitator, approves resulting decisions 3. Facilitator: Leads team meeting in determining evaluation method, criteria, weighting, scoring, and decision-making discussions. 4. Team members: Perform research for alternatives evaluate alternatives, and present findings at team meeting for discussion Tasks: 1.Initiate a DAR event 2.Formulate decision objective and scope 3.Generate criteria and weighting 4.Identify alternatives 5.Select decision-making method 6.Rate criteria for each alternative 7.Develop composite scores for the alternatives 8.Select and communicate best-fit alternative Output: Communicate best-fit selected alternative DAR Document (Optional) Stop

Metric Process Software process and product metrics are quantitative measures that enable software people to gain insight into the efficacy of the software process and the projects that are conducted using the process as a framework. Basic quality and productivity data are collected. These data are then analyzed, compared against past averages, and assessed to determine whether quality and productivity improvements have occurred. Metrics are also used to pinpoint problem areas so that remedies can be developed and the software process can be improved. Reference Process(QMS) :Metric Process Key Players\Group: Project Managers, QA

Metric Process Start Stop Roles & Responsibilities: 1. Project Manager Entry Criteria : Business objectives PMP ,schedules. Roles & Responsibilities: 1. Project Manager Metric Plan Inclusion in PMP Metric Analysis 2.QA:- Metric Plan Creation at Project and organization level. Data Collection Review Analysis Tasks: Data Collection Store Data Evaluate Data Result of Analysis Corrective and Preventive action Output: Metric reports. Review meeting of SEPG . Stop

Conclusion Thank You