Document 73

SEBoK *Agile Systems Engineering*, Distilled

framework

SEBoK Agile Systems Engineering, Distilled

Next-40 distillation, batch 5/5. Agile Systems Engineering defines agility as "a principle-based method for designing, building, sustaining, and evolving systems when knowledge is uncertain and/or environments are dynamic" (Dove et al, 2023). The eight strategic aspects (adaptable modular architectures, iterative incremental development, attentive situational awareness, attentive decision making, common-mission teaming, continual integration and test, shared-knowledge management, being-agile operations concept) are universal-sibling lattice (Doc 572 Appendix D) at the agility-discipline rung. The "being agile, not doing agile" distinction is keeper-substrate composition (Doc 510): agility as keeper-side disposition versus agile-as-substrate-procedure. The DARPA Agility Forum and INCOSE 2014 strategic priority are institutional-ground (Doc 571). ISO/IEC/IEEE 24748-10 is the under-development standardization carrier.

I. Source

II. Source Read

Agile SE is "a principle-based method for designing, building, sustaining, and evolving systems when knowledge is uncertain and/or environments are dynamic" (Dove et al, 2023). Core distinction: "being agile, not doing agile" — agility as strategic capability rather than procedural framework. Eight strategic aspects: (1) Adaptable Modular Architectures (composable/reconfigurable from reusable assets), (2) Iterative Incremental Development (build-evaluate-correct-improve loops), (3) Attentive Situational Awareness, (4) Attentive Decision Making (sensing-to-action linkage), (5) Common-Mission Teaming, (6) Continual Integration and Test, (7) Shared-Knowledge Management, (8) Being Agile (sensing-responding-evolving). History: 1991 DoD manufacturing competitiveness research, 1990s DARPA Agility Forum (1,200 participants across 125 organizations), 2001 software adoption, 2014 INCOSE strategic priority. Standard under development: ISO/IEC/IEEE 24748-10. Lead authors: Dove, Lunney, Orosz, Yokell. Position: Part 3 SE and Management > Development Approaches, between Lean Engineering and Industrial DevOps.

III. Structural Read

Cluster A — Universal-sibling lattice (Doc 572 Appendix D). The eight strategic aspects bind every agile engagement universally; the discriminator is aspect, not rung-of-application. SEBoK explicitly states "individual implementation provides incremental benefits; comprehensive application creates genuine agility" — the universality-of-co-presence is the lattice claim. Eighth Appendix D instance after lean principles (638). The cluster strengthens: SEBoK's Development Approaches surface is dense with universal-sibling lattices.

Cluster B — Multi-keeper composition (Doc 604). Common-Mission Teaming, Shared-Knowledge Management, and Continual Integration and Test all presuppose multiple co-keepers composing across a project's lifetime. Doc 604's apparatus reads agile teams as multi-keeper composition with the engagement itself as reconciliation rung; rule is coordination-by-rung. Sixth multi-keeper instance.

Cluster C — Architectural school (Doc 538). Agile is a school in Doc 538's sense: a practitioner population with sustained transmissible discipline (vocabulary, methodology, institutional memory through DARPA Agility Forum, INCOSE 2014 priority). The "being agile, not doing agile" distinction is the school's internal discipline against ritualization-by-borrowing — the procedure-only adopter is not in-school. Compare SE-072's lean-as-borrowed-from: agile is a co-present school in many SE engagements (school-composition), not merely a technique-source.

Cluster D — Co-Production at sub-rungs (Doc 573). Iterative Incremental Development is canonical co-production: each increment is jointly authored by keeper-side intent and substrate-side build/evaluate evidence. The build-evaluate-correct-improve loop is the co-production cycle named operationally. Adds to Doc 573's co-production cluster.

Cluster I — Pin-art / temporal-concurrency (Doc 270 / Doc 572 Appendix C). Continual Integration and Test, Attentive Situational Awareness, and Iterative Incremental Development together describe temporal-concurrency lattice: multiple lifecycle activities operate simultaneously and integrate at increment boundaries. Doc 572 Appendix C composes naturally with the eight aspects.

Form III — Substrate-and-Keeper Composition (Doc 510), with the "being agile" distinction. "Being agile, not doing agile" is structurally Doc 510's keeper-substrate distinction: agility-as-disposition lives keeper-side (rung-2 supply); agile-as-procedure lives substrate-side (rung-1 production). The school's discipline says rung-1 procedure without rung-2 disposition is not agility. This is a sharp keeper-substrate reading the apparatus reaches non-trivially.

Cluster E — Institutional ground (Doc 571). DARPA Agility Forum (1,200 participants, 125 organizations), INCOSE 2014 strategic priority, ISO/IEC/IEEE 24748-10 under development — institutional ground in three layers: research consortium, professional society, formal standards body. Section X.5 applies cleanly across the three.

IV. Tier-Tags

  • Agile SE definition (Dove et al, 2023) — π / α.
  • Eight strategic aspects — π / α as cited; μ / β under corpus when read as Doc 572 Appendix D universal-sibling at agility-discipline rung.
  • "Being agile, not doing agile" — π / α as cited; μ / β under corpus when read as Doc 510 keeper-substrate distinction.
  • Iterative Incremental Development build-evaluate-correct-improve loop — π / α; co-production reading under Doc 573.
  • ISO/IEC/IEEE 24748-10 (under development) — π / α; institutional-ground codification under Doc 571.
  • DARPA Agility Forum, INCOSE 2014 priority — π / α; school formation under Doc 538.

V. Residuals

No structural residuals. The page strengthens four clusters (A, B, C, I) and provides a sharp Doc 510 keeper-substrate reading.

VI. Provisional Refinements

Doc 510 worked example: keeper-disposition vs. substrate-procedure. The "being agile, not doing agile" distinction is a clean teaching-instance for Doc 510's keeper-substrate apparatus. Worth documenting as a worked example: rung-1 procedure execution (the agile rituals) is substrate-side; rung-2 disposition (the sensing-responding-evolving capacity) is keeper-side; the school's discipline says only the dyad's coherent composition counts as agility. This generalizes to other "doing X versus being X" distinctions in the practice traditions.

Cluster A density. Three Development Approaches pages (Lean, Agile, plus prior Sequential at SE-022) all exhibit universal-sibling lattices at their respective discipline rungs. The Development Approaches surface may have systematic A-cluster density; worth tag-pass confirmation in remaining sweep.

VII. Cross-Links

Form documents. Doc 572 (Lattice Extension, Appendix D and Appendix C), Doc 510 (Substrate-and-Keeper, "being vs. doing" worked example), Doc 538 (Architectural School), Doc 604 (Multi-keeper composition), Doc 573 (Co-Production), Doc 571 (Institutional Ground), Doc 270 (Pin-Art).

Part-level reformulation. SE-006 (Part 3 — SE and Management).

Related distillations. SE-072 (Lean SE — sibling). SE-022 (Sequential Development Approach — Development Approaches sibling). SE-035 (Risk Management). SE-036 (Decision Management).

Adjacent SEBoK concepts. Lean Engineering, Industrial DevOps, Sequential Development Approach, Iterative Development Approach.

Appendix: Originating Prompt

"Let's do the next 40 most likely articles to be most load bearing... my conjecture is that this will inform the next 40." / "It's ok to duplicate entries. It shows where the knowledge base folds back in on itself. Continue fanning out"

(SE-073 is one of the next-40 SEBoK distillations. Batch 5/5.)

Referenced Documents

More in framework