In this episode...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 Prof. 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 who're in this position to help you understand where other software companies often go wrong. Show SectionsLess evident modularityLonger design cyclesHigher functional interdependencePoor refactoring opportunitiesHigher need for specializationLonger time to demonstrate functionHigher cost of changeMore demanding range of operationDifferent testing demandsMore secondary design activitiesMore challenges in developing specificationsHigher difficulty proving a task is doneHigher price of premature commitment Related content...The New Product Introduction Process GuideWhy Designing Hardware Using Scrum is Difficult (Video)11 Common Electronic Product Certification And Compliance RequirementsHow To Do Product Reliability Testing?Cost Of Poor Quality and Reliability: “Pay Me Now, or Pay Me Later.”What Is Compliance Testing? [Podcast] Get in touch with usConnect with us on LinkedInSend us a tweet @sofeastPrefer Facebook? Check us out on FBContact us via Sofeast's contact pageSubscribe to our YouTube channel Subscribe to the podcast There are more episodes to come, so remember to subscribe! You can do so in your favorite podcast apps here and don't forget to give us a 5-star rating, please:Apple PodcastsSpotifyStitcherGoogle PodcastsTuneInAmazon PodcastsDeezeriHeartRADIOPlayerFMListen NotesPodcast AddictPodchaser