Agile in Hardware Intense Development | Petronella Andersson | LTG-23
-
Upload
lean-tribe -
Category
Technology
-
view
236 -
download
1
description
Transcript of Agile in Hardware Intense Development | Petronella Andersson | LTG-23
Slide 1
AGILE IN HARDWARE INTENSE DEVELOPMENT ???
~75%
ESAB - R&D EQUIPMENT AND AUTOMATION
• Welding Processes• Electronics• Power Electronics• Mechanics• Software• Industrial Design• Test and Verification• Certification
Slide 3
ESAB - R&D EQUIPMENT AND AUTOMATION
No universal solution – mix of agile and lean, adaption to fit for purpose
Define boundary conditions, everything else is up for negotiationHeadcountDelivery Teams as cross funtional as possibleR&D missionESAB overall product development process still stands......
Conviction key to success, ”process police” for the rest ;)
Std Equipment
backlog
Std Automation
backlog
R&D New
Technology Development
R&D Improvement
Backlog
Partner Support
Prod Care
R&D backlog
NPDCandidates
NPDDP0-DP1
NPDDP1-DP6
Pro
d C
are
NP
D P
re-
runn
ers
R&
D PS
PlattformOwners
Power Source
PCBa HMI
SW
System Architecture
&Welding
Performance
Wire Feeder
Delivery Teams
Integration plan (all ongoing efforts)
3-16 monthsRelease plan (one effort)1-12 months
EFFICIENCY GAIN
• Self organizing crossfunctional teams• Clear priorities• Technical decisions by the teams• Sprint = 2 weeks undisturbed work• Feedback from stakeholders every
2nd week - possible change in direction
0
50
100
150
200
250
300
TRANSITION TIME PER PRODUCT CARE ISSUE
- 50%
Sept -13 Sept -14
COST SAVINGS
Sept - 13 Sept - 14
OVERHEAD HC
• Self organizing crossfunctional teams• Clear priorities• Technical decisions by the teams• Sprint = 2 weeks undisturbed work• Feedback from stakeholders every
2nd week - possible change in directionSeries1
0
5
10
15
20
25
Chart Title
- 40%
* Managers, Project Managers, Administrative Personell etc
*
ESAB - R&D EQUIPMENT AND AUTOMATION
No universal solution – mix of agile and lean, adaption to fit for purpose
Define boundary conditions, everything else is up for negotiationHeadcountDelivery Teams as cross funtional as possibleR&D missionESAB overall product development process still stands......
Conviction key to success, ”process police” for the rest ;)