1. Assessing the Influence of System Engineering Processes on Project Success Presented by Paul J. Componation Professor, Industrial and Systems Engineering

2. Outline Project Background Assessment of Historical Projects Project Success Criteria System Engineering Processes Relationships Common and Uncommon Elements Next Steps 2

3. Project Background An effort has been initiated to address personnel training specific to SE&I, and develop effective ways to tailor standard SE&I processes. This activity will consist of an assessment of historical and current MSFC projects to determine the correlation between SE&I process and organizational implementation with programmatic and technical success. An SE&I Skill Board will be established to provide guidance. Results will be documented on a web-based Systems Engineering Guide currently under development at MSFC. Results will also be used to develop tailoring approaches to standard SE&I processes, and lessons learned. 3

4. Assessment of Historical Projects International Space Welding Experiment (ISWE) Chandra Solid Rocket Booster (SRB) Reusable Solid Rocket Motor (RSRM) X37 Express Rack Gravity Probe B (GP-B) ECLSS External Tank SME Advanced Health Monitoring System AXAF Saturn Booster IML 4

5. Project Success Criteria Technical success relative to initial requirements Technical success relative to similar projects On schedule relative to original project plan On schedule relative to similar projects On budget relative to original project plan On budget relative to similar projects Satisfaction with project management process Overall project success 5 Score ranges from 1 (low) to 5 (high)

6. 6

7. System Engineering Processes NPR 7123.1 7

8. Assessment of System Engineering Processes None (0): No direct reference to the SE processes. Low (1): Reference to the SE process is evident in the documentation. Medium (2): Reference to the SE process is evident in the documentation and tailored to the specific project. High (3): Reference to the SE process is evident in the documentation, tailored to the specific project, and cross referenced with other documents. 8

9. 9

10. 10

11. 11

12. Presence of the SE Process supports Project Success (Motivators) Project Success and System Engineering Processes Observed Data 1. Stakeholder ExpectationsDefinition2. Technical RequirementsDefinition3. Logical Decomposition4. Design Solution5. Product Implementation6. Product Integration7. Product Verification8. Product Validation9. Product Transition10. Technical Planning11. Requirements Management12. Interface Management13. Technical Risk Management14. Configuration Management15. Technical Data Management16. Technical Assessment17. Decision Analysis Technical success relative to initial req. Technical success relative to similar projects On schedule relative to original project plan On schedule relative to similar projects On budget relative to original project plan On budget relative to similar projects Satisfaction with project management process Overall project success 12

13. Absence of the SE Process hinders Project Success (Hygiene Factors) Project Success and System Engineering Processes Observed Data 1. Stakeholder ExpectationsDefinition2. Technical Requirements Definition3. Logical Decomposition4. Design Solution5. Product Implementation6. Product Integration7. Product Verification8. Product Validation9. Product Transition10. Technical Planning11. Requirements Management12. Interface Management13. Technical Risk Management14. Configuration Management15. Technical Data Management16. Technical Assessment17. Decision Analysis Technical success relative to initial req. Technical success relative to similar projects On schedule relative to original project plan On schedule relative to similar projects On budget relative to original project plan On budget relative to similar projects Satisfaction with project management process Overall project success 13

14. Support for Future Projects 14 High Technical Risk High Schedule Risk High Budget Risk Product Implementation Product Integration Product Verification Technical Risk Management Configuration Management Technical Requirements Definition Technical Planning Stakeholder Expectation Definition Technical Requirements Definition Technical Planning Technical Assessment Yes No Program/Project Characteristics

15. Common Elements Across Successful Projects Team members assigned 100% on the project Integration responsibility was either with contractor or shared jointly Teams met at least weekly, several daily Agendas and action item lists were used Teams consisted of good skill mix Unified commitment was shared among team members Project celebrated successes 15

16. Elements that were not Common Across Successful Projects Co-location of team members Common vision and common values not consistent Scope creep or number of changes were not consistent Reward structure not consistent Project size not consistent Leadership style not consistent Working approach not consistent 16

17. Next Steps Compare and contrast with related DoD studies Socialization of data Online tailoring of system engineering data. But, it takes more than two data points to make a line. 17