Re:Boeing push to make training profitable may have left 737...
by hliyan on Sunday December 22, 2019 @01:52AM
(#21855686)
Agile Manifesto[1], principle #3: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
There's nothing inherently wrong with this, if 3 months are considered "frequent" in your industry (true for mission/safety critical systems, or systems that should not be upgraded frequently for some reason).
The idea is to deliver small, non-breaking increments to production frequently, rather than infrequent, big bang releases.
Re:Boeing push to make training profitable may have left 737...
by austhrow743 on Sunday December 22, 2019 @03:40AM
(#21855974)
I took it as more of a "only did this one aspect of it" statement more so than a "the one thing they did was bad" statement.
Can someone explain why this is actually bad?
(EDIT: I'm being serious, so please don't just down vote it without explaining. For airline industry with legacy systems, I don't necessarily think it's bad, but maybe I'm missing something.)