Part IV: Organizing to Perform Systems Engineering

1. Part IV: Organizing to Perform Systems Engineering Art, Alice, Heidi, Richard, Hillary, James, Garry, Ken, Dick

2. Workshop VI Goals • Completed structure • Complete list of topics for the Part – RESTRUCTURED • Authors identified for every topic (1750 word limit) • 18 articles identified – 5 top level (Intro + 4 KAs), 13 topics • An understanding of level of reusable/to be done writing • By topic: amount of 0.25 material available (None, Some, Most) • By topic: amount of work left to be done (Low, Med, High) • A draft list of glossary terms for the Part • A draft list of [5] primary references by Part (Future: by KA, by Topic) • Forward plan to close on by next workshop • Adjudicated comments (to be released with v 0.5) • Initial Draft SEBoK version 0.5 in the wiki

3. Topics (1 of 2) • All integrate: • Product, Service, Enterprise Perspectives • Change over time – improvement or new direction • Intro (2 pp) – defines terminology • Strategy (5 pp) • Value Proposition for SE (Product, Service, Enterprise) • Organizational Purpose (Life Cycle, Domain, Supply/Acquisition, Alignment) • Governance • Individuals (5 pp) • SE Competencies and Performance (Roles) • Personal SE Development (including licensing/certification) • Ethics of SE Engineers

4. Topics (2 of 2) • Teams/Projects/Programs (5 pp) • Structure of SE Activities within T/P/P (includes Inter/Intra & Dynamics, Roles&Responsibilities, Authority) • T/P/P SE Capabilities • T/P/P SE Development/Improvement • Businesses/Enterprises (5 pp) • Structure of SE Activities within B/E (includes Inter/Intra & Dynamics, Roles&Responsibilities, Authority) • B/E SE Capabilities • B/E SE Development/Improvement(includes certification [CMMI], organization learning, knowledge management • Culture

5. Next Steps • Come to consensus on new structure with team (April) • Assign Writing (April) • Populate Wiki (May/June) • Close on review comment actions (May/June) • Glossary Terms (May/June) • Topic References (May/June)

6. Major Issues • Coming to consensus on the structure • Coming to consensus on presentation of the content • Consistent use of terminology throughout • Consistent use of enterprise, service, product • Collaboration with Part III

7. Backup Slides

8. Overview • Part 4 describes how to organize to effectively perform SE activities. Types of organizations are categorized into the following: • individuals • teams • projects • businesses • enterprises

9. Six Common Considerations • Each organization has to consider the following: • What is the organizational purpose? • How are the SE activities allocated among the various organizational entities? • Who performs the SE activities? • What competencies are expected from the parts of the organization that perform SE activities and how does the organization gain those competencies? • What does an organization need to do to improve and how does it do it • How do those who perform systems engineering activities interact with others in the organization?

10. Three Driving Factors • The six areas of organizational considerations are largely driven by three factors: • The characteristics of the system which the SE activities support; for example, the size, complexity, primary design factors, major components, critical specialties and areas of life cycle, required products, etc… • The organizational context in which the SE activities occur, including organizational purpose, value measures, and culture. • The phases of the life cycle in which the activities being performed; for example development, deployment, operations, or maintenance of a product or service.

11. Previous Structure • Each chapter follows the six common considerations: • Chapter 4.1:Strategy – weave purpose into strategy - how to approach the other four considerations in a holistic fashion (governance includes measures and controls, policies, pace, tailoring, contextual domain, cross culture, human nature, knowledge management, etc.) (Art) • Chapter 4.2:Structure – where in the organization are SE activities performed (resource sharing) (Richard) • Chapter 4.3: People – who performs SE activities (?) • Chapter 4.4:Competencies - what competencies should people possess to perform SE activities well (what do SEs need to know about specialty engineering) (Heidi) • Chapter 4.5: Organizational Learning – what does an organization need to do to improve and how does it do it (Alice) • Chapter 4.6: Interactions – how do those who perform SE activities interact with others in the organization (interactions with specialty engineers, emergent properties of the interactions, communications, dynamics at each level) (Hillary) • Each chapter explores its topic in the context of the three factors – system characteristics, organizational context, and life cycle phase.

12. Some References • Intelligent Enterprises: A Collection of Knowledge Claims, Document No.: INCOSE-TD-2007-001-01 -http://www.incose.org/practice/techactivities/wg/intelent/docs/IEWGKnowledgeClaimsCollectionReport2007-0315.pdf • Value chains (M. Porter, Competitive Advantage, Free Press, 1985); • Results chains (J. Thorp, The Information Paradox, McGraw Hill, 1998), • Benefits chains (B. Boehm, A. Jain, "A Value-Based Theory of Systems Engineering," Proceedings, INCOSE 2006). • R. Valerdi, The Constructive Systems Engineering Cost Model (COSYSMO), VDM Verlag, 2008. • SEI People Capability Maturity Model (B. Curtis, W. Hefley, and S. Miller, Addison Wesley, 2002) • Lawson 2010 Chapter 8 presents a treatment of quality and environment management standards (as systems) and addresses Organizations and Enterprises as Systems and provides some useful paradigms that can be considered • Peter Senge's discussion of a Learning Organization that will tie back to Systems Thinking in Chapter 2. • James Martin's thesis