Document 72

SEBoK *Lean Systems Engineering*, Distilled

framework

SEBoK Lean Systems Engineering, Distilled

Next-40 distillation, batch 5/5. Lean Systems Engineering (LSE) applies lean thinking to SE and project management. The six Oppenheim principles (capture customer value, map and eliminate waste, flow work, pull value, pursue perfection, respect people) are universal-sibling lattice (Doc 572 Appendix D) at the lean-discipline rung. The 2009 INCOSE Lean Enablers for Systems Engineering (LEfSE) is institutional-ground codification (Doc 571). The "respect people" principle brushes V1 Dignity of the Person (Doc 314) but stays operational in SEBoK's framing. The "fail early, fail often" technique is forward-pulverization (SE-035 candidate, now well-attested). LSE's claim that "LSE does not mean less SE; it means more and better SE" is a school-internal warrant against borrowing-as-dilution (Doc 538 Appendix B.5).

I. Source

II. Source Read

LSE is "the application of lean thinking to systems engineering and related aspects of enterprise and project management." Goal: superior lifecycle value with minimum waste for technically complex systems. Six lean principles (Oppenheim): (1) capture customer value, (2) map and eliminate waste, (3) flow work efficiently (with "fail early, fail often"), (4) let customers pull value, (5) pursue process perfection, (6) respect people. The INCOSE Lean SE Working Group's 2009 Lean Enablers for Systems Engineering (LEfSE) is "a collection of practices and recommendations formulated as 'dos' and 'don'ts' of SE, based on lean thinking" supplementing rather than replacing traditional SE practice. Position: Part 3 SE and Management > Development Approaches, between Agile Development and Agile Systems Engineering.

III. Structural Read

Cluster A — Universal-sibling lattice (Doc 572 Appendix D). The six Oppenheim principles bind every lean engagement universally; the discriminator is aspect (value capture vs. waste elimination vs. flow vs. pull vs. perfection vs. respect), not rung-of-application. This is the seventh Appendix D instance after requirement types (589), architecture views (596), competency dimensions (598), CMMI typical measures (599), MODA value axes (601), HSI domains (603). The lean-principles partition is keeper-authored content the corpus accepts; the structure is universal-sibling lattice at the lean-discipline rung.

Cluster E — Institutional ground (Doc 571). INCOSE Lean SE Working Group and the 2009 LEfSE codification are institutional-ground specific to the lean-SE practitioner population. The LEfSE document is the carrier; INCOSE the body. Section X.5 organization-vs-enterprise applies: LEfSE lives at the organization-component (formal codification); the lean-SE working tradition lives at the enterprise-component.

Cluster F — Pulverization (Doc 445), with forward-pulverization confirmed. "Fail early, fail often" is canonical forward-pulverization at the work-flow rung: imagine the design fails, surface the failure mode now rather than later. Third instance after Risk Management identification (SE-035) and Decision Management premortem (SE-036). The candidate (SE-035) is now well-attested across three independent SEBoK pages.

Cluster C — Architectural school (Doc 538), with school-borrowing discipline. "LSE does not mean less SE; it means more and better SE" is school-internal warrant against borrowing-as-dilution. The lean tradition (Toyota Production System) is borrowed from; the SE school imports techniques without surrendering its own coherence. Doc 538 Appendix B.5 reads this as canonical school-borrowing rather than school-composition: lean is a technique-source, not a co-present school.

Cluster K — Virtue constraints (Doc 314), softly. The "respect people" principle ("organizations recognize employees as critical resources") brushes V1 Dignity of the Person territory. SEBoK's voice keeps it operational (employees as resources for performance), not virtue-claim. Doc 372 hypostatic boundary holds: the formalization specifies what the organization must DO, not what the employee IS. The corpus accepts the functional framing.

IV. Tier-Tags

  • LSE definition (Oppenheim) — π / α.
  • Six lean principles — π / α as cited; μ / β under corpus when read as Doc 572 Appendix D universal-sibling at lean-discipline rung.
  • "Fail early, fail often" — π / α as cited; μ / β under corpus when read as forward-pulverization (SE-035 candidate, third instance).
  • LEfSE 2009 — π / α; institutional-ground codification under Doc 571.
  • "LSE does not mean less SE" — π / α; school-internal warrant under Doc 538 Appendix B.5 (school-borrowing discipline).
  • "Respect people" — π / α; brushes V1 territory but kept operational, Doc 372 boundary holds.

V. Residuals

No structural residuals. The page reinforces three established refinements: Doc 572 Appendix D cluster strength reaches seven instances, SE-035 forward-pulverization candidate reaches three independent attestations, Doc 538 Appendix B.5 school-borrowing distinct from school-composition.

VI. Provisional Refinements

Doc 538 Appendix B.5 school-borrowing vs. school-composition distinction strengthens. Lean is borrowed-from (the SE school imports lean techniques without lean-as-school being co-present in the engagement). Compare the Doc 538 SE-SWE and SE-PM cases where two schools are jointly co-present in a single engagement. The borrowing-vs-composition distinction is structurally clean and the LSE case is a strong borrowing instance.

SE-035 forward-pulverization candidate ripe for formalization. Three independent SEBoK pages (Risk Management, Decision Management, Lean Systems Engineering) attest to forward-pulverization as a distinct discipline from backward-pulverization. The Doc 445 refinement candidate (forward direction) has cluster strength to formalize.

VII. Cross-Links

Form documents. Doc 572 (Lattice Extension, Appendix D), Doc 571 (Institutional Ground), Doc 445 (Pulverization, forward direction), Doc 538 (Architectural School, Appendix B.5 borrowing), Doc 314 (Virtue Constraints, V1 brush), Doc 372 (Hypostatic Boundary).

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

Related distillations. SE-035 (Risk Management — forward-pulverization first instance). SE-036 (Decision Management — premortem instance). SE-073 (Agile Systems Engineering — sibling Development Approaches page).

Adjacent SEBoK concepts. Agile Systems Engineering, Agile Development, Industrial DevOps, Configuration Management.

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

Referenced Documents

More in framework