Chapter 10 Risks.

Slides:



Advertisements
Similar presentations
What is PEO?.
Advertisements

PeopleSoft Time & Labor What Roles are in Time & Labor? 1) Individual 2) Manager 3) Timekeeper.
TK3333 Software Management Topic 7: Schedule Control.
Copyright 2010, The World Bank Group. All Rights Reserved. Statistical Project Monitoring Section B 1.
Irwin/McGraw-Hill ©The McGraw-Hill Companies, 2000 Chapter 5 Managing Risk.
Systems Analysis and Design 8th Edition
1 Fundamental Principles of Solution Design and Implementation Chapter 3.
Risk Analysis- 1 MIS Practicum Risk Analysis Based on E.M. Bennatan, On Time, Within Budget. John Wiley & Sons, 1995.
Computer Engineering 203 R Smith Risk Management 7/ Risk Management The future can never be predicted with 100% accuracy. Failure to plan for risks.
IT Project Risk See also Sommerville Chapter 22.1.
Software Management Plan (part I) Software management’s 7 deadly sins The “3 P’s” of software management Why big software projects fail: the key 12 questions.
Presented by Levent Yıldızgören TTC Language Services Ltd & Learnproject.
Chapter 25 Risk Management
Team Skill 4 –Scope (Chapters Requirements Text) Team Skill 4 –Scope (Chapters Requirements Text) Sriram Mohan/Steve Chenoweth 1.
Succession Planning Who will replace your leaders? Presented by Jacquelyn Thorp, MSHR/SPHR -CA.
Do’s and Don’ts of Tendering Eddie Regan Senior PASS Consultant.
The benefits of being an Ericsson employee have never been clearer. introducing.
Prevue: Gaining & Retaining Clients The World’s Premiere Human Capital Assessment.
Chapter 7 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 7-1 Risk Management.
Object-Oriented Software Engineering
Note Excerpts from Object-Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R. Schach
1 The Concept of Risk A risk is defined as a variable that can take a value that endangers or eliminates success for a project. In plain terms, a risk.
October 2002J. B. Wordsworth: J2ISDQR11 Information Systems Development Quality and Risk (1)
Introducing Project Management Update December 2011.
7 Deadly Sins of Volunteer Recruitment District 1 FLC 2006 Membership Presentation.
2016 Budget October 19, Budget Parameters County Commissioners request that the UCBDD maintain the same annual budget. The amount in reserve.
Reaching Peak Performance In A High-Intensity Operating Environment TDL Summit September 14, 2004.
Need a roof inspection or roof certification? Need it done right? Conlon Exteriors, Inc. focuses on the existing roof by making sure that it is in good.
By Information Technology Resource Centre Limited (ITRC) Wholly owned by The Hong Kong Council of Social Service 31 st July 2013 (Wednesday)
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
Information Technology Project Management Managing IT Project Risk.
Risk planning Risks can be dealt with by: Risk acceptance – the cost of avoiding the risk may be greater than the actual cost of the damage that might.
Project Management Overview U08784Software Project Management Rosemary Phillimore.
2.8 Crisis Management and Contigency Planning Chapter 17.
NEM201 Week 4 Project Plan Create and complete outstanding items. 01. Front Cover 02. Document details 03. Scope Document 04. Technical Design 05. Creative.
Thank you for your time. Dress Code You need to dress appropriately for a school setting. Ensure tops are high enough and low enough to cover everything.
1 Chapter 11 Planning. 2 Project Planning “establishing a predetermined course of action within a forecasted environment” “establishing a predetermined.
R i s k If you don’t attack risks, they will attack you.
2016 Housing with Services Workforce Legislative Survey.
11 CPIT 456 by Dr. M. Rizwan Jameel Qureshi Chapter 3 Risk Management.
Risk Mitigation Submitted By, S. Anitha Devi, M.E-CSE.
Making it fail … A user guide to getting eportfolio implementation wrong.
You Can Charge for Phone Support Calls Effortlessly Brought to you by PaidSupport.com Have you ever watched your technical support team on the phone taking.
Risk management Here’s my section for risk management! ~ Christopher Thornton.
What is a Functional Spec?  Defines what the functionality will be NOT how it will be implemented  Describes features of the software product product's.
E&O Risk Management: Meeting the Challenge of Change
2017 Housing with Services Workforce Legislative Survey
Customer Service Chapter #4
Essential Needs of Software Test Automation
Chapter 13 Project Termination.
Collective Bargaining 101 Transfer Eligibility
Reasons why IT projects fail (and solutions)
Software Project Management
Chapter 10 Risks.
IMPACT HIRING #4 – Creating Success from the Start
VP, Institutional Services
2.8 Crisis Management and Contigency Planning
Chapter 13 Overall Audit Plan and Audit Program
Software Project Management
Fail Fail Poor Communication Lack of Documentation Poor Execution.
Justifying Gaslift Automation
CUSTOMER SERVICE.
How to fail at delivering software
Chapter 13 Overall Audit Plan and Audit Program
Late / Call Off Policy.
TRAINING Some firms see training as a core element of HRM. It is seen as a key to improving employee attitude, motivation and performance. Others value.
Effective communication in IT projects as a success factor
Chapter 13 Project Termination © 2012 John Wiley & Sons Inc.
Introduction to Projects
Good morning Come in and sit down. We will be skipping our reading today to get straight into book reports.
Presentation transcript:

Chapter 10 Risks

Risk Management Plan Risk is anything that may jeopardize the success of the project Risk Management Plan identifies the risks associated with a project and provide plans to manage them Risk Management Levels Elimination of risk -- transfer the risk, insurance Risk reduction -- matching offers for leaving staff Damage control -- circuit breaker contingency plan -- spare part, backups Accept the risks

Trouble signs Schedule slippage Over budget Score/feature creep Poor quality Lack client support Employee turnover

Change process control Up to 40% of a project’s cost comes from change of requirements Top reason for a project to fail, meaning Late Over budget Less features Poor quality Introduce strict process Introduce process for Emergency Change Request (ECRs)

Hurry up and wait syndrome Hurry – from client Nothing back from client on details Never mind – later