Is Agile methodology suitable for Firmware development? More generally, when Hardware and Software must be co-developed and manufactured, would Agile still be a good approach for the software development? Perhaps, Firmware can still be decomposed into an OTP (One Time Programmable) piece + a piece that can be updated "over the air", in which case the latter could still follow Agile. But what has been your experience with real Firmware projects? Thanks
top of page
bottom of page
Thanks a lot for the response! I do agree with your approach. Something that I forgot to mention. Altough the current project targets the development of AOCS actuactors products to fly in LEO, the development philosophy is "new space". That means we qualify EEE parts from automotive grade under representative space environment conditions. That also means we have assess to MCU discovery boards even before the HW simulation. That said, for particular target firmware features, like e.g. over the air sw patch capability, cooperative scheluler, device drivers, we can do it independently from the hw maturity evolution. Once the hw breadboard is assembled and comissioned we will strongly consider your approach. Thanks again!