Premium
4.2.1 Can Systems Engineering be Agile? Development Lifecycles for Systems, Hardware, and Software
Author(s) -
Carson Ronald S.
Publication year - 2013
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2013.tb03001.x
Subject(s) - agile software development , software engineering , computer science , software development , systems engineering , software , embedded system , operating system , engineering
“Agile” development is alluring because of the promise of shorter cycle times and improved customer satisfaction. Some characteristics of software development and systems (and hardware) development are identified as key differentiators in selecting traditional, plan‐driven vs. agile development. Additional underlying or root reasons are identified to substantiate these differences. These include gated vs. serialized processes, comprehensive vs. incremental system design, independent vs. dependent fabrication, up‐front definition vs. continuous validation, and finish‐to‐start vs. finish‐to‐finish planning and execution. Some additional programmatic and technical criteria are identified for selecting traditional, plan‐driven SE vs. agile methods. The two methods do not appear to be reconcilable when developmental hardware is involved.