The Successful Project Team: Project Manager (Scott Hubbard)
G. Scott Hubbard has been an innovator and leader in science, technology, and management for more than thirty years, including twenty years with NASA. He currently is a professor in the department of aeronautics and astronautics at Stanford University. From 2002 to 2006, Mr. Hubbard was the director of Ames Research Center. In 2003 he served as the sole NASA representative on the Columbia Accident Investigation Board, where he directed impact testing that demonstrated the definitive physical cause of the loss of Columbia. In 2000 he served as NASA’s first Mars program director and successfully restructured the entire Mars program in the wake of mission failures. He is the founder of NASA’s Astrobiology Institute. He conceived the Mars Pathfinder mission with its airbag landing and was the manager for NASA’s highly successful Lunar Prospector Mission.
To learn more, please visit:
http://appel.nasa.gov/knowledge-sharing/pi-team-masters-forums/
Related Resources
-
Houston, we had a problem…and we learned from it!Space is hard. Inevitably, problems may occur. We can all learn valuable lessons from past events to ensure the safety and success of current and future programs. Enjoy reading and learning from a selection of such events. This booklet produced by the Johnson Space Center Knowledge Management Office contains numerous lesson learned from NASA missions and projects.
-
Apollo 1-Challenger-ColumbiaEvery year as we get back in the saddle, our Remembrance Day signals us to think back to the tragic events of Apollo 1, Challenger and Columbia as well as the context surrounding them. We’re accountable for learning from not just what went wrong, but how we recovered. As an example, read these rules recorded by Wayne Hale, former NASA Flight Director and Space Shuttle Program Manager. By actually applying such lessons from the past to your current work, our actions can honor our lost crews beyond silent reflection.
-
Shuttle Software AnomalyCase Study–A few minutes after the Shuttle Endeavour reached orbit for STS-126 on Nov. 14, 2008, mission control noticed that the shuttle did not automatically transfer two communications processes from launch to orbit configuration. Primary communications continued to use S-band frequencies after they should have transferred to the more powerful Ku-band. The link between the shuttle and its payload — the Payload Signal Processor (PSP)–remained configured for a radio link rather than switching.
