Assessing the Influence of System Engineering Processes on Project Success Presented by Paul J. Componation Professor, Industrial and Systems Engineering
Assessing the Influence of System Engineering Processes on Project Success Presented by Paul J. Componation Professor, Industrial and Systems Engineering.
Mar 27, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Assessing the Influence of System Engineering Processes on Project Success
Presented by
Paul J. Componation
Professor, Industrial and Systems Engineering
Outline
Project Background Assessment of Historical Projects Project Success Criteria System Engineering Processes Relationships Common and Uncommon Elements Next Steps
2
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
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
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
Success Criteria
1 2 3 4 5
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
Rating
System Engineering ProcessesNPR 7123.1
7
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
System Design Processes
0 1 2 3
1. Stakeholder Expectations Definition
2. Technical Requirements Definition
3. Logical Decomposition
4. Design Solution
Rating
Average 1.94
Standard Deviation 0.43
10
Product Realization Processes
0 1 2 3
5. Product Implementation
6. Product Integration
7. Product Verification
8. Product Validation
9. Product Transition
Rating
Average 2.72
Standard Deviation 0.31
11
Technical Management Processes
0 1 2 3
10. Technical Planning
11. Requirements Management
12. Interface Management
13. Technical Risk Management
14. Configuration Management
15. Technical Data Management
16. Technical Assessment
17. Decision Analysis
Rating
Average 2.36Standard Deviation 0.54
Presence of the SE Process supports Project Success (Motivators)
Project Success and System Engineering Processes
Observed Data
1. Stakeholder E
xpectations Definition
2. Technical R
equirements D
efinition
3. Logical Decom
position
4. Design S
olution
5. Product Im
plementation
6. Product Integration
7. Product V
erification
8. Product V
alidation
9. Product T
ransition
10. Technical P
lanning
11. Requirem
ents Managem
ent
12. Interface Managem
ent
13. Technical R
isk Managem
ent
14. Configuration M
anagement
15. Technical D
ata Managem
ent
16. Technical A
ssessment
17. Decision A
nalysis
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
Absence of the SE Process hinders Project Success (Hygiene Factors)
Project Success and System Engineering Processes
Observed Data
1. Stakeholder E
xpectations Definition
2. Technical R
equirements D
efinition
3. Logical Decom
position
4. Design S
olution
5. Product Im
plementation
6. Product Integration
7. Product V
erification
8. Product V
alidation
9. Product T
ransition
10. Technical P
lanning
11. Requirem
ents Managem
ent
12. Interface Managem
ent
13. Technical R
isk Managem
ent
14. Configuration M
anagement
15. Technical D
ata Managem
ent
16. Technical A
ssessment
17. Decision A
nalysis
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
Support for Future Projects
14
HighTechnical
Risk
HighSchedule
Risk
HighBudget
Risk
Product ImplementationProduct IntegrationProduct VerificationTechnical Risk ManagementConfiguration Management
Technical Requirements DefinitionTechnical Planning
Stakeholder Expectation DefinitionTechnical Requirements DefinitionTechnical PlanningTechnical Assessment
Yes
Yes
Yes
No
No
Program/ProjectCharacteristics
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
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
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
Related Documents
