8 Tips For Software Companies Bringing A New Hardware Product To Market

Renaud and Andrew talk about how to develop hardware products specifically for software companies used to using an agile design approach (often SCRUM) for software products that now need to create a new hardware product to support their business (such as a device that runs on the software).

They share their thoughts on the book ‘SCRUM for hardware design‘ by David G. Ullman, warnings about the limitations of the agile design approach where hardware is concerned that you’ll need to be aware of and plan for, and 8 tips for software companies, especially SaaS companies, who’re starting out on the road to designing, developing, and launching a new hardware product.


Listen to the episode here 👇

Listen: to the podcast episode

Watch: on Youtube


Episode sections

  • 00:00 – Greetings & today’s topic.
  • 01:56 – What’s the difference between traditional project management and the agile approach?
  • 08:18 – Why is the agile design approach so popular with software companies?
  • 11:07 – 13 points about hardware design is different from software design from the book ‘SCRUM for hardware design’ by Prof. David G. Ullman:
  1. Less evident modularity
  2. Longer design cycles
  3. Higher functional interdependence
  4. Poor refactoring opportunities
  5. Higher need for specialization
  6. Longer time to demonstrate function
  7. Higher cost of change
  8. More demanding range of operation
  9. Different testing demands
  10. More secondary design activities
  11. More challenges in developing specifications
  12. Higher difficulty proving a task is done
  13. Higher price of premature commitment

8 points that companies that are used to running agile design for software development tend to overlook when developing new hardware products.

  • 23:39 – 1. Agile is good, but planning and documentation can’t be skipped.
  • 31:35 – 2. You need to freeze the product design (including freezing the firmware) at one point.
  • 33:48 – 3. An engineering change management process must be taken seriously from a certain point.
  • 35:46 – 4. You need supply chain visibility and to manage it yourself.
  • 39:15 – 5. You will need a quality function.
  • 42:21 – 6. BOM, drawings, schematics, etc. are all as important as software code.
  • 47:55 – 7. Product reliability is important, especially if they have a “product as a service” business model.
  • 52:46 – 8. Product compliance is an entire topic to take seriously.
  • 54:37 – Summary and wrapping up.


Related content…


Listen, rate, & subscribe to the ‘China Manufacturing Decoded’ podcast on your favorite provider

More episodes are coming, so remember to rate us and subscribe! You can find us on:

If you enjoyed this episode, don’t forget to give us a 5* rating and share it with your network if you enjoy listening!

This entry was posted in Sofeast Podcast and tagged , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *