First few words of: Agile Embedded Software Development

There are two (almost) universal truths of embedded systems development. The first truth is
shared with software development projects of all kinds. The date is fixed long before the
requirements are known. The second truth is unique to embedded development. The target
hardware is not available until late in the project. Without hardware in the early part of the
project, progress can be limited. Teams are limited to the creation of speculative requirements
and design documents. The software development team is often on the critical path for
delivering the product. Wouldn’t it be helpful if the team could make concrete progress on the
software earlier in the development cycle?

Click here for the rest of the story: Agile Embedded Software Development