2006 Governance Risk Software 
Rebel’s Guide to PM
APRIL 5, 2022
The Airbus A380 was due to take to the skies in 2006. The international team did not use compatible design software which led to snowballing problems. The Channel Tunnel construction project saw its budget rise from £4.8 billion to £10.9 Each year the project is overdue costs €1 billion in penalties to their 16 customers.
Herding Cats
MAY 10, 2019
Risk Management is essential for development and production programs. Risk issues that can be identified early in the program, which will potentially impact the program later, termed Known Unknowns and can be alleviated with good risk management. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Herding Cats
MAY 11, 2019
This blog page is dedicated to the resources used to manage the risk encountered on software-intensive systems using traditional and agile development methods. Let's start with a critical understanding of the purpose of managing risk on software development projects. México, 1 al 3 de Febrero de 2006. De Meyer, C.
Herding Cats
MARCH 17, 2019
Here are my collected works, presentations, briefings, journal papers, articles, white papers, and essays, used to increase the Probability of Project Success (PoPS) I've developed and applied over my career in the software-intensive system of systems domain. Business, Technical, Systems, Risk, and Project Management. Risk Management.
Herding Cats
OCTOBER 11, 2016
There is a current rash of suggestions on how to improve the performance of software projects. One case of 12 projects from a large contractor of Software Intensive System (SIS) shows similar variances . I'd suggest the Principles for project success on non-trivial software efforts are universal. NASA Cost Estimating Handbook.
Herding Cats
OCTOBER 5, 2018
The primary purpose of software estimation is not to predict a project’s outcome; it is to determine whether a project’s targets are realistic enough to allow the project to be controlled to meet them ? This variation can be explained by the fact that initial concepts do not describe the final software system accurate enough.
Herding Cats
MARCH 11, 2017
The naturally occurring work effort in the development of a software feature - even if we've built the feature before - is an irreducible uncertainty. The risk is created when we have not accounted for this natural variances in our management plan for the project. An aleatory risk is expressed as a relation to a value.
Expert insights. Personalized for you.
264 
Let's personalize your content