1

Agile Conference 2011, Salt Lake CityTimo Punkka, Schneider Electrictimo.punkka at schneider-electric.com

Agile Hardware and Co-Design

Timo?

2

Agenda for today:What is happening in R&DBenefits of agile co-designWhat enables agile co-design?Advice to Agile/Scrum ceremonies

#1: Speed of Change

3

Second need; innovation#2: Innovation accelerated by 360

#3: Software Development Changes

4

Benefits of Agile Hardware and Co-Design• Avoiding the big surprises• Up-front prototyping

System

FunctionalReq

System Spec

System Design

Software

Spec

Software

Architecture

Design

Software

implementation

testing and

Integration

Hardware

Spec

Abstract

Hardware

Design

Hardware

implementation testing and

integration

System

Integration

testing

System field tests

Customer Approval

and evaluation

Detailed

Hardware

Design

Software

Module

Design

Illusion of Control Chaos

1000W20EURScandinavia

750W24EUREurope

5

Over time:a) speculations become factsb) reviewers get blindc) change happens

Alternative: Cross-Disciplined Up-front prototyping :

“Experimenting, not validating”

6

What enables agile hw and co-design?

• Vertical slicing• Cross disciplined Whole Team• Customer team• Economics of prototyping• HW Unit Tests

Think Big, Think Horizontal

Design for manuf.

Mechanics

PCB layout

Electronics/schematic

Adapted fromDoing Hard Time, Bruce Douglas

Vertical Slicing

7

Implement Small,Implement Vertical

Power andbuses

Uncertainblocks

FullSolution

Optimize

Adapted fromDoing Hard Time, Bruce Douglas

Vertical Slicing

Serial in large, incremental in small

Demonstrate progressGet and act on feedback

8

Schematics

3d models

Simulation

Bread board prototypes

Re-usable generic prototypes

Evaluation boards

Partial prototypes

FPGA

3d printers

Evaluation board

Bread board

Partial Prototype

Evaluation board

Partial Prototype

Partial Prototype

9

Flexible Architecture

10

1. Identify and prioritize uncertainties

2. Deal with it:

1. Use focused prototypes to buy uncertainty down

2. Keep options and defer decisions

3. Isolate uncertainty

Remember to learn from prototypes!

Cross-Disciplined Whole Team approach

SchematicsPCB layoutMechanicsIndustrial designSupply chainIndustrializationLaunch

Software

11

Cross-Disciplined

Customer Team

Domain experts:Other disciplinesTechnical lead Novel technology provider EMC test labIndustrialization

12

No Free Prototypes?

Design

Review Manufacture

Prepare

Material

Labor

Testing

Rework

(Imaginary) True Cost of Prototyping

Multiply of cost of labor day

REWORK

13

Hardware Unit Tests

Hardware unit tests

CLI

14

Innovating tobring testing and automation forward

Reducing the ‘get it right the first time’ attitude

Diminishing difference between disciplines

Positive reinforcing loop of agile co-design

Examples on practices• Planning • Daily Scrum • Review

15

Schematics of [technology]

Acc.Criteria: Schematic enabling PCB work

3

Block diagram for ceiling mounted relay

Acc.Criteria: Draft (block diagram) to identify the job to be done.

5

Planning

16

Daily Scrum

• 3 pieces of information create agenda for latter part

• Find appropriate level of detail• Creates shared sense of direction

Review

17

IKIWITI

Books

18

Photo credits:Light bulb: asifthebesSoftware plane: cyanocoraxQuestion marks: immrchris

All @ stock.xchng