IoT standards

I attended the Embedded Conference Syd last week, which had both exhibitors and presentation tracks covering Internet-of-things. One thing that struck me is the lack of dominating standards in the area. It seems most proposed solutions and available devices are ether based on proprietary solutions, or relies on one of many various standards controlling how to integrate devices and services.

I assume that over time some standards will emerge and dominate also for IoT, in the same way as http/html for internet hypertext (does anybody remember Gopher and WAIS?). But we are not there yet…

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shit.

Comic from XKCD.

Does the architecture matter when the ways-of-working change?

More and more embedded companies adopts agile development as their way-of-working for software. For small systems this is straightforward, but for large development projects with hundreds of developers working on the same product there seems to be a typical evolution that an organisation goes through before successfully scaling agile.

Typically the transition starts with individual teams adopting agile practices, but fast iterations and shorter lead-times on team level does not automatically lead to shorter lead-times for new or updated products. The organisation as a whole still uses a stage-gate process or V-model for the product development. If the organisation is successful in changing their entire ways-of-working across all departments it becomes evident if the product architecture supports or hinders the new way-of-working.

The presentation concludes with some general guidelines for how software should be designed to support agile development of large embedded software systems.