3 ms·

Reference 1 is nearly 20 years old, much has changed in those 20 years. Reference 2 is non sequitur; nobody is suggesting that there are zero errors/failures i

by jtdev 7y ago

Reference 1 is nearly 20 years old, much has changed in those 20 years. Reference 2 is non sequitur; nobody is suggesting that there are zero errors/failures in agile, simply that Boeing may benefit from taking a more agile approach. Here's how iteration works: https://www.youtube.com/watch?v=bvim4rsNHkQ https://www.youtube.com/watch?v=bvim4rsNHkQ

bumby 7y ago
I agree that the attitude regarding agile development has changed, but the point from Ref. 1 was that the topic isn't nearly as settled yet as your comment might lead one to believe. There is still considerable debate within the aerospace industry on how and when agile development is appropriate. I would be legitimately interested if you have relevant references to successful applications of agile methodologies to safety-critical human rated space software development. Sorry if I wasn't clear enough on the point of Ref. 2. The reason that was brought up was the issue found was related to supplier quality. The fact that these checks were not in place is a bit surprising from a quality perspective and SpaceX indicated they will include additional quality oversight in the future.[1] I.e., through failures, they are adding additional processes that move them away from being an agile organization and closer towards the bureaucratic processes they are often contrasted against. "SpaceX will implement additional hardware quality audits throughout the vehicle to further ensure all parts received perform as expected per their certification documentation."[1] [1]https://www.spacex.com/news/2015/07/20/crs-7-investigation-update https://www.spacex.com/news/2015/07/20/crs-7-investigation-u...
- jtdev 7y ago
  "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." - The Agile Manifesto
  - bumby 7y ago
    I'm familiar with the agile approach, but what you quoted isn't unique to agile; it can be found in any quality program that implements continuous improvement. It also slightly begs the question by using the agile manifesto as a reference to justify agile development. What I am hoping to find is more concrete examples of successful application of agile processes to safety-critical software. For example, how can user stories be used in lieu of a traditional software requirements specification and still effectively capture all the necessary safety requirements (including those the customer may be unaware of).

by jtdev 7y ago

bumby 7y ago

I agree that the attitude regarding agile development has changed, but the point from Ref. 1 was that the topic isn't nearly as settled yet as your comment might lead one to believe. There is still considerable debate within the aerospace industry on how and when agile development is appropriate. I would be legitimately interested if you have relevant references to successful applications of agile methodologies to safety-critical human rated space software development. Sorry if I wasn't clear enough on the point of Ref. 2. The reason that was brought up was the issue found was related to supplier quality. The fact that these checks were not in place is a bit surprising from a quality perspective and SpaceX indicated they will include additional quality oversight in the future.[1] I.e., through failures, they are adding additional processes that move them away from being an agile organization and closer towards the bureaucratic processes they are often contrasted against. "SpaceX will implement additional hardware quality audits throughout the vehicle to further ensure all parts received perform as expected per their certification documentation."[1] [1]https://www.spacex.com/news/2015/07/20/crs-7-investigation-update https://www.spacex.com/news/2015/07/20/crs-7-investigation-u...

jtdev 7y ago
"At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." - The Agile Manifesto
- bumby 7y ago
  I'm familiar with the agile approach, but what you quoted isn't unique to agile; it can be found in any quality program that implements continuous improvement. It also slightly begs the question by using the agile manifesto as a reference to justify agile development. What I am hoping to find is more concrete examples of successful application of agile processes to safety-critical software. For example, how can user stories be used in lieu of a traditional software requirements specification and still effectively capture all the necessary safety requirements (including those the customer may be unaware of).