agile42

Agile Embedded Software Development, what's wrong with it?

On February 18th we will give the keynote to the "Embedded meets Agile" conference in Munich

On
17 February 2014
In
Events

We are in 2014 and still someone is challenging the fact that you can't use an Agile approach to develop embedded systems, why? What's wrong with embedded software development? Well, there are somethings which makes it harder than needed: Dependencies with hardware releases, fixed delivery dates, inadequate software tools, limited adaptation possibility due to hardware costs… and yes, one more thing, really special: culture!

Agile embedded software development at Ericsson

We would like to focus the keynote we are giving to Embedded Meets Agile 2014 in analyzing some example cases that include the “limitations” listed above and also give you some hints on how to solve them. Finally we will also attack the “culture” issue. This is especially important for companies which grew out of hardware development and do not have a solid culture that include software, and therefore are stuck with waterfall development process and a traditional view on professional barriers for their employees. These companies are usually the ones not understanding that the complexity for years gone away from pure hardware, and landed in integrated product development. Without more focus in increasing quality of the process and the techniques to build - especially mission critical - functionality, the cost of failure are going to be very high, as the amount of bugs exposed to the users will rise and the competition sharpens at the same time.

Updated: watch the full recording of the keynote.

Photo courtesy of Ericsson R&D Italy, used upon permission. Ericsson innovation case will be discussed at the Keynote.

Subscribe to new blog posts

Did you find this article valuable? To be promptly noticed of new blog posts by agile42 you can subscribe to our notification system via email.

Discussion 2 Comments

We also value working software over comprehensive documentation. Working software is massively important to us. We try to review the game very regularly – towards the end of the production process as often as once or even twice a day – so it’s really important to get a build of the game easily and quickly.

Again, tools are a complement to that: we have built a dedicated build server that is always integrating the latest data through Perforce, so we can create a build in just a few hours, often as little as half an hour. Ten or so years ago, it often took all night to create a build, despite having far less data.

Mark Simon
http://www.agileinfoways.com

The myths busted.... Eye opener article on how Agile can be used for Embedded development. I heard these myths at the Automobile company I work for, Agile was discouraged due to same myths. I will share this article with our leadership and make an attempt...

(required)

(required)


(required)


(required)
Refresh captcha

 

Latest entries

Bridging the Unknown

In an Agile transformation small steps and reassuring inspections of the path ahead are not random ...

 

Article on Agile Leadership in Swiss magazine Computerworld

New article published in the issue 6/2017 of Swiss Computerworld

 

SUGSA Coaching Day in Pretoria

Regina Martins will present at the first SUGSA Coaching Day in Pretoria

 

Managing Work Without Resource Managers

Moving to self-organized teams causes a manager’s role to change focusing on creating a safe-to-fail environment, ...

 

Sponsorship of Mile High Agile 2017 in Denver

agile42 sponsoring MHA17 in Denver, 22-23 May 2017 featuring a talk by Richard Dolman and Dhaval ...