Stephen Cox: Project Management
Finishing as much work as possible early on is one of the keys to keeping a project on schedule.
You can’t get schedule back on a project once you have lost it. Successful project managers often try to get ahead of schedule, get work done as soon as possible, and compress the schedule.
Stephen Cox is the Launch Control Center Manager for Exploration Ground Systems (EGS) at Kennedy Space Center. He gives several tips in the video clip to help project managers be successful.
Video key learning points:
- 1.
Finish as much work as possible early on during a project rather than wait for later to stay ahead of schedule. You can’t make up for lost schedule so try to get ahead when you have the opportunity.
- 2.
Operations and development teams should work closely together to prevent requirements creep or unknown requirements from slowing down your project schedule. Operations should understand the basic requirements needed for the mission but not push a specific solution so that the design team is free to come up with a solution.
- 3.
Project managers must decide if a requirement change is necessary for the mission.
- 4.
Understand when you make decisions on requirements what the risk is to other elements of your project such as budget and schedule.
- 5.
All requirements don’t have to be there at the beginning of a project. Some requirements come later as you learn more on a project. Some requirements implemented later will be improvements to the project but need to be examined for their impact on cost and schedule.
Related Resources
Videos: Stephen Cox on Launch Control Center
Kennedy Space Center Launch Control Center
Related Resources
-
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.
-
Overview on Organizational Silence (SMA-OV-WBT-131)The course is for all NASA personnel and defines the basic knowledge, types, factors and consequences behind organizational silence; identifies organizational silence conditions; and describes tactics and steps to combat organizational silence.
