This document summarizes key points from a presentation on software estimating and its impact on successful missions. It discusses how software is a critical and increasingly complex component of systems that is prone to failures and costly overruns if not estimated properly. Estimation processes and using metrics can help program managers reduce risks. The document provides examples of software failures and their high costs, and emphasizes that software estimates should be treated as high risk and reviewed at each program review. It also outlines best practices for software estimation like using a 10 step process and accounting for size, complexity, productivity and risks.
Arizona Broadband Policy Past, Present, and Future Presentation 3/25/24
NASA PM Challenge 2011: Software Estimating and its Impact On Successful Missions
1. NASA PM Challenge 2011
What Program Managers Need to Know About
Software Estimating and its Impact On
Successful Missions
Dan Galorath
galorath@galorath.com
Used with permission
What Program Managers Need to Know About Software Estimating and its Impact On Successful Missions Abstract 250Program managers sometimes give software secondary status next to more tangible items in a space system development. Yet software is responsible for many program delays and failures. For example, ESA’s Arian- 5 disaster was completely due to a software issue. The purpose of this presentation is to bring up the significance of software and appropriate software estimating in the development of successful systems. It covers cost and schedule estimation and how that impacts mission success along with numerous “why should we care” points for program managers to increase awareness of software and software issues that should be managed. Review From A Recent 2 Hour Presentation: “Thanks for your excellent seminar. I just finished reviewing the students’ evaluation of our course content and I want to pass along that your seminar on SW cost estimating received TOP marks! One student wrote, “While I don’t fully understand software and IT and I now know that I better pay more attention to it or else watch my program tank.””