SYSTEMS ENGINEERING RESOURCES

value impacted by RE can be broken into five dimensions:

• User Value

• Business Value

• Learning Value

• Risk Reduction and Opportunity Enablement (RR & OE)

• Time Criticality

Podeswa defines the practice of Agile RE and describes numerous RE techniques by which such value is delivered:

• Lean Startup Minimum Viable Product (MVP)

• Minimum Marketable Product (MMP), Minimum Marketable Feature (MMF)

• User Story-Splitting

• Feature Preparation (aka Backlog Refinement)

• Triad Meetings

• Acceptance Test-Driven Development/ Behavior-Driven Development (ATDD/BDD)

Check out other articles from the Requirements Engineering Magazine here. Subscribe to the Requirements Engineering Magazine.

Agile and Systems Engineering: The Good, The Bad and The Ugly

This keynote presentation by Stuart Jobbins won the Best Paper Award at the INCOSE UK ASEC 2022 conference.

Abstract: Acceptance of Agile approaches is not without controversy, even within software circles, but increasingly the author is asked for his opinion on its application to Systems Engineering. Early Agile texts suggest an “all-or-nothing” mantra that decries other methods as mediocre by comparison, and that ‘partial compliance’ is invalid. In this paper we consider the major differences in context between Agile’s original intended environment of software development and the implications when applied in Systems Engineering. We also consider the implications on the Systems Engineering lifecycle stages of using Agile concepts. We conclude by identifying which components fit well with Systems Engineering, and those that should be avoided.