From Fragile to True Agile Methodology - Keys to Achieving the Agile Promise

Sep 12, 2026

Upload by Jacob

The paper analyzes the gap between agile methods and foundational systems engineering practices, arguing that many agile practitioners risk losing critical engineering value despite agile frameworks like SAFe® integrating systems engineering concepts. It summarizes SAFe® 5.1, including configurations and organizational scope, and explains scalability mechanisms through cadence and synchronization. The document further defines key SAFe constructs such as timeboxes, features and capabilities, stories, and core roles, then proposes additional principles to help teams realize both agile intent and promised outcomes.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages8

Reading Time3 min

AccessFree to download

From Fragile to True Agile Methodology - Keys to Achieving the Agile Promise

Scaled Agile Framework® Background

SAFe Configuration Scope

Alignment Using Cadence and Synchronization

Feature and Capabilities Concepts

Stories and Roles

This paper describes objective technical results and analysis. Any subjective views or opinions that might be expressed in SAND2021-14459C the paper do not necessarily represent the views of the U.S. Department of Energy or the United States Government. From Fragile to True Agile Methodology – Keys to Achieving the Agile Promise Author’s Name (only one author) Organization Mailing Address Telephone [author.one@gmail.com](author.one@gmail.com) Copyright © 202X by Author Name. Permission granted to INCOSE to publish and use. Abstract. Benefits of agile development have been proclaimed for decades, with the battle between agile and more “traditional” approaches waging fiercely to this day. Agile methodologies such as Scaled Agile Framework® seem to weave in systems engineering considerations in their values, principles, and practices – yet agile practitioners often ignore foundational systems engineering practices at their peril. This paper proposes additional principles that will help practitioners achieve both the spirit and promised benefits of using an agile approach. Scaled Agile Framework® Background Before describing the additional principles that will help weave systems engineering in the tapestry of agile practices, one of the leading agile frameworks will be summarized to provide some context for the discussion. Scaled Agile Framework® (SAFe) contains scalable organization and workflow patterns of agile and lean practices. SAFe is freely available from Scaled Agile, Inc. and 5 major versions have been released since 2011, with February 2021 version 5.1 being the latest release. This paper will use SAFe 5.1 as the agile methodology example since 37% of organizations utilize SAFe for scaling agile practices beyond a single team ([Digital.ai](Digital.ai), 2021). SAFe Configuration Scope. One aspect of scalability is the organizational scope. The SAFe configurations and their scope include: 􀀃 Essential is the most basic SAFe configuration, consisting of the key elements necessary to provide most of the framework’s benefits. Team and program levels (a team of multiple Agile teams, also known as an Agile Release Train [ART]) are included in this SAFe configuration. This used to be the Team and Program Levels in SAFe 4.0. 􀀃 Large Solution SAFe supports coordination and synchronization across multiple programs, but doesn’t require the portfolio aspects. This level used to be called a value stream in SAFe v4 .0. 􀀃 Portfolio SAFe includes strategic planning, relevant investment funding, organizes and provides portfolio operations and governance. 􀀃 Full SAFe combines the other 3 configuration levels. Sandia National Laboratories is a multimission laboratory managed and operated by National Technology & Engineering Solutions of Sandia, LLC, a wholly owned subsidiary of Honeywell International Inc. , for the U.S. Department of Energy's National Nuclear Security Administration under contract DE-NA0003525 . Alignment Using Cadence and Synchronization. Cadence is a repeating pattern of development events. Cadence is achieved using a hierarchy of timeboxes. Synchronization is achieved by integration and assessment of multiple development activities using timeboxes. Scalability is supported by the combination of cadence and synchronization across configuration levels described earlier.1 The hierarchy of timeboxes includes 􀀃 Sprint: At the lowest level is the increment, often called a sprint, which is a fixed-length timebox. Sprint durations are typically 1 to 3 weeks. For the remainder of this document, the term “sprint” will be used instead of increment for better clarity. 􀀃 Program increment: A program increment delivers additional value in the form of a working product and is the next level in the hierarchy. A program increment consists of multiple sprints and is typically 8-12 weeks in duration. 􀀃 Epic: The next level timebox is an epic, which consists of a significant product development wit

FAQs

What problem does the paper focus on in agile adoption?

It focuses on the disconnect where agile practitioners may ignore foundational systems engineering practices, even when frameworks such as SAFe® embed systems engineering concepts into values and practices.

Why does the paper use SAFe 5.1 as its agile example?

It uses SAFe 5.1 for context because it is the latest released version referenced in the paper, and because many organizations use SAFe to scale beyond a single team.

How does SAFe support scalability according to the document?

Scalability is supported by cadence and synchronization across configuration levels, using a hierarchy of timeboxes and coordinated integration and assessment.

Sep 12, 2026

Upload by Jacob