What is the Stride glossary?

A curated reference for software-delivery terms (agile, DevOps, SRE, process mining, AI agents, architecture) written with crisp definitions of 200-400 characters so AI search engines can cite them verbatim. Every term is its own URL with DefinedTerm JSON-LD schema.

How are the terms organised?

By category aligned to Stride's product modules: Plan (sprint planning, capacity, estimation), Design (architecture, ADRs, domain modelling), Optimize (process mining, flow), Verify (testing, observability, SRE), and Cross-cutting (AI-native delivery, prompt engineering, agentic workflows).

How can I contribute a term?

The glossary is editorial. We maintain it as part of our research and content workflow. If you spot an error or want to suggest a term, file a GitHub issue against stride.page; we triage suggestions quarterly.

Why are definitions so short?

Definitions are 200-400 characters because that's the size AI systems (Google AI Overview, ChatGPT, Perplexity, Claude) can cite as a self-contained answer. Deeper context lives in the optional body section; the definition is the citation target.

Are these definitions consistent with industry standards?

Where industry standards exist (ISO 19510 for BPMN, Maslach Burnout Inventory for burnout, DORA metrics for delivery performance) we cite them. Where the field disagrees or is evolving (AI-native delivery, prompt engineering), we make our editorial position explicit.

Glossary

Software-delivery terms, defined crisply

The vocabulary Stride works with (Plan, Design, Optimize, and Verify modules) plus the cross-cutting concepts that underlie all four. Crisp definitions, deeper context where it helps, and links to the relevant product surface.

Plan · 73 terms

Design · 56 terms

Optimize · 57 terms

Verify · 73 terms

Cross-cutting · 75 terms

About this glossary

What is the Stride glossary?: A curated reference for software-delivery terms (agile, DevOps, SRE, process mining, AI agents, architecture) written with crisp definitions of 200-400 characters so AI search engines can cite them verbatim. Every term is its own URL with DefinedTerm JSON-LD schema.
How are the terms organised?: By category aligned to Stride's product modules: Plan (sprint planning, capacity, estimation), Design (architecture, ADRs, domain modelling), Optimize (process mining, flow), Verify (testing, observability, SRE), and Cross-cutting (AI-native delivery, prompt engineering, agentic workflows).
How can I contribute a term?: The glossary is editorial. We maintain it as part of our research and content workflow. If you spot an error or want to suggest a term, file a GitHub issue against stride.page; we triage suggestions quarterly.
Why are definitions so short?: Definitions are 200-400 characters because that's the size AI systems (Google AI Overview, ChatGPT, Perplexity, Claude) can cite as a self-contained answer. Deeper context lives in the optional body section; the definition is the citation target.
Are these definitions consistent with industry standards?: Where industry standards exist (ISO 19510 for BPMN, Maslach Burnout Inventory for burnout, DORA metrics for delivery performance) we cite them. Where the field disagrees or is evolving (AI-native delivery, prompt engineering), we make our editorial position explicit.