Remove Presentation Remove Project Cost Remove Risk Remove Software Engineering
article thumbnail

Risk Management Resources

Herding Cats

Risk Management is essential for development and production programs. Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. Effective Risk Management 2 nd Edition , Edmund Conrow, AIAA, 2003. Risk Management Papers. “A

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

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. IEEE Transactions on Software Engineering , Vol.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Misunderstanding Making Decisions in the Presence of Uncertainty

Herding Cats

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.

2003 46
article thumbnail

A Wrap Up of the #NoEstimating Conjecture Analysis to Date

Herding Cats

- There is an immutable set of questions that need answers before we can determine the probability of success for our project. Predicting the Future - With the #NoEstimates topic still ringing in my ears, here's an interesting presentation from one of the supporters of this concept. What's Gonna Cost and When Will We Be Done?

article thumbnail

DDSTOP The Saga Continues

Herding Cats

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . Let's start with the obvious.

article thumbnail

The Beginner’s Guide to Using Project Planning Software

Paymo App

Clarifying the project’s background and context. Defining the project’s objectives. Selecting project team members. Identifying risks and planning to prevent them. Setting the project’s schedule. Deciding upon a project budget. Choosing the project’s resources. When should the project be completed?

article thumbnail

DDSTOP The Saga Continues

Herding Cats

This also meant developing software systems to support this effort. We were one of the first users of eXtreme Programming, long before Scrum was around and presented that early work in 2003, " Making Agile Development Work in a Government Contracting Environment, Measuring velocity with Earned Value." . So how do we get ±10% accuracy?