Document 53

SEBoK *Agile Development Approach*, Distilled

framework

SEBoK Agile Development Approach, Distilled

Next-40 distillation, batch 2/5, doc 6 of 8. Agile Development Approach is the SEBoK page that imports the 2001 Agile Manifesto into the SE practice with explicit hedge: "these principles were initially formulated within the context of software engineering and may not transfer seamlessly to the broader, more complex domain of systems engineering." The hedge is structurally important: it is the SE school's school-borrowing discipline (Cluster C, Doc 538) explicitly named at the page level. The agile pattern itself is Cluster I (pin-art) at the sprint cadence and Cluster B (multi-keeper) at the cross-functional team rung. The Manifesto's four values brush V3 (truth-telling, Cluster K) at the customer-collaboration axis. Five corpus forms compose; the school-borrowing-with-hedge reading is the structurally novel yield.

I. Source

II. Source Read

"An approach based on iterative development, frequent inspection and adaptation, and incremental deliveries in which requirements and solutions evolve through collaboration in cross-functional teams and through continual stakeholder feedback." Agile Manifesto introduced 2001 for software development. Caveat: "these principles were initially formulated within the context of software engineering and may not transfer seamlessly to the broader, more complex domain of systems engineering." Sprints "usually lasting 1 to 4 weeks." Manifesto's four values: individuals over processes, working systems over documentation, customer collaboration over contracts, responsiveness to change over rigid planning. References: Beck et al. 2001 Agile Manifesto, ISO/IEC/IEEE 26515:2018, ISO/IEC/IEEE 15288:2023. Position: Part 3 SE and Management, Development Approaches, between Evolutionary and Lean Engineering.

III. Structural Read

Cluster C — Architectural school (Doc 538), school-borrowing with explicit hedge. The page is a worked example of school-borrowing surfaced explicitly. Agile is software-engineering school content; the SE school imports it. The page's "may not transfer seamlessly" caveat is the school's discipline of acknowledging the borrowing-direction: SE borrows from SWE, with awareness that the borrowed content's transferability is partial. This is Doc 538 Appendix B.5's school-borrowing case named directly in source rather than reconstructed structurally. Pairs with SE-026 (SE-SWE composition) and SE-037 (SE-PM composition): SE-SWE here exhibits both composition and borrowing, depending on which school-content is engaged.

Cluster I — Pin-art / temporal-concurrency (Doc 270 / Doc 572 Appendix C), at sprint cadence. The 1-4-week sprint is pin-art at finer cadence than SE-052's iteration. Each sprint is a pin-set; the sprint review is the integration point; the next sprint composes accumulated shape forward. Doc 572 Appendix C's temporal-concurrency lattice operates at the sprint+release+life-cycle multi-cadence stack.

Cluster B — Multi-keeper composition (Doc 510 / Doc 604), at the cross-functional team rung. "Cross-functional teams" is multi-keeper composition explicitly named: developer-keeper, QA-keeper, product-owner-keeper, designer-keeper compose at the team rung; reconciliation rung is the daily standup and sprint planning. Composition rule is coordination-by-rung. "Continual stakeholder feedback" extends the composition outward to stakeholder-keepers.

Cluster K — Virtue constraints (Doc 314), at the Manifesto-values axis. "Customer collaboration over contracts" brushes V3 (truth-telling): the value commits to honest collaborative dialogue over contractually-mediated representations. "Responsiveness to change" brushes V3 again: honest acknowledgment of new information rather than defensive plan-defense. Light brushing; the SEBoK voice keeps the framing functional, but the corpus reads V3 territory under the surface.

Cluster F — Pulverization (Doc 445), at the sprint-retrospective rung. Sprint retrospectives are explicit backward-pulverization: the sprint's plan is pulverized against the sprint's actual outcomes. Sprint planning is forward-pulverization: the next sprint's plan is pulverized against anticipated risk. Agile institutionalizes the Doc 445 pulverization loop at the sprint cadence.

IV. Tier-Tags

  • Agile definition — π / α as cited.
  • "May not transfer seamlessly" caveat — π / α as cited; μ / β under corpus when read as Cluster C school-borrowing-with-hedge discipline.
  • Manifesto four values — π / α as cited; μ / β under corpus when read as Cluster K V3-brushing.
  • Sprint cadence — π / α as cited; μ / β under corpus when read as Cluster I sprint-pin-art.
  • Cross-functional team framing — π / α as cited; μ / β under corpus when read as Cluster B at team rung.

V. Residuals

R1 — The "may not transfer seamlessly" hedge raises the question of which agile principles the SE school accepts unmodified, which it tailors, and which it rejects. The page does not enumerate. Structurally interesting candidate for a sub-article-level pulverization pass.

VI. Provisional Refinements

Cluster C school-borrowing gains an explicit-hedge instance. Prior Cluster C members were composition cases (SE-SWE, SE-PM). Agile is the first member where the borrowing is named directly with hedge. Worth landing as canonical school-borrowing-with-hedge worked example, complementing the school-composition worked examples (SE-026, SE-037).

VII. Cross-Links

Form documents. Doc 538 (Cluster C, school-borrowing with explicit hedge), Doc 270 / Doc 572 Appendix C (Cluster I, sprint cadence), Doc 510 / Doc 604 (Cluster B, cross-functional team), Doc 314 (Cluster K, Manifesto-values), Doc 445 (Cluster F, sprint retrospective).

Part-level reformulation. SE-006 (Part 3).

Related distillations. SE-026 (SE-SWE composition). SE-052 (Incremental Development Approach, adjacent peer-axis, this batch). SE-050 (Life Cycle Model Selection and Adaptation, parent knowledge area, this batch).

Adjacent SEBoK concepts (per source). Incremental Development Approach, Evolutionary Development Approach, Lean Engineering, Agile Manifesto.

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-053 is one of the next-40 SEBoK distillations. Batch 2/5.)

Referenced Documents

More in framework