INTEGRATION of PROJECT MANAGEMENT and SYSTEMS ENGINEERING

Size: px
Start display at page:

Download "INTEGRATION of PROJECT MANAGEMENT and SYSTEMS ENGINEERING"

Transcription

1 Copyright 2018 by Yves Theriault. Permission granted to INCOSE to publish and use. INTEGRATION of PROJECT MANAGEMENT and SYSTEMS ENGINEERING San Diego INCOSE Mini-Conference December 1, 2018 John Wood, PhD, PMP, ASEP Director, Systems Engineering Education Yves Theriault, PhD, PMP President

2 Selected Prior Work 680 Systems Engineers & Program Managers o 467 Program Managers o 356 Chief Systems Engineers Organizations that are better integrated use standards. They are also more effective. What are the most important skills to succeed as PM or SE? 2 Skill PM (%) SE (%) Formal integration reduce unproductive tension between PM and Leadership SE Demonstrate Communication a more complete integration 61 of both 42discipline. Stakeholder Systems Thinking Key Lever is improving the integration of SE and PM by Requirements o Using standards form both domains: 11 Training 46 and Alignment o Formalizing the definition of integration o Developing integrated engineering program assessments o Effectively sharing responsibility for risk management, quality, lifecycle, and external suppliers.

3 Selected Prior Work 3 Part I: In search of integrated solutions Part II: Building capabilities to effectively execute engineering programs Part III: Developing integration competencies in your organization Part IV: A call to action

4 Selected Prior Work 4 The Learning Organization Model

5 Combining Project and Systems Engineering Standards IMPORTANT ASSUMPTIONS 5 1. Integration must start with Project and Systems Engineering Standards 2. The relationships between Project and Program shall be as defined by PMI 3. The Project Manager and Systems Engineer must work together as a TEAM and share ALL responsibilities 4. Leadership and Communication should be a Priority when training and aligning 5. The Model of the Learning Organization shall govern the Standards

6 Combining the Processes Important Assumption: The PMBOK can be used to manage Any and All projects, to include Engineered Systems Projects 6 Integrate PMBOK Covers these 3 knowledge areas Integrate

7 Integrated Processes Project & Product Process Groups Project Life Cycle Product Life Cycle Knowledge Areas Initiating Planning Executing Monitoring and Controlling Closing Utilizing and Supporting Disposing 7 4. Project Integration 4.1 Develop Project Charter 4.2 Develop Project Plan.* 4.3 Direct and Manage Project Work. 4.4 Manage Project Knowledge 4.5 Monitor and Control Project Work. 4.6 Perform Integrated Change Control. 4.7 Close Project or Phase 4.9 Operate System 4.10 Maintain System 4.11 Dispose of System 5. Project Scope 5.1 Plan Scope. 5.2 Collect Requirements 5.3 Define Scope. 5.4 Create WBS 5.5 Validate Scope. 5.6 Control Scope. Project & Product Process Groups Project Life Cycle Product Life Cycle Knowledge Areas Initiating Planning Executing Monitoring and Controlling Closing Utilizing and Supporting Disposing 4. Project Integration 4.1 Develop Project Charter Business Analyze or Business Mission or Mission. Analysis Stakeholder Define Customer needs & 4.2 Develop Project Needs requirements and Requirements. Definition Plan.* 4.3 Direct and Manage Project Work Direct Define and Design. Manage Project Implement Work. Design Design Integrate Definition Parts, 4.6 Monitor and Control Project Work Validate Design Requirements Verify Systems Parts, Components, 4.7 Implementation Sub-Systems, Components, 4.5 Monitor and Sub-systems, Control Systems. 4.8 Integration Transition Systems to to Operations Manage Project Knowledge and Project Systems Work. Requirements Verification Perform System Analysis 4.6 Perform Integrated 4.7 Change Perform Control. Integrated Change 4.6 System Control. Analysis Close Project or Phase Operate Operation System Maintain Maintenance System Dispose Disposalof System 5. Project Scope 5.1 Plan Scope. 5.2 Collect Requirements System Elicit and Requirements Define System definition Requirements Architecture Define Architecture. Definition 5.3 Define Scope. 5.4 Create WBS 5.5 Validate Scope Validate Scope. System of Interest 4.11 Validation 5.6 Control Scope.

8 Integrated Processes Project & Product Process Groups Project Life Cycle Product Life Cycle Knowledge Areas Initiating Planning Executing Monitoring and Controlling Closing Utilizing and Supporting Disposing 6. Project Schedule 6.1 Plan Schedule. 6.2 Define Activities. 6.3 Sequence Activities. 6.4 Estimate Activity Durations. 6.5 Develop Schedule. 6.6 Control Schedule. 7. Project Cost 7.1 Plan Cost. 7.2 Estimate Costs. 7.3 Determine Budget. 7.4 Control Costs 8. Project Quality 8.1 Plan Quality 8.2 Manage Quality 8.3 Control Quality 9. Project Resource The Remainder of the Mapping Remains the same. 9.1 Plan Resource. 9.2 Estimate Activity Resources. 9.3 Acquire Resources. 9.4 Develop team. 9.5 Manage Team 9.6 Control Resources Project Communications 11. Project Risks 12. Project Procurement 13. Project Stakeholders 13.1 Identify Stakeholders 10.1 Plan Communications 10.2 Manage Communications Monitor Communications Plan Project Risks Identify Risks Perform Qualitative Risk Analysis Perform Quantitative Risk Analysis Implement Risk 11.5 Plan Risks Responses. Responses 11.7 Monitor Risks 12.1 Plan Procurement 12.2 Conduct Procurements 12.3 Control Procurements Plan Stakeholder 13.3 Manage Stakeholder 13.4 Monitor Stakeholder Engagement Engagement Engagement

9 WORK BREAKDOWN STRUCTURE 1.0 Project Project 1.2 System 1.3 Legal PROGRESSIVELY ELABORATED

10 WORK BREAKDOWN STRUCTURE 1.1 Project Project Charter Project Plan Scope management plan Systems Engineering management plan Requirements management plan Schedule plan Cost management plan Quality management plan Resource management plan Communications management plan Risk management plan Procurement management plan Stakeholder engagement plan Scope baseline Schedule baseline Cost baseline Systems Engineering Plan*** System Engineering Engineering Specialty Process Integration System Functional operational engineering requirements Maintenance Software engineering concepts Technical Reliability Performance engineering Measures (TPMs) Functional Maintainability analysis engineering (System level) Allocation Human factors of Requirements engineering Systems Safety engineering Synthesis, Analysis, and System definition System Security test engineering and evaluation Construction/Production Manufacturing and production requirements engineering System Logistics utilization and supportability and sustaining engineering support System Disposability retirement engineering and material recycling/disposal Engineering Quality engineering Specialty Integration Environmental engineering Value/Cost engineering Other disciplines as needed References (Specifications, Standards, Plans, Procedures, etc.) 10 *** Adapted from Systems Engineering, Blanchard Benjamin S. 4 th Edition, 2008, John Wiley & Sons. ISBN:

11 WORK BREAKDOWN STRUCTURE 1.2 System Context Diagram Block Diagrams Validated Requirements Component x Component X 1.2.x+1 Subsystem x+x Subsystem x System 1.2.Y Test & Evaluation 1.2.Y+1 Integrated System 1.2.Y+2 Validated/Operational System

12 MORE TO COME 12 IN 2019 STAY TUNED