Agile Development for Embedded Systems
We use the following Agile/eXtreme Programming paradigms for Embedded Software Development, applying a best fit approach, depending on the nature of the work. Obviously, when working closely with the hardware, for instance with a Board Support Package for a new piece of hardware, Pair Programming and Test Driven Development will not fit well, as many days of upfront development and debugging are required before the BSP comes to life. The complete suite of Agile development will fit well for a complete application that can be developed from scratch.
| Board Support Package | Device Driver | Library | Embedded System / Application | |
| Pair Programming |  | |  | |
| Test Driven Development | | | | |
| Acceptance Test | | | | |
| Continuous Integration | | | | |
| Version Control | | | | |
| Collective Code Ownership | | | | |
| Performance Optimization | | | | |
| Root-Cause Analysis | | | | |
| "Done Done" | | | | |
| Incremental Design | | | | |
| Ubiquitous Language | | | | |
| Informative Workspace | | | | |
