Fomenting Change
summary
Describes how JPL reduced risk while changing spacecraft-related software, testing and processes by first mapping applications and use cases, brainstorming improvements, making incremental changes, and using a ‘ask forgiveness not permission’ tactic to get approvals. Covers concrete changes to software testing practices for Multi-Mission Software (including spacecraft simulators and ground data systems) and explains the process steps that led to those changes, illustrated with pictures and videos.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:39Hardware Innovations - Sky Crane
- 2:33Sky Crane Video
- 8:41Mars Helicopter Video
- 12:04Software Risk Aversion
- 12:32Elements of Instigating Changes
- 14:47CubeSats
- 16:49Marco Video
- 20:45"Verify" Jira Sub-Task
- 22:05Quad Chart for CubeSat Proposal
- 22:18Unexpected Incremental Changes
- 25:21Understanding What "NO" Means
- 26:13Possible Reasons for Rejection
- 27:21Applying Lessons Learned
- 28:29Implementing the Changes
- 30:00Final Report Outline CubeSat Study Outline
- 31:09The Most Important Aspect for Change
- 31:36Videos from the Dawn Spacecraft
- 32:01Comparison of Ceres and Vesta
- 32:27Another New Concept - Ion Propulsion
- 36:10Comparison of Ceres Pictures
- 36:22Flyby of Ceres
related talks
25mHow to Drive Cross Team Techincal Changes
27mTransforming Traditional Enterprise Software Development Processes
58mSoftware Modernisation
50mLearning in Production (or Why the Apollo 11 Landing Nearly Failed)
20mMaking the Case for Change
01h 01mEngineering for Software - How to Amplify Creativity
45mTaking Back "Software Engineering"
01h 02mThe Enterprise DevOps Challenge