Top Banner
Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th , 2014 Dinner / Lecture
30

Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner

Jan 12, 2016

Download

Documents

Donald Shields
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
Page 1: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Special Thanks to JHU APL for providing the use of their facilities tonight

Leading Technical Teams

Dr. Michael Ryschkewitsch

June 18th, 2014 Dinner / Lecture

Page 2: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Broadening the Conversation on the Art and Science of Systems

Engineering

Leading Technical Teams

M.G. Ryschkewitsch

Page 3: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

What is Systems Engineering?

Systems engineering is the art and science of developing an operable system that can meet requirements within imposed constraints. It is holistic and integrative and

incorporates and balances the contributions of the “standard” engineering disciplines plus cross-cutting

ones to produce a coherent whole that no single discipline dominates. Systems engineering is about tradeoffs and compromises, about generalists rather

than specialists.

Page 4: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

What is the fundamental process in creating new things?

Needs, goals,

objectives

evolving into

requirements Systems

Concept

Evolving

into

design

Operations

and

Life Cycle

Concept

Evolving into

Plans

Alternatives,

Assessments

Synthesis

Failure response

Analysis,

Decomposition

Ideas,

Constraints

Options

Page 5: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Can we be more explicit?

All rights reserved

by Sidney Harris,

not for publication

Page 6: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

What is the fundamental process in creating new things?

Need

Use

Concept

Object Concept

Page 7: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A very fundamental circulation but how does this happen? Is it a “process”?

Need

Use

Concept

Object Concept

Page 8: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

The coupling of the science with the creative processes is what makes modern engineering

Need

Object Concept

Use concept

Analyzing

Testing/Choosing

Page 9: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

The coupling of the science with the creative processes is what makes modern engineering

Need

Object Concept

Use concept

Analyzing

Testing/Choosing

Page 10: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

The Coupling of the science with the creative processes is what makes modern engineering

Need

Object Concept

Use concept

Analyzing

Testing/ChoosingArt

Science

Page 11: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

For the creation of new complicated systems, there is a third nested processes going on

Need

Object Concept

Use concept

Analyzing

Testing/ChoosingArt

Science

Coordinating

Communicating

Controlling

Team Dynamics

Page 12: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

So what is a Systems Engineer Anyway?

Manager

Organizer

Process Controller

Detailed Verifier

Creative Architect

Problem finder

Constructive Paranoid

Big Picture Thinker

Technical

Leadership

Systems

Management

Systems Engineer

Systems

Manager

Technical

Leader

A brilliantly conceived system executed poorly is as worthless as a badly conceived system executed perfectly

Page 13: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

The Mentioned and the Unmentioned

•The things we talk about

• Analyzing

• Documenting

• Controlling

• Coordinating

• Decomposing

• Verifying

•The things we don’t

• Creating

• Communicating

• Team Dynamics

• Challenging

• Problem hunting

• Gaps

• Situational awareness

“The prescription of technique cannot be a substitute for talent and

capability, but that is precisely how we have tried to use technique.

” – Robert Frosch, 1969

Page 14: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

The Mentioned and the Unmentioned

•The things we talk about

• Easy to write down

• Easy to measure

• Can be learned in classroom

• Amenable to “guidelines” and “metrics”

•The things we don’t

• Hard to write down

• Hard to measure

• Mostly learned by doing

• Noticed mostly when absent

•Commonly absent from training and development programs

Page 15: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Playing Instruments and Making Music

Musicality/Pleasing

Creative combinations

Musical message

Artistic interaction

Technique

Scales, fingering

Musical forms

Timing/cadence

Achieving Objectives

Creative Architect

Problem finder

Constructive paranoid

Meeting Requirements

Organizing

Process Control

Detailed Verifier

Page 16: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Are Systems Engineers “made” or “found” ?

Like musicians, the answer is “yes”

- look for talent

- teach the techniques

- coach the soft skills

- practice, practice, practice

Page 17: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A NASA-centric Study - What makes a great systems engineer

•The NASA Chief Engineer commissioned a study to interview “go to” systems engineers to identify common characteristics and behaviors

•Social scientists interviewed subjects and then observed them at work

•Results were remarkably similar across NASA

•Used to formalize the basis for identifying high potential candidates

•Used to update curricula, training programs, etc

Page 18: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A NASA-centric Study - What makes a great systems engineer

• Technical Acumen -- Possesses Technical Competence and Has Comprehensive Previous Experience

• Problem Solving & Systems Thinking -- Has the Ability to Find Connections and Patterns Across the System; Identifies the Real Problem

• Attitudes & Attributes -- Has a Comprehensive View, Possesses a Positive Attitude and Dedication to Mission Success; Is Aware of Personal Limitations; Adapts to Change and Uncertainty; Uses Intuition/ Sensing

• Communication -- Listens Effectively and Translates Information; Facilitates an Environment of Open and Honest Communication; Communicates Through Story Telling and Analogies

• Leadership -- Creates Vision and Direction; Appreciates/ Recognizes Others; Understands the Human Dynamics of a Team; Coaches and Mentors; Delegates

18

Page 19: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A NASA-centric Study - What makes a great systems engineer

Technical Acumen

•Possesses Technical Competence and Has Comprehensive Previous Experience

•Shares project experience and acts as a reliable resource to the team and serves as the ‘go to’ person

•Demonstrates the depth of technical knowledge and expertise necessary to perform, manage, and coordinate work-related activities.

•Possesses a strong, fundamental understanding of engineering principles along with a cross disciplinary background.

•Demonstrates ability to focus on details while keeping the big picture in mind. Able to shift focus between the two with ease

Page 20: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A NASA-centric Study - What makes a great systems engineer

Problem Solving &

Systems Thinking

•Identifies the Real Problem

•Assimilates, Analyzes, and Synthesizes Data

•Thinks Systemically

•Has the Ability to Find Connections and Patterns Across the System

•Sets Priorities

•Keeps the Focus on Mission Requirements

•Possesses Creativity and Problem Solving Abilities

•Validates Facts, Information and Assumptions

•Remains Open Minded and Objective

•Draws on Past Experiences

•Manages Risk

Page 21: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A NASA-centric Study - What makes a great systems engineer

Attitudes & Attributes

•Remains Inquisitive and Curious

•Seeks Information and Uses the Art of Questioning

•Advances Ideas

•Gains Respect Credibility, and Trust

•Possesses Self-Confidence

•Has a Comprehensive View

•Possesses a Positive Attitude and Dedication to Mission Success

•Is Aware of Personal Limitations

•Adapts to Change and Uncertainty

•Uses Intuition/ Sensing

Page 22: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A NASA-centric Study - What makes a great systems engineer

Communication •Listens Effectively and Translates Information

•Communicates Effectively Through Personal Interaction

•Facilitates an Environment of Open and Honest Communication

•Uses Visuals to Communicate Complex Interactions

•Communicates Through Story Telling and Analogies

•Is Comfortable with Making Decisions

Page 23: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A NASA-centric Study - What makes a great systems engineer

Leadership•Creates Vision and Direction

•Ensures System Integrity – problem hunts

•Sees Situations Objectively

•Appreciates/ Recognizes Others

•Builds Team Cohesion

•Understands the Human Dynamics of a Team

•Possesses Influencing Skills

•Coaches and Mentors

•Delegates

•Ensures Resources are Available

Page 24: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Leadership

“A team is made up of many individuals. The more individualistic, the better. When putting a team together, the director should not try to find people whom he can outsmart, but people who are smarter than he is..”

Then comes a test of leadership. All the people around the table are experts in their own field. Each one should be a strong individual, with strong feelings, capable of thinking problems through on his own -- or he should not be there. When a conflict arises, the director must be able to find a compromise solution that is best for the satisfactory accomplishment of the mission, and get willing agreement from the dissenters.”

Page 25: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Leadership

“A team is made up of many individuals. The more individualistic, the better. When putting a team together, the director should not try to find people whom he can outsmart, but people who are smarter than he is..”

Then comes a test of leadership. All the people around the table are experts in their own field. Each one should be a strong individual, with strong feelings, capable of thinking problems through on his own -- or he should not be there. When a conflict arises, the director must be able to find a compromise solution that is best for the satisfactory accomplishment of the mission, and get willing agreement from the dissenters.”

Werner von Braun

Page 26: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Suggested reading

----Mike Griffin, speech on the two cultures of engineering at Purdue University, March 28, 2007 http://www.nasa.gov/news/speeches/admin/mg_speech_collection_archive_2.html

----

http://www.nasa.gov/news/reports/NASA_SE_Behavior_Study.html <

http://www.nasa.gov/news/reports/NASA_SE_Behavior_Study.html>

The easiest way is to just go to:         http://appel.nasa., which redirects to the OCE site and then they

can look for SELDP.

Page 27: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

27

Page 28: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

We need to be aware to whom we are talking

28

Page 29: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

Questions & Innovation

Application

KnowledgeCirculation

Information, tools, techniques

Policy, Process

CompetenciesHuman BehaviorsCulture of rigorous inquiry

There is no cookbook which can guarantee success but there are necessary ingredients

Page 30: Special Thanks to JHU APL for providing the use of their facilities tonight Leading Technical Teams Dr. Michael Ryschkewitsch June 18 th, 2014 Dinner /

A NASA-centric Study - What makes a great systems engineer

CommunicationAttitudes & Attributes

Leadership

Technical Acumen

Problem Solving &

Systems Thinking