I think we gave up on the chip then software idea a long time ago. Unfortunately nothing to do with agile - just the need for co-development to meet schedules. As for everyone going agile - well, I cannot talk about software, but I dont see a lot of agile HW development going on - perhaps a little bit when we think about verification.
I'm guessing you won't be surprised that I've picked out a couple of quotes here. One from john ("The waterfall method that some people did: chip then software -- it's just not viable.") and another from warren ("Everybody's going Agile, on the software side and even on the hardware side.").
I'd sure be interested in understanding what "going agile" means and who "everybody" is. These comments make john and warren sound more optimistic about agile development than even I am :). I've seen optimism and interest building but I think we're several years away from any kind of movement or shift toward agile development. There are pockets of interest for sure but I've seen zero indication that everyone's doing it.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.