(Scrum Gathering 2013) Scrum for Hardware and Co-Design
Agile software development is getting more and more attention also in embedded software development. Embedded system development on the other hand requires different engineering disciplines working together towards a shared goal. When embedded software development begins using agile methods it triggers a need for change also in other disciplines. Agile development emphasizes continuous learning through experimenting and collaboration instead of following a detailed up-front plan. Agile embedded software team expects different behavior in system co-design. In addition to the above, product development in general and not only software development is facing the demands of ever-increasing amounts of change and learning. Change happens in several areas, such as technology, competition, and the marketplace. This is what agile methods aim at tackling. This implies that new product development in general could benefit from the knowledge created on agile development. This presentation summarizes the author's observations on hardware development team members and hardware teams using Scrum and agile methods during the past 10 years. Team configurations range from the collocated cross-disciplined team (electronics, printed circuit board, mechanics, and embedded software) to globally distributed teams of different disciplines. Several real-life products will be used as examples.
![PMI:
Overlapping phases, Iterative model.
Stage-Gate:
These activities [Market analysis and customer feedback]
are back-and-forth or iterative, with each development result
for example, rapid prototype, working model, or first prototype
taken to the customer for assessment and feedback.
Waterfall (Royce):
Sequential does not work.](https://image.slidesharecdn.com/agilehwscrumgathering2013punkkadelivered-221201145434-4348f570/85/Scrum-Gathering-2013-Scrum-for-Hardware-and-Co-Design-6-320.jpg)
![Learning and discovery
[Kuva tosi teknisest辰 laitteesta,
Kuvaamaan ett辰 ei voi tehd辰 etuk辰teen??]](https://image.slidesharecdn.com/agilehwscrumgathering2013punkkadelivered-221201145434-4348f570/85/Scrum-Gathering-2013-Scrum-for-Hardware-and-Co-Design-8-320.jpg)
(Scrum Gathering 2013) Scrum for Hardware and Co-Design
- 1. Scrum for Hardware and Co-Design Timo Punkka Scrum Gathering 2013, Paris
- 2. 15+ years of professional product development 10+ years of Agile development Certified Scrum Professional Timo Punkka timo.punkka at ngware.eu ng-embedded.blogspot.com @tpunkka
- 3. Motivation to consider Agile development for hardware development New prototyping approach for learning in addition to validating How fast-paced iterative planning can fit development with longer natural cycles?
- 4. System Functional Req 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 REWORK Illusion of Control Chaos 1000W 20EUR Scandinavia 750W 24EUR Europe
- 6. PMI: Overlapping phases, Iterative model. Stage-Gate: These activities [Market analysis and customer feedback] are back-and-forth or iterative, with each development result for example, rapid prototype, working model, or first prototype taken to the customer for assessment and feedback. Waterfall (Royce): Sequential does not work.
- 7. 39% use waterfall 2010 PMIs Pulse of the Profession
- 8. Learning and discovery [Kuva tosi teknisest辰 laitteesta, Kuvaamaan ett辰 ei voi tehd辰 etuk辰teen??]
- 9. Organizational Culture; This is how we do things here Software development Hardware development
- 10. 54% Scrum 11% Scrum/XP Hybrid 7th Annual State of Agile Development Survey, 2013
- 11. Motivation to consider Agile development for hardware development New prototyping approach for learning in addition to validating How fast-paced iterative planning can fit development with longer natural cycles?
- 12. Up-front prototyping; Experimenting, not validating 4 Week Sprint
- 13. No Free Prototypes? Design Review Manufacture Prepare Material Labour Testing Rework
- 15. Co-Design Up-Front Testing Iterative Hardware Innovating to bring testing and automation forward Reducing the get it right the first time attitude Diminishing difference between disciplines Positive reinforcing loop of agile co-design
- 16. Hardware unit tests > set led on OK. > start serial_port_test (ctrl-c to quit) Sent 10, received 10 (100%) CLI
- 18. Motivation to consider Agile development for hardware development New prototyping approach for learning in addition to validating How fast-paced iterative planning can fit development with longer natural cycles?
- 19. Think Big, Think Horizontal Adapted from Doing Hard Time, Bruce Douglas Vertical Slicing Design for manuf. Mechanics PCB layout Electronics/schematic
- 20. Implement Small, Implement Vertical Power and buses Uncertain blocks Full Solution Optimize Adapted from Doing Hard Time, Bruce Douglas Vertical Slicing
- 21. Schematics 3d models Simulation Bread board prototypes Re-usable generic prototypes Evaluation boards Partial prototypes FPGA 3d printers
- 22. Bread board Evaluation board 6 x 1 Week Sprints
- 23. Partial Prototype Evaluation board 6 x 1 Week Sprints
- 24. Partial Prototype Partial Prototype 6 x 1 Week Sprints
- 25. 6 x 1 Week Sprints
- 26. Embedded system development involves multiple perspectives, learning and discovery Up-front prototyping is used for experimenting, not validating Vertical slicing can be used for learning with partial prototypes
- 28. Photo credits (all @stock.xchng) Gear: deafstar Light meter: GlennPeb Question marks: immrchris