They did have peer review just not on every module. This is very common even amongst companies who say they do peer review.
And curious about the lack of a bug tracking software. Many companies including the one I work for "technically" don't use them. I wouldn't call Rally or Trello a bug tracker but that do work just fine for that purpose.
I also did find it amusing that they called out lack of formal specifications as an issue given that Agile encourages you not to create them.
> They did have peer review just not on every module. This is very common even amongst companies who say they do peer review.
This is not common at all in safety-critical applications.
> I also did find it amusing that they called out lack of formal specifications as an issue given that Agile encourages you not to create them.
This shouldn't be amusing if you understand Agile. Agile is for systems where you don't yet fully know the scope or the desired end behavior. The guts of a production car are as waterfall as it possibly can get.
It's not acceptable for a system that can kill you to be programmed without at least two programmers looking over every line of code. Common practice or not, given what we know about programming, it's immoral.
And curious about the lack of a bug tracking software. Many companies including the one I work for "technically" don't use them. I wouldn't call Rally or Trello a bug tracker but that do work just fine for that purpose.
I also did find it amusing that they called out lack of formal specifications as an issue given that Agile encourages you not to create them.