OCTOBER 23 - 24, 2017
Raleigh Convention Center
Raleigh, NC

Sign Up For More Info

IoT Continuous Engineering: Pitfalls and Solutions for Agile and System Developers

Jim Ruehlin   

Agile and open source developers have a high risk of failure when starting to work on IoT systems. There are unique issues with developing in the IoT that must be addressed or the project will fail technically or commercially. IoT systems are more complex, have higher risk and cost of failure, require physical deployment considerations, and critical architectural concerns must be addressed early. Similarly, Systems Engineers often don’t have the perspective of iterative development, continuous engineering, and requirements flexibility that makes an IoT project successful in an Internet enabled world.

This session is an introduction to successful practices that are unfamiliar to engineers entering IoT development. We’ll illustrate how to successfully deliver IoT systems by:

  • Continuously and iteratively deploying products that include multi-platform hardware and software components
  • Understanding the high cost of IoT development failures as compared to other types of software development
  • Making post-deployment cognitive analytics part of the development lifecycle
  • Addressing risks early to increase the likelihood of successful delivery
  • Illustrating the dangers of ignoring IoT architectural issues
  • Addressing critical IoT architectural issues without committing “analysis paralysis”
  • Avoiding unhelpful Agile and systems development practices and perspectives
  • Embracing Agile and systems development practices and perspectives that are helpful for IoT product development