A plain-language glossary

Sourced finding

The guide’s sourced findings summarize TOGAF and BIZBOK context and list capabilities, value streams, information, organization, strategies, and metrics as connected domains [1]. The definition is an editorial paraphrase, not a quotation.

Sourced finding

The guide reports that capability mapping describes what an organization can do independently of its current structure or process [4][5]. The wording here is a plain-language paraphrase.

Guide editorial guidance

The guide’s practical workflow recommends agreeing scope, naming, levels, and categories, then recording definitions, owners, outcomes, dependencies, measures, and evidence. This glossary definition summarizes that editorial guidance.

Sourced finding

The guide lists value streams as a connected business-architecture domain in its BIZBOK summary [1], but does not give a standalone definition. The wording here is an editorial aid, not a sourced finding.

Guide editorial guidance

The guide’s “Build the current view” step asks readers to capture definitions, owners, outcomes, dependencies, measures, sources, dates, and confidence. This is a summary of the guide’s editorial workflow.

Guide editorial guidance

The guide’s “Define a comparable target view” step says to mark a target as proposed until accepted and to compare it at the same level as the current view. This is editorial guidance.

Guide editorial guidance

The guide’s “Gap and transition diagnosis” and transition-choice steps recommend describing the difference, its evidence, dependencies, risks, and decisions needed. This definition summarizes those recommendations.

Guide editorial guidance

The guide’s transition-planning workflow asks teams to compare options and work packages by benefit, trade-off, reversibility, risk, capacity, and decision required. This is editorial guidance, not a measured result.

Guide editorial guidance

The guide’s “Evidence register” prompt asks readers to record source, date, owner, access limits, and whether information is verified, reported, assumed, conflicting, or unknown. This glossary definition summarizes that prompt.

Sourced finding

The guide’s sourced summary describes Lean-Agile as flow-based and combines Lean themes such as waste elimination, visual control, and systems thinking with Agile iteration, collaboration, and adaptive delivery. This is a concise paraphrase of the supplied brief, not a universal standard.

Sourced finding

The guide reports that SAFe treats uninterrupted flow and continuous value delivery as central concerns, and says interruptions should be identified and addressed systematically [1][2]. The definition is an editorial paraphrase.

Guide editorial guidance

This follows the guide’s “Make flow visible” step. The recommendation is presented as editorial guidance from the guide, not as a universal rule or a research result.

Sourced finding

The guide’s research summary says Agile Alliance material discusses pull-like practices in Lean-Agile work [3][4]. It does not provide a formal definition of pull; the wording here is an editorial explanation.

Guide editorial guidance

The guide recommends choosing a thin, responsible slice that can produce useful learning, then demonstrating it and reviewing its evidence with affected people. This definition summarizes that guidance.

Guide editorial guidance

The guide’s “Choose a thin, responsible slice” step recommends defining acceptance examples and a Definition of Done with evidence. This is a plain-language summary of the guide’s editorial recommendation.

Guide editorial guidance

The guide’s “Improve one constraint” step recommends testing one improvement locally and cautions against treating a process measure as proof of business value. This is editorial guidance.