RISK CONTROL.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Project Management Process. Managing the Information Systems Project Focus of project management To ensure that information system projects meet customer.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Systems Analysis and Design 8 th Edition Chapter 3 Managing Systems Projects.
Module 11 Session 11.2 Visual 1 Module 11 Executing and Controlling the Work Session 11. 2: Managing Contracts.
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
CS 325: Software Engineering April 7, 2015 Software Configuration Management Task Scheduling & Prioritization Reporting Project Progress Configuration.
ICS Management Poor management is the downfall of many software projects Software project management is different from other engineering management.
Systems Analysis and Design 8th Edition
Chapter 5 IT Processes Presented by Dr. Mohamed Sammouda.
Managing the Information Technology Resource Jerry N. Luftman
What is a project? Project Management Institute definition
CS Integration Management (Part 6) Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009 Dr.Çağatay ÜNDEĞER Instructor Bilkent University,
Project Management Session 7
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Project Management and Scheduling
Release & Deployment ITIL Version 3
What is Business Analysis Planning & Monitoring?
Unit Introduction and Overview
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Computer System Analysis
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Sense of Initiative and Entrepreneurship This project has been funded with support from the European Commission. This [publication] communication reflects.
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
S/W Project Management
Copyright Course Technology 1999
Software Testing Lifecycle Practice
Test Organization and Management
Information System Design IT60105 Lecture 21 Staff Organization, Risk Management and Software Configuration Management.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
1 Project Management Introduction. 2 Chap 1 What is the impact? 1994: 16% of IT projects completed “On-Time” 2004 : 29% of IT projects “On- Time” 53%
Software Project Management
Webster Visualize Webster Financial Team Visual Scrumware Joe Andrusyszyn Mark Bryant Brian Hannan Robert Songer.
Effective Project Management: Traditional, Agile, Extreme Presented by (facilitator name) Managing Complexity in the Face of Uncertainty Ch08: How to Close.
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.
N O T E “CLICK” TO CONTINUE… If the slide show is not launched, click on View  Slide Show in the menu bar at the top of the Power Point window. When the.
Risk( 风险 ) Management Presented by Basker George.
Initiation and Planning for Success Sridhar Seshagiri Rao, PMP Innova Solutions Inc. Santa Clara, CA. April 9 th 2004.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
Project Management.
1A FAST EXCELLENCE THROUGH FACILITATION Gary Rush The FAST Process MGR Consulting
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Monitoring Risk Factors General attitude of team members based on project pressures The degree to which the team is jelled Interpersonal relationships.
Team-Based Development ISYS321 Managing the Information Systems Project.
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
MIS Project Management Instructor: Sihem Smida Project Man agent 3Future Managers1.
Risk Mitigation Submitted By, S. Anitha Devi, M.E-CSE.
Chapter 3 Managing the Information Systems Project
Project Integration Management
Description of Revision
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Planning a Software Project
Software Testing Lifecycle Practice
Project Management Techniques Project Management Life Cycle
Chapter 3 Managing the Information Systems Project
{Project Name} Organizational Chart, Roles and Responsibilities
Chapter 2 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Presentation transcript:

RISK CONTROL

RISK MANAGEMENT PLANNING Once risks are identify and prioritized, it should be clear which risks the project should handle. For managing risks , proper planning is essential. The main task is to identify the action needed to minimize the risk consequences.This steps are generally called a “risk mitigation steps”. As in risk identification, a list of commonly used risk mitigation steps for various risks is compiled to aid the project leader in selecting a suitable risk mitigation step.

Goal of risk management Once the risk have been identified and prioritized,the question becomes what to do with them? The risk is the value only if we can prepare such that their consequences are minimal-That is the basic goal of risk management. Minimizing the risk effects is done in the second phase of risk management-risk control. This step involves planning of risk matigation , followed by execution of plan and monitoring of the risk.

Top ten risk and their risk mitigation steps Sequence no Risk category Risk Mitigation steps 1 Shortage of technically trained manpower Make estimate with little allowance for initial learning time. Maintain buffers of extra resources. Define a project-specific training program. Conduct cross-training session. 2 Too many requirement changes. Obtain sign-off for initial requirement specification from the client. Convince the client that changes in requirements will affect the schedule. Define procedure to handle requirement changes. Negotiate payment on actual effort.

Top ten risk and their risk mitigation steps Sequence no Risk category Risk Mitigation steps 3 Unclear requirements Use experience and Logic to make some assumption and keep the client informed. Develop a prototype/get the requirements reviewed by the client. 4 Manpower attrition Ensure that multiple resources are assigned on key project areas. Have team building sessions Rotate jobs among team members. Keep extra resources in the project as backup

Top ten risk and their risk mitigation steps Sequence no Risk category Risk Mitigation steps Maintain proper documentation of individual’s work. Follow the configuration management process and guidelines strictly. 5 Externally driven decisions forced on the project Outline disadvantages with supporting facts/data and negotiate with the personnel responsibility for forcing the decision. If inevitable, identify the actual risk and follow its mitigation plan.

Top ten risk and their risk mitigation steps Sequence no Risk category Risk Mitigation steps 6 Not meeting performance requirements Define the performance criteria clearly and get them reviewed by the client. Define standard to be followed to meet the performance criteria. Prepare the design to meet performance criteria and review it. 7 Unrealistic schedule Negotiate for a better schedule. Identify parallel task. Identify areas that can be automated.

Top ten risk and their risk mitigation steps Sequence no Risk category Risk Mitigation steps 8 working on new technology Begin with delivery of critical modules. Include time in the schedule for learning curve. Provide training in the new technology. 9 Insufficient business knowledge increase interaction with the client and ensure adequate knowledge transfer. Organize domain knowledge training.

Top ten risk and their risk mitigation steps Sequence no Risk category Risk Mitigation steps 10 Link failure/slow performance Set proper expectation with client. Plan for optimal link usage.

RISK MONITORING AND TRACKING Risk prioritization and consequent planning are based on the risk perception at the time the risk analysis is performed. The first risk analysis takes place at the time of project planning, and the initial risk management plan reflects the situation as viewed at that time. This dynamism implies that risks in a project should not be treat as static and reevalution of risk needs to be done periodically.

RISK MONITORING AND TRACKING Hence besides monitoring the progress of risk mitigation steps that have been planned , the risk perception for the entire project needs to be revisited periodically. This revision is prepared by doing afresh the risk analysis to determine whether the priority have changed.

Thank you