12.07.2015 Views

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

GP-B Post-Flight Analysis—Final Report - Gravity Probe B - Stanford ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Description of the <strong>GP</strong>-B experience:Cross training of operations team members is being implemented and is effective. Observed cross trainingbenefits include:1. more people to provide gap coverage for planned and unplanned gaps in schedule coverage,2. broadened team member knowledge and provides systems approach,3. avoids single string team members,4. minimizes team member fatigue caused by long work hours,5. shared workload improves teamwork,6. improves individual professional developmentBest Practices:Start cross training early and practice in mission simulations to ensure team is ready and flexible to handlechanging mission needs.16.2.7 Peer reviews in software developmentIssue Summary: Including peer reviews during software development was effective in finding errors and savingtime and money.Description of the <strong>GP</strong>-B experience:Peer reviews were introduced after several years of work as part of the U.S. Defense Department’s SoftwareEngineering Institute (SEI), based at Carnegie Mellon University, Level-3 certification. The peer reviews werepreceded by formal training, which was beneficial. Also, we were careful not to include management in thesereviews, as recommend by the process. As a result, code that was properly reviewed was very stable andexperienced fewer test errors. Software peer reviews should be provided priorityBest Practices:Peer reviews have shown their worth in finding errors early in the development cycle, which save time andmoney.16.2.8 Minimizing program risks with formal risk management planIssue Summary: IA formal, regular risk review is effective at early identification and control of program risks.Description of the <strong>GP</strong>-B experience:<strong>GP</strong>-B instituted a high visibility risk steering committee, which program management used to evaluate and setoverall program priorities. Risk groups met on a monthly basis; both <strong>Stanford</strong> and MSFC had independent riskevaluation teams that met regularly to share their assessments.456 March 2007 Chapter 16 — Lessons Learned and Best Practices

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!