Agile Embedded Software Development, what's wrong with it?
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

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

  • 3,429 views
Uploaded on

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......

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!

We would like to focus this keynote 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.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
3,429
On Slideshare
2,576
From Embeds
853
Number of Embeds
13

Actions

Shares
Downloads
65
Comments
0
Likes
9

Embeds 853

http://www.agile42.com 793
http://lanyrd.com 15
http://www.google.com 13
https://twitter.com 12
http://www.agileandlean.de 4
http://softwaredevelopmentperestroika.wordpress.com 3
http://www.linkedin.com 3
https://www.linkedin.com 3
http://www.feedspot.com 2
http://reader.aol.com 2
http://feedly.com 1
http://feedreader.com 1
http://digg.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Agile Embedded Software, what's wrong with it? We are in 2014 and still someone is challenging the fact that you can't use an Agile approach to develop embedded systems, why? agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 2. Andrea Tomasini Agile Coach & Trainer andrea.tomasini@agile42.com @tumma72 @agile42/coaches agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 3. Bent Myllerup Agile Coach & Trainer bent.myllerup@agile42.com @bentmyllerup @agile42/coaches agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 4. A bit of context agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 5. What is embedded software development? In system engineering we refer to embedded software when pointing at the software required to operate the system. As the system is the Product, and entails dedicated hardware components, it requires specifically developed drivers, and run often on custom real-time operating systems… agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 6. System Engineering = integrated products Value agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 7. Why Agile doesn’t work in Embedded… agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 8. Statement #1 We cannot have potential releasable functionality in four weeks or less! agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 9. Statement #2 There is to much diversity in the required skills for a cross functional team… agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 10. Statement #3 First we must develop the hardware, then comes software. It cannot be done in parallel agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 11. Statement #4 Continues integration and automated test does not work in hardware development agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 12. Statement #5 “Welcome changing requirements, even late in development” - Hello, Earth calling the agile coach! agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 13. Statement #6 Lead time can be six weeks or more… agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 14. Statement #7 User stories do not work for embedded system development agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 15. Our Experience… agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 16. Optical Network Infrastructure agile42 | We make your Agile transition succeed! Ericsson R&D for Optical Infrastructure www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 17. End-to-End global product development • Classical Engineering approach with separation of: • Requirement Engineering • Hardware Development • Software Development • Distributed teams across the globe in 4 different locations agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 18. Challenges • Release cycles and feedback loops very long, with major product releases happening in 12 to 18 months cycles • Very high business risk, multiple customers requests merging into a single product release • high number of competing change requests, very tight deadlines • Distributed development requires a lot more of synchronization to work, and detailed planning up-front (really?) • Average time before full test integration over 6 months, for first service-able hardware prototypes • Split responsibility distributed on a large number of roles, cause delay in decision making, in particular by issue handling agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 19. • Fully distributed cross-functional HW+FW+SW Teams with up to 10 people • Pairing over 2h timezone overlapping (Italy & China) • Team focusing on Features and not technology agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 20. Automated testing in short cycles Delivered serviceable Product in just 2 months Release incrementally, with higher quality agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 21. 19” Backbone Product agile42 | We make your Agile transition succeed! New standards for real time processing… www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 22. From Matrix Organization to Focus on the Business Project Office Project #4 Project #3 Project #2 Project #1 Business Unit #1 C g Analo Business Unit #2 DSP EMC Digital De sig n Digital t en C++ em DSP Test C ag an M EM C s es Simmulation User Do main nt e m Tes ge t a + an M C+ s es Design in us B FPGA sin Con stru ctio n ion truct Cons FPGA on mulati Sim User Domain Bu Product Management • Business Units formed as selfHardware Line organized Scrum teams • High Line Softwarediversity in skills - true cross functionality Mechanical Lineresponsibility for the • End-to-end project Operations (including the business case) • Focus was now making fantastic products rather that being fantastic at some technical practice Ana log Business Unit #3 ain User Do m nt e m e Dig ital ag an ++ M C C s s ne Analog i us S B im mu lation Co nst ru cti on Test EMC ety DS Saf P FPGA Operations agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 23. New Platform Project the Agile Way nd ra e ? om e ds t s Cu r Ne e Us Wh at? hy W ? Technology? Vision th r Wo g? in do Velocity! Product Backlog agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 24. From First MVP to Final Product 1. 2. 3. agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 25. Busting the Myths… agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 26. Myth #1 We cannot have potential releasable functionality in four weeks ! •The important thing is that you show agreed and valuable results every sprint. Challenge yourself (and the organization) to find alternative ways to verify your designs agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 27. Myth #2 There is to much diversity in the required skills for a cross functional team ! •The more the team is cross-functional the less you will have to deal with hand-over, reducing waste agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 28. Myth #3 First we must develop the hardware, then comes software. It cannot be done in parallel ! •With cross functional teams and clever ideas on developing Minimal Valuable Products, that is not necessarily a fact! agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 29. Myth #4 • Continuous integration and automated test does not work in hardware development ! • Several vendors are actually offering tools that can help you with this. Some times making an automated test tool is actually more fun than you ever expected. agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 30. 1. Statement #5 2. 3. “Welcome changing requirements, even late in development” - Hello, Earth calling the agile coach! ! • Building iteratively and incrementally by validating requirements on the way, reduces the stress of changes and the risk agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 31. Statement #6 Lead time can be six weeks or more ! • Is this really a “must” or is a choice that can be revised? It doesn’t have to be the final hardware, and you can decide to reduce the lead time and increase the production costs, by developing few samples locally… agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 32. Statement #7 User stories do not work for embedded system development ! • User Stories help focusing on the value instead of the technology, and allow to develop optimal technology to solve the given problems agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 33. Now let’s look at the culture agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 34. Actuality Agile Values & Principles Cultivation Control Competence Possibility agile42 | We make your Agile transition succeed! Impersonal People Collaboration William Schneider - The four Core Cultures www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 35. e Ma na g if ba t t h la nc e e Beliefs Le sh Culture Actions ad Results coaching is an ongoing long term investment Experiences The “Results Pyramid” is copyright of Partners in Leadership LLC agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 36. From Individuals or Groups to Teams In a complex world, team organization is the best answer to coping and handling the complexity and chaos in projects agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 37. 1. Agile is simple but isn’t easy, and applying it to system development might be tricky… but worth the effort! agile42 | We make your Agile transition succeed!building software advise, train and coach companies www.agile42.com | | All rights reserved. Copyright © 2007 - 2014. www.agile42.com 2009.
  • 38. 2. Remember to focus on Value first, and on technology later! agile42 | We make your Agile transition succeed!building software advise, train and coach companies www.agile42.com | | All rights reserved. Copyright © 2007 - 2014. www.agile42.com 2009.
  • 39. 3. Agile is a new paradigm rather than a new “method” it’s about thinking different! agile42 | We make your Agile transition succeed!building software advise, train and coach companies www.agile42.com | | All rights reserved. Copyright © 2007 - 2014. www.agile42.com 2009.
  • 40. 4. Start by challenging the constraints, and understand how are they limiting you from delivering shippable products in short cycles! agile42 | We make your Agile transition succeed!building software advise, train and coach companies www.agile42.com | | All rights reserved. Copyright © 2007 - 2014. www.agile42.com 2009.
  • 41. k n a h T ! u o Y agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 42. More food for thought... http://slideshare.net/tumma72 agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.
  • 43. Copyrights notice All material produced in this presentation is protected by the Creative Common License 3.0 (by-nc-sa). agile42 | We make your Agile transition succeed! www.agile42.com | All rights reserved. Copyright © 2007 - 2014.