Upload
paer-hammarstroem
View
357
Download
1
Embed Size (px)
DESCRIPTION
Presentation about Integration Driven Development held at DevLin2013 Linköping 15/3 2013. IDD is a method for large scale systems development, especially embedded and cyber physical systems
Citation preview
Knowit Technology Management
Integration Driven Development Large Scale Software Intensive Systems
Pär Hammarström Senior Mgmt Consultant Knowit Technology Management [email protected] 072 202 6277
DEVLIN 2013 Linköping
What is the Best Development Method?
Technology Management
It Depends!
Contingency theory is a class of behavioral theory that claims that there is no best way to organize a corporation, to lead a company, or to make decisions. Instead, the optimal course of action is contingent (dependent) upon the internal and external situation.
Up to 80 percent of the development cost is software related Most of the innovation is software related
The Hidden Software Industry
Technology Management
Technology Management
Scale IS a Problem
Teams Handshakes 5 10 10 45 25 300 50 1125
What is Large Scale Product Development?
A Shared Understanding about What to Build!
Technology Management
Technology Management
The Forest and the Trees
Emergence comes from hindsight
The Whole >> the Sum of its Parts
Technology Management
A Social Construct
• Common Point of Reference
• Different Meanings • Means of
Coordina?on and Alignment
• Means of Transla?on • Plas?c -‐ Working
Arrangements • Different Concerns
Simultanously
Boundary objects are objects which are both plastic enough to adapt to local needs and constraints of the several parties employing them, yet robust enough to maintain a common identity across sites. They are weakly structured in common use, and become strongly structured in individual-site use. They may be abstract or concrete. They have different meanings in different social worlds but their structure is common enough to more than one world to make them recognizable, a means of translation. The creation and management of boundary objects is key in developing and maintaining coherence across intersecting social worlds.
- Star & Griesemer
Community of Interest
Technology Management
A Shared Mental Model
Dialogue through Visualiza9ons
Technology Management
Sensemaking - Analysis/Insight - Synthesis/Architecting - Detailed Design
Dialogue Experimentation/Reflection
Bracketing Formalism Gestalt Supports
Designers Needs
Technology Management
Design as a Duality – Seeing the Forest and the Trees
Technology Management
T e c h n o l o g y M a n a g e m e n t
Customer
Withdraw Cash
Check Balance
Use Case model
Dispend Cash
Show Balance
Provide User Interface
Authen?cate
Communicate with Bank
Vault Cash
Functions/Capabilities
Different Views
T e c h n o l o g y M a n a g e m e n t
Customer
Withdraw Cash
Check Balance
Use Case model
Dispend Cash
Show Balance
Provide User Interface
Authen?cate
Communicate With Bank
Vault Cash
Anatomy
Dependencies Governs Integration, Verification & Validation
The Anatomy day
T e c h n o l o g y M a n a g e m e n t
How to Eat an Elephant?
T e c h n o l o g y M a n a g e m e n t
F G
E
C
A B
D
Anatomy
Incr ++
Team X
Team Y
Team Z
Spr 1 Spr 2 Spr 3 Spr 4
E, F, G
D
A
B
C
Integration Plan
Increment Plan
Anatomy Day
F G
E
C
A B
D Incr
Incr ++
Integration Plan
Technology Management
IV&V
xBoxed Risk V&V V&V V&V V&V System
All Large Systems Starts as Small Systems
D A B C
Decreasin
g n
ecessity
Integration skeleton
Second wave
Third wave
Technology Management
Minimum Viable Product for Valida?on
Technology Management
Pro
du
ct In
teg
ratio
n
Team
/Sp
rint
System Architects
Architectural Runway
Product Vision
Product B
acklo
g
Product Mgmt
Sprints Sprints
Incr Incr ++
Scaled Agile Framework (Example)
Release Train
Integration Planning
Increm
ent B
acklo
g
Integration Mgr
A Lightweight adaption from Dean Leafingwell’s Scaled Agile Framework
Team
Back
log
Team
Back
log
Component Team A
Component Team B
System Valida?on / Spike
System Valida?on / Spike
• A shared mental model of the system • Focus on dependencies • Create pull from valida?on needs • Just enough inten?onal architecture • Done is the engine of more • LIGHTWEIGHT ...it depends
Summary
Technology Management