(314) 234-9651 How Planning for Success Can Open the Door to Failure Bill Schoening Aug 31, 2005 – St. Louis, MO.

Slides:



Advertisements
Similar presentations
HOW TO BUILD A CHAMPIONSHIP TEAM
Advertisements

BALANCING LIFES ISSUES, INC. Managing Multiple Priorities at Work.
Finding the Few Critical Process Steps That Are Essential for Success Bill Schoening
Process and Product Quality Assurance (PPQA)
Refereeing By Yourself Education Session – February 28, 2013.
Chapter: 3 Agile Development
The CRM Textbook: customer relationship training Terry James © 2006 Chapter 11: Management.
Project management Project manager must;
Project Management.
You Got a Problem with That? Pete Stamps, CPPO, VCO Procurement Management Account Executive DGS/DPS.
Risks  All projects have some degree of risk  Risks are issues that can cause problems  Delay in schedule  Increased project costs  Technical risk.
7.1 A Bridge to Design & Construction
Conflict Management.
The Skill That Makes The Difference
Project Workshops Results and Evaluation. General The Results section presents the results to demonstrate the performance of the proposed solution. It.
Root Cause Analysis: Why? Why? Why?
BUILDING SELF-ESTEEM AND SELF-CONFIDENCE TAKING STEPS TO A HAPPIER MORE STRESS FREE YOU.
CSE Senior Design I Risk Management Instructor: Mike O’Dell This presentations was derived from the textbook used for this class: McConnell, Steve, Rapid.
CUSTOMER SERVICE AND TECHNOLOGY - YOU CAN WIN ONLINE CONSULTING.
Don Cole Risk Assessment and Mitigation Project Management for ARA Engineers and Scientists.
Software Engineering Principles Chapter 3 From Software Engineering by I. Sommerville, Slide 1 project managementorganizing planning scheduling Learning.
Timed Writing Exam When?Week 6 What?Problem/Solution Essay 250 words - 40 minutes.
S/W Project Management
Social Impact, May 2008 Risk Analysis & Contingency Planning “Failing to plan is planning to fail” -Effie Jones.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Systems Development Lifecycle Project Identification & Selection Project Initiation & Planning Analysis Logical Design Physical Design Implementation Maintenance.
Project Design Assumptions, Pre-conditions, Risks.
Alertness What Is Alertness? Alertness is being aware of what is taking place around me so I can have the right responses.
Risk management process
CONTROLLING TIME. ”Remember that time is money” Benjamin Franklin 1748.
Difficult Employees. SOME OTHER OPTIONS IN DISCIPLINE 1. Demotion 2. Transfer 3. Performance improvement plan.
Plan Design Analyze Develop Test Implement Maintain Systems Development Life Cycle MAT Dirtbikes.
The Fork in the Road “Expect the unexpected” Troy Phillips ©2010.
Copyright 2007, Information Builders. Slide 1 So You Just Bought WebFOCUS… Dan Schultz Director June, 2008.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
AP-1 5. Project Management. AP-2 Software Failure Software fails at a significant rate What is failure? Not delivering it on time is an estimation failure.
Ch 10 - Risk Management Learning Objectives You should be able to: List and describe risk management processes, inputs, outputs, and tools List and describe.
Ms. Paschitti. What is your definition of success? bcitech.org/lpaschitti 2.
CS CS 5150 Software Engineering Lecture 2 Software Processes 1.
Copyright © 2015 Curt Hill Software Development Paradigms What do you need to know?
Project Management presented by Aaron Molloy - Jimmy Kenny - Taras Voloshyn Newspaper Delivery System.
Chapter II: 9-Step Proposal Process: An Overview.
Introducing Project Management Update December 2011.
February 15, 2004 Software Risk Management Copyright © , Dennis J. Frailey, All Rights Reserved Simple Steps for Effective Software Risk Management.
Lynn E. Lawrence, CMSgt (ret), CPOT, ABOC.  The value of effective training  What is a process  Determining key processes ◦ Show stoppers ◦ Critical.
Project & Risk Management
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
Information Technology Project Management Managing IT Project Risk.
Lecture 4: Requirements Engineering COSI 120b, Principles of Software Engineering.
Quick Recap.
MODULE 9 MANAGERS AS DECISION MAKERS “Decide first, then act” How do managers use information to make decisions and solve problems? What are the steps.
Welcome to HRMS SELF SERVICE for EMPLOYEES Warwickshire County Council’s Self-Service Human Resources system Press Enter or Left Mouse click when you are.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
What makes a leader? A leader is a person who directs or who is in charge of others. Leadership is a blend of talents, qualities and skills that a leader.
Ashima Wadhwa.  Probably the most time-consuming project management activity.  Continuous activity from initial concept through to system delivery.
By: Antonio Vazquez.  As far as this year goes, there were a lot of struggles that I had this year, I can’t really explain why, they just occurred. 
Software Engineering Process
The value of a project-oriented approach to IT and how we do it in IBM
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
By Kean Tak, MSc, Lecturer at RUPP
Ch. 14 – Project Audit & Closure
Root Cause Analysis: Why? Why? Why?
Presented To: Sir Ali Raza Presented By: Kainat(06)Riffat(024)Asqsa(034) Group#06.
Software Engineering Process
Software Risk Management
Software Engineering Process
Presentation transcript:

(314) How Planning for Success Can Open the Door to Failure Bill Schoening Aug 31, 2005 – St. Louis, MO

Failure Comes in Many Forms Massive cost overruns Huge schedule delays Products that customers do not like Show-cause letters Cancellation Every failure is an embarrassment for Boeing – and for us as employees How does this happen?

Todays Topics What do we do that leads to failure? How can we recognize potential failures? What can we do to avoid failure?

Excitement of the Win

Then We Plan for Success

Doom & Gloom Doubters Not Welcome Risk Management: Address what we can handle Ignore the rest

Ignoring High Risk = Accepting High Risk

How We React without a Plan Panic Failure Press on with what we know – even if it is wrong Hope with untried approaches Overwhelmed R. I. P.

Solved Problems Reoccur Underlying causes –Long lag between decision and effect –Months, maybe even weeks, are too long for humans to perceive Solutions –Charge someone with stepping back and looking for recurring problems on a regular basis

Impossible Objectives Underlying causes –Requirements viewed as untouchable –Solution is just around the corner –Rarely teach Learning to suspect something is impossible Learning to show something is impossible Solutions –Teach how to demonstrate that something is impossible

length beam length beam constant Turret Diameter Ship Weight Demonstrating Why Not Max

Unknown User Needs Underlying causes –Focus on written requirements rather than users –Important user needs discovered late in development Solutions –Validate early and often –Primary objective is discovery, not showing –Requires real users, not surrogates

Verification and Validation Verification – process for demonstrating that a product satisfies written specifications. Validation – process for discovering unmet needs ? ? So this doesnt happen

Frequent Surprises Underlying causes –Managing things rather than intellectual content –Questions imply unknowns –Questions that go unanswered too long represent significant risks –Plans focus on deliverables and not on answering questions Solutions –Keep a running list of significant unanswered questions with due dates –Making answering questions part of the plan

Insufficient Time & Resources Underlying causes –Do not understand tasks –Staff before inputs are ready –Defer difficult tasks too often Done Defer Done Defer Solutions –Understand the necessary steps leading to SRR and SFR –Match staffing to plan –Hold NAR on feasibility of plan execution before starting

Quick Fixes Fail Underlying causes –Denial of risk –Lack of mitigation plans –Or even contingency plans –Quick, easy fix looks good, but has unknown consequences Solutions –Preplan courses of action –Pre-examine consequences of actions

Not Asking for Help Underlying causes –Loss of self esteem when asking for help –Non-advocate reviews come too late –Failure to consider possibility of catastrophic failure Solutions –Gate reviews address plans for when things go very wrong –Pay attention to symptoms of potential failure

In Conclusion Programs will fail if we are not prepared for really bad occurrences Risk Management is not enough Must teach and institutionalize –How to look –Not to be afraid to look –Looking frequently Do we need a new process? Discover Potential Catastrophes!