https://www.stride.page/blog/roi-of-ai-in-software-delivery https://www.stride.page/api/og?title=What's%20the%20actual%20ROI%20of%20AI%20in%20software%20delivery%3F&subtitle=%244-%248%20back%20for%20every%20dollar%20spent%20within%206%20months%2C%20for%20most%20teams.%20The%20honest%20math%20from%20real%20data%2C%20not%20the%20deck.&eyebrow=BLOG What's the actual ROI of AI in software delivery? $4-$8 back for every dollar spent within 6 months, for most teams. The honest math from real data, not the deck. https://www.stride.page/blog/ai-generated-test-cases-worth-shipping https://www.stride.page/api/og?title=Are%20AI-generated%20test%20cases%20worth%20shipping%3F&subtitle=Yes%2C%20with%20a%20sharp%20caveat%20%E2%80%94%20when%20they're%20tied%20to%20AC%20and%20reviewed%20by%20a%20human.%20Five%20categories%20where%20AI%20test%20generation%20is%20great%2C%20five%20anti-patterns%20to%20catch.&eyebrow=BLOG Are AI-generated test cases worth shipping? Yes, with a sharp caveat — when they're tied to AC and reviewed by a human. Five categories where AI test generation is great, five anti-patterns to catch. https://www.stride.page/blog/can-ai-write-gherkin https://www.stride.page/api/og?title=Can%20AI%20write%20Gherkin%3F%20(yes%20%E2%80%94%20here's%20how)&subtitle=Yes.%20AI%20writes%20Gherkin%20well%2C%20often%20better%20than%20humans%20for%20surface%20area%20coverage.%20Five%20wins%2C%20five%20recognisable%20failure%20modes%2C%20and%20the%20prompts%20that%20work.&eyebrow=BLOG Can AI write Gherkin? (yes — here's how) Yes. AI writes Gherkin well, often better than humans for surface area coverage. Five wins, five recognisable failure modes, and the prompts that work. https://www.stride.page/blog/ai-acceptance-criteria https://www.stride.page/api/og?title=How%20AI%20writes%20acceptance%20criteria%20(and%20where%20it%20fails)&subtitle=The%20honest%20map%20of%20where%20AI%20is%20dramatically%20better%20than%20humans%20at%20writing%20acceptance%20criteria%20%E2%80%94%20and%20the%20five%20places%20it%20confidently%20writes%20garbage.%20Plus%20the%20prompts%20that%20work.&eyebrow=BLOG How AI writes acceptance criteria (and where it fails) The honest map of where AI is dramatically better than humans at writing acceptance criteria — and the five places it confidently writes garbage. Plus the prompts that work. https://www.stride.page/blog/bpmn-process-mining-celonis-alternative https://www.stride.page/api/og?title=BPMN%20process%20mining%20without%20Celonis%20money&subtitle=Celonis%20charges%20%24100K-%241M%2B%20for%20process%20mining.%20It's%20genuinely%20good.%20It's%20also%20wildly%20overpriced%20for%2095%25%20of%20teams.%20This%20is%20the%20lighter-weight%20playbook%20that%20actually%20works.&eyebrow=BLOG BPMN process mining without Celonis money Celonis charges $100K-$1M+ for process mining. It's genuinely good. It's also wildly overpriced for 95% of teams. This is the lighter-weight playbook that actually works. https://www.stride.page/blog/replacing-jira-30-day-playbook https://www.stride.page/api/og?title=Replacing%20Jira%3A%20a%2030-day%20playbook&subtitle=The%20honest%2030-day%20playbook%20for%20moving%20off%20Jira.%20Four%20phases%20%E2%80%94%20audit%2C%20parallel%20run%2C%20cutover%2C%20decommission%20%E2%80%94%20plus%20the%20three%20patterns%20where%20this%20doesn't%20work.&eyebrow=BLOG Replacing Jira: a 30-day playbook The honest 30-day playbook for moving off Jira. Four phases — audit, parallel run, cutover, decommission — plus the three patterns where this doesn't work. https://www.stride.page/blog/migrate-from-confluence https://www.stride.page/api/og?title=How%20to%20migrate%20from%20Confluence%20to%20a%20structured%20doc%20tool&subtitle=The%2030-day%20playbook%20for%20leaving%20Confluence.%20The%20hard%20part%20isn't%20the%20content%20move%20%E2%80%94%20it's%20deciding%20what%20NOT%20to%20move.&eyebrow=BLOG How to migrate from Confluence to a structured doc tool The 30-day playbook for leaving Confluence. The hard part isn't the content move — it's deciding what NOT to move. https://www.stride.page/blog/should-engineers-write-adrs https://www.stride.page/api/og?title=Should%20engineers%20write%20ADRs%20for%20every%20architecture%20decision%3F&subtitle=Yes%20%E2%80%94%20the%20bar%20isn't%20'big%20decision'%2C%20it's%20'would%20a%20new%20engineer%20six%20months%20from%20now%20wonder%20why%20we%20did%20this%3F'%20Most%20teams%20under-write%20ADRs.&eyebrow=BLOG Should engineers write ADRs for every architecture decision? Yes — the bar isn't 'big decision', it's 'would a new engineer six months from now wonder why we did this?' Most teams under-write ADRs. https://www.stride.page/blog/sprint-length-with-ai https://www.stride.page/api/og?title=How%20long%20should%20a%20sprint%20be%20when%20using%20AI%20to%20write%20stories%3F&subtitle=1-week%20sprints%20become%20the%20right%20default%20with%20AI.%20The%202-week%20standard%20was%20calibrated%20to%20slow%20manual%20planning%20%E2%80%94%20AI%20changes%20the%20math.&eyebrow=BLOG How long should a sprint be when using AI to write stories? 1-week sprints become the right default with AI. The 2-week standard was calibrated to slow manual planning — AI changes the math. https://www.stride.page/blog/best-ai-tool-for-sprint-planning https://www.stride.page/api/og?title=What's%20the%20best%20AI%20tool%20for%20sprint%20planning%3F&subtitle=Stride%20leads%2C%20Linear%20is%20second%2C%20everything%20else%20competes%20on%20a%20different%20axis.%20The%20litmus%20test%3A%20drop%20a%20PRD%20in%20and%20see%20what%20comes%20back%20in%2090%20seconds.&eyebrow=BLOG What's the best AI tool for sprint planning? Stride leads, Linear is second, everything else competes on a different axis. The litmus test: drop a PRD in and see what comes back in 90 seconds. https://www.stride.page/blog/connected-delivery-graph https://www.stride.page/api/og?title=The%20connected%20delivery%20graph%3A%20one%20source%20of%20truth%20from%20PRD%20to%20prod&subtitle=Most%20teams%20ship%20software%20with%20five%20tools%20that%20don't%20talk%20to%20each%20other.%20The%20friction%20isn't%20any%20individual%20tool%20%E2%80%94%20it's%20the%20missing%20graph%20between%20them.%20This%20is%20the%20case%20for%20one%20conne&eyebrow=BLOG The connected delivery graph: one source of truth from PRD to prod Most teams ship software with five tools that don't talk to each other. The friction isn't any individual tool — it's the missing graph between them. This is the case for one connected graph. https://www.stride.page/vs/jira https://www.stride.page/api/og?title=Stride%20vs%20Jira&subtitle=Stride%20vs%20Jira%20%E2%80%94%20for%20teams%20who%20want%20AI%2C%20not%20configuration.&eyebrow=Comparison Stride vs Jira Jira is the incumbent issue tracker, endlessly configurable. Stride is an AI-native delivery platform that replaces Jira AND adds architect, QA, and process intelligence — with a fraction of the admin surface. https://www.stride.page/vs/linear https://www.stride.page/api/og?title=Stride%20vs%20Linear&subtitle=Stride%20vs%20Linear%20%E2%80%94%20beautiful%20issues%20AND%20architect%20%2B%20QA%20in%20one%20tool.&eyebrow=Comparison Stride vs Linear Linear nailed the opinionated issue-tracking UX that Jira forgot. Stride is similarly opinionated on UX but solves a wider problem — same speed and polish, plus architecture decisions, QA coverage, and AI-generated artifacts across every module. https://www.stride.page/vs/asana https://www.stride.page/api/og?title=Stride%20vs%20Asana&subtitle=Stride%20vs%20Asana%20%E2%80%94%20for%20teams%20who%20want%20AI%20writing%20the%20work%2C%20not%20assigning%20it.&eyebrow=Comparison Stride vs Asana Asana is a generalist work-management tool that scales from marketing campaigns to engineering. Stride is purpose-built for software delivery — AI that writes acceptance criteria from stories, generates test cases from requirements, and connects PRDs to ADRs to defects on one graph. If you're shipping software, the depth matters. https://www.stride.page/vs/clickup https://www.stride.page/api/og?title=Stride%20vs%20ClickUp&subtitle=Stride%20vs%20ClickUp%20%E2%80%94%20focused%20AI%20for%20delivery%2C%20not%20surface%20sprawl.&eyebrow=Comparison Stride vs ClickUp ClickUp ships a feature for every workflow your team has ever asked for — docs, whiteboards, chat, mind maps, time tracking, CRM. Stride is the opposite philosophy: deep AI on four software-delivery surfaces (Plan, Design, Optimize, Verify) and integrations for the rest. Choose ClickUp if breadth matters; choose Stride if your team ships software for a living. https://www.stride.page/vs/notion https://www.stride.page/api/og?title=Stride%20vs%20Notion&subtitle=Stride%20vs%20Notion%20%E2%80%94%20when%20your%20%22PM%20database%22%20stops%20scaling.&eyebrow=Comparison Stride vs Notion Notion is a brilliant document-and-database hybrid that early-stage teams stretch into a PM tool. It works — until it doesn't. Stride is what teams move to when the sprints get serious, the test cases need traceability, and the AI prompts need real software-delivery context instead of free-form pages. We say this with love: Notion is the right answer for the first 18 months. https://www.stride.page/vs/monday https://www.stride.page/api/og?title=Stride%20vs%20Monday.com&subtitle=Stride%20vs%20Monday.com%20%E2%80%94%20software%20delivery%2C%20not%20work-OS%20slick.&eyebrow=Comparison Stride vs Monday.com Monday.com built its category as the spreadsheet-meets-CRM "Work OS" — colorful, configurable, and equally at home in marketing, sales ops, and engineering. Stride is the opposite: opinionated, software-delivery-focused, with AI that speaks Gherkin and ADRs. If your engineering team is running on Monday boards, this is the page for you. https://www.stride.page/vs/shortcut https://www.stride.page/api/og?title=Stride%20vs%20Shortcut&subtitle=Stride%20vs%20Shortcut%20%E2%80%94%20when%20your%20tracker%20needs%20to%20think.&eyebrow=Comparison Stride vs Shortcut Shortcut (formerly Clubhouse) earned its loyal user base by keeping the tracker simple — fast, opinionated, focused on stories and iterations. Stride is built for teams who appreciate Shortcut's restraint but want more: AI that writes acceptance criteria and test cases, architecture decisions on the same graph, and process intelligence across the delivery pipeline. https://www.stride.page/vs/productboard https://www.stride.page/api/og?title=Stride%20vs%20Productboard&subtitle=Stride%20vs%20Productboard%20%E2%80%94%20when%20the%20PM%20tool%20needs%20to%20talk%20to%20engineering.&eyebrow=Comparison Stride vs Productboard Productboard is a PM-favourite for prioritisation and roadmapping — strong opinions on how product strategy should be structured. Stride is built on the premise that strategy is meaningless if the PRDs don't connect to the stories, ADRs, and tests engineering ships against. Different bet on where the PM workflow should live. https://www.stride.page/vs/aha https://www.stride.page/api/og?title=Stride%20vs%20Aha!&subtitle=Stride%20vs%20Aha!%20%E2%80%94%20strategic%20roadmaps%20plus%20the%20engineering%20execution.&eyebrow=Comparison Stride vs Aha! Aha! built its category on strategy-first roadmapping — goals, initiatives, releases, features cascading top-down. Stride is built on the premise that strategy without the connected delivery layer is theatre. Different theory of where the PM tool should optimise. https://www.stride.page/vs/trello https://www.stride.page/api/og?title=Stride%20vs%20Trello&subtitle=Stride%20vs%20Trello%20%E2%80%94%20when%20boards%20stop%20being%20enough.&eyebrow=Comparison Stride vs Trello Trello pioneered Kanban-for-everyone — beautifully simple, infinitely flexible, and beloved by small teams. Stride is what teams move to when 'flexible' starts feeling like 'unstructured', when sprints get real, and when AI working on actual delivery artifacts starts mattering more than colour-coded cards. https://www.stride.page/vs/testrail https://www.stride.page/api/og?title=Stride%20vs%20TestRail&subtitle=Stride%20vs%20TestRail%20%E2%80%94%20when%20QA%20tooling%20stops%20needing%20its%20own%20silo.&eyebrow=Comparison Stride vs TestRail TestRail is the incumbent test management tool — strong feature surface, mature, and broadly deployed in QA-heavy organisations. Stride takes a different bet: test management belongs on the same graph as stories, defects, and code, not in a separate tool that maintains its own copy of every story. https://www.stride.page/vs/lucidchart https://www.stride.page/api/og?title=Stride%20vs%20Lucidchart&subtitle=Stride%20vs%20Lucidchart%20%E2%80%94%20when%20diagrams%20need%20to%20connect%20to%20the%20rest%20of%20delivery.&eyebrow=Comparison Stride vs Lucidchart Lucidchart is the best general-purpose diagramming tool: smooth canvas, huge shape library, real-time collaboration. Stride takes a narrower position: architecture work for software delivery is more than diagrams — it's ADRs, scored alternatives, tech radar, fitness, and traceability to the stories implementing each decision. Lucidchart draws; Stride decides. https://www.stride.page/vs/wrike https://www.stride.page/api/og?title=Stride%20vs%20Wrike&subtitle=Stride%20vs%20Wrike%20%E2%80%94%20software%20delivery%2C%20not%20enterprise%20project%20portfolio.&eyebrow=Comparison Stride vs Wrike Wrike is built for enterprise project portfolio management (PPM) — heavy reporting, custom workflows, Gantt charts, and time tracking for organisations running 100+ initiatives across departments. Stride is the opposite: opinionated software-delivery focus with AI on real delivery artifacts. If your engineering team has been forcibly moved onto a PPM tool because finance or PMO mandated it, this is your page. https://www.stride.page/vs/azure-devops https://www.stride.page/api/og?title=Stride%20vs%20Azure%20DevOps&subtitle=Stride%20vs%20Azure%20DevOps%20%E2%80%94%20for%20teams%20who%20want%20the%20AI%20without%20the%20ALM%20weight.&eyebrow=Comparison Stride vs Azure DevOps Azure DevOps is Microsoft's mature, end-to-end ALM — work items, Git repos, pipelines, test plans, artifacts — built around classic enterprise development. Stride is the AI-native alternative for teams who treat PRDs, ADRs, and tests as connected artifacts rather than tabs in five different tools. https://www.stride.page/vs/basecamp https://www.stride.page/api/og?title=Stride%20vs%20Basecamp&subtitle=Stride%20vs%20Basecamp%20%E2%80%94%20when%20your%20team%20ships%20software%20and%20needs%20more%20than%20to-dos.&eyebrow=Comparison Stride vs Basecamp Basecamp is a flat-pricing, opinionated PM tool built for cross-functional small teams to track to-dos, message threads, and shared docs. Stride is an AI-native platform built specifically for software delivery — PRDs, stories, ADRs, test cases, defects — connected as one graph. https://www.stride.page/vs/pivotal-tracker https://www.stride.page/api/og?title=Stride%20vs%20Pivotal%20Tracker&subtitle=Stride%20for%20teams%20migrating%20from%20Pivotal%20Tracker%20%E2%80%94%20Broadcom%20shut%20it%20down.%20Land%20somewhere%20that's%20also%20good.&eyebrow=Comparison Stride vs Pivotal Tracker Broadcom retired Pivotal Tracker on December 1, 2024, after acquiring VMware. Stride is the AI-native modern alternative — story-pointing, automated velocity, accept/reject workflows preserved, plus PRDs, ADRs, QA, and AI-generated artifacts the Tracker era never reached. https://www.stride.page/vs/zephyr https://www.stride.page/api/og?title=Stride%20vs%20Zephyr&subtitle=Stride%20vs%20Zephyr%20(SmartBear)%20%E2%80%94%20test%20management%20built%20into%20the%20delivery%20graph%2C%20not%20bolted%20onto%20Jira.&eyebrow=Comparison Stride vs Zephyr Zephyr (Squad, Scale, and Enterprise editions) is SmartBear's test-management family, dominantly used as a Jira add-on. Stride bundles test management into a connected delivery platform — test cases live next to the stories they cover and the defects they fail against, not in a sibling app. https://www.stride.page/vs/qtest https://www.stride.page/api/og?title=Stride%20vs%20qTest&subtitle=Stride%20vs%20qTest%20(Tricentis)%20%E2%80%94%20modern%20test%20management%20without%20the%20enterprise%20sales%20cycle.&eyebrow=Comparison Stride vs qTest qTest is Tricentis' enterprise test management platform — comprehensive, deeply integrated with Tricentis automation (Tosca, Testim), and priced for organizations with dedicated QA leadership. Stride bundles test management into a connected delivery platform with self-serve pricing and AI on test generation. https://www.stride.page/vs/xray https://www.stride.page/api/og?title=Stride%20vs%20Xray&subtitle=Stride%20vs%20Xray%20(Xpand%20IT)%20%E2%80%94%20Jira's%20most-popular%20test%20add-on%2C%20replaced%20by%20a%20connected%20delivery%20graph.&eyebrow=Comparison Stride vs Xray Xray is the most-popular test-management app on the Atlassian Marketplace — installed on 5,000+ Jira instances, deeply integrated with Jira's issue type model. Stride is the alternative when you want test management without first paying for Jira, with AI on test generation that Xray doesn't natively offer. https://www.stride.page/vs/smartsheet https://www.stride.page/api/og?title=Stride%20vs%20Smartsheet&subtitle=Stride%20vs%20Smartsheet%20%E2%80%94%20when%20grid-style%20PM%20stops%20being%20enough%20for%20engineering%20work.&eyebrow=Comparison Stride vs Smartsheet Smartsheet is a spreadsheet-meets-PM tool used widely for project portfolios in non-software organizations. Stride is built specifically for software delivery — story types, sprint cadence, AI on delivery artifacts, code-side integrations — none of which Smartsheet attempts. https://www.stride.page/vs/slite https://www.stride.page/api/og?title=Stride%20vs%20Slite&subtitle=Stride%20vs%20Slite%20%E2%80%94%20when%20your%20team's%20docs%20need%20to%20be%20connected%20to%20the%20work%20they%20describe.&eyebrow=Comparison Stride vs Slite Slite is a modern knowledge base for teams — clean writing experience, AI search, simple permissions. Stride is a connected delivery platform that includes Docs as one module among four; the docs live next to the stories, ADRs, tests, and defects they describe. https://www.stride.page/vs/coda https://www.stride.page/api/og?title=Stride%20vs%20Coda&subtitle=Stride%20vs%20Coda%20%E2%80%94%20when%20%22build%20your%20PM%20tool%20yourself%22%20stops%20scaling.&eyebrow=Comparison Stride vs Coda Coda is a docs + tables + buttons + automation platform — teams build their PM tool inside Coda. Stride is a purpose-built software-delivery platform with the work-types, schemas, and workflows already shipped. https://www.stride.page/vs/outline https://www.stride.page/api/og?title=Stride%20vs%20Outline&subtitle=Stride%20vs%20Outline%20%E2%80%94%20when%20your%20wiki%20needs%20to%20know%20about%20the%20work%20it%20describes.&eyebrow=Comparison Stride vs Outline Outline is a fast, open-source knowledge base — self-hosted or SaaS, clean editor, good search. Stride is a connected software-delivery platform where docs are one module among four; PRDs link to stories, ADRs link to tests, runbooks link to release notes. https://www.stride.page/vs/mermaid https://www.stride.page/api/og?title=Stride%20vs%20Mermaid&subtitle=Stride%20vs%20Mermaid%20%E2%80%94%20when%20diagrams-as-code%20becomes%20%22where%20does%20this%20decision%20live%3F%22&eyebrow=Comparison Stride vs Mermaid Mermaid is an open-source diagrams-as-code library (flowcharts, sequence diagrams, ER diagrams, etc.) embedded in Markdown across GitHub, Notion, Confluence, and many docs platforms. Stride bundles diagram rendering inside ADRs (Architecture Decision Records) connected to the stories, tests, and defects the architecture decision affects. https://www.stride.page/vs/excalidraw https://www.stride.page/api/og?title=Stride%20vs%20Excalidraw&subtitle=Stride%20vs%20Excalidraw%20%E2%80%94%20when%20your%20sketch%20needs%20to%20become%20a%20decision%20the%20team%20commits%20to.&eyebrow=Comparison Stride vs Excalidraw Excalidraw is a free, hand-drawn-style whiteboard for sketching diagrams collaboratively — beloved for sequence diagrams, system maps, and meeting whiteboards. Stride is a connected delivery platform with structured ADRs (Architecture Decision Records); diagrams are inputs to a decision, not the artifact itself. https://www.stride.page/vs/miro https://www.stride.page/api/og?title=Stride%20vs%20Miro&subtitle=Stride%20vs%20Miro%20%E2%80%94%20when%20your%20team's%20whiteboards%20need%20to%20turn%20into%20committed%20decisions.&eyebrow=Comparison Stride vs Miro Miro is the dominant collaborative whiteboard — used for design workshops, sprint retrospectives, sticky-note sessions, and architecture diagrams at enterprise scale. Stride is a connected delivery platform with structured ADRs (Architecture Decision Records); the whiteboard session becomes a committed decision linked to the stories, tests, and code it affects. https://www.stride.page/vs/airfocus https://www.stride.page/api/og?title=Stride%20vs%20Airfocus&subtitle=Stride%20vs%20Airfocus%20%E2%80%94%20when%20prioritization%20needs%20to%20flow%20into%20the%20stories%20the%20team%20actually%20ships.&eyebrow=Comparison Stride vs Airfocus Airfocus is a roadmap + prioritization platform — RICE, MoSCoW, and weighted scoring frameworks for product managers building strategic roadmaps. Stride is an AI-native delivery platform where the roadmap connects to the PRDs, stories, ADRs, and tests engineering ships against. https://www.stride.page/vs/roadmunk https://www.stride.page/api/og?title=Stride%20vs%20Roadmunk&subtitle=Stride%20vs%20Roadmunk%20%E2%80%94%20when%20a%20polished%20roadmap%20PDF%20isn't%20enough.&eyebrow=Comparison Stride vs Roadmunk Roadmunk is a roadmap visualization tool — clean exports, multiple swim views, stakeholder-friendly. Stride is an AI-native delivery platform where the roadmap connects to PRDs, stories, ADRs, tests, and release notes in one graph; the roadmap is the front door, not the artifact. https://www.stride.page/vs/github-projects https://www.stride.page/api/og?title=Stride%20vs%20GitHub%20Projects&subtitle=Stride%20vs%20GitHub%20Projects%20%E2%80%94%20when%20GitHub-native%20PM%20stops%20scaling.&eyebrow=Comparison Stride vs GitHub Projects GitHub Projects (v2) is GitHub's built-in project management — issues, pull requests, and milestones in a flexible board/table/roadmap layout. Free with any GitHub plan. Stride is an AI-native delivery platform that adds PRDs, ADRs, test management, defect lifecycle, and AI generation that GitHub Projects deliberately doesn't cover. https://www.stride.page/vs/favro https://www.stride.page/api/og?title=Stride%20vs%20Favro&subtitle=Stride%20vs%20Favro%20%E2%80%94%20when%20planning%20board%20flexibility%20stops%20being%20the%20bottleneck.&eyebrow=Comparison Stride vs Favro Favro is a flexible planning + collaboration board — multi-level boards, cards across teams, opinionated SAFe support. Stride is an AI-native delivery platform where boards are one surface; AI on PRDs, stories, ADRs, tests, and defects is the value. https://www.stride.page/vs/redmine https://www.stride.page/api/og?title=Stride%20vs%20Redmine&subtitle=Stride%20vs%20Redmine%20%E2%80%94%20when%20free-and-self-hosted%20stops%20being%20free.&eyebrow=Comparison Stride vs Redmine Redmine is the original open-source project management — issue tracking, time tracking, Gantt, wiki, repository integration. Free and self-hosted, used widely by ops-heavy teams who want full control. Stride is an AI-native SaaS that ships PRDs, ADRs, test management, defect prediction, and AI on delivery artifacts — none of which Redmine attempts. https://www.stride.page/vs/taiga https://www.stride.page/api/og?title=Stride%20vs%20Taiga&subtitle=Stride%20vs%20Taiga%20%E2%80%94%20when%20%22free%20open-source%20agile%22%20hits%20the%20limits%20of%20free%20open-source.&eyebrow=Comparison Stride vs Taiga Taiga is an open-source Scrum + Kanban tool — sprints, story points, retrospectives, simple and free. Self-hosted or SaaS with a free tier. Stride is an AI-native delivery platform that adds PRDs, ADRs, test management, defect prediction, AI generation, and a connected graph that Taiga doesn't attempt. https://www.stride.page/vs/jira-service-management https://www.stride.page/api/og?title=Stride%20vs%20Jira%20Service%20Management&subtitle=Stride%20vs%20Jira%20Service%20Management%20%E2%80%94%20when%20your%20team%20builds%20software%2C%20not%20handles%20service%20requests.&eyebrow=Comparison Stride vs Jira Service Management Jira Service Management (formerly Jira Service Desk) is Atlassian's ITSM platform — incident management, change management, service request workflows, ITIL-aligned. Stride is an AI-native software-delivery platform; we don't compete on ITSM. This page exists for teams comparing the two by mistake. https://www.stride.page/vs/archi https://www.stride.page/api/og?title=Stride%20vs%20Archi&subtitle=Stride%20vs%20Archi%20%E2%80%94%20when%20ArchiMate%20is%20overkill%20and%20you%20actually%20need%20ADRs.&eyebrow=Comparison Stride vs Archi Archi is an open-source ArchiMate-modeling tool — enterprise architecture diagrams following the ArchiMate 3.x specification, used by EA teams for stakeholder communication. Stride is an AI-native delivery platform with ADRs (Architecture Decision Records); we don't replace ArchiMate modeling but cover the lightweight ADR use case Archi isn't designed for. https://www.stride.page/glossary/acceptance-criteria https://www.stride.page/api/og?title=Acceptance%20criteria&subtitle=Acceptance%20criteria%20are%20the%20conditions%20a%20story%20must%20satisfy%20to%20be%20considered%20complete%20%E2%80%94%20testable%2C%20bounded%20statements%20describing%20what%20the%20system%20does.%20Good%20AC%20are%20behavioural%20(user-&eyebrow=Glossary Acceptance criteria Acceptance criteria are the conditions a story must satisfy to be considered complete — testable, bounded statements describing what the system does. Good AC are behavioural (user-visible outcome), no https://www.stride.page/glossary/accessibility-tree https://www.stride.page/api/og?title=Accessibility%20tree&subtitle=The%20accessibility%20tree%20is%20the%20structured%20representation%20of%20a%20webpage%20that%20assistive%20technologies%20%E2%80%94%20screen%20readers%2C%20voice%20control%2C%20switch%20devices%20%E2%80%94%20read%20instead%20of%20the%20visual%20render&eyebrow=Glossary Accessibility tree The accessibility tree is the structured representation of a webpage that assistive technologies — screen readers, voice control, switch devices — read instead of the visual rendering. Browsers comput https://www.stride.page/glossary/adr https://www.stride.page/api/og?title=ADR&subtitle=An%20Architecture%20Decision%20Record%20is%20a%20short%20document%20that%20captures%20a%20single%20architecture%20choice%20%E2%80%94%20what%20was%20decided%2C%20why%2C%20what%20alternatives%20were%20rejected%2C%20and%20what%20consequences%20the%20t&eyebrow=Glossary ADR An Architecture Decision Record is a short document that captures a single architecture choice — what was decided, why, what alternatives were rejected, and what consequences the team accepts. ADRs ar https://www.stride.page/glossary/agent-loop https://www.stride.page/api/og?title=Agent%20loop&subtitle=An%20agent%20loop%20is%20the%20orchestration%20pattern%20where%20an%20LLM%20iteratively%20reasons%2C%20calls%20tools%2C%20observes%20results%2C%20and%20continues%20%E2%80%94%20until%20a%20terminal%20condition%20is%20met%20(task%20complete%2C%20max%20it&eyebrow=Glossary Agent loop An agent loop is the orchestration pattern where an LLM iteratively reasons, calls tools, observes results, and continues — until a terminal condition is met (task complete, max iterations reached, er https://www.stride.page/glossary/agentic-rag https://www.stride.page/api/og?title=Agentic%20RAG&subtitle=Agentic%20RAG%20extends%20traditional%20retrieval-augmented%20generation%20with%20an%20agent%20loop%3A%20instead%20of%20one%20retrieval%20pass%20before%20generation%2C%20the%20model%20iteratively%20refines%20its%20queries%2C%20retri&eyebrow=Glossary Agentic RAG Agentic RAG extends traditional retrieval-augmented generation with an agent loop: instead of one retrieval pass before generation, the model iteratively refines its queries, retrieves more context, e https://www.stride.page/glossary/agentic-workflow https://www.stride.page/api/og?title=Agentic%20workflow&subtitle=An%20agentic%20workflow%20is%20a%20software%20process%20in%20which%20one%20or%20more%20LLM-driven%20agents%20drive%20the%20work%2C%20making%20decisions%20and%20invoking%20tools%20at%20each%20step%20rather%20than%20following%20a%20hardcoded%20&eyebrow=Glossary Agentic workflow An agentic workflow is a software process in which one or more LLM-driven agents drive the work, making decisions and invoking tools at each step rather than following a hardcoded script. Agentic work https://www.stride.page/glossary/agile-release-train https://www.stride.page/api/og?title=Agile%20release%20train%20(ART)&subtitle=An%20Agile%20Release%20Train%20is%20a%20long-lived%20team-of-teams%20in%20SAFe%20%E2%80%94%20typically%2050-125%20people%20across%205-12%20Agile%20teams%20%E2%80%94%20that%20plans%2C%20commits%2C%20and%20releases%20together%20on%20a%20fixed%20cadence%20calle&eyebrow=Glossary Agile release train (ART) An Agile Release Train is a long-lived team-of-teams in SAFe — typically 50-125 people across 5-12 Agile teams — that plans, commits, and releases together on a fixed cadence called a Program Incremen https://www.stride.page/glossary/ai-citation https://www.stride.page/api/og?title=AI%20citation%20(cross-LLM)&subtitle=AI%20citation%20is%20the%20inclusion%20of%20a%20website's%20content%20(with%20source%20attribution)%20in%20the%20response%20of%20an%20AI%20assistant%20%E2%80%94%20ChatGPT%20search%2C%20Perplexity%2C%20Claude%20with%20web%20access%2C%20Gemini%2C%20Bing%20&eyebrow=Glossary AI citation (cross-LLM) AI citation is the inclusion of a website's content (with source attribution) in the response of an AI assistant — ChatGPT search, Perplexity, Claude with web access, Gemini, Bing Copilot. Citation in https://www.stride.page/glossary/ai-code-review https://www.stride.page/api/og?title=AI%20code%20review&subtitle=AI%20code%20review%20is%20the%20use%20of%20large%20language%20models%20to%20review%20pull%20requests%20automatically%20%E2%80%94%20flagging%20bugs%2C%20suggesting%20improvements%2C%20checking%20for%20security%20issues%2C%20enforcing%20style.%20Th&eyebrow=Glossary AI code review AI code review is the use of large language models to review pull requests automatically — flagging bugs, suggesting improvements, checking for security issues, enforcing style. The dominant tools (Gi https://www.stride.page/glossary/ai-overview https://www.stride.page/api/og?title=AI%20Overview%20(Google%20SERP)&subtitle=AI%20Overview%20is%20the%20LLM-generated%20answer%20that%20Google%20shows%20at%20the%20top%20of%20search%20results%20for%20many%20queries%20%E2%80%94%20synthesising%20information%20from%20multiple%20sources%20and%20citing%20them%20inline.%20AI%20&eyebrow=Glossary AI Overview (Google SERP) AI Overview is the LLM-generated answer that Google shows at the top of search results for many queries — synthesising information from multiple sources and citing them inline. AI Overview replaced Fe https://www.stride.page/glossary/ai-pair-programming https://www.stride.page/api/og?title=AI%20pair%20programming&subtitle=AI%20pair%20programming%20works%20alongside%20an%20AI%20coding%20assistant%20(Claude%2C%20Copilot%2C%20Cursor%2C%20Continue)%20as%20a%20continuous%20collaborator%20on%20coding%20tasks%20%E2%80%94%20suggesting%20completions%2C%20generating%20tes&eyebrow=Glossary AI pair programming AI pair programming works alongside an AI coding assistant (Claude, Copilot, Cursor, Continue) as a continuous collaborator on coding tasks — suggesting completions, generating tests, explaining unfam https://www.stride.page/glossary/ai-test-generation https://www.stride.page/api/og?title=AI%20test%20generation&subtitle=AI%20test%20generation%20is%20the%20use%20of%20LLMs%20to%20author%20tests%20%E2%80%94%20unit%20tests%20from%20source%20code%2C%20acceptance%20tests%20from%20user%20stories%2C%20end-to-end%20tests%20from%20product%20descriptions.%20The%20pattern%20wor&eyebrow=Glossary AI test generation AI test generation is the use of LLMs to author tests — unit tests from source code, acceptance tests from user stories, end-to-end tests from product descriptions. The pattern works well for the mech https://www.stride.page/glossary/ai-native-delivery https://www.stride.page/api/og?title=AI-native%20delivery&subtitle=AI-native%20delivery%20is%20the%20operating%20model%20for%20software-development%20organisations%20in%20which%20AI%20is%20structurally%20embedded%20in%20every%20stage%20of%20the%20delivery%20lifecycle%20%E2%80%94%20discovery%2C%20planning&eyebrow=Glossary AI-native delivery AI-native delivery is the operating model for software-development organisations in which AI is structurally embedded in every stage of the delivery lifecycle — discovery, planning, architecture, impl https://www.stride.page/glossary/anti-corruption-layer https://www.stride.page/api/og?title=Anti-corruption%20layer&subtitle=An%20anti-corruption%20layer%20is%20the%20translation%20boundary%20between%20two%20bounded%20contexts%20that%20prevents%20the%20model%20of%20one%20from%20leaking%20into%20the%20other.%20The%20ACL%20converts%20incoming%20external%20con&eyebrow=Glossary Anti-corruption layer An anti-corruption layer is the translation boundary between two bounded contexts that prevents the model of one from leaking into the other. The ACL converts incoming external concepts into the consu https://www.stride.page/glossary/apdex https://www.stride.page/api/og?title=Apdex%20score&subtitle=Apdex%20(Application%20Performance%20Index)%20is%20a%20single%200-1%20score%20that%20summarises%20user-perceived%20performance%3A%20requests%20faster%20than%20a%20target%20T%20are%20'satisfied'%20(weight%201)%2C%20requests%20between&eyebrow=Glossary Apdex score Apdex (Application Performance Index) is a single 0-1 score that summarises user-perceived performance: requests faster than a target T are 'satisfied' (weight 1), requests between T and 4T are 'toler https://www.stride.page/glossary/api-gateway https://www.stride.page/api/og?title=API%20gateway&subtitle=An%20API%20gateway%20is%20the%20single%20entry%20point%20in%20front%20of%20a%20service%20ecosystem%20that%20handles%20cross-cutting%20concerns%20%E2%80%94%20authentication%2C%20rate%20limiting%2C%20request%20routing%2C%20response%20aggregation%2C&eyebrow=Glossary API gateway An API gateway is the single entry point in front of a service ecosystem that handles cross-cutting concerns — authentication, rate limiting, request routing, response aggregation, caching, observabil https://www.stride.page/glossary/fitness-function https://www.stride.page/api/og?title=Architecture%20fitness%20function&subtitle=An%20architecture%20fitness%20function%20is%20an%20executable%20test%20that%20asserts%20an%20architectural%20characteristic%20%E2%80%94%20coupling%20between%20modules%2C%20cyclic-dependency%20absence%2C%20response-time%20budget%2C%20dep&eyebrow=Glossary Architecture fitness function An architecture fitness function is an executable test that asserts an architectural characteristic — coupling between modules, cyclic-dependency absence, response-time budget, dependency direction. F https://www.stride.page/glossary/autonomous-agent https://www.stride.page/api/og?title=Autonomous%20agent&subtitle=An%20autonomous%20agent%20is%20an%20AI%20system%20that%20pursues%20a%20goal%20over%20multiple%20steps%20with%20minimal%20human%20intervention%20%E2%80%94%20deciding%20what%20actions%20to%20take%2C%20executing%20them%20via%20tools%2C%20observing%20res&eyebrow=Glossary Autonomous agent An autonomous agent is an AI system that pursues a goal over multiple steps with minimal human intervention — deciding what actions to take, executing them via tools, observing results, and iterating https://www.stride.page/glossary/backend-for-frontend https://www.stride.page/api/og?title=Backend%20for%20frontend%20(BFF)&subtitle=A%20backend-for-frontend%20is%20a%20dedicated%20server-side%20layer%20per%20client%20type%20(web%2C%20iOS%2C%20Android%2C%20partner%20API)%20that%20adapts%20the%20underlying%20services%20to%20that%20client's%20specific%20needs%20%E2%80%94%20aggre&eyebrow=Glossary Backend for frontend (BFF) A backend-for-frontend is a dedicated server-side layer per client type (web, iOS, Android, partner API) that adapts the underlying services to that client's specific needs — aggregating multiple serv https://www.stride.page/glossary/backlog-refinement https://www.stride.page/api/og?title=Backlog%20refinement&subtitle=Backlog%20refinement%20(sometimes%20called%20grooming)%20is%20the%20recurring%20practice%20of%20clarifying%2C%20splitting%2C%20estimating%2C%20and%20prioritising%20stories%20before%20they%20enter%20a%20sprint.%20A%20well-refined%20b&eyebrow=Glossary Backlog refinement Backlog refinement (sometimes called grooming) is the recurring practice of clarifying, splitting, estimating, and prioritising stories before they enter a sprint. A well-refined backlog has its top 2 https://www.stride.page/glossary/backpressure https://www.stride.page/api/og?title=Backpressure&subtitle=Backpressure%20is%20the%20signal%20a%20downstream%20component%20sends%20upstream%20to%20indicate%20that%20it%20cannot%20accept%20more%20work%20%E2%80%94%20explicitly%20slowing%20or%20rejecting%20incoming%20requests%20so%20the%20queue%20doesn'&eyebrow=Glossary Backpressure Backpressure is the signal a downstream component sends upstream to indicate that it cannot accept more work — explicitly slowing or rejecting incoming requests so the queue doesn't grow unboundedly. https://www.stride.page/glossary/bdd https://www.stride.page/api/og?title=BDD&subtitle=Behavior-Driven%20Development%20is%20a%20software%20practice%20that%20builds%20on%20TDD%20by%20writing%20tests%20in%20business-readable%2C%20scenario-style%20language%20(typically%20Gherkin).%20The%20goal%3A%20shared%20understan&eyebrow=Glossary BDD Behavior-Driven Development is a software practice that builds on TDD by writing tests in business-readable, scenario-style language (typically Gherkin). The goal: shared understanding between enginee https://www.stride.page/glossary/blameless-postmortem https://www.stride.page/api/og?title=Blameless%20postmortem&subtitle=A%20blameless%20postmortem%20is%20an%20incident%20review%20structured%20to%20identify%20systemic%20causes%20%E2%80%94%20flawed%20processes%2C%20missing%20alerts%2C%20fragile%20dependencies%20%E2%80%94%20rather%20than%20individual%20fault.%20The%20bla&eyebrow=Glossary Blameless postmortem A blameless postmortem is an incident review structured to identify systemic causes — flawed processes, missing alerts, fragile dependencies — rather than individual fault. The blameless framing, popu https://www.stride.page/glossary/blue-green-deploy https://www.stride.page/api/og?title=Blue-green%20deploy&subtitle=Blue-green%20deployment%20maintains%20two%20identical%20production%20environments%20%E2%80%94%20blue%20(current)%20and%20green%20(new).%20Releases%20deploy%20to%20green%3B%20once%20health%20checks%20pass%2C%20traffic%20flips%20from%20blue%20t&eyebrow=Glossary Blue-green deploy Blue-green deployment maintains two identical production environments — blue (current) and green (new). Releases deploy to green; once health checks pass, traffic flips from blue to green. Rollback is https://www.stride.page/glossary/bounded-context https://www.stride.page/api/og?title=Bounded%20context&subtitle=A%20bounded%20context%20is%20the%20boundary%20within%20which%20a%20particular%20domain%20model%20%E2%80%94%20its%20terms%2C%20rules%2C%20and%20invariants%20%E2%80%94%20is%20consistent%20and%20authoritative.%20The%20same%20business%20concept%20(e.g.%2C%20'Ord&eyebrow=Glossary Bounded context A bounded context is the boundary within which a particular domain model — its terms, rules, and invariants — is consistent and authoritative. The same business concept (e.g., 'Order') may exist in mu https://www.stride.page/glossary/bpmn https://www.stride.page/api/og?title=BPMN&subtitle=Business%20Process%20Model%20and%20Notation%20is%20the%20ISO%2019510%20standard%20for%20graphically%20representing%20business%20processes%20as%20flowcharts.%20BPMN%20diagrams%20use%20a%20small%20vocabulary%20of%20shapes%20(rectang&eyebrow=Glossary BPMN Business Process Model and Notation is the ISO 19510 standard for graphically representing business processes as flowcharts. BPMN diagrams use a small vocabulary of shapes (rectangles for activities, https://www.stride.page/glossary/branded-type https://www.stride.page/api/og?title=Branded%20type&subtitle=A%20branded%20type%20is%20a%20TypeScript%20pattern%20that%20distinguishes%20structurally-identical%20types%20by%20adding%20a%20phantom%20'brand'%20property%20%E2%80%94%20UserId%20and%20ProductId%20can%20both%20be%20string%20at%20runtime%20but&eyebrow=Glossary Branded type A branded type is a TypeScript pattern that distinguishes structurally-identical types by adding a phantom 'brand' property — UserId and ProductId can both be string at runtime but cannot be assigned https://www.stride.page/glossary/breaking-change https://www.stride.page/api/og?title=Breaking%20change&subtitle=A%20breaking%20change%20is%20any%20change%20to%20a%20published%20interface%20(API%20endpoint%2C%20library%20function%20signature%2C%20CLI%20flag%2C%20configuration%20key)%20that%20requires%20consumer%20code%20or%20configuration%20change&eyebrow=Glossary Breaking change A breaking change is any change to a published interface (API endpoint, library function signature, CLI flag, configuration key) that requires consumer code or configuration changes to keep working. B https://www.stride.page/glossary/built-in-quality https://www.stride.page/api/og?title=Built-in%20quality&subtitle=Built-in%20quality%20is%20the%20SAFe%20principle%20that%20quality%20is%20engineered%20into%20the%20product%20as%20it's%20built%20%E2%80%94%20through%20test%20automation%2C%20pair%20programming%2C%20continuous%20integration%2C%20code%20review%2C%20d&eyebrow=Glossary Built-in quality Built-in quality is the SAFe principle that quality is engineered into the product as it's built — through test automation, pair programming, continuous integration, code review, definition of done — https://www.stride.page/glossary/c4-model https://www.stride.page/api/og?title=C4%20model&subtitle=The%20C4%20model%2C%20created%20by%20Simon%20Brown%20around%202011%2C%20is%20a%20hierarchical%20way%20to%20diagram%20software%20architecture%20using%20four%20levels%3A%20Context%20(system%20and%20its%20users%2Fexternal%20systems)%2C%20Contain&eyebrow=Glossary C4 model The C4 model, created by Simon Brown around 2011, is a hierarchical way to diagram software architecture using four levels: Context (system and its users/external systems), Container (deployable units https://www.stride.page/glossary/calibration-error https://www.stride.page/api/og?title=Calibration%20error&subtitle=Calibration%20error%20is%20the%20gap%20between%20the%20confidence%20someone%20reports%20in%20a%20prediction%20and%20the%20empirical%20accuracy%20of%20those%20predictions.%20A%20well-calibrated%20estimator%20who%20says%20they%20are%208&eyebrow=Glossary Calibration error Calibration error is the gap between the confidence someone reports in a prediction and the empirical accuracy of those predictions. A well-calibrated estimator who says they are 80% confident is righ https://www.stride.page/glossary/canary-release https://www.stride.page/api/og?title=Canary%20release&subtitle=A%20canary%20release%20routes%20a%20small%20percentage%20of%20production%20traffic%20(typically%201-5%25)%20to%20a%20new%20version%2C%20monitors%20error%20rates%20and%20latency%2C%20and%20rolls%20forward%20to%20100%25%20only%20when%20metrics%20st&eyebrow=Glossary Canary release A canary release routes a small percentage of production traffic (typically 1-5%) to a new version, monitors error rates and latency, and rolls forward to 100% only when metrics stay healthy. The name https://www.stride.page/glossary/capacity-planning https://www.stride.page/api/og?title=Capacity%20planning&subtitle=Capacity%20planning%20estimates%20how%20much%20work%20a%20team%20can%20realistically%20take%20on%20in%20a%20sprint%2C%20accounting%20for%20PTO%2C%20meetings%2C%20on-call%20duty%2C%20and%20other%20non-coding%20time.%20Capacity%20is%20the%20upper&eyebrow=Glossary Capacity planning Capacity planning estimates how much work a team can realistically take on in a sprint, accounting for PTO, meetings, on-call duty, and other non-coding time. Capacity is the upper bound on what you c https://www.stride.page/glossary/case-duration https://www.stride.page/api/og?title=Case%20duration&subtitle=Case%20duration%20is%20the%20elapsed%20time%20from%20a%20case's%20start%20to%20its%20completion.%20The%20distribution%20of%20case%20durations%20is%20the%20most%20useful%20operational%20view%3A%20median%20tells%20you%20typical%20experience&eyebrow=Glossary Case duration Case duration is the elapsed time from a case's start to its completion. The distribution of case durations is the most useful operational view: median tells you typical experience, p95 tells you SLA- https://www.stride.page/glossary/case-throughput https://www.stride.page/api/og?title=Case%20throughput&subtitle=Case%20throughput%20is%20the%20number%20of%20cases%20completed%20per%20unit%20time%20(cases%20per%20day%2C%20per%20week)%20%E2%80%94%20the%20basic%20flow%20metric%20of%20a%20process.%20Throughput%20trends%20reveal%20whether%20the%20process%20is%20keepi&eyebrow=Glossary Case throughput Case throughput is the number of cases completed per unit time (cases per day, per week) — the basic flow metric of a process. Throughput trends reveal whether the process is keeping up with demand; t https://www.stride.page/glossary/cdn-edge https://www.stride.page/api/og?title=CDN%20edge&subtitle=A%20CDN%20edge%20is%20one%20of%20the%20geographically%20distributed%20points-of-presence%20operated%20by%20a%20content%20delivery%20network%20%E2%80%94%20typically%20hundreds%20of%20locations%20worldwide%20where%20static%20and%20cacheable&eyebrow=Glossary CDN edge A CDN edge is one of the geographically distributed points-of-presence operated by a content delivery network — typically hundreds of locations worldwide where static and cacheable content is served f https://www.stride.page/glossary/chain-of-thought https://www.stride.page/api/og?title=Chain-of-thought%20(CoT)&subtitle=Chain-of-thought%20prompting%20asks%20the%20LLM%20to%20reason%20step%20by%20step%20before%20producing%20the%20final%20answer%20%E2%80%94%20'let's%20think%20through%20this%20carefully'%20or%20'show%20your%20work'.%20The%20technique%20dramatica&eyebrow=Glossary Chain-of-thought (CoT) Chain-of-thought prompting asks the LLM to reason step by step before producing the final answer — 'let's think through this carefully' or 'show your work'. The technique dramatically improves perform https://www.stride.page/glossary/change-failure-rate https://www.stride.page/api/og?title=Change%20failure%20rate&subtitle=Change%20failure%20rate%20(CFR)%20is%20the%20percentage%20of%20deployments%20that%20cause%20a%20degradation%20in%20service%20requiring%20remediation%20(a%20hotfix%2C%20rollback%2C%20or%20patch).%20It%20is%20the%20fourth%20DORA%20metric%20an&eyebrow=Glossary Change failure rate Change failure rate (CFR) is the percentage of deployments that cause a degradation in service requiring remediation (a hotfix, rollback, or patch). It is the fourth DORA metric and the noisiest of th https://www.stride.page/glossary/chaos-engineering https://www.stride.page/api/og?title=Chaos%20engineering&subtitle=Chaos%20engineering%20deliberately%20injects%20failures%20into%20production%20(or%20production-like)%20systems%20to%20validate%20they%20recover%20gracefully.%20Pioneered%20by%20Netflix%20with%20Chaos%20Monkey%20in%202010%2C%20it&eyebrow=Glossary Chaos engineering Chaos engineering deliberately injects failures into production (or production-like) systems to validate they recover gracefully. Pioneered by Netflix with Chaos Monkey in 2010, it catches reliability https://www.stride.page/glossary/ci-cd https://www.stride.page/api/og?title=CI%2FCD%20pipeline&subtitle=A%20CI%2FCD%20pipeline%20is%20the%20automated%20chain%20of%20build%20%2F%20test%20%2F%20deploy%20steps%20that%20runs%20on%20every%20code%20change.%20CI%20(continuous%20integration)%20means%20merging%20changes%20to%20a%20shared%20branch%20frequent&eyebrow=Glossary CI/CD pipeline A CI/CD pipeline is the automated chain of build / test / deploy steps that runs on every code change. CI (continuous integration) means merging changes to a shared branch frequently with automated te https://www.stride.page/glossary/circuit-breaker https://www.stride.page/api/og?title=Circuit%20breaker&subtitle=A%20circuit%20breaker%20is%20a%20pattern%20that%20monitors%20calls%20to%20a%20downstream%20service%20and%20'trips'%20(stops%20calling)%20when%20failures%20exceed%20a%20threshold%2C%20returning%20a%20fallback%20or%20error%20immediately.%20&eyebrow=Glossary Circuit breaker A circuit breaker is a pattern that monitors calls to a downstream service and 'trips' (stops calling) when failures exceed a threshold, returning a fallback or error immediately. After a cool-down, i https://www.stride.page/glossary/clean-architecture https://www.stride.page/api/og?title=Clean%20architecture&subtitle=Clean%20architecture%2C%20presented%20by%20Robert%20C.%20Martin%20(Uncle%20Bob)%20in%202012%2C%20organises%20a%20system%20into%20concentric%20layers%3A%20entities%20(business%20rules)%20at%20the%20centre%2C%20use%20cases%20around%20them%2C%20in&eyebrow=Glossary Clean architecture Clean architecture, presented by Robert C. Martin (Uncle Bob) in 2012, organises a system into concentric layers: entities (business rules) at the centre, use cases around them, interface adapters nex https://www.stride.page/glossary/client-component https://www.stride.page/api/og?title=Client%20component&subtitle=A%20client%20component%20(in%20React%20Server%20Components%20terminology)%20is%20a%20component%20marked%20with%20'use%20client'%20that%20hydrates%20on%20the%20client%20and%20can%20use%20browser%20APIs%2C%20event%20handlers%2C%20state%2C%20and&eyebrow=Glossary Client component A client component (in React Server Components terminology) is a component marked with 'use client' that hydrates on the client and can use browser APIs, event handlers, state, and effects. Client com https://www.stride.page/glossary/code-coverage https://www.stride.page/api/og?title=Code%20coverage&subtitle=Code%20coverage%20is%20the%20percentage%20of%20source%20code%20executed%20by%20a%20test%20suite%2C%20broken%20down%20by%20statement%2C%20branch%2C%20or%20line.%20High%20coverage%20indicates%20wide%20test%20reach%3B%20it%20does%20NOT%20indicate%20te&eyebrow=Glossary Code coverage Code coverage is the percentage of source code executed by a test suite, broken down by statement, branch, or line. High coverage indicates wide test reach; it does NOT indicate test quality — tests c https://www.stride.page/glossary/code-review https://www.stride.page/api/og?title=Code%20review&subtitle=Code%20review%20has%20another%20engineer%20evaluate%20proposed%20changes%20before%20they%20merge.%20It%20catches%20bugs%2C%20enforces%20style%20consistency%2C%20distributes%20knowledge%20across%20the%20team%2C%20and%20surfaces%20desig&eyebrow=Glossary Code review Code review has another engineer evaluate proposed changes before they merge. It catches bugs, enforces style consistency, distributes knowledge across the team, and surfaces design issues before they https://www.stride.page/glossary/cognitive-load https://www.stride.page/api/og?title=Cognitive%20load&subtitle=In%20engineering-team%20contexts%2C%20cognitive%20load%20is%20the%20amount%20of%20mental%20effort%20required%20for%20a%20team%20to%20be%20effective%20at%20its%20work%20%E2%80%94%20encompassing%20the%20domain%20knowledge%2C%20technical%20knowledge&eyebrow=Glossary Cognitive load In engineering-team contexts, cognitive load is the amount of mental effort required for a team to be effective at its work — encompassing the domain knowledge, technical knowledge, and tool/process k https://www.stride.page/glossary/cone-of-uncertainty https://www.stride.page/api/og?title=Cone%20of%20Uncertainty&subtitle=The%20Cone%20of%20Uncertainty%20is%20a%20model%20of%20estimation%20variance%20over%20a%20software%20project's%20lifecycle%2C%20articulated%20by%20Barry%20Boehm%20in%201981.%20Estimates%20at%20project%20inception%20have%20~4%C3%97%20variance%20&eyebrow=Glossary Cone of Uncertainty The Cone of Uncertainty is a model of estimation variance over a software project's lifecycle, articulated by Barry Boehm in 1981. Estimates at project inception have ~4× variance (a 100-staff-week bu https://www.stride.page/glossary/confidence-vote https://www.stride.page/api/og?title=Confidence%20vote&subtitle=A%20confidence%20vote%20is%20the%20closing%20ritual%20of%20SAFe%20PI%20Planning%20in%20which%20every%20team%20and%20the%20entire%20ART%20vote%201-5%20fingers%20on%20their%20confidence%20in%20meeting%20the%20committed%20PI%20Objectives.%20A%20vo&eyebrow=Glossary Confidence vote A confidence vote is the closing ritual of SAFe PI Planning in which every team and the entire ART vote 1-5 fingers on their confidence in meeting the committed PI Objectives. A vote of 1-2 from anyon https://www.stride.page/glossary/configuration-drift https://www.stride.page/api/og?title=Configuration%20drift&subtitle=Configuration%20drift%20is%20the%20gradual%20divergence%20between%20a%20system's%20actual%20configuration%20and%20its%20declared%2Fdocumented%20configuration%2C%20caused%20by%20manual%20changes%20that%20bypass%20the%20infrastruc&eyebrow=Glossary Configuration drift Configuration drift is the gradual divergence between a system's actual configuration and its declared/documented configuration, caused by manual changes that bypass the infrastructure-as-code source https://www.stride.page/glossary/conformance-checking https://www.stride.page/api/og?title=Conformance%20checking&subtitle=Conformance%20checking%20is%20the%20formal%20process-mining%20technique%20of%20comparing%20an%20event%20log%20to%20a%20reference%20process%20model%20and%20producing%20fitness%2C%20precision%2C%20generalisation%2C%20and%20simplicity%20&eyebrow=Glossary Conformance checking Conformance checking is the formal process-mining technique of comparing an event log to a reference process model and producing fitness, precision, generalisation, and simplicity scores. The output q https://www.stride.page/glossary/connected-delivery-graph https://www.stride.page/api/og?title=Connected%20delivery%20graph&subtitle=A%20connected%20delivery%20graph%20is%20a%20unified%20data%20model%20in%20which%20every%20artefact%20of%20software%20delivery%20%E2%80%94%20initiatives%2C%20PRDs%2C%20ADRs%2C%20stories%2C%20acceptance%20criteria%2C%20code%20commits%2C%20test%20cases%2C%20t&eyebrow=Glossary Connected delivery graph A connected delivery graph is a unified data model in which every artefact of software delivery — initiatives, PRDs, ADRs, stories, acceptance criteria, code commits, test cases, test runs, defects, d https://www.stride.page/glossary/context-window https://www.stride.page/api/og?title=Context%20window&subtitle=The%20context%20window%20is%20the%20maximum%20number%20of%20tokens%20an%20LLM%20can%20process%20in%20a%20single%20request%20%E2%80%94%20including%20the%20prompt%2C%20retrieved%20context%2C%20conversation%20history%2C%20and%20the%20generated%20respons&eyebrow=Glossary Context window The context window is the maximum number of tokens an LLM can process in a single request — including the prompt, retrieved context, conversation history, and the generated response. Modern LLMs range https://www.stride.page/glossary/context-switching-cost https://www.stride.page/api/og?title=Context-switching%20cost&subtitle=Context-switching%20cost%20is%20the%20productivity%20lost%20when%20an%20engineer%20moves%20between%20tasks%2C%20projects%2C%20or%20interruption%20types.%20The%20widely-cited%20research%20(Gerald%20Weinberg%201992)%20finds%20a%20sing&eyebrow=Glossary Context-switching cost Context-switching cost is the productivity lost when an engineer moves between tasks, projects, or interruption types. The widely-cited research (Gerald Weinberg 1992) finds a single context switch co https://www.stride.page/glossary/continuous-deployment https://www.stride.page/api/og?title=Continuous%20deployment&subtitle=Continuous%20deployment%20automatically%20deploys%20every%20change%20that%20passes%20the%20test%20suite%20into%20production%20%E2%80%94%20no%20human%20gate%20between%20merging%20code%20and%20serving%20traffic.%20CD%20assumes%20high%20test%20c&eyebrow=Glossary Continuous deployment Continuous deployment automatically deploys every change that passes the test suite into production — no human gate between merging code and serving traffic. CD assumes high test coverage, automated r https://www.stride.page/glossary/continuous-exploration https://www.stride.page/api/og?title=Continuous%20exploration&subtitle=Continuous%20exploration%20is%20SAFe's%20umbrella%20term%20for%20ongoing%20discovery%20work%20%E2%80%94%20hypothesis%20generation%2C%20customer%20research%2C%20prototyping%2C%20experiments%20%E2%80%94%20that%20feeds%20the%20backlog%20of%20features%20&eyebrow=Glossary Continuous exploration Continuous exploration is SAFe's umbrella term for ongoing discovery work — hypothesis generation, customer research, prototyping, experiments — that feeds the backlog of features and enablers. It's t https://www.stride.page/glossary/contract-testing https://www.stride.page/api/og?title=Contract%20testing&subtitle=Contract%20testing%20verifies%20that%20two%20services%20communicate%20correctly%20without%20requiring%20both%20to%20be%20deployed%20for%20the%20test.%20The%20consumer%20specifies%20its%20expected%20interactions%20with%20the%20prod&eyebrow=Glossary Contract testing Contract testing verifies that two services communicate correctly without requiring both to be deployed for the test. The consumer specifies its expected interactions with the producer (the contract); https://www.stride.page/glossary/conways-law https://www.stride.page/api/og?title=Conway's%20Law&subtitle=Conway's%20Law%2C%20formulated%20by%20Melvin%20Conway%20in%20a%201968%20paper%2C%20states%20that%20any%20system's%20design%20mirrors%20the%20communication%20structure%20of%20the%20organisation%20that%20built%20it.%20Systems%20built%20by%20t&eyebrow=Glossary Conway's Law Conway's Law, formulated by Melvin Conway in a 1968 paper, states that any system's design mirrors the communication structure of the organisation that built it. Systems built by three teams will have https://www.stride.page/glossary/cost-of-delay https://www.stride.page/api/og?title=Cost%20of%20delay&subtitle=Cost%20of%20delay%20is%20the%20economic%20impact%20of%20not%20having%20a%20feature%20available%20%E2%80%94%20revenue%20forgone%2C%20cost%20incurred%2C%20risk%20that%20compounds%20%E2%80%94%20expressed%20as%20a%20per-unit-time%20number%20(per%20week%2C%20per%20mo&eyebrow=Glossary Cost of delay Cost of delay is the economic impact of not having a feature available — revenue forgone, cost incurred, risk that compounds — expressed as a per-unit-time number (per week, per month). It's the econo https://www.stride.page/glossary/cqrs https://www.stride.page/api/og?title=CQRS&subtitle=Command%20Query%20Responsibility%20Segregation%20is%20an%20architectural%20pattern%20that%20splits%20a%20system's%20write%20path%20(commands%20that%20change%20state)%20from%20its%20read%20path%20(queries%20that%20return%20state)%20%E2%80%94&eyebrow=Glossary CQRS Command Query Responsibility Segregation is an architectural pattern that splits a system's write path (commands that change state) from its read path (queries that return state) — typically with sepa https://www.stride.page/glossary/cumulative-flow-diagram https://www.stride.page/api/og?title=Cumulative%20flow%20diagram%20(CFD)&subtitle=A%20cumulative%20flow%20diagram%20is%20a%20stacked%20area%20chart%20showing%2C%20for%20each%20state%20in%20a%20workflow%2C%20how%20many%20items%20are%20in%20that%20state%20over%20time.%20CFDs%20visualise%20WIP%20per%20state%2C%20lead%20time%20(horizo&eyebrow=Glossary Cumulative flow diagram (CFD) A cumulative flow diagram is a stacked area chart showing, for each state in a workflow, how many items are in that state over time. CFDs visualise WIP per state, lead time (horizontal width between a https://www.stride.page/glossary/cycle-time https://www.stride.page/api/og?title=Cycle%20time&subtitle=Cycle%20time%20is%20the%20elapsed%20time%20from%20when%20work%20starts%20on%20an%20item%20(first%20commit%2C%20status%20change%20to%20In%20Progress)%20to%20when%20it%20ships%20to%20users.%20It%20measures%20team%20flow%20without%20the%20queue%20nois&eyebrow=Glossary Cycle time Cycle time is the elapsed time from when work starts on an item (first commit, status change to In Progress) to when it ships to users. It measures team flow without the queue noise that lead time inc https://www.stride.page/glossary/dark-launch https://www.stride.page/api/og?title=Dark%20launch&subtitle=A%20dark%20launch%20ships%20a%20feature%20to%20production%20but%20leaves%20it%20disabled%20for%20users%20%E2%80%94%20the%20code%20runs%20(sometimes%20against%20real%20traffic%2C%20sometimes%20against%20shadow%20traffic)%20to%20validate%20behaviou&eyebrow=Glossary Dark launch A dark launch ships a feature to production but leaves it disabled for users — the code runs (sometimes against real traffic, sometimes against shadow traffic) to validate behaviour under load before https://www.stride.page/glossary/decision-mining https://www.stride.page/api/og?title=Decision%20mining&subtitle=Decision%20mining%20is%20the%20process-mining%20extension%20that%20discovers%20the%20data-driven%20rules%20behind%20branching%20decisions%20in%20a%20process%20%E2%80%94%20why%20this%20case%20took%20variant%20A%20and%20that%20one%20took%20varian&eyebrow=Glossary Decision mining Decision mining is the process-mining extension that discovers the data-driven rules behind branching decisions in a process — why this case took variant A and that one took variant B. Decision rules https://www.stride.page/glossary/deep-work https://www.stride.page/api/og?title=Deep%20work&subtitle=Deep%20work%2C%20a%20term%20coined%20by%20Cal%20Newport%20in%20his%202016%20book%20of%20the%20same%20name%2C%20is%20professional%20activity%20performed%20in%20a%20state%20of%20distraction-free%20concentration%20that%20pushes%20cognitive%20cap&eyebrow=Glossary Deep work Deep work, a term coined by Cal Newport in his 2016 book of the same name, is professional activity performed in a state of distraction-free concentration that pushes cognitive capabilities to their l https://www.stride.page/glossary/defense-in-depth https://www.stride.page/api/og?title=Defense%20in%20depth&subtitle=Defense%20in%20depth%20is%20the%20security%20principle%20of%20layering%20multiple%20independent%20controls%20so%20that%20a%20failure%20in%20any%20one%20doesn't%20expose%20the%20system%20%E2%80%94%20input%20validation%20plus%20parameterised%20qu&eyebrow=Glossary Defense in depth Defense in depth is the security principle of layering multiple independent controls so that a failure in any one doesn't expose the system — input validation plus parameterised queries plus least-pri https://www.stride.page/glossary/definition-of-done https://www.stride.page/api/og?title=Definition%20of%20Done&subtitle=Definition%20of%20Done%20(DoD)%20is%20a%20team-wide%20checklist%20that%20every%20story%20must%20satisfy%20before%20being%20marked%20complete%20%E2%80%94%20typical%20entries%20include%3A%20code%20reviewed%2C%20tests%20passing%2C%20documentation%20&eyebrow=Glossary Definition of Done Definition of Done (DoD) is a team-wide checklist that every story must satisfy before being marked complete — typical entries include: code reviewed, tests passing, documentation updated, deployed to https://www.stride.page/glossary/definition-of-ready https://www.stride.page/api/og?title=Definition%20of%20ready&subtitle=Definition%20of%20Ready%20is%20the%20team's%20explicit%20checklist%20that%20a%20story%20must%20pass%20before%20it%20can%20enter%20a%20sprint.%20Companion%20to%20Definition%20of%20Done%2C%20but%20at%20the%20entry%20side.%20Typical%20entries%3A%20a&eyebrow=Glossary Definition of ready Definition of Ready is the team's explicit checklist that a story must pass before it can enter a sprint. Companion to Definition of Done, but at the entry side. Typical entries: acceptance criteria a https://www.stride.page/glossary/delivery-debt https://www.stride.page/api/og?title=Delivery%20debt&subtitle=Delivery%20debt%20is%20the%20umbrella%20term%20for%20the%20accumulated%20friction%20in%20a%20software-delivery%20organisation's%20ability%20to%20ship%20%E2%80%94%20encompassing%20technical%20debt%20(debt%20in%20the%20code)%2C%20process%20debt&eyebrow=Glossary Delivery debt Delivery debt is the umbrella term for the accumulated friction in a software-delivery organisation's ability to ship — encompassing technical debt (debt in the code), process debt (debt in the team's https://www.stride.page/glossary/dependency-injection https://www.stride.page/api/og?title=Dependency%20injection&subtitle=Dependency%20injection%20is%20the%20design%20pattern%20where%20a%20component%20receives%20its%20dependencies%20as%20parameters%20rather%20than%20constructing%20them%20internally.%20The%20pattern%20decouples%20a%20component%20fro&eyebrow=Glossary Dependency injection Dependency injection is the design pattern where a component receives its dependencies as parameters rather than constructing them internally. The pattern decouples a component from the concrete imple https://www.stride.page/glossary/dependency-pinning https://www.stride.page/api/og?title=Dependency%20pinning&subtitle=Dependency%20pinning%20fixes%20the%20exact%20version%20of%20every%20dependency%20(and%20transitively%2C%20every%20transitive%20dependency)%20so%20the%20same%20source%20produces%20the%20same%20build%20artefact%20regardless%20of%20whe&eyebrow=Glossary Dependency pinning Dependency pinning fixes the exact version of every dependency (and transitively, every transitive dependency) so the same source produces the same build artefact regardless of when or where it's buil https://www.stride.page/glossary/depersonalization https://www.stride.page/api/og?title=Depersonalization&subtitle=Depersonalization%2C%20also%20called%20cynicism%20or%20callousness%2C%20is%20the%20second%20dimension%20of%20burnout%20in%20the%20Maslach%20framework%3A%20a%20defensive%20emotional%20detachment%20from%20the%20work%20and%20the%20people%20t&eyebrow=Glossary Depersonalization Depersonalization, also called cynicism or callousness, is the second dimension of burnout in the Maslach framework: a defensive emotional detachment from the work and the people the work serves. In k https://www.stride.page/glossary/deployment-frequency https://www.stride.page/api/og?title=Deployment%20frequency&subtitle=Deployment%20frequency%20is%20the%20rate%20at%20which%20a%20team%20deploys%20to%20production.%20It%20is%20the%20first%20of%20the%20four%20DORA%20metrics%20(alongside%20lead%20time%20for%20changes%2C%20mean%20time%20to%20restore%2C%20and%20change%20&eyebrow=Glossary Deployment frequency Deployment frequency is the rate at which a team deploys to production. It is the first of the four DORA metrics (alongside lead time for changes, mean time to restore, and change failure rate) and th https://www.stride.page/glossary/deprecation-window https://www.stride.page/api/og?title=Deprecation%20window&subtitle=A%20deprecation%20window%20is%20the%20period%20between%20announcing%20that%20a%20feature%20will%20be%20removed%20and%20actually%20removing%20it%20%E2%80%94%20typically%203-12%20months%20for%20SaaS%20APIs%2C%20longer%20for%20libraries.%20The%20windo&eyebrow=Glossary Deprecation window A deprecation window is the period between announcing that a feature will be removed and actually removing it — typically 3-12 months for SaaS APIs, longer for libraries. The window gives consumers ti https://www.stride.page/glossary/deviation-analysis https://www.stride.page/api/og?title=Deviation%20analysis&subtitle=Deviation%20analysis%20quantifies%20how%20often%20and%20how%20much%20an%20observed%20process%20diverges%20from%20its%20reference%20model%20%E2%80%94%20measuring%20missed%20steps%2C%20extra%20steps%2C%20out-of-order%20steps%2C%20and%20loops.%20Eac&eyebrow=Glossary Deviation analysis Deviation analysis quantifies how often and how much an observed process diverges from its reference model — measuring missed steps, extra steps, out-of-order steps, and loops. Each deviation type is https://www.stride.page/glossary/disaster-recovery https://www.stride.page/api/og?title=Disaster%20recovery&subtitle=Disaster%20recovery%20is%20the%20set%20of%20plans%2C%20procedures%2C%20and%20infrastructure%20that%20restores%20a%20service%20after%20a%20major%20failure%20%E2%80%94%20region%20outage%2C%20data%20corruption%2C%20ransomware%2C%20deletion%20of%20produc&eyebrow=Glossary Disaster recovery Disaster recovery is the set of plans, procedures, and infrastructure that restores a service after a major failure — region outage, data corruption, ransomware, deletion of production data. DR is dis https://www.stride.page/glossary/discovery-vs-delivery https://www.stride.page/api/og?title=Discovery%20vs%20delivery&subtitle=Discovery%20vs%20delivery%20is%20the%20foundational%20distinction%20in%20modern%20product%20development%3A%20discovery%20activities%20(research%2C%20prototyping%2C%20hypothesis%20testing)%20determine%20WHAT%20to%20build%20and%20wh&eyebrow=Glossary Discovery vs delivery Discovery vs delivery is the foundational distinction in modern product development: discovery activities (research, prototyping, hypothesis testing) determine WHAT to build and why; delivery activiti https://www.stride.page/glossary/discriminated-union https://www.stride.page/api/og?title=Discriminated%20union&subtitle=A%20discriminated%20union%20is%20a%20union%20type%20whose%20variants%20share%20a%20literal-typed%20property%20(the%20discriminant)%20that%20uniquely%20identifies%20each%20variant%20%E2%80%94%20typically%20named%20'type'%2C%20'kind'%2C%20or%20't&eyebrow=Glossary Discriminated union A discriminated union is a union type whose variants share a literal-typed property (the discriminant) that uniquely identifies each variant — typically named 'type', 'kind', or 'tag'. The discriminan https://www.stride.page/glossary/distillation https://www.stride.page/api/og?title=Distillation&subtitle=Knowledge%20distillation%20trains%20a%20smaller%20'student'%20model%20to%20mimic%20the%20outputs%20of%20a%20larger%20'teacher'%20model%20%E2%80%94%20producing%20a%20model%20that%20runs%20faster%20and%20cheaper%20while%20retaining%20most%20of%20th&eyebrow=Glossary Distillation Knowledge distillation trains a smaller 'student' model to mimic the outputs of a larger 'teacher' model — producing a model that runs faster and cheaper while retaining most of the teacher's capabili https://www.stride.page/glossary/tracing https://www.stride.page/api/og?title=Distributed%20tracing&subtitle=Distributed%20tracing%20records%20the%20path%20of%20a%20single%20request%20as%20it%20traverses%20multiple%20services%2C%20producing%20a%20tree-like%20view%20of%20every%20span%20%E2%80%94%20a%20unit%20of%20work%20in%20a%20single%20service%20%E2%80%94%20with%20tim&eyebrow=Glossary Distributed tracing Distributed tracing records the path of a single request as it traverses multiple services, producing a tree-like view of every span — a unit of work in a single service — with timings, parent-child r https://www.stride.page/glossary/domain-driven-design https://www.stride.page/api/og?title=Domain-driven%20design&subtitle=Domain-driven%20design%20(DDD)%20is%20a%20software-design%20approach%2C%20formalised%20by%20Eric%20Evans%20in%202003%2C%20that%20places%20the%20business%20domain%20at%20the%20centre%20of%20model%20design.%20Engineers%20and%20domain%20expe&eyebrow=Glossary Domain-driven design Domain-driven design (DDD) is a software-design approach, formalised by Eric Evans in 2003, that places the business domain at the centre of model design. Engineers and domain experts collaborate on a https://www.stride.page/glossary/dora-metrics https://www.stride.page/api/og?title=DORA%20metrics&subtitle=The%20four%20DORA%20metrics%20measure%20software-delivery%20performance%3A%20deployment%20frequency%2C%20lead%20time%20for%20changes%2C%20mean%20time%20to%20recovery%20(MTTR)%2C%20and%20change-failure%20rate.%20Defined%20by%20Google's&eyebrow=Glossary DORA metrics The four DORA metrics measure software-delivery performance: deployment frequency, lead time for changes, mean time to recovery (MTTR), and change-failure rate. Defined by Google's DORA team via the a https://www.stride.page/glossary/dotted-chart https://www.stride.page/api/og?title=Dotted%20chart&subtitle=A%20dotted%20chart%20is%20a%20process-mining%20visualisation%20that%20plots%20every%20event%20in%20a%20log%20as%20a%20dot%20on%20a%202D%20grid%20%E2%80%94%20typically%20time%20on%20one%20axis%20and%20cases%20on%20the%20other%2C%20with%20dot%20colour%20or%20size%20&eyebrow=Glossary Dotted chart A dotted chart is a process-mining visualisation that plots every event in a log as a dot on a 2D grid — typically time on one axis and cases on the other, with dot colour or size encoding activity ty https://www.stride.page/glossary/dual-track-agile https://www.stride.page/api/og?title=Dual-track%20agile&subtitle=Dual-track%20agile%20(sometimes%20called%20dual-track%20discovery%20and%20delivery)%20is%20a%20product-development%20model%2C%20codified%20by%20Marty%20Cagan%20and%20Jeff%20Patton%2C%20that%20runs%20two%20parallel%20workstreams%3A%20a&eyebrow=Glossary Dual-track agile Dual-track agile (sometimes called dual-track discovery and delivery) is a product-development model, codified by Marty Cagan and Jeff Patton, that runs two parallel workstreams: a discovery track tha https://www.stride.page/glossary/dunbars-number https://www.stride.page/api/og?title=Dunbar's%20number&subtitle=Dunbar's%20number%2C%20proposed%20by%20anthropologist%20Robin%20Dunbar%20in%20the%201990s%2C%20is%20a%20cognitive%20limit%20on%20the%20number%20of%20stable%20social%20relationships%20a%20human%20can%20maintain%20%E2%80%94%20approximately%20150%20fo&eyebrow=Glossary Dunbar's number Dunbar's number, proposed by anthropologist Robin Dunbar in the 1990s, is a cognitive limit on the number of stable social relationships a human can maintain — approximately 150 for casual acquaintanc https://www.stride.page/glossary/edge-function https://www.stride.page/api/og?title=Edge%20function&subtitle=An%20edge%20function%20executes%20at%20the%20CDN's%20edge%20locations%20close%20to%20the%20user%20%E2%80%94%20typically%20with%20sub-millisecond%20cold%20starts%20(V8%20isolates)%20and%20~10-50ms%20latency%20advantage%20vs%20origin-region%20f&eyebrow=Glossary Edge function An edge function executes at the CDN's edge locations close to the user — typically with sub-millisecond cold starts (V8 isolates) and ~10-50ms latency advantage vs origin-region functions. Examples: https://www.stride.page/glossary/embedding-vector https://www.stride.page/api/og?title=Embedding%20vector&subtitle=An%20embedding%20vector%20is%20a%20numerical%20representation%20of%20a%20piece%20of%20content%20(text%2C%20image%2C%20audio)%20as%20a%20fixed-length%20vector%20%E2%80%94%20typically%20384%20to%203072%20dimensions%20%E2%80%94%20produced%20by%20a%20neural%20netw&eyebrow=Glossary Embedding vector An embedding vector is a numerical representation of a piece of content (text, image, audio) as a fixed-length vector — typically 384 to 3072 dimensions — produced by a neural network trained so that https://www.stride.page/glossary/emotional-exhaustion https://www.stride.page/api/og?title=Emotional%20exhaustion&subtitle=Emotional%20exhaustion%20is%20the%20first%20dimension%20of%20burnout%20in%20the%20Maslach%20framework%3A%20the%20chronic%20depletion%20of%20emotional%20and%20physical%20resources%20from%20sustained%20work%20demand.%20It%20is%20typical&eyebrow=Glossary Emotional exhaustion Emotional exhaustion is the first dimension of burnout in the Maslach framework: the chronic depletion of emotional and physical resources from sustained work demand. It is typically the dimension tha https://www.stride.page/glossary/enabler-epic https://www.stride.page/api/og?title=Enabler%20epic&subtitle=An%20enabler%20epic%20is%20the%20portfolio-level%20version%20of%20an%20enabler%20story%20%E2%80%94%20a%20large%20infrastructure%2C%20architecture%2C%20or%20exploration%20investment%20that%20spans%20multiple%20PIs%20and%20provides%20foundation&eyebrow=Glossary Enabler epic An enabler epic is the portfolio-level version of an enabler story — a large infrastructure, architecture, or exploration investment that spans multiple PIs and provides foundation for business epics. https://www.stride.page/glossary/enabler-story https://www.stride.page/api/og?title=Enabler%20story&subtitle=An%20enabler%20story%20is%20a%20SAFe%20story%20that%20delivers%20infrastructure%2C%20architecture%2C%20exploration%2C%20or%20compliance%20work%20needed%20to%20support%20future%20business%20value%20%E2%80%94%20not%20directly%20user-facing%2C%20but&eyebrow=Glossary Enabler story An enabler story is a SAFe story that delivers infrastructure, architecture, exploration, or compliance work needed to support future business value — not directly user-facing, but tracked and planned https://www.stride.page/glossary/e2e-testing https://www.stride.page/api/og?title=End-to-end%20testing&subtitle=End-to-end%20(E2E)%20tests%20exercise%20an%20entire%20user%20journey%20across%20the%20full%20stack%20%E2%80%94%20UI%2C%20API%2C%20database%2C%20external%20services%20%E2%80%94%20as%20a%20real%20user%20would.%20The%20dominant%20tools%20are%20Playwright%2C%20Cypre&eyebrow=Glossary End-to-end testing End-to-end (E2E) tests exercise an entire user journey across the full stack — UI, API, database, external services — as a real user would. The dominant tools are Playwright, Cypress, and Selenium for https://www.stride.page/glossary/engineering-ladder https://www.stride.page/api/og?title=Engineering%20ladder&subtitle=An%20engineering%20ladder%20is%20a%20documented%20framework%20defining%20the%20levels%2C%20expectations%2C%20and%20progression%20criteria%20for%20engineering%20roles%20at%20an%20organisation.%20Typical%20ladders%20span%206-10%20leve&eyebrow=Glossary Engineering ladder An engineering ladder is a documented framework defining the levels, expectations, and progression criteria for engineering roles at an organisation. Typical ladders span 6-10 levels from junior engin https://www.stride.page/glossary/error-budget https://www.stride.page/api/og?title=Error%20budget&subtitle=An%20error%20budget%20is%20the%20allowable%20reliability%20gap%20between%20the%20SLA%20(customer%20contract)%20and%20the%20SLO%20(operational%20target).%20If%20your%20SLO%20is%2099.9%25%20and%20you're%20meeting%2099.95%25%2C%20you%20have%20a%200.&eyebrow=Glossary Error budget An error budget is the allowable reliability gap between the SLA (customer contract) and the SLO (operational target). If your SLO is 99.9% and you're meeting 99.95%, you have a 0.05% error budget to https://www.stride.page/glossary/event-log https://www.stride.page/api/og?title=Event%20log&subtitle=An%20event%20log%20is%20the%20chronological%20record%20of%20activities%20executed%20in%20a%20process%2C%20structured%20so%20each%20row%20represents%20one%20event%20(case%20ID%2C%20activity%20name%2C%20timestamp%2C%20optional%20resource).%20Pr&eyebrow=Glossary Event log An event log is the chronological record of activities executed in a process, structured so each row represents one event (case ID, activity name, timestamp, optional resource). Process mining algorit https://www.stride.page/glossary/event-sourcing https://www.stride.page/api/og?title=Event%20sourcing&subtitle=Event%20sourcing%20is%20a%20persistence%20pattern%20that%20stores%20every%20state%20change%20as%20an%20immutable%20event%20in%20an%20append-only%20log.%20The%20current%20state%20of%20an%20entity%20is%20derived%20by%20replaying%20its%20event&eyebrow=Glossary Event sourcing Event sourcing is a persistence pattern that stores every state change as an immutable event in an append-only log. The current state of an entity is derived by replaying its events. Reading is fast b https://www.stride.page/glossary/event-storming https://www.stride.page/api/og?title=Event%20storming&subtitle=Event%20storming%20is%20a%20collaborative%20domain-discovery%20workshop%20technique%20created%20by%20Alberto%20Brandolini%20around%202013.%20Participants%20%E2%80%94%20engineers%2C%20product%2C%20domain%20experts%20%E2%80%94%20write%20domain%20ev&eyebrow=Glossary Event storming Event storming is a collaborative domain-discovery workshop technique created by Alberto Brandolini around 2013. Participants — engineers, product, domain experts — write domain events (past-tense bus https://www.stride.page/glossary/event-driven-architecture https://www.stride.page/api/og?title=Event-driven%20architecture&subtitle=Event-driven%20architecture%20is%20the%20design%20pattern%20where%20services%20communicate%20by%20emitting%20and%20consuming%20events%20rather%20than%20by%20direct%20synchronous%20calls.%20A%20service%20emits%20an%20event%20(an%20im&eyebrow=Glossary Event-driven architecture Event-driven architecture is the design pattern where services communicate by emitting and consuming events rather than by direct synchronous calls. A service emits an event (an immutable fact about s https://www.stride.page/glossary/evolutionary-architecture https://www.stride.page/api/og?title=Evolutionary%20architecture&subtitle=Evolutionary%20architecture%20is%20the%20design%20approach%20that%20explicitly%20plans%20for%20architectural%20change%20over%20time%20%E2%80%94%20building%20in%20fitness%20functions%2C%20modular%20boundaries%2C%20and%20incremental%20migra&eyebrow=Glossary Evolutionary architecture Evolutionary architecture is the design approach that explicitly plans for architectural change over time — building in fitness functions, modular boundaries, and incremental migration paths so the ar https://www.stride.page/glossary/exception-path https://www.stride.page/api/og?title=Exception%20path&subtitle=An%20exception%20path%20handles%20a%20deviation%20from%20the%20happy%20path%20%E2%80%94%20a%20validation%20failure%2C%20a%20missing%20input%2C%20an%20escalation%2C%20a%20customer%20dispute.%20Exception%20paths%20are%20necessary%20by%20design%20(some%20&eyebrow=Glossary Exception path An exception path handles a deviation from the happy path — a validation failure, a missing input, an escalation, a customer dispute. Exception paths are necessary by design (some cases really are exc https://www.stride.page/glossary/exploratory-testing https://www.stride.page/api/og?title=Exploratory%20testing&subtitle=Exploratory%20testing%20is%20a%20structured%20but%20unscripted%20form%20of%20manual%20testing%20where%20a%20tester%20simultaneously%20designs%20and%20executes%20tests%2C%20using%20their%20understanding%20of%20the%20product%20to%20prob&eyebrow=Glossary Exploratory testing Exploratory testing is a structured but unscripted form of manual testing where a tester simultaneously designs and executes tests, using their understanding of the product to probe for failures. The https://www.stride.page/glossary/fault-tolerance https://www.stride.page/api/og?title=Fault%20tolerance&subtitle=Fault%20tolerance%20is%20the%20property%20of%20a%20system%20to%20continue%20operating%2C%20possibly%20in%20a%20degraded%20state%2C%20when%20one%20or%20more%20of%20its%20components%20fail.%20A%20fault-tolerant%20system%20has%20redundancy%20at%20&eyebrow=Glossary Fault tolerance Fault tolerance is the property of a system to continue operating, possibly in a degraded state, when one or more of its components fail. A fault-tolerant system has redundancy at every layer where fa https://www.stride.page/glossary/feature-branch https://www.stride.page/api/og?title=Feature%20branch&subtitle=A%20feature%20branch%20is%20a%20Git%20branch%20that%20diverges%20from%20the%20main%20line%20for%20the%20duration%20of%20a%20single%20feature's%20development%2C%20with%20all%20that%20work%20isolated%20from%20main%20until%20the%20feature%20is%20com&eyebrow=Glossary Feature branch A feature branch is a Git branch that diverges from the main line for the duration of a single feature's development, with all that work isolated from main until the feature is complete and merged via https://www.stride.page/glossary/feature-flag https://www.stride.page/api/og?title=Feature%20flag&subtitle=A%20feature%20flag%20is%20a%20runtime%20toggle%20that%20gates%20whether%20a%20code%20path%20is%20active.%20Flags%20decouple%20deployment%20(ship%20the%20code%20dark)%20from%20release%20(turn%20the%20flag%20on%20for%20some%2Fall%20users)%20and%20e&eyebrow=Glossary Feature flag A feature flag is a runtime toggle that gates whether a code path is active. Flags decouple deployment (ship the code dark) from release (turn the flag on for some/all users) and enable instant rollba https://www.stride.page/glossary/few-shot-prompting https://www.stride.page/api/og?title=Few-shot%20prompting&subtitle=Few-shot%20prompting%20provides%20the%20model%20with%20example%20input-output%20pairs%20in%20the%20prompt%20to%20demonstrate%20the%20desired%20pattern%20before%20asking%20it%20to%20handle%20the%20actual%20input.%20'Here%20are%203%20exam&eyebrow=Glossary Few-shot prompting Few-shot prompting provides the model with example input-output pairs in the prompt to demonstrate the desired pattern before asking it to handle the actual input. 'Here are 3 examples of how to class https://www.stride.page/glossary/fine-tuning https://www.stride.page/api/og?title=Fine-tuning&subtitle=Fine-tuning%20continues%20the%20training%20of%20a%20pre-trained%20LLM%20on%20a%20custom%20dataset%20%E2%80%94%20typically%20a%20few%20thousand%20to%20a%20few%20million%20examples%20%E2%80%94%20to%20adapt%20its%20behaviour%20to%20a%20specific%20domain%2C%20task&eyebrow=Glossary Fine-tuning Fine-tuning continues the training of a pre-trained LLM on a custom dataset — typically a few thousand to a few million examples — to adapt its behaviour to a specific domain, task, or output style. T https://www.stride.page/glossary/five-whys https://www.stride.page/api/og?title=Five%20whys&subtitle=Five%20Whys%20is%20a%20root-cause-analysis%20technique%3A%20ask%20'why%3F'%20five%20times%20in%20a%20row%20(or%20until%20the%20answer%20becomes%20systemic%20rather%20than%20situational)%20to%20find%20the%20underlying%20cause%20of%20a%20proble&eyebrow=Glossary Five whys Five Whys is a root-cause-analysis technique: ask 'why?' five times in a row (or until the answer becomes systemic rather than situational) to find the underlying cause of a problem. Popularised by To https://www.stride.page/glossary/flaky-test https://www.stride.page/api/og?title=Flaky%20test&subtitle=A%20flaky%20test%20is%20one%20that%20sometimes%20passes%20and%20sometimes%20fails%20without%20any%20code%20change%20%E2%80%94%20typically%20caused%20by%20timing%20dependencies%2C%20shared%20state%2C%20network%2Fexternal-system%20reliance%2C%20or%20&eyebrow=Glossary Flaky test A flaky test is one that sometimes passes and sometimes fails without any code change — typically caused by timing dependencies, shared state, network/external-system reliance, or race conditions. Fla https://www.stride.page/glossary/flow-efficiency https://www.stride.page/api/og?title=Flow%20efficiency&subtitle=Flow%20efficiency%20is%20the%20ratio%20of%20value-add%20time%20to%20total%20elapsed%20time%20for%20a%20case%20%E2%80%94%20typically%20expressed%20as%20a%20percentage.%20A%20case%20that%20took%205%20days%20end-to-end%20but%20only%204%20hours%20of%20actual&eyebrow=Glossary Flow efficiency Flow efficiency is the ratio of value-add time to total elapsed time for a case — typically expressed as a percentage. A case that took 5 days end-to-end but only 4 hours of actual work has 10% flow e https://www.stride.page/glossary/golden-signals https://www.stride.page/api/og?title=Four%20golden%20signals&subtitle=The%20four%20golden%20signals%20%E2%80%94%20latency%2C%20traffic%2C%20errors%2C%20saturation%20%E2%80%94%20are%20the%20minimum%20monitoring%20set%20Google%20SRE%20recommends%20for%20any%20user-facing%20service.%20Together%20they%20cover%20the%20questions&eyebrow=Glossary Four golden signals The four golden signals — latency, traffic, errors, saturation — are the minimum monitoring set Google SRE recommends for any user-facing service. Together they cover the questions 'is the service res https://www.stride.page/glossary/four-key-metrics https://www.stride.page/api/og?title=Four%20key%20metrics&subtitle=The%20four%20key%20metrics%20are%20the%20DORA%20framework%20for%20measuring%20software-delivery%20performance%3A%20deployment%20frequency%2C%20lead%20time%20for%20changes%2C%20mean%20time%20to%20restore%2C%20and%20change%20failure%20rate.&eyebrow=Glossary Four key metrics The four key metrics are the DORA framework for measuring software-delivery performance: deployment frequency, lead time for changes, mean time to restore, and change failure rate. Together they form https://www.stride.page/glossary/function-as-a-service https://www.stride.page/api/og?title=Function%20as%20a%20service%20(FaaS)&subtitle=Function%20as%20a%20Service%20is%20the%20serverless%20compute%20model%20where%20the%20deployment%20unit%20is%20a%20single%20function%20with%20a%20defined%20entry%20point%20%E2%80%94%20the%20provider%20invokes%20it%20in%20response%20to%20events%20(HTT&eyebrow=Glossary Function as a service (FaaS) Function as a Service is the serverless compute model where the deployment unit is a single function with a defined entry point — the provider invokes it in response to events (HTTP request, queue mes https://www.stride.page/glossary/function-calling https://www.stride.page/api/og?title=Function%20calling&subtitle=Function%20calling%20lets%20an%20LLM%20invoke%20external%20tools%20by%20emitting%20a%20structured%20request%20matching%20a%20function%20specification%20provided%20in%20the%20prompt.%20The%20model%20decides%20when%20to%20call%20a%20funct&eyebrow=Glossary Function calling Function calling lets an LLM invoke external tools by emitting a structured request matching a function specification provided in the prompt. The model decides when to call a function, with what argum https://www.stride.page/glossary/function-spec https://www.stride.page/api/og?title=Function%20spec%20(tool%20definition)&subtitle=A%20function%20spec%20is%20the%20structured%20declaration%20that%20tells%20an%20LLM%20what%20a%20tool%20does%2C%20what%20arguments%20it%20takes%2C%20and%20what%20it%20returns%20%E2%80%94%20typically%20a%20JSON%20Schema%20describing%20parameters%20with%20&eyebrow=Glossary Function spec (tool definition) A function spec is the structured declaration that tells an LLM what a tool does, what arguments it takes, and what it returns — typically a JSON Schema describing parameters with name, type, and desc https://www.stride.page/glossary/game-day https://www.stride.page/api/og?title=Game%20day&subtitle=A%20game%20day%20is%20a%20scheduled%20exercise%20in%20which%20an%20engineering%20team%20intentionally%20exercises%20a%20failure%20scenario%20in%20a%20live%20or%20production-like%20environment%20%E2%80%94%20pulling%20a%20database%2C%20killing%20a%20&eyebrow=Glossary Game day A game day is a scheduled exercise in which an engineering team intentionally exercises a failure scenario in a live or production-like environment — pulling a database, killing a region, exhausting a https://www.stride.page/glossary/gherkin https://www.stride.page/api/og?title=Gherkin&subtitle=Gherkin%20is%20a%20structured%20plain-English%20DSL%20for%20writing%20executable%20acceptance%20tests%2C%20using%20the%20Given%20%2F%20When%20%2F%20Then%20format.%20It%20originated%20with%20Cucumber%20and%20is%20now%20used%20across%20BDD%20fram&eyebrow=Glossary Gherkin Gherkin is a structured plain-English DSL for writing executable acceptance tests, using the Given / When / Then format. It originated with Cucumber and is now used across BDD frameworks (SpecFlow, Be https://www.stride.page/glossary/gitflow https://www.stride.page/api/og?title=Gitflow&subtitle=Gitflow%20is%20a%20branching%20model%20with%20long-lived%20develop%20and%20main%20branches%2C%20plus%20feature%2C%20release%2C%20and%20hotfix%20branches.%20It%20was%20designed%20for%20software%20with%20discrete%20versioned%20releases%20(t&eyebrow=Glossary Gitflow Gitflow is a branching model with long-lived develop and main branches, plus feature, release, and hotfix branches. It was designed for software with discrete versioned releases (think shrink-wrapped https://www.stride.page/glossary/gitops https://www.stride.page/api/og?title=GitOps&subtitle=GitOps%20is%20a%20deployment%20methodology%2C%20coined%20by%20Weaveworks%20in%202017%2C%20in%20which%20the%20desired%20state%20of%20infrastructure%20and%20applications%20is%20declared%20in%20Git%20and%20reconciled%20to%20running%20systems&eyebrow=Glossary GitOps GitOps is a deployment methodology, coined by Weaveworks in 2017, in which the desired state of infrastructure and applications is declared in Git and reconciled to running systems by an automated age https://www.stride.page/glossary/graceful-degradation https://www.stride.page/api/og?title=Graceful%20degradation&subtitle=Graceful%20degradation%20is%20the%20design%20property%20of%20a%20system%20that%2C%20when%20a%20dependency%20fails%20or%20saturates%2C%20returns%20reduced%20functionality%20rather%20than%20no%20functionality.%20A%20graceful-degradati&eyebrow=Glossary Graceful degradation Graceful degradation is the design property of a system that, when a dependency fails or saturates, returns reduced functionality rather than no functionality. A graceful-degradation example: a produc https://www.stride.page/glossary/grounding https://www.stride.page/api/og?title=Grounding%20(LLM)&subtitle=Grounding%20provides%20an%20LLM%20with%20authoritative%20context%20%E2%80%94%20retrieved%20documents%2C%20structured%20data%2C%20real-time%20API%20responses%20%E2%80%94%20and%20instructs%20it%20to%20base%20its%20response%20on%20that%20context%20rather%20&eyebrow=Glossary Grounding (LLM) Grounding provides an LLM with authoritative context — retrieved documents, structured data, real-time API responses — and instructs it to base its response on that context rather than its pre-trained https://www.stride.page/glossary/guardrails https://www.stride.page/api/og?title=Guardrails&subtitle=Guardrails%20are%20the%20policies%20that%20constrain%20investment%20decisions%20within%20a%20Lean%20Budget%20%E2%80%94%20capacity%20allocation%20across%20horizons%20(sustaining%20vs%20growth%20vs%20innovation)%2C%20epic-approval%20thres&eyebrow=Glossary Guardrails Guardrails are the policies that constrain investment decisions within a Lean Budget — capacity allocation across horizons (sustaining vs growth vs innovation), epic-approval thresholds, and continuou https://www.stride.page/glossary/hallucination https://www.stride.page/api/og?title=Hallucination&subtitle=Hallucination%20is%20the%20LLM%20failure%20mode%20in%20which%20the%20model%20generates%20content%20that%20is%20plausible-sounding%20but%20factually%20wrong%20%E2%80%94%20invented%20citations%2C%20fabricated%20quotes%2C%20non-existent%20func&eyebrow=Glossary Hallucination Hallucination is the LLM failure mode in which the model generates content that is plausible-sounding but factually wrong — invented citations, fabricated quotes, non-existent functions, misremembered https://www.stride.page/glossary/happy-path https://www.stride.page/api/og?title=Happy%20path&subtitle=The%20happy%20path%20is%20the%20variant%20of%20a%20process%20in%20which%20everything%20goes%20as%20intended%20%E2%80%94%20no%20exceptions%2C%20no%20rework%2C%20no%20manual%20interventions.%20In%20process%20mining%2C%20the%20happy%20path%20is%20usually%20th&eyebrow=Glossary Happy path The happy path is the variant of a process in which everything goes as intended — no exceptions, no rework, no manual interventions. In process mining, the happy path is usually the most frequent vari https://www.stride.page/glossary/hexagonal-architecture https://www.stride.page/api/og?title=Hexagonal%20architecture&subtitle=Hexagonal%20architecture%20(also%20called%20ports%20and%20adapters)%2C%20introduced%20by%20Alistair%20Cockburn%20in%202005%2C%20structures%20an%20application%20so%20the%20core%20domain%20logic%20depends%20only%20on%20abstract%20'ports&eyebrow=Glossary Hexagonal architecture Hexagonal architecture (also called ports and adapters), introduced by Alistair Cockburn in 2005, structures an application so the core domain logic depends only on abstract 'ports' — and concrete ada https://www.stride.page/glossary/high-availability https://www.stride.page/api/og?title=High%20availability&subtitle=High%20availability%20is%20the%20design%20objective%20of%20keeping%20a%20system%20continuously%20operational%20for%20a%20defined%20uptime%20target%20%E2%80%94%20typically%20expressed%20in%20nines%20(99.9%25%20%3D%20~8.7%20hours%2Fyear%20downtime%2C&eyebrow=Glossary High availability High availability is the design objective of keeping a system continuously operational for a defined uptime target — typically expressed in nines (99.9% = ~8.7 hours/year downtime, 99.99% = ~52 minute https://www.stride.page/glossary/horizontal-autoscaling https://www.stride.page/api/og?title=Horizontal%20autoscaling&subtitle=Horizontal%20autoscaling%20adds%20or%20removes%20service%20instances%20in%20response%20to%20load%20%E2%80%94%20typically%20CPU%2C%20memory%2C%20or%20a%20custom%20metric%20like%20queue%20depth.%20In%20Kubernetes%20this%20is%20the%20HorizontalPodAu&eyebrow=Glossary Horizontal autoscaling Horizontal autoscaling adds or removes service instances in response to load — typically CPU, memory, or a custom metric like queue depth. In Kubernetes this is the HorizontalPodAutoscaler resource; o https://www.stride.page/glossary/safe-house-of-lean https://www.stride.page/api/og?title=House%20of%20Lean&subtitle=The%20House%20of%20Lean%20is%20SAFe's%20overarching%20values%20framework%2C%20depicted%20as%20a%20building%3A%20the%20roof%20is%20'value'%20(the%20goal)%2C%20the%20four%20pillars%20are%20respect-for-people-and-culture%2C%20flow%2C%20innovat&eyebrow=Glossary House of Lean The House of Lean is SAFe's overarching values framework, depicted as a building: the roof is 'value' (the goal), the four pillars are respect-for-people-and-culture, flow, innovation, and relentless https://www.stride.page/glossary/hydration https://www.stride.page/api/og?title=Hydration&subtitle=Hydration%20is%20the%20process%20of%20attaching%20JavaScript%20event%20handlers%20and%20state%20to%20server-rendered%20HTML%20on%20the%20client%20%E2%80%94%20the%20page%20is%20visible%20immediately%20(fast%20FCP)%20but%20interaction%20works%20o&eyebrow=Glossary Hydration Hydration is the process of attaching JavaScript event handlers and state to server-rendered HTML on the client — the page is visible immediately (fast FCP) but interaction works only after hydration https://www.stride.page/glossary/idempotency https://www.stride.page/api/og?title=Idempotency&subtitle=An%20operation%20is%20idempotent%20if%20calling%20it%20multiple%20times%20has%20the%20same%20effect%20as%20calling%20it%20once.%20In%20distributed%20systems%2C%20idempotent%20operations%20let%20you%20retry%20on%20network%20failure%20witho&eyebrow=Glossary Idempotency An operation is idempotent if calling it multiple times has the same effect as calling it once. In distributed systems, idempotent operations let you retry on network failure without duplicating side https://www.stride.page/glossary/immutable-infrastructure https://www.stride.page/api/og?title=Immutable%20infrastructure&subtitle=Immutable%20infrastructure%20is%20the%20operational%20pattern%20where%20servers%20are%20never%20modified%20after%20deployment%20%E2%80%94%20to%20change%20configuration%20or%20apply%20patches%2C%20a%20new%20image%20is%20built%20and%20the%20old%20i&eyebrow=Glossary Immutable infrastructure Immutable infrastructure is the operational pattern where servers are never modified after deployment — to change configuration or apply patches, a new image is built and the old instances are replace https://www.stride.page/glossary/incident-commander https://www.stride.page/api/og?title=Incident%20commander&subtitle=The%20incident%20commander%20is%20the%20single%20individual%20with%20end-to-end%20authority%20during%20a%20production%20incident%20%E2%80%94%20coordinating%20responders%2C%20deciding%20on%20mitigation%20actions%2C%20communicating%20to%20s&eyebrow=Glossary Incident commander The incident commander is the single individual with end-to-end authority during a production incident — coordinating responders, deciding on mitigation actions, communicating to stakeholders, and dec https://www.stride.page/glossary/incremental-static-regeneration https://www.stride.page/api/og?title=Incremental%20static%20regeneration%20(ISR)&subtitle=Incremental%20static%20regeneration%20is%20the%20hybrid%20where%20pages%20are%20pre-rendered%20to%20static%20HTML%20but%20the%20framework%20refreshes%20them%20in%20the%20background%20after%20a%20defined%20revalidation%20period%20%E2%80%94%20c&eyebrow=Glossary Incremental static regeneration (ISR) Incremental static regeneration is the hybrid where pages are pre-rendered to static HTML but the framework refreshes them in the background after a defined revalidation period — combining SSG's first https://www.stride.page/glossary/inference-cost https://www.stride.page/api/og?title=Inference%20cost&subtitle=Inference%20cost%20is%20the%20per-request%20economic%20cost%20of%20running%20an%20LLM%20%E2%80%94%20typically%20billed%20per%20million%20input%20tokens%20and%20per%20million%20output%20tokens%2C%20with%20output%20tokens%20often%203-5x%20more%20expe&eyebrow=Glossary Inference cost Inference cost is the per-request economic cost of running an LLM — typically billed per million input tokens and per million output tokens, with output tokens often 3-5x more expensive than input. At https://www.stride.page/glossary/infrastructure-as-code https://www.stride.page/api/og?title=Infrastructure%20as%20code&subtitle=Infrastructure%20as%20code%20(IaC)%20is%20the%20practice%20of%20defining%20and%20provisioning%20infrastructure%20%E2%80%94%20servers%2C%20networks%2C%20databases%2C%20IAM%20policies%20%E2%80%94%20through%20machine-readable%20declaration%20files%20r&eyebrow=Glossary Infrastructure as code Infrastructure as code (IaC) is the practice of defining and provisioning infrastructure — servers, networks, databases, IAM policies — through machine-readable declaration files rather than manual co https://www.stride.page/glossary/ingress-controller https://www.stride.page/api/og?title=Ingress%20controller&subtitle=An%20ingress%20controller%20is%20the%20Kubernetes%20component%20that%20translates%20Ingress%20resource%20definitions%20into%20actual%20layer-7%20routing%20%E2%80%94%20typically%20backed%20by%20Nginx%2C%20Envoy%2C%20Traefik%2C%20or%20HAProxy.%20&eyebrow=Glossary Ingress controller An ingress controller is the Kubernetes component that translates Ingress resource definitions into actual layer-7 routing — typically backed by Nginx, Envoy, Traefik, or HAProxy. It terminates TLS, a https://www.stride.page/glossary/inspect-and-adapt https://www.stride.page/api/og?title=Inspect%20%26%20adapt%20workshop&subtitle=Inspect%20%26%20Adapt%20is%20the%20SAFe%20event%20at%20the%20end%20of%20each%20Program%20Increment%20in%20which%20the%20ART%20reviews%20quantitative%20results%20(PI%20Objectives%20achieved%2C%20predictability%20measure%2C%20business%20value&eyebrow=Glossary Inspect & adapt workshop Inspect & Adapt is the SAFe event at the end of each Program Increment in which the ART reviews quantitative results (PI Objectives achieved, predictability measure, business value scoring), demos the https://www.stride.page/glossary/integration-test https://www.stride.page/api/og?title=Integration%20test&subtitle=An%20integration%20test%20verifies%20that%20multiple%20components%20work%20together%20correctly%20%E2%80%94%20a%20service%20hitting%20a%20real%20database%2C%20two%20microservices%20communicating%2C%20a%20frontend%20talking%20to%20a%20real%20API&eyebrow=Glossary Integration test An integration test verifies that multiple components work together correctly — a service hitting a real database, two microservices communicating, a frontend talking to a real API. Integration tests https://www.stride.page/glossary/inversion-of-control https://www.stride.page/api/og?title=Inversion%20of%20control&subtitle=Inversion%20of%20control%20is%20the%20design%20principle%20that%20a%20component%20should%20not%20control%20the%20flow%20of%20its%20dependencies%20%E2%80%94%20instead%2C%20the%20framework%20or%20container%20controls%20flow%20and%20passes%20resourc&eyebrow=Glossary Inversion of control Inversion of control is the design principle that a component should not control the flow of its dependencies — instead, the framework or container controls flow and passes resources to the component https://www.stride.page/glossary/invest-criteria https://www.stride.page/api/og?title=INVEST%20criteria&subtitle=INVEST%20is%20a%20mnemonic%20%E2%80%94%20coined%20by%20Bill%20Wake%20in%202003%20%E2%80%94%20for%20the%20qualities%20of%20a%20good%20user%20story%3A%20Independent%20(can%20be%20worked%20on%20without%20depending%20on%20other%20stories)%2C%20Negotiable%20(not%20a%20ri&eyebrow=Glossary INVEST criteria INVEST is a mnemonic — coined by Bill Wake in 2003 — for the qualities of a good user story: Independent (can be worked on without depending on other stories), Negotiable (not a rigid contract, room t https://www.stride.page/glossary/island-architecture https://www.stride.page/api/og?title=Island%20architecture&subtitle=Island%20architecture%20is%20the%20frontend%20pattern%20where%20most%20of%20a%20page%20is%20static%20server-rendered%20HTML%20with%20no%20client%20JavaScript%2C%20and%20only%20the%20interactive%20components%20(the%20'islands')%20hydra&eyebrow=Glossary Island architecture Island architecture is the frontend pattern where most of a page is static server-rendered HTML with no client JavaScript, and only the interactive components (the 'islands') hydrate independently. Fr https://www.stride.page/glossary/iteration-planning https://www.stride.page/api/og?title=Iteration%20planning&subtitle=Iteration%20planning%20is%20the%20team-level%20event%20at%20the%20start%20of%20each%20SAFe%20iteration%20(typically%202%20weeks)%20where%20the%20team%20selects%20stories%20from%20its%20backlog%20to%20commit%20to%2C%20breaks%20them%20into%20ta&eyebrow=Glossary Iteration planning Iteration planning is the team-level event at the start of each SAFe iteration (typically 2 weeks) where the team selects stories from its backlog to commit to, breaks them into tasks, and confirms te https://www.stride.page/glossary/iteration-retrospective https://www.stride.page/api/og?title=Iteration%20retrospective&subtitle=The%20iteration%20retrospective%20is%20the%20team-level%20event%20at%20iteration%20end%20where%20the%20team%20inspects%20how%20it%20worked%20together%20%E2%80%94%20process%2C%20collaboration%2C%20technical%20practices%20%E2%80%94%20and%20commits%20to%20s&eyebrow=Glossary Iteration retrospective The iteration retrospective is the team-level event at iteration end where the team inspects how it worked together — process, collaboration, technical practices — and commits to specific changes for https://www.stride.page/glossary/iteration-review https://www.stride.page/api/og?title=Iteration%20review&subtitle=The%20iteration%20review%20is%20the%20team-level%20demo%20at%20the%20end%20of%20each%20iteration%20in%20which%20completed%20stories%20are%20shown%20to%20the%20team%20and%20to%20direct%20stakeholders.%20It's%20a%20working%20session%2C%20not%20a%20&eyebrow=Glossary Iteration review The iteration review is the team-level demo at the end of each iteration in which completed stories are shown to the team and to direct stakeholders. It's a working session, not a presentation: the te https://www.stride.page/glossary/jobs-to-be-done https://www.stride.page/api/og?title=Jobs-to-be-done&subtitle=Jobs-to-be-done%20(JTBD)%20is%20a%20product-discovery%20framework%2C%20popularised%20by%20Clayton%20Christensen%2C%20that%20frames%20features%20in%20terms%20of%20the%20'job'%20a%20customer%20is%20hiring%20the%20product%20to%20do%20%E2%80%94%20the&eyebrow=Glossary Jobs-to-be-done Jobs-to-be-done (JTBD) is a product-discovery framework, popularised by Clayton Christensen, that frames features in terms of the 'job' a customer is hiring the product to do — the underlying outcome https://www.stride.page/glossary/json-mode https://www.stride.page/api/og?title=JSON%20mode&subtitle=JSON%20mode%20is%20an%20LLM%20API%20parameter%20that%20guarantees%20the%20response%20is%20valid%20JSON%20%E2%80%94%20even%20when%20no%20specific%20schema%20is%20provided.%20It's%20the%20lighter%20version%20of%20structured%20output%3A%20the%20response&eyebrow=Glossary JSON mode JSON mode is an LLM API parameter that guarantees the response is valid JSON — even when no specific schema is provided. It's the lighter version of structured output: the response will parse, but the https://www.stride.page/glossary/kanban https://www.stride.page/api/og?title=Kanban&subtitle=Kanban%20is%20a%20flow-based%20work-management%20method%2C%20adapted%20to%20software%20by%20David%20J.%20Anderson%20around%202007%20from%20the%20Toyota%20Production%20System.%20Work%20moves%20across%20a%20board%20(Backlog%20%E2%86%92%20In%20Progr&eyebrow=Glossary Kanban Kanban is a flow-based work-management method, adapted to software by David J. Anderson around 2007 from the Toyota Production System. Work moves across a board (Backlog → In Progress → Review → Done) https://www.stride.page/glossary/kano-model https://www.stride.page/api/og?title=Kano%20model&subtitle=The%20Kano%20model%20(Noriaki%20Kano%2C%201984)%20categorises%20product%20features%20by%20their%20non-linear%20relationship%20to%20customer%20satisfaction.%20Five%20categories%3A%20Basic%20(expected%3B%20absence%20dissatisfies%2C%20&eyebrow=Glossary Kano model The Kano model (Noriaki Kano, 1984) categorises product features by their non-linear relationship to customer satisfaction. Five categories: Basic (expected; absence dissatisfies, presence doesn't del https://www.stride.page/glossary/kappa-architecture https://www.stride.page/api/og?title=Kappa%20architecture&subtitle=Kappa%20architecture%20handles%20all%20data%20processing%20through%20a%20single%20streaming%20pipeline%20that%20can%20be%20replayed%20from%20the%20beginning%20of%20the%20log%20when%20computations%20need%20to%20be%20reprocessed.%20Elim&eyebrow=Glossary Kappa architecture Kappa architecture handles all data processing through a single streaming pipeline that can be replayed from the beginning of the log when computations need to be reprocessed. Eliminates the dual-pipe https://www.stride.page/glossary/karasek-demand-control https://www.stride.page/api/og?title=Karasek%20demand-control%20model&subtitle=The%20Karasek%20demand-control%20model%20is%20the%20dominant%20occupational-stress%20framework%2C%20developed%20by%20Robert%20Karasek%20in%201979%20and%20extended%20with%20T%C3%B6res%20Theorell%20in%201990.%20It%20frames%20psychologica&eyebrow=Glossary Karasek demand-control model The Karasek demand-control model is the dominant occupational-stress framework, developed by Robert Karasek in 1979 and extended with Töres Theorell in 1990. It frames psychological strain as the join https://www.stride.page/glossary/lambda-architecture https://www.stride.page/api/og?title=Lambda%20architecture&subtitle=Lambda%20architecture%20is%20the%20data-processing%20pattern%20that%20runs%20two%20parallel%20pipelines%3A%20a%20batch%20layer%20that%20computes%20complete%20views%20over%20all%20data%20with%20high%20latency%2C%20and%20a%20speed%20layer%20t&eyebrow=Glossary Lambda architecture Lambda architecture is the data-processing pattern that runs two parallel pipelines: a batch layer that computes complete views over all data with high latency, and a speed layer that computes increme https://www.stride.page/glossary/large-language-model https://www.stride.page/api/og?title=Large%20language%20model%20(LLM)&subtitle=A%20large%20language%20model%20is%20a%20neural%20network%20trained%20on%20enormous%20text%20corpora%20to%20predict%20the%20next%20token%20given%20preceding%20tokens%20%E2%80%94%20typically%20with%20billions%20to%20trillions%20of%20parameters.%20M&eyebrow=Glossary Large language model (LLM) A large language model is a neural network trained on enormous text corpora to predict the next token given preceding tokens — typically with billions to trillions of parameters. Modern LLMs (GPT-4, C https://www.stride.page/glossary/latency-percentile https://www.stride.page/api/og?title=Latency%20percentile&subtitle=A%20latency%20percentile%20(p50%2C%20p95%2C%20p99%2C%20p999)%20is%20the%20response%20time%20below%20which%20that%20share%20of%20requests%20completed.%20p99%20%3D%20500ms%20means%2099%25%20of%20requests%20finished%20in%20500ms%20or%20less%3B%20the%20slowe&eyebrow=Glossary Latency percentile A latency percentile (p50, p95, p99, p999) is the response time below which that share of requests completed. p99 = 500ms means 99% of requests finished in 500ms or less; the slowest 1% took longer. A https://www.stride.page/glossary/layered-architecture https://www.stride.page/api/og?title=Layered%20architecture&subtitle=Layered%20architecture%20organises%20an%20application%20into%20horizontal%20layers%20%E2%80%94%20typically%20presentation%2C%20business%20logic%2C%20data%20access%20%E2%80%94%20with%20each%20layer%20depending%20only%20on%20the%20layer%20below.%20The%20&eyebrow=Glossary Layered architecture Layered architecture organises an application into horizontal layers — typically presentation, business logic, data access — with each layer depending only on the layer below. The pattern is the most https://www.stride.page/glossary/lead-time https://www.stride.page/api/og?title=Lead%20time&subtitle=Lead%20time%20is%20the%20elapsed%20time%20from%20when%20work%20is%20requested%20(story%20created%2C%20ticket%20filed)%20to%20when%20it's%20delivered%20(deployed%20to%20production).%20It's%20a%20DORA%20metric%20measuring%20end-to-end%20del&eyebrow=Glossary Lead time Lead time is the elapsed time from when work is requested (story created, ticket filed) to when it's delivered (deployed to production). It's a DORA metric measuring end-to-end delivery flow — includi https://www.stride.page/glossary/lean-budget https://www.stride.page/api/og?title=Lean%20budget&subtitle=A%20Lean%20Budget%20is%20SAFe's%20value-stream-funded%20alternative%20to%20project-based%20budgeting.%20Each%20value%20stream%20gets%20a%20persistent%20annual%20budget%20envelope%3B%20the%20people%20inside%20it%20stay%20together%3B%20&eyebrow=Glossary Lean budget A Lean Budget is SAFe's value-stream-funded alternative to project-based budgeting. Each value stream gets a persistent annual budget envelope; the people inside it stay together; investment decisions https://www.stride.page/glossary/lean-portfolio-management https://www.stride.page/api/og?title=Lean%20portfolio%20management&subtitle=Lean%20Portfolio%20Management%20is%20SAFe's%20approach%20to%20aligning%20strategy%20and%20execution%20at%20the%20portfolio%20level%20%E2%80%94%20funding%20value%20streams%20(not%20projects)%2C%20managing%20portfolio%20flow%20through%20a%20Por&eyebrow=Glossary Lean portfolio management Lean Portfolio Management is SAFe's approach to aligning strategy and execution at the portfolio level — funding value streams (not projects), managing portfolio flow through a Portfolio Kanban, and g https://www.stride.page/glossary/lockfile https://www.stride.page/api/og?title=Lockfile&subtitle=A%20lockfile%20records%20the%20exact%20resolved%20version%20of%20every%20package%20in%20a%20dependency%20tree%20%E2%80%94%20direct%20and%20transitive%20%E2%80%94%20so%20any%20subsequent%20install%20reproduces%20the%20same%20versions.%20Examples%3A%20pack&eyebrow=Glossary Lockfile A lockfile records the exact resolved version of every package in a dependency tree — direct and transitive — so any subsequent install reproduces the same versions. Examples: package-lock.json, yarn. https://www.stride.page/glossary/lora-adapter https://www.stride.page/api/og?title=LoRA%20adapter&subtitle=LoRA%20(Low-Rank%20Adaptation)%20is%20a%20fine-tuning%20technique%20that%20updates%20only%20a%20small%20number%20of%20parameters%20in%20low-rank%20decomposition%20matrices%2C%20leaving%20the%20base%20model%20frozen.%20LoRA%20dramati&eyebrow=Glossary LoRA adapter LoRA (Low-Rank Adaptation) is a fine-tuning technique that updates only a small number of parameters in low-rank decomposition matrices, leaving the base model frozen. LoRA dramatically reduces traini https://www.stride.page/glossary/maslach-burnout-inventory https://www.stride.page/api/og?title=Maslach%20Burnout%20Inventory&subtitle=The%20Maslach%20Burnout%20Inventory%20(MBI)%20is%20the%20most-cited%20clinical%20instrument%20for%20measuring%20occupational%20burnout.%20Developed%20by%20Christina%20Maslach%20and%20Susan%20Jackson%20in%201981%2C%20it%20operation&eyebrow=Glossary Maslach Burnout Inventory The Maslach Burnout Inventory (MBI) is the most-cited clinical instrument for measuring occupational burnout. Developed by Christina Maslach and Susan Jackson in 1981, it operationalises burnout as a https://www.stride.page/glossary/mean-time-to-restore https://www.stride.page/api/og?title=Mean%20time%20to%20restore&subtitle=Mean%20time%20to%20restore%20(MTTR%2C%20also%20called%20'Time%20to%20Restore%20Service'%20in%20the%202024%20DORA%20report)%20is%20the%20average%20time%20between%20a%20production%20incident's%20detection%20and%20its%20resolution.%20It%20is%20t&eyebrow=Glossary Mean time to restore Mean time to restore (MTTR, also called 'Time to Restore Service' in the 2024 DORA report) is the average time between a production incident's detection and its resolution. It is the third DORA metric https://www.stride.page/glossary/micro-frontend https://www.stride.page/api/og?title=Micro-frontend&subtitle=A%20micro-frontend%20architecture%20decomposes%20a%20single%20web%20application%20into%20multiple%20independently%20developed%20and%20deployed%20frontend%20modules%20%E2%80%94%20each%20owned%20by%20a%20different%20team%20and%20integrate&eyebrow=Glossary Micro-frontend A micro-frontend architecture decomposes a single web application into multiple independently developed and deployed frontend modules — each owned by a different team and integrated at runtime (via Mo https://www.stride.page/glossary/microservices https://www.stride.page/api/og?title=Microservices&subtitle=Microservices%20is%20an%20architectural%20style%20where%20a%20single%20application%20is%20composed%20of%20many%20small%2C%20independently-deployable%20services%2C%20each%20owning%20its%20own%20data%20and%20communicating%20over%20the&eyebrow=Glossary Microservices Microservices is an architectural style where a single application is composed of many small, independently-deployable services, each owning its own data and communicating over the network. Services a https://www.stride.page/glossary/minimum-marketable-feature https://www.stride.page/api/og?title=Minimum%20marketable%20feature%20(MMF)&subtitle=A%20minimum%20marketable%20feature%20is%20the%20smallest%20increment%20of%20functionality%20that%20delivers%20real%20user%20value%20and%20could%20plausibly%20be%20released%20to%20customers%20as%20a%20standalone%20improvement.%20Unli&eyebrow=Glossary Minimum marketable feature (MMF) A minimum marketable feature is the smallest increment of functionality that delivers real user value and could plausibly be released to customers as a standalone improvement. Unlike an MVP (a learnin https://www.stride.page/glossary/minimum-viable-product https://www.stride.page/api/og?title=Minimum%20viable%20product%20(MVP)&subtitle=A%20minimum%20viable%20product%20is%20the%20smallest%20version%20of%20a%20product%20that%20lets%20the%20team%20test%20a%20specific%20hypothesis%20with%20real%20users%20%E2%80%94%20not%20a%20beta%2C%20not%20a%20stripped-down%20v1%2C%20but%20a%20deliberate%20e&eyebrow=Glossary Minimum viable product (MVP) A minimum viable product is the smallest version of a product that lets the team test a specific hypothesis with real users — not a beta, not a stripped-down v1, but a deliberate experiment whose only https://www.stride.page/glossary/mob-programming https://www.stride.page/api/og?title=Mob%20programming&subtitle=Mob%20programming%20is%20a%20practice%20where%20the%20entire%20team%20works%20on%20the%20same%20problem%20at%20the%20same%20time%2C%20on%20the%20same%20screen%2C%20with%20one%20person%20typing%20(the%20'driver')%20and%20the%20rest%20navigating.%20O&eyebrow=Glossary Mob programming Mob programming is a practice where the entire team works on the same problem at the same time, on the same screen, with one person typing (the 'driver') and the rest navigating. Originated at Hunter https://www.stride.page/glossary/mock-vs-stub https://www.stride.page/api/og?title=Mock%20vs%20stub&subtitle=A%20stub%20returns%20pre-defined%20responses%20to%20method%20calls%20without%20assertions%3B%20a%20mock%20additionally%20asserts%20that%20specific%20calls%20happened%20with%20specific%20arguments.%20Stubs%20answer%20'what%20does%20t&eyebrow=Glossary Mock vs stub A stub returns pre-defined responses to method calls without assertions; a mock additionally asserts that specific calls happened with specific arguments. Stubs answer 'what does the dependency return https://www.stride.page/glossary/model-context-protocol https://www.stride.page/api/og?title=Model%20Context%20Protocol%20(MCP)&subtitle=Model%20Context%20Protocol%20is%20the%20open%20standard%20introduced%20by%20Anthropic%20in%20late%202024%20for%20connecting%20LLM%20applications%20to%20external%20data%20sources%20and%20tools.%20MCP%20defines%20a%20uniform%20schema%20fo&eyebrow=Glossary Model Context Protocol (MCP) Model Context Protocol is the open standard introduced by Anthropic in late 2024 for connecting LLM applications to external data sources and tools. MCP defines a uniform schema for declaring tools, r https://www.stride.page/glossary/modular-monolith https://www.stride.page/api/og?title=Modular%20monolith&subtitle=A%20modular%20monolith%20is%20a%20single%20deployable%20application%20internally%20organised%20into%20well-defined%20modules%20with%20explicit%20boundaries%2C%20typed%20contracts%20between%20modules%2C%20and%20independent%20owne&eyebrow=Glossary Modular monolith A modular monolith is a single deployable application internally organised into well-defined modules with explicit boundaries, typed contracts between modules, and independent ownership. The pattern c https://www.stride.page/glossary/monorepo https://www.stride.page/api/og?title=Monorepo&subtitle=A%20monorepo%20is%20a%20version-control%20repository%20that%20contains%20many%20distinct%20projects%20(services%2C%20libraries%2C%20tools)%20with%20shared%20tooling%20and%20atomic%20cross-project%20changes.%20Adopters%20include%20&eyebrow=Glossary Monorepo A monorepo is a version-control repository that contains many distinct projects (services, libraries, tools) with shared tooling and atomic cross-project changes. Adopters include Google, Meta, and Ub https://www.stride.page/glossary/mttr https://www.stride.page/api/og?title=MTTR&subtitle=Mean%20Time%20To%20Recovery%20is%20the%20average%20elapsed%20time%20between%20an%20incident's%20detection%20and%20its%20resolution.%20It's%20one%20of%20the%20four%20DORA%20metrics%20(lead%20time%2C%20deploy%20frequency%2C%20change%20failure&eyebrow=Glossary MTTR Mean Time To Recovery is the average elapsed time between an incident's detection and its resolution. It's one of the four DORA metrics (lead time, deploy frequency, change failure rate, MTTR) and ind https://www.stride.page/glossary/multi-agent-system https://www.stride.page/api/og?title=Multi-agent%20system&subtitle=A%20multi-agent%20system%20uses%20multiple%20LLM-driven%20agents%20working%20together%20%E2%80%94%20typically%20with%20role%20specialisation%20(planner%2C%20executor%2C%20critic)%20or%20domain%20specialisation%20(researcher%2C%20coder%2C%20&eyebrow=Glossary Multi-agent system A multi-agent system uses multiple LLM-driven agents working together — typically with role specialisation (planner, executor, critic) or domain specialisation (researcher, coder, writer). Coordinatio https://www.stride.page/glossary/mutation-testing https://www.stride.page/api/og?title=Mutation%20testing&subtitle=Mutation%20testing%20measures%20test%20quality%20by%20introducing%20small%20bugs%20(mutations)%20into%20the%20source%20code%20and%20checking%20whether%20tests%20catch%20them.%20If%20a%20test%20suite%20has%2080%25%20coverage%20but%20kills%20&eyebrow=Glossary Mutation testing Mutation testing measures test quality by introducing small bugs (mutations) into the source code and checking whether tests catch them. If a test suite has 80% coverage but kills only 40% of mutants, https://www.stride.page/glossary/n-tier-architecture https://www.stride.page/api/og?title=N-tier%20architecture&subtitle=N-tier%20architecture%20distributes%20an%20application%20across%20N%20physical%20tiers%20%E2%80%94%20typically%20presentation%20(browser%20or%20client)%2C%20application%20server%20(business%20logic)%2C%20and%20database.%20Each%20tier%20ru&eyebrow=Glossary N-tier architecture N-tier architecture distributes an application across N physical tiers — typically presentation (browser or client), application server (business logic), and database. Each tier runs on separate hardw https://www.stride.page/glossary/north-star-metric https://www.stride.page/api/og?title=North%20Star%20metric&subtitle=A%20North%20Star%20metric%20is%20a%20single%20quantitative%20measure%20that%20captures%20the%20value%20a%20product%20delivers%20to%20its%20users%20%E2%80%94%20chosen%20to%20align%20an%20entire%20organisation's%20decisions%20toward%20customer%20va&eyebrow=Glossary North Star metric A North Star metric is a single quantitative measure that captures the value a product delivers to its users — chosen to align an entire organisation's decisions toward customer value rather than vani https://www.stride.page/glossary/observability https://www.stride.page/api/og?title=Observability&subtitle=Observability%20is%20the%20property%20of%20a%20system%20that%20lets%20engineers%20understand%20its%20internal%20state%20from%20external%20outputs%20%E2%80%94%20answering%20questions%20about%20how%20the%20system%20is%20behaving%20without%20mod&eyebrow=Glossary Observability Observability is the property of a system that lets engineers understand its internal state from external outputs — answering questions about how the system is behaving without modifying it. Modern ob https://www.stride.page/glossary/okrs https://www.stride.page/api/og?title=OKRs&subtitle=Objectives%20and%20Key%20Results%20(OKRs)%20is%20a%20goal-setting%20framework%2C%20originated%20at%20Intel%20under%20Andy%20Grove%20and%20popularised%20at%20Google%20by%20John%20Doerr%2C%20that%20pairs%20qualitative%20Objectives%20(wher&eyebrow=Glossary OKRs Objectives and Key Results (OKRs) is a goal-setting framework, originated at Intel under Andy Grove and popularised at Google by John Doerr, that pairs qualitative Objectives (where you want to go) wi https://www.stride.page/glossary/on-call-rotation https://www.stride.page/api/og?title=On-call%20rotation&subtitle=An%20on-call%20rotation%20is%20the%20scheduled%20assignment%20of%20engineers%20to%20be%20the%20primary%20responder%20for%20production%20incidents%20during%20a%20defined%20window%20%E2%80%94%20usually%201%20week%20per%20engineer%2C%2024%2F7%2C%20with%20&eyebrow=Glossary On-call rotation An on-call rotation is the scheduled assignment of engineers to be the primary responder for production incidents during a defined window — usually 1 week per engineer, 24/7, with a secondary backup w https://www.stride.page/glossary/onion-architecture https://www.stride.page/api/og?title=Onion%20architecture&subtitle=Onion%20architecture%20organises%20code%20in%20concentric%20layers%20from%20the%20domain%20model%20at%20the%20centre%20outward%20through%20application%20services%2C%20domain%20services%2C%20and%20infrastructure%20at%20the%20edge.%20De&eyebrow=Glossary Onion architecture Onion architecture organises code in concentric layers from the domain model at the centre outward through application services, domain services, and infrastructure at the edge. Dependencies point inw https://www.stride.page/glossary/opentelemetry https://www.stride.page/api/og?title=OpenTelemetry&subtitle=OpenTelemetry%20(OTel)%20is%20the%20CNCF%20observability%20standard%20for%20instrumenting%20software%20to%20emit%20traces%2C%20metrics%2C%20and%20logs%20in%20a%20vendor-neutral%20format.%20Formed%20in%202019%20from%20the%20merger%20of%20O&eyebrow=Glossary OpenTelemetry OpenTelemetry (OTel) is the CNCF observability standard for instrumenting software to emit traces, metrics, and logs in a vendor-neutral format. Formed in 2019 from the merger of OpenCensus and OpenTr https://www.stride.page/glossary/orchestrator-agent https://www.stride.page/api/og?title=Orchestrator%20agent&subtitle=An%20orchestrator%20agent%20is%20the%20top-level%20controller%20in%20a%20multi-agent%20system%20%E2%80%94%20it%20decomposes%20the%20user's%20request%20into%20sub-tasks%2C%20dispatches%20them%20to%20specialist%20agents%2C%20integrates%20their%20&eyebrow=Glossary Orchestrator agent An orchestrator agent is the top-level controller in a multi-agent system — it decomposes the user's request into sub-tasks, dispatches them to specialist agents, integrates their outputs, and handles https://www.stride.page/glossary/owasp-top-10 https://www.stride.page/api/og?title=OWASP%20Top%2010&subtitle=The%20OWASP%20Top%2010%20is%20a%20community-curated%20list%20of%20the%20most%20critical%20web%20application%20security%20risks%2C%20published%20every%203-4%20years%20by%20the%20Open%20Web%20Application%20Security%20Project.%20The%202021%20l&eyebrow=Glossary OWASP Top 10 The OWASP Top 10 is a community-curated list of the most critical web application security risks, published every 3-4 years by the Open Web Application Security Project. The 2021 list leads with broke https://www.stride.page/glossary/pair-programming https://www.stride.page/api/og?title=Pair%20programming&subtitle=Pair%20programming%20has%20two%20engineers%20at%20one%20workstation%2C%20alternating%20between%20driver%20(typing)%20and%20navigator%20(reviewing%2C%20suggesting%2C%20thinking%20ahead).%20Practiced%20widely%20at%20Pivotal%2C%20Thoug&eyebrow=Glossary Pair programming Pair programming has two engineers at one workstation, alternating between driver (typing) and navigator (reviewing, suggesting, thinking ahead). Practiced widely at Pivotal, Thoughtworks, and other X https://www.stride.page/glossary/petri-net https://www.stride.page/api/og?title=Petri%20net&subtitle=A%20Petri%20net%20is%20a%20mathematical%20modelling%20language%20for%20distributed%20systems%20using%20places%20(states)%2C%20transitions%20(events)%2C%20and%20tokens%20(markers%20showing%20current%20state).%20Petri%20nets%20are%20the&eyebrow=Glossary Petri net A Petri net is a mathematical modelling language for distributed systems using places (states), transitions (events), and tokens (markers showing current state). Petri nets are the formal foundation o https://www.stride.page/glossary/pi-planning https://www.stride.page/api/og?title=PI%20planning&subtitle=PI%20Planning%20is%20the%201-2%20day%20event%20at%20the%20start%20of%20each%20Program%20Increment%20where%20the%20entire%20Agile%20Release%20Train%20%E2%80%94%20all%20teams%2C%20Product%20Management%2C%20Business%20Owners%2C%20System%20Architect%20%E2%80%94%20as&eyebrow=Glossary PI planning PI Planning is the 1-2 day event at the start of each Program Increment where the entire Agile Release Train — all teams, Product Management, Business Owners, System Architect — assembles to plan the https://www.stride.page/glossary/planning-fallacy https://www.stride.page/api/og?title=Planning%20fallacy&subtitle=The%20planning%20fallacy%20is%20the%20cognitive%20bias%20toward%20predicting%20that%20one's%20own%20task%20will%20take%20less%20time%20than%20past%20tasks%20of%20similar%20scope.%20Identified%20by%20Daniel%20Kahneman%20and%20Amos%20Tversk&eyebrow=Glossary Planning fallacy The planning fallacy is the cognitive bias toward predicting that one's own task will take less time than past tasks of similar scope. Identified by Daniel Kahneman and Amos Tversky in 1979 and replic https://www.stride.page/glossary/planning-poker https://www.stride.page/api/og?title=Planning%20poker&subtitle=Planning%20poker%20is%20a%20consensus-based%20estimation%20technique%20where%20each%20engineer%20privately%20picks%20a%20Fibonacci%20card%20(1%2C%202%2C%203%2C%205%2C%208%2C%2013%2C%20%E2%80%A6)%20for%20a%20story%2C%20then%20reveals%20simultaneously.%20Diver&eyebrow=Glossary Planning poker Planning poker is a consensus-based estimation technique where each engineer privately picks a Fibonacci card (1, 2, 3, 5, 8, 13, …) for a story, then reveals simultaneously. Divergent estimates trigg https://www.stride.page/glossary/polyrepo https://www.stride.page/api/og?title=Polyrepo&subtitle=A%20polyrepo%20(or%20multirepo)%20architecture%20puts%20each%20service%20or%20library%20in%20its%20own%20version-control%20repository%2C%20with%20independent%20CI%2C%20versioning%2C%20and%20release%20cadences.%20It's%20the%20default%20f&eyebrow=Glossary Polyrepo A polyrepo (or multirepo) architecture puts each service or library in its own version-control repository, with independent CI, versioning, and release cadences. It's the default for most organisation https://www.stride.page/glossary/portfolio-kanban https://www.stride.page/api/og?title=Portfolio%20kanban&subtitle=A%20Portfolio%20Kanban%20is%20the%20visual%20board%20that%20tracks%20large%20initiatives%20(portfolio%20epics)%20across%20discovery%2C%20analysis%2C%20implementation%2C%20and%20done%20%E2%80%94%20with%20WIP%20limits%20at%20each%20state%20to%20const&eyebrow=Glossary Portfolio kanban A Portfolio Kanban is the visual board that tracks large initiatives (portfolio epics) across discovery, analysis, implementation, and done — with WIP limits at each state to constrain how much portfo https://www.stride.page/glossary/ports-and-adapters https://www.stride.page/api/og?title=Ports%20and%20adapters&subtitle=Ports%20and%20adapters%20(also%20called%20hexagonal%20architecture)%20is%20the%20design%20pattern%20that%20surrounds%20a%20core%20domain%20model%20with%20a%20layer%20of%20ports%20(interfaces%20describing%20what%20the%20core%20needs)%20a&eyebrow=Glossary Ports and adapters Ports and adapters (also called hexagonal architecture) is the design pattern that surrounds a core domain model with a layer of ports (interfaces describing what the core needs) and adapters (concret https://www.stride.page/glossary/postmortem https://www.stride.page/api/og?title=Postmortem&subtitle=A%20postmortem%20is%20a%20structured%20retrospective%20on%20an%20incident%20or%20failure%20%E2%80%94%20capturing%20what%20happened%2C%20why%2C%20what%20was%20learned%2C%20and%20what%20will%20change.%20Blameless%20postmortems%20focus%20on%20systemic&eyebrow=Glossary Postmortem A postmortem is a structured retrospective on an incident or failure — capturing what happened, why, what was learned, and what will change. Blameless postmortems focus on systemic causes rather than https://www.stride.page/glossary/premortem https://www.stride.page/api/og?title=Premortem&subtitle=A%20premortem%20is%20a%20planning%20exercise%20%E2%80%94%20formalised%20by%20Gary%20Klein%20in%20a%202007%20Harvard%20Business%20Review%20article%20%E2%80%94%20where%2C%20before%20starting%20a%20project%2C%20the%20team%20imagines%20the%20project%20has%20failed&eyebrow=Glossary Premortem A premortem is a planning exercise — formalised by Gary Klein in a 2007 Harvard Business Review article — where, before starting a project, the team imagines the project has failed and works backward https://www.stride.page/glossary/principle-of-least-privilege https://www.stride.page/api/og?title=Principle%20of%20least%20privilege&subtitle=The%20principle%20of%20least%20privilege%20is%20the%20security%20rule%20that%20every%20user%2C%20process%2C%20and%20system%20should%20have%20only%20the%20minimum%20permissions%20needed%20to%20do%20its%20job%20%E2%80%94%20no%20extra%20access%20'just%20in%20&eyebrow=Glossary Principle of least privilege The principle of least privilege is the security rule that every user, process, and system should have only the minimum permissions needed to do its job — no extra access 'just in case'. PoLP minimise https://www.stride.page/glossary/process-bottleneck https://www.stride.page/api/og?title=Process%20bottleneck&subtitle=A%20process%20bottleneck%20is%20the%20step%20in%20a%20workflow%20with%20the%20lowest%20throughput%20%E2%80%94%20the%20constraint%20that%20limits%20the%20entire%20process's%20output.%20Identifying%20the%20bottleneck%20is%20the%20prerequisite%20t&eyebrow=Glossary Process bottleneck A process bottleneck is the step in a workflow with the lowest throughput — the constraint that limits the entire process's output. Identifying the bottleneck is the prerequisite to any throughput-imp https://www.stride.page/glossary/process-conformance https://www.stride.page/api/og?title=Process%20conformance&subtitle=Process%20conformance%20is%20the%20analysis%20of%20how%20well%20an%20observed%20event%20log%20matches%20a%20reference%20process%20model%20%E2%80%94%20measuring%20deviations%2C%20missing%20steps%2C%20and%20extra%20steps.%20Conformance%20checking&eyebrow=Glossary Process conformance Process conformance is the analysis of how well an observed event log matches a reference process model — measuring deviations, missing steps, and extra steps. Conformance checking surfaces where the https://www.stride.page/glossary/process-debt https://www.stride.page/api/og?title=Process%20debt&subtitle=Process%20debt%20is%20the%20accumulated%20friction%20from%20team%20processes%20that%20no%20longer%20fit%20the%20work%20they%20govern%20%E2%80%94%20sprint%20structures%20that%20produce%20overcommitment%2C%20retrospectives%20that%20surface%20ac&eyebrow=Glossary Process debt Process debt is the accumulated friction from team processes that no longer fit the work they govern — sprint structures that produce overcommitment, retrospectives that surface action items without f https://www.stride.page/glossary/process-discovery https://www.stride.page/api/og?title=Process%20discovery&subtitle=Process%20discovery%20is%20the%20process-mining%20technique%20of%20constructing%20a%20process%20model%20(typically%20BPMN%20or%20a%20Petri%20net)%20from%20an%20event%20log%20without%20prior%20knowledge%20of%20the%20intended%20process.&eyebrow=Glossary Process discovery Process discovery is the process-mining technique of constructing a process model (typically BPMN or a Petri net) from an event log without prior knowledge of the intended process. Discovery algorithm https://www.stride.page/glossary/program-board https://www.stride.page/api/og?title=Program%20board&subtitle=The%20program%20board%20is%20the%20visual%20artefact%20produced%20during%20PI%20Planning%3A%20a%20grid%20of%20iterations%20%C3%97%20teams%20showing%20which%20features%20each%20team%20is%20committing%20to%20in%20which%20iteration%2C%20with%20explic&eyebrow=Glossary Program board The program board is the visual artefact produced during PI Planning: a grid of iterations × teams showing which features each team is committing to in which iteration, with explicit dependency lines https://www.stride.page/glossary/program-increment https://www.stride.page/api/og?title=Program%20increment%20(PI)&subtitle=A%20Program%20Increment%20is%20SAFe's%20timebox%20for%20an%20Agile%20Release%20Train%20%E2%80%94%20typically%208-12%20weeks%2C%20usually%205%20iterations%20of%202%20weeks%20each.%20The%20PI%20is%20the%20planning%2C%20execution%2C%20and%20inspection%20uni&eyebrow=Glossary Program increment (PI) A Program Increment is SAFe's timebox for an Agile Release Train — typically 8-12 weeks, usually 5 iterations of 2 weeks each. The PI is the planning, execution, and inspection unit above the iteratio https://www.stride.page/glossary/progressive-enhancement https://www.stride.page/api/og?title=Progressive%20enhancement&subtitle=Progressive%20enhancement%20is%20the%20design%20strategy%20of%20building%20a%20page%20that%20works%20at%20a%20minimum%20HTML%2BCSS%20baseline%2C%20then%20layering%20interactive%20enhancements%20on%20top%20via%20JavaScript.%20A%20progres&eyebrow=Glossary Progressive enhancement Progressive enhancement is the design strategy of building a page that works at a minimum HTML+CSS baseline, then layering interactive enhancements on top via JavaScript. A progressively-enhanced form https://www.stride.page/glossary/prompt-caching https://www.stride.page/api/og?title=Prompt%20caching&subtitle=Prompt%20caching%20is%20the%20LLM%20API%20feature%20that%20caches%20the%20processing%20of%20repeated%20prompt%20prefixes%20so%20subsequent%20requests%20with%20the%20same%20prefix%20run%20faster%20and%20cost%20less.%20Useful%20for%20long%20s&eyebrow=Glossary Prompt caching Prompt caching is the LLM API feature that caches the processing of repeated prompt prefixes so subsequent requests with the same prefix run faster and cost less. Useful for long system prompts, large https://www.stride.page/glossary/prompt-engineering-software https://www.stride.page/api/og?title=Prompt%20engineering%20for%20software%20teams&subtitle=Prompt%20engineering%20for%20software%20teams%20is%20the%20discipline%20of%20writing%20prompts%20that%20consistently%20produce%20useful%20output%20from%20LLMs%20in%20engineering%20workflows%20%E2%80%94%20code%20generation%2C%20test%20author&eyebrow=Glossary Prompt engineering for software teams Prompt engineering for software teams is the discipline of writing prompts that consistently produce useful output from LLMs in engineering workflows — code generation, test authoring, PR review, tech https://www.stride.page/glossary/property-based-testing https://www.stride.page/api/og?title=Property-based%20testing&subtitle=Property-based%20testing%20%E2%80%94%20popularised%20by%20QuickCheck%20(Haskell%2C%201999)%20and%20now%20available%20across%20most%20languages%20(Hypothesis%20for%20Python%2C%20fast-check%20for%20TypeScript%2C%20ScalaCheck)%20%E2%80%94%20generate&eyebrow=Glossary Property-based testing Property-based testing — popularised by QuickCheck (Haskell, 1999) and now available across most languages (Hypothesis for Python, fast-check for TypeScript, ScalaCheck) — generates many random inputs https://www.stride.page/glossary/pull-request https://www.stride.page/api/og?title=Pull%20request&subtitle=A%20pull%20request%20(PR)%20%E2%80%94%20also%20called%20a%20merge%20request%20in%20GitLab%20%2F%20Bitbucket%20%E2%80%94%20is%20a%20proposal%20to%20merge%20changes%20from%20one%20git%20branch%20into%20another%2C%20typically%20with%20code%20review%20and%20CI%20checks%20&eyebrow=Glossary Pull request A pull request (PR) — also called a merge request in GitLab / Bitbucket — is a proposal to merge changes from one git branch into another, typically with code review and CI checks gating the merge. PR https://www.stride.page/glossary/quantization https://www.stride.page/api/og?title=Quantization&subtitle=Quantization%20reduces%20the%20numerical%20precision%20of%20LLM%20weights%20(typically%20from%20FP16%20to%20INT8%20or%20INT4)%20to%20shrink%20memory%20footprint%20and%20speed%20up%20inference%2C%20with%20modest%20accuracy%20loss.%20Quan&eyebrow=Glossary Quantization Quantization reduces the numerical precision of LLM weights (typically from FP16 to INT8 or INT4) to shrink memory footprint and speed up inference, with modest accuracy loss. Quantization lets large https://www.stride.page/glossary/rate-limiting https://www.stride.page/api/og?title=Rate%20limiting&subtitle=Rate%20limiting%20caps%20the%20number%20of%20requests%20a%20client%20can%20make%20to%20a%20service%20within%20a%20defined%20window%20%E2%80%94%20typically%20expressed%20as%20'N%20requests%20per%20second'%20or%20'N%20requests%20per%20minute%20per%20API%20&eyebrow=Glossary Rate limiting Rate limiting caps the number of requests a client can make to a service within a defined window — typically expressed as 'N requests per second' or 'N requests per minute per API key'. Excess request https://www.stride.page/glossary/real-user-monitoring https://www.stride.page/api/og?title=Real%20user%20monitoring%20(RUM)&subtitle=Real%20user%20monitoring%20(RUM)%20instruments%20actual%20user%20sessions%20in%20the%20browser%20or%20mobile%20client%20to%20capture%20performance%20and%20error%20metrics%20as%20users%20experience%20them%20%E2%80%94%20Core%20Web%20Vitals%20(LCP&eyebrow=Glossary Real user monitoring (RUM) Real user monitoring (RUM) instruments actual user sessions in the browser or mobile client to capture performance and error metrics as users experience them — Core Web Vitals (LCP, INP, CLS), JavaScr https://www.stride.page/glossary/rebase-vs-merge https://www.stride.page/api/og?title=Rebase%20vs%20merge&subtitle=Rebase%20and%20merge%20are%20two%20strategies%20for%20integrating%20changes%20from%20one%20branch%20into%20another.%20Merge%20creates%20a%20merge%20commit%20that%20preserves%20the%20branching%20history%3B%20rebase%20replays%20the%20bran&eyebrow=Glossary Rebase vs merge Rebase and merge are two strategies for integrating changes from one branch into another. Merge creates a merge commit that preserves the branching history; rebase replays the branch's commits on top https://www.stride.page/glossary/refactor https://www.stride.page/api/og?title=Refactor&subtitle=Refactoring%20is%20changing%20the%20internal%20structure%20of%20code%20without%20changing%20its%20external%20behaviour.%20The%20goal%20is%20to%20make%20code%20easier%20to%20understand%2C%20modify%2C%20or%20test%20%E2%80%94%20not%20to%20add%20features&eyebrow=Glossary Refactor Refactoring is changing the internal structure of code without changing its external behaviour. The goal is to make code easier to understand, modify, or test — not to add features. Refactoring under https://www.stride.page/glossary/regression-test https://www.stride.page/api/og?title=Regression%20test&subtitle=A%20regression%20test%20verifies%20that%20previously%20working%20functionality%20still%20works%20after%20a%20code%20change.%20Regression%20tests%20are%20run%20on%20every%20change%20(CI)%2C%20every%20release%2C%20or%20on%20a%20schedule%2C%20an&eyebrow=Glossary Regression test A regression test verifies that previously working functionality still works after a code change. Regression tests are run on every change (CI), every release, or on a schedule, and are the primary de https://www.stride.page/glossary/rlhf https://www.stride.page/api/og?title=Reinforcement%20learning%20from%20human%20feedback%20(RLHF)&subtitle=RLHF%20is%20the%20LLM%20training%20stage%20in%20which%20the%20model%20is%20refined%20using%20human%20preferences%20%E2%80%94%20humans%20rank%20model%20outputs%2C%20a%20reward%20model%20is%20trained%20from%20those%20rankings%2C%20and%20the%20LLM%20is%20opti&eyebrow=Glossary Reinforcement learning from human feedback (RLHF) RLHF is the LLM training stage in which the model is refined using human preferences — humans rank model outputs, a reward model is trained from those rankings, and the LLM is optimised against the re https://www.stride.page/glossary/relative-estimation https://www.stride.page/api/og?title=Relative%20estimation&subtitle=Relative%20estimation%20sizes%20work%20items%20against%20each%20other%20(this%20story%20is%20twice%20as%20big%20as%20that%20one)%20rather%20than%20in%20absolute%20units%20(this%20story%20will%20take%206%20hours).%20Story%20points%2C%20t-shirt&eyebrow=Glossary Relative estimation Relative estimation sizes work items against each other (this story is twice as big as that one) rather than in absolute units (this story will take 6 hours). Story points, t-shirt sizes, and Fibonacc https://www.stride.page/glossary/release-on-demand https://www.stride.page/api/og?title=Release%20on%20demand&subtitle=Release%20on%20demand%20is%20the%20SAFe%20principle%20that%20the%20technical%20capability%20to%20deploy%20and%20the%20business%20decision%20to%20release%20are%20decoupled.%20Code%20reaches%20production%20continuously%20through%20CI%2F&eyebrow=Glossary Release on demand Release on demand is the SAFe principle that the technical capability to deploy and the business decision to release are decoupled. Code reaches production continuously through CI/CD; the decision of https://www.stride.page/glossary/release-train-engineer https://www.stride.page/api/og?title=Release%20train%20engineer%20(RTE)&subtitle=The%20Release%20Train%20Engineer%20is%20the%20chief%20Scrum%20Master%20of%20an%20Agile%20Release%20Train%20%E2%80%94%20facilitating%20PI%20Planning%2C%20removing%20impediments%20across%20teams%2C%20managing%20risks%20and%20dependencies%2C%20and%20c&eyebrow=Glossary Release train engineer (RTE) The Release Train Engineer is the chief Scrum Master of an Agile Release Train — facilitating PI Planning, removing impediments across teams, managing risks and dependencies, and coaching the ART on S https://www.stride.page/glossary/retention-cohort https://www.stride.page/api/og?title=Retention%20cohort&subtitle=A%20retention%20cohort%20is%20a%20group%20of%20users%20who%20joined%20in%20the%20same%20time%20window%20(e.g.%20all%20signups%20in%20week%2014)%2C%20tracked%20over%20time%20to%20measure%20how%20many%20remain%20active.%20Cohort%20analysis%20surfac&eyebrow=Glossary Retention cohort A retention cohort is a group of users who joined in the same time window (e.g. all signups in week 14), tracked over time to measure how many remain active. Cohort analysis surfaces whether retention https://www.stride.page/glossary/retrieval-augmented-generation https://www.stride.page/api/og?title=Retrieval-augmented%20generation%20(RAG)&subtitle=Retrieval-augmented%20generation%20is%20the%20pattern%20where%20an%20LLM%20is%20given%20relevant%20context%20retrieved%20from%20an%20external%20source%20%E2%80%94%20typically%20via%20semantic%20search%20over%20a%20vector%20database%20%E2%80%94%20befo&eyebrow=Glossary Retrieval-augmented generation (RAG) Retrieval-augmented generation is the pattern where an LLM is given relevant context retrieved from an external source — typically via semantic search over a vector database — before generating its re https://www.stride.page/glossary/rice-scoring https://www.stride.page/api/og?title=RICE%20scoring&subtitle=RICE%20scoring%20is%20a%20prioritisation%20framework%20from%20Intercom%20that%20ranks%20initiatives%20by%20Reach%20(how%20many%20users%20affected)%2C%20Impact%20(per-user%20effect%2C%20typically%20scored%200.25%20to%203)%2C%20Confidence&eyebrow=Glossary RICE scoring RICE scoring is a prioritisation framework from Intercom that ranks initiatives by Reach (how many users affected), Impact (per-user effect, typically scored 0.25 to 3), Confidence (certainty of the e https://www.stride.page/glossary/risk-roaming https://www.stride.page/api/og?title=Risk%20ROAMing&subtitle=ROAM%20is%20the%20SAFe%20protocol%20for%20handling%20risks%20identified%20during%20PI%20Planning%3A%20each%20risk%20is%20categorised%20Resolved%20(already%20handled)%2C%20Owned%20(someone%20now%20owns%20the%20mitigation)%2C%20Accepted%20(&eyebrow=Glossary Risk ROAMing ROAM is the SAFe protocol for handling risks identified during PI Planning: each risk is categorised Resolved (already handled), Owned (someone now owns the mitigation), Accepted (the team accepts the https://www.stride.page/glossary/rto-rpo https://www.stride.page/api/og?title=RTO%20and%20RPO&subtitle=Recovery%20Time%20Objective%20(RTO)%20is%20the%20maximum%20acceptable%20time%20between%20a%20disaster%20and%20service%20restoration.%20Recovery%20Point%20Objective%20(RPO)%20is%20the%20maximum%20acceptable%20data%20loss%20measured&eyebrow=Glossary RTO and RPO Recovery Time Objective (RTO) is the maximum acceptable time between a disaster and service restoration. Recovery Point Objective (RPO) is the maximum acceptable data loss measured backwards from the https://www.stride.page/glossary/runbook https://www.stride.page/api/og?title=Runbook&subtitle=A%20runbook%20is%20a%20step-by-step%20operational%20document%20that%20describes%20how%20to%20diagnose%20and%20resolve%20a%20specific%20failure%20mode%20%E2%80%94%20what%20alert%20fires%2C%20what%20to%20check%20first%2C%20which%20commands%20to%20run%2C%20&eyebrow=Glossary Runbook A runbook is a step-by-step operational document that describes how to diagnose and resolve a specific failure mode — what alert fires, what to check first, which commands to run, when to escalate. Ru https://www.stride.page/glossary/safe-framework https://www.stride.page/api/og?title=SAFe%20(Scaled%20Agile%20Framework)&subtitle=The%20Scaled%20Agile%20Framework%20(SAFe)%2C%20created%20by%20Dean%20Leffingwell%20in%202011%2C%20is%20the%20most-adopted%20methodology%20for%20applying%20agile%20practices%20at%20enterprise%20scale%20(typically%20100%2B%20engineers).&eyebrow=Glossary SAFe (Scaled Agile Framework) The Scaled Agile Framework (SAFe), created by Dean Leffingwell in 2011, is the most-adopted methodology for applying agile practices at enterprise scale (typically 100+ engineers). SAFe organises work https://www.stride.page/glossary/saga-pattern https://www.stride.page/api/og?title=Saga%20pattern&subtitle=A%20saga%20is%20a%20sequence%20of%20local%20transactions%20across%20multiple%20services%20that%20together%20accomplish%20a%20distributed%20business%20transaction.%20Because%20distributed%20ACID%20transactions%20are%20usually%20i&eyebrow=Glossary Saga pattern A saga is a sequence of local transactions across multiple services that together accomplish a distributed business transaction. Because distributed ACID transactions are usually impractical, each ste https://www.stride.page/glossary/saturation https://www.stride.page/api/og?title=Saturation&subtitle=Saturation%20is%20the%20measure%20of%20how%20full%20the%20most-constrained%20resource%20of%20a%20system%20is%20%E2%80%94%20CPU%2C%20memory%2C%20IOPS%2C%20network%20bandwidth%2C%20queue%20depth%2C%20file%20descriptors.%20Saturation%20is%20the%20leading%20&eyebrow=Glossary Saturation Saturation is the measure of how full the most-constrained resource of a system is — CPU, memory, IOPS, network bandwidth, queue depth, file descriptors. Saturation is the leading indicator of capacit https://www.stride.page/glossary/semantic-html https://www.stride.page/api/og?title=Semantic%20HTML&subtitle=Semantic%20HTML%20uses%20HTML%20elements%20according%20to%20their%20meaning%20%E2%80%94%20%3Cbutton%3E%20for%20buttons%2C%20%3Cnav%3E%20for%20navigation%2C%20%3Carticle%3E%20for%20self-contained%20content%2C%20%3Ch1%3E-%3Ch6%3E%20for%20hierarchical%20headings%20&eyebrow=Glossary Semantic HTML Semantic HTML uses HTML elements according to their meaning — <button> for buttons, <nav> for navigation, <article> for self-contained content, <h1>-<h6> for hierarchical headings — rather than reachi https://www.stride.page/glossary/semantic-search https://www.stride.page/api/og?title=Semantic%20search&subtitle=Semantic%20search%20retrieves%20documents%20based%20on%20meaning%20rather%20than%20keyword%20overlap%20%E2%80%94%20using%20embedding%20vectors%20and%20similarity%20scoring%20to%20match%20queries%20to%20documents%20that%20express%20the%20sam&eyebrow=Glossary Semantic search Semantic search retrieves documents based on meaning rather than keyword overlap — using embedding vectors and similarity scoring to match queries to documents that express the same concept in differe https://www.stride.page/glossary/semantic-versioning https://www.stride.page/api/og?title=Semantic%20versioning%20(semver)&subtitle=Semantic%20versioning%20is%20the%20package-versioning%20convention%20MAJOR.MINOR.PATCH%20where%20MAJOR%20is%20incremented%20for%20breaking%20changes%2C%20MINOR%20for%20backwards-compatible%20feature%20additions%2C%20and%20PA&eyebrow=Glossary Semantic versioning (semver) Semantic versioning is the package-versioning convention MAJOR.MINOR.PATCH where MAJOR is incremented for breaking changes, MINOR for backwards-compatible feature additions, and PATCH for backwards-co https://www.stride.page/glossary/server-component https://www.stride.page/api/og?title=Server%20component&subtitle=A%20server%20component%20(React%20Server%20Components)%20is%20a%20React%20component%20that%20runs%20only%20on%20the%20server%20%E2%80%94%20it%20can%20fetch%20data%20directly%20from%20the%20database%2C%20use%20server-only%20secrets%2C%20and%20ship%20zer&eyebrow=Glossary Server component A server component (React Server Components) is a React component that runs only on the server — it can fetch data directly from the database, use server-only secrets, and ship zero JavaScript to the https://www.stride.page/glossary/server-side-rendering https://www.stride.page/api/og?title=Server-side%20rendering%20(SSR)&subtitle=Server-side%20rendering%20generates%20the%20HTML%20for%20a%20page%20on%20the%20server%20per%20request%20%E2%80%94%20the%20response%20is%20fully-formed%20HTML%20that%20the%20browser%20can%20render%20immediately%20without%20waiting%20for%20client&eyebrow=Glossary Server-side rendering (SSR) Server-side rendering generates the HTML for a page on the server per request — the response is fully-formed HTML that the browser can render immediately without waiting for client-side JavaScript. SS https://www.stride.page/glossary/serverless https://www.stride.page/api/og?title=Serverless&subtitle=Serverless%20is%20the%20cloud-computing%20model%20in%20which%20the%20cloud%20provider%20runs%20and%20scales%20the%20underlying%20infrastructure%20transparently%20%E2%80%94%20the%20developer%20deploys%20code%20(functions%2C%20containers)&eyebrow=Glossary Serverless Serverless is the cloud-computing model in which the cloud provider runs and scales the underlying infrastructure transparently — the developer deploys code (functions, containers) and the provider ha https://www.stride.page/glossary/service-mesh https://www.stride.page/api/og?title=Service%20mesh&subtitle=A%20service%20mesh%20is%20an%20infrastructure%20layer%20for%20service-to-service%20communication%2C%20typically%20implemented%20as%20a%20sidecar%20proxy%20(Envoy%2C%20Linkerd-proxy)%20running%20alongside%20each%20service.%20The%20&eyebrow=Glossary Service mesh A service mesh is an infrastructure layer for service-to-service communication, typically implemented as a sidecar proxy (Envoy, Linkerd-proxy) running alongside each service. The mesh handles concern https://www.stride.page/glossary/service-oriented-architecture https://www.stride.page/api/og?title=Service-oriented%20architecture%20(SOA)&subtitle=Service-oriented%20architecture%20is%20the%20design%20approach%20that%20structures%20applications%20as%20a%20collection%20of%20services%20communicating%20over%20a%20network%20%E2%80%94%20distinct%20from%20monoliths%20(single%20applica&eyebrow=Glossary Service-oriented architecture (SOA) Service-oriented architecture is the design approach that structures applications as a collection of services communicating over a network — distinct from monoliths (single application) and microservi https://www.stride.page/glossary/shape-up https://www.stride.page/api/og?title=Shape%20Up&subtitle=Shape%20Up%20is%20Basecamp's%20product-development%20methodology%20(Ryan%20Singer%2C%202019).%20The%20cycle%20has%20three%20phases%3A%20shaping%20(a%20senior%20PM%20scopes%20a%206-week%20project%20with%20hard%20boundaries%20%E2%80%94%20what's%20i&eyebrow=Glossary Shape Up Shape Up is Basecamp's product-development methodology (Ryan Singer, 2019). The cycle has three phases: shaping (a senior PM scopes a 6-week project with hard boundaries — what's in, what's out, sketc https://www.stride.page/glossary/shift-left-security https://www.stride.page/api/og?title=Shift-left%20security&subtitle=Shift-left%20security%20moves%20security%20activities%20%E2%80%94%20threat%20modelling%2C%20static%20analysis%2C%20dependency%20scanning%2C%20secret%20detection%20%E2%80%94%20earlier%20in%20the%20development%20lifecycle%2C%20ideally%20into%20the%20de&eyebrow=Glossary Shift-left security Shift-left security moves security activities — threat modelling, static analysis, dependency scanning, secret detection — earlier in the development lifecycle, ideally into the developer's IDE and PR https://www.stride.page/glossary/site-reliability-engineering https://www.stride.page/api/og?title=Site%20reliability%20engineering&subtitle=Site%20reliability%20engineering%20(SRE)%20is%20a%20discipline%20originated%20at%20Google%20in%202003%20(codified%20in%20the%202016%20SRE%20book)%20that%20applies%20software-engineering%20practices%20to%20operations.%20Rather%20th&eyebrow=Glossary Site reliability engineering Site reliability engineering (SRE) is a discipline originated at Google in 2003 (codified in the 2016 SRE book) that applies software-engineering practices to operations. Rather than treating uptime a https://www.stride.page/glossary/skip-level-1on1 https://www.stride.page/api/og?title=Skip-level%201%3A1&subtitle=A%20skip-level%201%3A1%20is%20a%20recurring%20meeting%20between%20an%20engineering%20manager%20and%20a%20direct%20report%20of%20one%20of%20their%20reports%20%E2%80%94%20bypassing%20one%20layer%20of%20the%20org%20chart.%20The%20format%20gives%20senior%20m&eyebrow=Glossary Skip-level 1:1 A skip-level 1:1 is a recurring meeting between an engineering manager and a direct report of one of their reports — bypassing one layer of the org chart. The format gives senior managers direct signa https://www.stride.page/glossary/sla https://www.stride.page/api/og?title=SLA&subtitle=A%20Service%20Level%20Agreement%20is%20the%20contractual%20commitment%20a%20service%20provider%20makes%20to%20its%20customers%20about%20expected%20service%20behaviour%2C%20with%20financial%20or%20contractual%20consequences%20when%20&eyebrow=Glossary SLA A Service Level Agreement is the contractual commitment a service provider makes to its customers about expected service behaviour, with financial or contractual consequences when the commitment is mi https://www.stride.page/glossary/sli https://www.stride.page/api/og?title=SLI&subtitle=A%20Service%20Level%20Indicator%20is%20a%20numerical%20measurement%20of%20one%20specific%20dimension%20of%20a%20service's%20behaviour%20%E2%80%94%20request%20latency%2C%20error%20rate%2C%20throughput%2C%20availability%20%E2%80%94%20expressed%20over%20a%20d&eyebrow=Glossary SLI A Service Level Indicator is a numerical measurement of one specific dimension of a service's behaviour — request latency, error rate, throughput, availability — expressed over a defined window. SLIs https://www.stride.page/glossary/slo https://www.stride.page/api/og?title=SLO&subtitle=A%20Service-Level%20Objective%20is%20a%20target%20reliability%20metric%20for%20a%20service%20%E2%80%94%20typically%20expressed%20as%20a%20percentage%20over%20a%20time%20window.%20For%20example%3A%2099.9%25%20of%20API%20requests%20return%20successfu&eyebrow=Glossary SLO A Service-Level Objective is a target reliability metric for a service — typically expressed as a percentage over a time window. For example: 99.9% of API requests return successfully within 200ms ove https://www.stride.page/glossary/smoke-test https://www.stride.page/api/og?title=Smoke%20test&subtitle=A%20smoke%20test%20is%20a%20small%2C%20fast%20set%20of%20tests%20that%20verify%20the%20most%20critical%20paths%20of%20a%20system%20work%20at%20all%20%E2%80%94%20does%20the%20app%20start%2C%20can%20a%20user%20log%20in%2C%20do%20the%20top%20three%20workflows%20respond.%20&eyebrow=Glossary Smoke test A smoke test is a small, fast set of tests that verify the most critical paths of a system work at all — does the app start, can a user log in, do the top three workflows respond. Smoke tests run on e https://www.stride.page/glossary/snapshot-testing https://www.stride.page/api/og?title=Snapshot%20testing&subtitle=Snapshot%20testing%20captures%20the%20serialised%20output%20of%20a%20function%20or%20component%20(rendered%20HTML%2C%20formatted%20JSON%2C%20computed%20data%20structure)%20and%20compares%20against%20a%20committed%20baseline%20on%20eve&eyebrow=Glossary Snapshot testing Snapshot testing captures the serialised output of a function or component (rendered HTML, formatted JSON, computed data structure) and compares against a committed baseline on every run. Differences https://www.stride.page/glossary/sbom https://www.stride.page/api/og?title=Software%20bill%20of%20materials%20(SBOM)&subtitle=A%20Software%20Bill%20of%20Materials%20is%20a%20machine-readable%20inventory%20of%20every%20component%2C%20library%2C%20and%20dependency%20in%20a%20software%20artefact%20%E2%80%94%20typically%20in%20SPDX%20or%20CycloneDX%20format.%20SBOMs%20let%20d&eyebrow=Glossary Software bill of materials (SBOM) A Software Bill of Materials is a machine-readable inventory of every component, library, and dependency in a software artefact — typically in SPDX or CycloneDX format. SBOMs let downstream consumers https://www.stride.page/glossary/specialist-agent https://www.stride.page/api/og?title=Specialist%20agent&subtitle=A%20specialist%20agent%20in%20a%20multi-agent%20system%20is%20scoped%20to%20a%20narrow%20domain%20%E2%80%94%20code%20review%2C%20data%20analysis%2C%20document%20drafting%2C%20web%20research%20%E2%80%94%20with%20a%20system%20prompt%2C%20tool%20set%2C%20and%20context%20&eyebrow=Glossary Specialist agent A specialist agent in a multi-agent system is scoped to a narrow domain — code review, data analysis, document drafting, web research — with a system prompt, tool set, and context window tuned to that https://www.stride.page/glossary/spike https://www.stride.page/api/og?title=Spike&subtitle=A%20spike%20is%20a%20timeboxed%20research%20story%20%E2%80%94%20the%20team%20commits%20to%20spending%20a%20fixed%20amount%20of%20effort%20(1%20day%2C%203%20days%2C%20a%20sprint)%20exploring%20a%20question%2C%20with%20a%20defined%20deliverable%20(a%20recommen&eyebrow=Glossary Spike A spike is a timeboxed research story — the team commits to spending a fixed amount of effort (1 day, 3 days, a sprint) exploring a question, with a defined deliverable (a recommendation, a prototype, https://www.stride.page/glossary/spotify-model https://www.stride.page/api/og?title=Spotify%20model&subtitle=The%20Spotify%20model%20(Kniberg%20%26%20Ivarsson%2C%202012)%20organises%20engineering%20teams%20into%20Squads%20(cross-functional%206-12%20person%20teams%20each%20owning%20a%20product%20slice)%2C%20Tribes%20(collections%20of%20relate&eyebrow=Glossary Spotify model The Spotify model (Kniberg & Ivarsson, 2012) organises engineering teams into Squads (cross-functional 6-12 person teams each owning a product slice), Tribes (collections of related squads), Chapters https://www.stride.page/glossary/sprint-burndown https://www.stride.page/api/og?title=Sprint%20burndown&subtitle=A%20sprint%20burndown%20chart%20shows%20remaining%20work%20in%20a%20sprint%20over%20time%20%E2%80%94%20typically%20Y-axis%20is%20story%20points%20or%20hours%2C%20X-axis%20is%20sprint%20day.%20The%20ideal%20line%20is%20a%20straight%20diagonal%20from%20spr&eyebrow=Glossary Sprint burndown A sprint burndown chart shows remaining work in a sprint over time — typically Y-axis is story points or hours, X-axis is sprint day. The ideal line is a straight diagonal from sprint start to sprint https://www.stride.page/glossary/sprint-goals https://www.stride.page/api/og?title=Sprint%20goals&subtitle=A%20sprint%20goal%20is%20a%20one-sentence%20outcome%20the%20team%20commits%20to%20delivering%20in%20the%20sprint%20%E2%80%94%20not%20a%20list%20of%20stories%2C%20but%20the%20customer%20or%20business%20outcome%20those%20stories%20produce.%20Sprint%20goa&eyebrow=Glossary Sprint goals A sprint goal is a one-sentence outcome the team commits to delivering in the sprint — not a list of stories, but the customer or business outcome those stories produce. Sprint goals are what protect https://www.stride.page/glossary/squash-merge https://www.stride.page/api/og?title=Squash%20merge&subtitle=A%20squash%20merge%20collapses%20all%20commits%20on%20a%20feature%20branch%20into%20a%20single%20commit%20on%20main%2C%20discarding%20the%20intermediate%20history.%20The%20result%20is%20a%20clean%20main-line%20history%20where%20each%20commi&eyebrow=Glossary Squash merge A squash merge collapses all commits on a feature branch into a single commit on main, discarding the intermediate history. The result is a clean main-line history where each commit corresponds to one https://www.stride.page/glossary/static-site-generation https://www.stride.page/api/og?title=Static%20site%20generation%20(SSG)&subtitle=Static%20site%20generation%20pre-renders%20every%20page%20to%20plain%20HTML%20at%20build%20time%2C%20then%20serves%20the%20HTML%20directly%20from%20a%20CDN%20with%20no%20server-side%20execution%20per%20request.%20SSG%20produces%20the%20fast&eyebrow=Glossary Static site generation (SSG) Static site generation pre-renders every page to plain HTML at build time, then serves the HTML directly from a CDN with no server-side execution per request. SSG produces the fastest possible page lo https://www.stride.page/glossary/story-points https://www.stride.page/api/og?title=Story%20points&subtitle=A%20story-point%20estimate%20is%20a%20unit-less%20measure%20of%20relative%20effort%20assigned%20to%20a%20user%20story.%20Points%20capture%20complexity%2C%20uncertainty%2C%20and%20time%20taken%20together%3B%20they're%20meant%20to%20be%20comp&eyebrow=Glossary Story points A story-point estimate is a unit-less measure of relative effort assigned to a user story. Points capture complexity, uncertainty, and time taken together; they're meant to be compared within a team ( https://www.stride.page/glossary/story-splitting https://www.stride.page/api/og?title=Story%20splitting&subtitle=Story%20splitting%20breaks%20a%20large%20user%20story%20into%20smaller%20stories%20that%20each%20independently%20deliver%20value.%20The%20smaller%20the%20stories%2C%20the%20smoother%20the%20flow%20%E2%80%94%20and%20the%20easier%20they%20are%20to%20es&eyebrow=Glossary Story splitting Story splitting breaks a large user story into smaller stories that each independently deliver value. The smaller the stories, the smoother the flow — and the easier they are to estimate, review, and https://www.stride.page/glossary/strangler-fig-pattern https://www.stride.page/api/og?title=Strangler%20fig%20pattern&subtitle=The%20strangler%20fig%20pattern%20is%20a%20migration%20approach%20for%20legacy%20systems%3A%20instead%20of%20replacing%20the%20system%20in%20one%20big-bang%20cutover%2C%20incrementally%20route%20specific%20functionality%20to%20a%20new%20i&eyebrow=Glossary Strangler fig pattern The strangler fig pattern is a migration approach for legacy systems: instead of replacing the system in one big-bang cutover, incrementally route specific functionality to a new implementation while https://www.stride.page/glossary/streaming-response https://www.stride.page/api/og?title=Streaming%20response&subtitle=A%20streaming%20response%20delivers%20LLM-generated%20tokens%20to%20the%20client%20as%20they're%20produced%20rather%20than%20waiting%20for%20the%20full%20response%20%E2%80%94%20typically%20over%20Server-Sent%20Events%20or%20WebSocket.%20Str&eyebrow=Glossary Streaming response A streaming response delivers LLM-generated tokens to the client as they're produced rather than waiting for the full response — typically over Server-Sent Events or WebSocket. Streaming makes long re https://www.stride.page/glossary/structured-output https://www.stride.page/api/og?title=Structured%20output&subtitle=Structured%20output%20is%20the%20LLM%20feature%20that%20guarantees%20the%20response%20matches%20a%20provided%20schema%20(JSON%20Schema%2C%20Zod%2C%20Pydantic)%20%E2%80%94%20eliminating%20the%20parsing%20failures%20and%20format%20drift%20that%20pl&eyebrow=Glossary Structured output Structured output is the LLM feature that guarantees the response matches a provided schema (JSON Schema, Zod, Pydantic) — eliminating the parsing failures and format drift that plagued early LLM appl https://www.stride.page/glossary/swarm-pattern https://www.stride.page/api/og?title=Swarm%20pattern&subtitle=Swarming%20has%20multiple%20team%20members%20work%20on%20the%20same%20story%20until%20it's%20done%2C%20then%20move%20together%20to%20the%20next.%20Swarming%20maximises%20throughput%20(one%20story%20done%20in%20a%20day%20beats%20five%20stories&eyebrow=Glossary Swarm pattern Swarming has multiple team members work on the same story until it's done, then move together to the next. Swarming maximises throughput (one story done in a day beats five stories partially done in a https://www.stride.page/glossary/synthetic-monitoring https://www.stride.page/api/og?title=Synthetic%20monitoring&subtitle=Synthetic%20monitoring%20runs%20scripted%2C%20simulated%20user%20transactions%20against%20a%20production%20service%20from%20external%20locations%20on%20a%20fixed%20cadence%20%E2%80%94%20typically%20every%201-5%20minutes%20from%20multiple%20&eyebrow=Glossary Synthetic monitoring Synthetic monitoring runs scripted, simulated user transactions against a production service from external locations on a fixed cadence — typically every 1-5 minutes from multiple geographies. Unlike https://www.stride.page/glossary/system-demo https://www.stride.page/api/og?title=System%20demo&subtitle=The%20System%20Demo%20is%20SAFe's%20event%20at%20the%20end%20of%20each%20iteration%20in%20which%20the%20integrated%20solution%20%E2%80%94%20every%20team's%20work%20combined%20into%20a%20working%20artefact%20%E2%80%94%20is%20demonstrated%20to%20Business%20Own&eyebrow=Glossary System demo The System Demo is SAFe's event at the end of each iteration in which the integrated solution — every team's work combined into a working artefact — is demonstrated to Business Owners and stakeholders https://www.stride.page/glossary/system-of-systems https://www.stride.page/api/og?title=System%20of%20systems&subtitle=A%20system%20of%20systems%20is%20an%20architectural%20composition%20where%20independently%20developed%2C%20independently%20owned%2C%20independently%20operated%20systems%20are%20integrated%20to%20produce%20capability%20greater%20&eyebrow=Glossary System of systems A system of systems is an architectural composition where independently developed, independently owned, independently operated systems are integrated to produce capability greater than the sum of part https://www.stride.page/glossary/system-prompt https://www.stride.page/api/og?title=System%20prompt&subtitle=A%20system%20prompt%20is%20the%20initial%20instruction%20given%20to%20an%20LLM%20at%20the%20start%20of%20a%20session%20that%20sets%20behaviour%2C%20persona%2C%20output%20format%2C%20and%20constraints%20%E2%80%94%20distinct%20from%20user%20messages%20that&eyebrow=Glossary System prompt A system prompt is the initial instruction given to an LLM at the start of a session that sets behaviour, persona, output format, and constraints — distinct from user messages that follow. The system https://www.stride.page/glossary/t-shirt-sizing https://www.stride.page/api/og?title=T-shirt%20sizing&subtitle=T-shirt%20sizing%20is%20a%20relative-estimation%20technique%20that%20assigns%20work%20items%20to%20size%20buckets%20%E2%80%94%20XS%2C%20S%2C%20M%2C%20L%2C%20XL%20%E2%80%94%20instead%20of%20point%20or%20hour%20estimates.%20The%20lack%20of%20numeric%20precision%20is%20t&eyebrow=Glossary T-shirt sizing T-shirt sizing is a relative-estimation technique that assigns work items to size buckets — XS, S, M, L, XL — instead of point or hour estimates. The lack of numeric precision is the point: it surface https://www.stride.page/glossary/takt-time https://www.stride.page/api/og?title=Takt%20time&subtitle=Takt%20time%20is%20the%20rate%20at%20which%20a%20process%20must%20produce%20output%20to%20meet%20demand%20%E2%80%94%20calculated%20as%20available%20production%20time%20divided%20by%20customer%20demand%20in%20that%20time.%20If%20a%20team%20has%208%20hours&eyebrow=Glossary Takt time Takt time is the rate at which a process must produce output to meet demand — calculated as available production time divided by customer demand in that time. If a team has 8 hours/day and customers d https://www.stride.page/glossary/tdd https://www.stride.page/api/og?title=TDD&subtitle=Test-Driven%20Development%20is%20a%20workflow%20where%20you%20write%20a%20failing%20test%20first%2C%20write%20the%20minimum%20code%20to%20make%20it%20pass%2C%20then%20refactor%20%E2%80%94%20repeated%20in%20tight%20loops.%20Popularised%20by%20Kent%20Bec&eyebrow=Glossary TDD Test-Driven Development is a workflow where you write a failing test first, write the minimum code to make it pass, then refactor — repeated in tight loops. Popularised by Kent Beck in the early 2000s https://www.stride.page/glossary/team-topologies https://www.stride.page/api/og?title=Team%20Topologies&subtitle=Team%20Topologies%20(Skelton%20%26%20Pais%2C%202019)%20is%20a%20framework%20for%20organising%20engineering%20teams%20using%20four%20team%20types%20and%20three%20interaction%20modes.%20The%20four%20team%20types%3A%20stream-aligned%20(deliv&eyebrow=Glossary Team Topologies Team Topologies (Skelton & Pais, 2019) is a framework for organising engineering teams using four team types and three interaction modes. The four team types: stream-aligned (delivers customer value e https://www.stride.page/glossary/technical-debt https://www.stride.page/api/og?title=Technical%20debt&subtitle=Technical%20debt%20is%20the%20accumulated%20cost%20of%20shortcuts%20taken%20during%20development%20%E2%80%94%20code%20that's%20harder%20to%20change%20than%20it%20should%20be%2C%20missing%20tests%2C%20outdated%20dependencies%2C%20or%20architectura&eyebrow=Glossary Technical debt Technical debt is the accumulated cost of shortcuts taken during development — code that's harder to change than it should be, missing tests, outdated dependencies, or architectural choices that no lo https://www.stride.page/glossary/temperature https://www.stride.page/api/og?title=Temperature%20(sampling)&subtitle=Temperature%20is%20the%20LLM%20sampling%20parameter%20that%20controls%20randomness%20in%20token%20selection%20%E2%80%94%200%20produces%20deterministic%20output%20(always%20the%20most-likely%20token)%2C%201%20samples%20roughly%20proportion&eyebrow=Glossary Temperature (sampling) Temperature is the LLM sampling parameter that controls randomness in token selection — 0 produces deterministic output (always the most-likely token), 1 samples roughly proportional to probability, h https://www.stride.page/glossary/test-coverage https://www.stride.page/api/og?title=Test%20coverage&subtitle=Test%20coverage%20is%20the%20percentage%20of%20code%20(typically%20measured%20by%20line%2C%20branch%2C%20or%20function)%20exercised%20by%20the%20test%20suite.%20Coverage%20is%20a%20necessary-but-insufficient%20quality%20signal%3A%20low%20&eyebrow=Glossary Test coverage Test coverage is the percentage of code (typically measured by line, branch, or function) exercised by the test suite. Coverage is a necessary-but-insufficient quality signal: low coverage indicates u https://www.stride.page/glossary/test-data-management https://www.stride.page/api/og?title=Test%20data%20management&subtitle=Test%20data%20management%20is%20the%20discipline%20of%20producing%2C%20maintaining%2C%20and%20isolating%20the%20data%20used%20in%20tests%20%E2%80%94%20fixtures%2C%20factories%2C%20seeded%20databases%2C%20anonymised%20production%20snapshots.%20Poo&eyebrow=Glossary Test data management Test data management is the discipline of producing, maintaining, and isolating the data used in tests — fixtures, factories, seeded databases, anonymised production snapshots. Poor test data manageme https://www.stride.page/glossary/test-double https://www.stride.page/api/og?title=Test%20double&subtitle=A%20test%20double%20is%20any%20object%20that%20stands%20in%20for%20a%20real%20dependency%20in%20a%20test%20%E2%80%94%20mock%2C%20stub%2C%20fake%2C%20spy%2C%20dummy.%20The%20'double'%20umbrella%20term%20(Gerard%20Meszaros)%20avoids%20the%20precise-but-confu&eyebrow=Glossary Test double A test double is any object that stands in for a real dependency in a test — mock, stub, fake, spy, dummy. The 'double' umbrella term (Gerard Meszaros) avoids the precise-but-confusing distinctions be https://www.stride.page/glossary/test-fixture https://www.stride.page/api/og?title=Test%20fixture&subtitle=A%20test%20fixture%20is%20the%20prepared%20state%20required%20to%20run%20a%20test%20%E2%80%94%20input%20data%2C%20mocked%20dependencies%2C%20configured%20environment%2C%20seeded%20database%20rows.%20Fixtures%20separate%20the%20'arrange'%20setup%20f&eyebrow=Glossary Test fixture A test fixture is the prepared state required to run a test — input data, mocked dependencies, configured environment, seeded database rows. Fixtures separate the 'arrange' setup from the 'act' and 'a https://www.stride.page/glossary/test-impact-analysis https://www.stride.page/api/og?title=Test%20impact%20analysis&subtitle=Test%20impact%20analysis%20identifies%20the%20subset%20of%20tests%20relevant%20to%20a%20code%20change%20%E2%80%94%20by%20analysing%20the%20dependency%20graph%20between%20source%20files%20and%20test%20files%20%E2%80%94%20so%20CI%20runs%20only%20the%20affected&eyebrow=Glossary Test impact analysis Test impact analysis identifies the subset of tests relevant to a code change — by analysing the dependency graph between source files and test files — so CI runs only the affected tests instead of th https://www.stride.page/glossary/test-isolation https://www.stride.page/api/og?title=Test%20isolation&subtitle=Test%20isolation%20is%20the%20property%20that%20each%20test%20runs%20independently%20%E2%80%94%20no%20shared%20state%2C%20no%20execution-order%20dependency%2C%20no%20side%20effects%20bleeding%20to%20the%20next%20test.%20Isolated%20tests%20can%20run&eyebrow=Glossary Test isolation Test isolation is the property that each test runs independently — no shared state, no execution-order dependency, no side effects bleeding to the next test. Isolated tests can run in any order or in https://www.stride.page/glossary/test-pyramid https://www.stride.page/api/og?title=Test%20pyramid&subtitle=The%20test%20pyramid%20is%20the%20testing-strategy%20heuristic%20that%20recommends%20many%20fast%20unit%20tests%20at%20the%20base%2C%20fewer%20integration%20tests%20in%20the%20middle%2C%20and%20very%20few%20slow%20end-to-end%20tests%20at%20th&eyebrow=Glossary Test pyramid The test pyramid is the testing-strategy heuristic that recommends many fast unit tests at the base, fewer integration tests in the middle, and very few slow end-to-end tests at the top. The pyramid s https://www.stride.page/glossary/test-quarantine https://www.stride.page/api/og?title=Test%20quarantine&subtitle=Test%20quarantine%20moves%20a%20flaky%20test%20out%20of%20the%20blocking%20suite%20into%20a%20tagged%20'quarantine'%20suite%20that%20runs%20but%20doesn't%20fail%20the%20build.%20Quarantine%20prevents%20the%20flaky%20test%20from%20blocking&eyebrow=Glossary Test quarantine Test quarantine moves a flaky test out of the blocking suite into a tagged 'quarantine' suite that runs but doesn't fail the build. Quarantine prevents the flaky test from blocking deploys while prese https://www.stride.page/glossary/theory-of-constraints https://www.stride.page/api/og?title=Theory%20of%20constraints&subtitle=Theory%20of%20constraints%20is%20Eli%20Goldratt's%20management%20methodology%20built%20on%20the%20observation%20that%20every%20system%20has%20one%20constraint%20(bottleneck)%20that%20limits%20its%20total%20throughput%20%E2%80%94%20and%20the&eyebrow=Glossary Theory of constraints Theory of constraints is Eli Goldratt's management methodology built on the observation that every system has one constraint (bottleneck) that limits its total throughput — and the only improvement th https://www.stride.page/glossary/observability-pillars https://www.stride.page/api/og?title=Three%20pillars%20of%20observability&subtitle=The%20three%20pillars%20of%20observability%20%E2%80%94%20logs%2C%20metrics%2C%20traces%20%E2%80%94%20are%20the%20foundational%20telemetry%20types%20that%20together%20let%20engineers%20reason%20about%20a%20system's%20runtime%20behaviour.%20Logs%20record&eyebrow=Glossary Three pillars of observability The three pillars of observability — logs, metrics, traces — are the foundational telemetry types that together let engineers reason about a system's runtime behaviour. Logs record discrete events wit https://www.stride.page/glossary/three-point-estimation https://www.stride.page/api/og?title=Three-point%20estimation&subtitle=Three-point%20estimation%20produces%20a%20single%20expected%20value%20from%20three%20estimates%3A%20optimistic%20(best-case)%2C%20most%20likely%2C%20and%20pessimistic%20(worst-case).%20The%20most%20common%20formula%20is%20PERT%20%E2%80%94%20E&eyebrow=Glossary Three-point estimation Three-point estimation produces a single expected value from three estimates: optimistic (best-case), most likely, and pessimistic (worst-case). The most common formula is PERT — Expected = (O + 4M + https://www.stride.page/glossary/throughput https://www.stride.page/api/og?title=Throughput&subtitle=Throughput%20is%20the%20count%20of%20work%20items%20completed%20per%20unit%20of%20time%20(typically%20per%20week%20or%20per%20sprint).%20Unlike%20velocity%20(which%20is%20points-based%20and%20team-specific)%2C%20throughput%20uses%20raw%20&eyebrow=Glossary Throughput Throughput is the count of work items completed per unit of time (typically per week or per sprint). Unlike velocity (which is points-based and team-specific), throughput uses raw story count and is c https://www.stride.page/glossary/toil https://www.stride.page/api/og?title=Toil&subtitle=Toil%2C%20as%20defined%20in%20Google's%20SRE%20practice%2C%20is%20operational%20work%20that%20is%20manual%2C%20repetitive%2C%20automatable%2C%20tactical%20(not%20strategic)%2C%20and%20scales%20linearly%20with%20service%20growth%20%E2%80%94%20patching&eyebrow=Glossary Toil Toil, as defined in Google's SRE practice, is operational work that is manual, repetitive, automatable, tactical (not strategic), and scales linearly with service growth — patching servers, manually r https://www.stride.page/glossary/token-budget https://www.stride.page/api/og?title=Token%20budget&subtitle=A%20token%20budget%20is%20the%20cap%20an%20application%20imposes%20on%20tokens%20consumed%20per%20request%20or%20per%20user%20%E2%80%94%20for%20cost%20control%2C%20latency%20control%2C%20and%20abuse%20prevention.%20The%20budget%20includes%20prompt%20to&eyebrow=Glossary Token budget A token budget is the cap an application imposes on tokens consumed per request or per user — for cost control, latency control, and abuse prevention. The budget includes prompt tokens, context tokens https://www.stride.page/glossary/tool-use https://www.stride.page/api/og?title=Tool%20use%20(LLM%20agent)&subtitle=Tool%20use%20is%20the%20LLM-agent%20pattern%20in%20which%20the%20model%20has%20access%20to%20a%20defined%20set%20of%20tools%20%E2%80%94%20read%20file%2C%20search%20web%2C%20run%20code%2C%20query%20API%20%E2%80%94%20and%20decides%20which%20to%20invoke%20and%20with%20what%20a&eyebrow=Glossary Tool use (LLM agent) Tool use is the LLM-agent pattern in which the model has access to a defined set of tools — read file, search web, run code, query API — and decides which to invoke and with what arguments based on th https://www.stride.page/glossary/top-p-sampling https://www.stride.page/api/og?title=Top-p%20sampling&subtitle=Top-p%20(or%20nucleus)%20sampling%20restricts%20token%20selection%20to%20the%20smallest%20set%20whose%20cumulative%20probability%20exceeds%20p%20%E2%80%94%20typically%200.9%20or%200.95.%20The%20technique%20adapts%20to%20the%20model's%20confid&eyebrow=Glossary Top-p sampling Top-p (or nucleus) sampling restricts token selection to the smallest set whose cumulative probability exceeds p — typically 0.9 or 0.95. The technique adapts to the model's confidence: when the model https://www.stride.page/glossary/traceability-matrix https://www.stride.page/api/og?title=Traceability%20matrix&subtitle=A%20traceability%20matrix%20maps%20requirements%20to%20the%20test%20cases%20that%20verify%20them%2C%20and%20to%20the%20defects%20discovered%20against%20each.%20Traceability%20lets%20a%20QA%20lead%20answer%20'is%20requirement%20X%20tested%3F&eyebrow=Glossary Traceability matrix A traceability matrix maps requirements to the test cases that verify them, and to the defects discovered against each. Traceability lets a QA lead answer 'is requirement X tested?' and 'which require https://www.stride.page/glossary/tree-of-thought https://www.stride.page/api/og?title=Tree-of-thought%20(ToT)&subtitle=Tree-of-thought%20prompting%20extends%20chain-of-thought%20by%20exploring%20multiple%20reasoning%20paths%20in%20parallel%2C%20evaluating%20each%2C%20and%20pursuing%20the%20most%20promising%20%E2%80%94%20analogous%20to%20tree%20search%20in&eyebrow=Glossary Tree-of-thought (ToT) Tree-of-thought prompting extends chain-of-thought by exploring multiple reasoning paths in parallel, evaluating each, and pursuing the most promising — analogous to tree search in game-playing AI. To https://www.stride.page/glossary/trunk-based-development https://www.stride.page/api/og?title=Trunk-based%20development&subtitle=Trunk-based%20development%20is%20a%20source-control%20workflow%20where%20engineers%20integrate%20small%20changes%20to%20a%20single%20shared%20branch%20(trunk%20%2F%20main)%20at%20least%20once%20per%20day%2C%20gated%20by%20automated%20test&eyebrow=Glossary Trunk-based development Trunk-based development is a source-control workflow where engineers integrate small changes to a single shared branch (trunk / main) at least once per day, gated by automated tests and feature flags https://www.stride.page/glossary/type-narrowing https://www.stride.page/api/og?title=Type%20narrowing&subtitle=Type%20narrowing%20is%20TypeScript's%20ability%20to%20refine%20a%20value's%20type%20within%20a%20conditional%20branch%20based%20on%20runtime%20checks%20%E2%80%94%20typeof%2C%20instanceof%2C%20in%20operator%2C%20equality%20checks%2C%20custom%20type%20&eyebrow=Glossary Type narrowing Type narrowing is TypeScript's ability to refine a value's type within a conditional branch based on runtime checks — typeof, instanceof, in operator, equality checks, custom type predicates. Narrowin https://www.stride.page/glossary/typescript-strict-mode https://www.stride.page/api/og?title=TypeScript%20strict%20mode&subtitle=TypeScript's%20strict%20mode%20enables%20a%20bundle%20of%20compiler%20flags%20that%20produce%20stricter%20type%20checking%20%E2%80%94%20noImplicitAny%2C%20strictNullChecks%2C%20strictFunctionTypes%2C%20strictBindCallApply%2C%20alwaysS&eyebrow=Glossary TypeScript strict mode TypeScript's strict mode enables a bundle of compiler flags that produce stricter type checking — noImplicitAny, strictNullChecks, strictFunctionTypes, strictBindCallApply, alwaysStrict, strictPropert https://www.stride.page/glossary/ubiquitous-language https://www.stride.page/api/og?title=Ubiquitous%20language&subtitle=Ubiquitous%20language%20is%20the%20shared%20vocabulary%20that%20the%20engineering%20team%20and%20the%20business%20stakeholders%20use%20to%20discuss%20a%20domain%20%E2%80%94%20the%20same%20word%20means%20the%20same%20thing%20in%20code%2C%20in%20conver&eyebrow=Glossary Ubiquitous language Ubiquitous language is the shared vocabulary that the engineering team and the business stakeholders use to discuss a domain — the same word means the same thing in code, in conversation, in user stor https://www.stride.page/glossary/user-story-mapping https://www.stride.page/api/og?title=User-story%20mapping&subtitle=User-story%20mapping%20(Jeff%20Patton%2C%202014)%20is%20a%20workshop%20technique%20for%20organising%20product%20backlogs%20around%20the%20user's%20journey%20rather%20than%20as%20a%20flat%20list.%20The%20map%20has%20activities%20across%20t&eyebrow=Glossary User-story mapping User-story mapping (Jeff Patton, 2014) is a workshop technique for organising product backlogs around the user's journey rather than as a flat list. The map has activities across the top (the user's h https://www.stride.page/glossary/value-stream https://www.stride.page/api/og?title=Value%20stream&subtitle=A%20value%20stream%20is%20the%20end-to-end%20sequence%20of%20activities%20that%20delivers%20a%20product%20or%20feature%20to%20a%20customer.%20Value-stream%20mapping%20(VSM)%20makes%20the%20stream%20visible%2C%20identifies%20waste%20(han&eyebrow=Glossary Value stream A value stream is the end-to-end sequence of activities that delivers a product or feature to a customer. Value-stream mapping (VSM) makes the stream visible, identifies waste (handoffs, queues, rewor https://www.stride.page/glossary/value-stream-mapping https://www.stride.page/api/og?title=Value%20stream%20mapping&subtitle=Value%20stream%20mapping%20is%20the%20Lean%20technique%20of%20drawing%20a%20current-state%20diagram%20of%20a%20process%20%E2%80%94%20every%20step%2C%20every%20queue%2C%20every%20handoff%2C%20with%20cycle%20time%20and%20wait%20time%20labelled%20%E2%80%94%20to%20ide&eyebrow=Glossary Value stream mapping Value stream mapping is the Lean technique of drawing a current-state diagram of a process — every step, every queue, every handoff, with cycle time and wait time labelled — to identify where value is https://www.stride.page/glossary/variant-analysis https://www.stride.page/api/og?title=Variant%20analysis&subtitle=Variant%20analysis%20groups%20cases%20by%20the%20unique%20sequence%20of%20activities%20they%20followed%20and%20ranks%20variants%20by%20frequency%20and%20cost.%20The%20top%203-5%20variants%20typically%20account%20for%2070-90%25%20of%20case&eyebrow=Glossary Variant analysis Variant analysis groups cases by the unique sequence of activities they followed and ranks variants by frequency and cost. The top 3-5 variants typically account for 70-90% of cases; the long tail of https://www.stride.page/glossary/vector-database https://www.stride.page/api/og?title=Vector%20database&subtitle=A%20vector%20database%20stores%20embedding%20vectors%20and%20supports%20fast%20approximate-nearest-neighbour%20search%20at%20scale%20%E2%80%94%20answering%20'find%20the%20K%20vectors%20most%20similar%20to%20this%20query%20vector'%20in%20mil&eyebrow=Glossary Vector database A vector database stores embedding vectors and supports fast approximate-nearest-neighbour search at scale — answering 'find the K vectors most similar to this query vector' in milliseconds across mil https://www.stride.page/glossary/velocity https://www.stride.page/api/og?title=Velocity&subtitle=A%20team's%20velocity%20is%20the%20average%20number%20of%20story%20points%20completed%20per%20sprint%20over%20a%20rolling%20window%20(typically%20the%20last%203-6%20sprints).%20Velocity%20is%20used%20to%20plan%20future%20sprints%3A%20if%20a%20t&eyebrow=Glossary Velocity A team's velocity is the average number of story points completed per sprint over a rolling window (typically the last 3-6 sprints). Velocity is used to plan future sprints: if a team's average is 32 https://www.stride.page/glossary/vertical-autoscaling https://www.stride.page/api/og?title=Vertical%20autoscaling&subtitle=Vertical%20autoscaling%20resizes%20an%20existing%20instance%20%E2%80%94%20adding%20CPU%2C%20memory%2C%20or%20storage%20%E2%80%94%20rather%20than%20adding%20more%20instances.%20Useful%20for%20workloads%20that%20don't%20parallelise%20well%20(single-thr&eyebrow=Glossary Vertical autoscaling Vertical autoscaling resizes an existing instance — adding CPU, memory, or storage — rather than adding more instances. Useful for workloads that don't parallelise well (single-threaded servers, state https://www.stride.page/glossary/vertical-slicing https://www.stride.page/api/og?title=Vertical%20slicing&subtitle=Vertical%20slicing%20breaks%20work%20into%20thin%20slices%20that%20cut%20through%20every%20layer%20of%20the%20architecture%20%E2%80%94%20UI%2C%20business%20logic%2C%20data%2C%20infrastructure%20%E2%80%94%20so%20each%20slice%20delivers%20end-user%20value%20in&eyebrow=Glossary Vertical slicing Vertical slicing breaks work into thin slices that cut through every layer of the architecture — UI, business logic, data, infrastructure — so each slice delivers end-user value independently. The opp https://www.stride.page/glossary/visual-regression https://www.stride.page/api/og?title=Visual%20regression&subtitle=Visual%20regression%20testing%20captures%20screenshots%20of%20UI%20components%20and%20compares%20them%20pixel-by-pixel%20(with%20tolerance)%20against%20baseline%20images%20on%20every%20change%20%E2%80%94%20catching%20unintended%20visu&eyebrow=Glossary Visual regression Visual regression testing captures screenshots of UI components and compares them pixel-by-pixel (with tolerance) against baseline images on every change — catching unintended visual changes that esca https://www.stride.page/glossary/webhook https://www.stride.page/api/og?title=Webhook&subtitle=A%20webhook%20is%20an%20HTTP%20callback%20that%20one%20service%20invokes%20on%20another%20when%20a%20defined%20event%20occurs%20%E2%80%94%20typically%20a%20POST%20request%20with%20the%20event%20payload%20to%20a%20URL%20the%20consumer%20registered.%20We&eyebrow=Glossary Webhook A webhook is an HTTP callback that one service invokes on another when a defined event occurs — typically a POST request with the event payload to a URL the consumer registered. Webhooks are the simpl https://www.stride.page/glossary/wsjf https://www.stride.page/api/og?title=Weighted%20shortest%20job%20first%20(WSJF)&subtitle=Weighted%20Shortest%20Job%20First%20is%20SAFe's%20prioritisation%20formula%3A%20WSJF%20%3D%20Cost%20of%20Delay%20%C3%B7%20Job%20Size%2C%20where%20Cost%20of%20Delay%20is%20a%20relative%20score%20combining%20user-business%20value%2C%20time%20criticali&eyebrow=Glossary Weighted shortest job first (WSJF) Weighted Shortest Job First is SAFe's prioritisation formula: WSJF = Cost of Delay ÷ Job Size, where Cost of Delay is a relative score combining user-business value, time criticality, and risk reducti https://www.stride.page/glossary/wip-limit https://www.stride.page/api/og?title=WIP%20limit&subtitle=A%20work-in-progress%20(WIP)%20limit%20caps%20how%20many%20items%20the%20team%20can%20have%20in%20flight%20at%20once%2C%20per%20workflow%20stage.%20WIP%20limits%20force%20teams%20to%20finish%20work%20before%20starting%20new%20work%20%E2%80%94%20the%20cen&eyebrow=Glossary WIP limit A work-in-progress (WIP) limit caps how many items the team can have in flight at once, per workflow stage. WIP limits force teams to finish work before starting new work — the central practice of Kan https://www.stride.page/glossary/xml-tags-prompt https://www.stride.page/api/og?title=XML-tagged%20prompt&subtitle=XML-tagged%20prompts%20use%20XML-style%20tags%20to%20delineate%20sections%20of%20a%20prompt%20%E2%80%94%20%3Cinstructions%3E...%3C%2Finstructions%3E%2C%20%3Ccontext%3E...%3C%2Fcontext%3E%2C%20%3Cexample%3E...%3C%2Fexample%3E%20%E2%80%94%20so%20the%20model%20can%20clearl&eyebrow=Glossary XML-tagged prompt XML-tagged prompts use XML-style tags to delineate sections of a prompt — <instructions>...</instructions>, <context>...</context>, <example>...</example> — so the model can clearly distinguish parts. https://www.stride.page/glossary/zero-trust-architecture https://www.stride.page/api/og?title=Zero%20trust%20architecture&subtitle=Zero%20trust%20is%20the%20security%20model%20that%20assumes%20no%20implicit%20trust%20based%20on%20network%20location%20%E2%80%94%20every%20request%2C%20internal%20or%20external%2C%20must%20be%20authenticated%2C%20authorised%2C%20and%20continuously&eyebrow=Glossary Zero trust architecture Zero trust is the security model that assumes no implicit trust based on network location — every request, internal or external, must be authenticated, authorised, and continuously verified. The model https://www.stride.page/use-cases/ai-sprint-planning https://www.stride.page/api/og?title=AI%20sprint%20planning&subtitle=Let%20the%20AI%20fill%20the%20sprint.%20You%20spend%20the%20saved%20hours%20on%20actual%20work.&eyebrow=Use%20case AI sprint planning Most sprint planning meetings spend 60% of the time on capacity math the AI can do in 2 seconds. Stride's Plan module computes realistic capacity from PTO + meetings + historical velocity, then proposes a draft sprint your team can edit instead of author from scratch. https://www.stride.page/use-cases/ai-prd-generation https://www.stride.page/api/og?title=AI%20PRD%20generation&subtitle=From%20a%204-page%20PRD%20to%2015%20stories%2C%2060%20acceptance%20criteria%2C%20and%20a%20sprint%20draft%20in%2090%20seconds.&eyebrow=Use%20case AI PRD generation Translating a PRD into actionable stories takes most PMs a half-day per epic. Stride generates the epic, story breakdown, acceptance criteria, test cases, and dependency graph in under two minutes — leaving the PM to edit instead of author. https://www.stride.page/use-cases/bpmn-process-mining https://www.stride.page/api/og?title=BPMN%20process%20mining&subtitle=Find%20the%20bottleneck%20in%20your%20delivery%20pipeline%20without%20paying%20Celonis%20money.&eyebrow=Use%20case BPMN process mining Celonis is great. It also starts at $200K/year. For most software-delivery teams, the diagnostic value of process mining (finding where lead time is actually being spent) doesn't require enterprise BI. Stride mines your Jira/Linear/Stride events into BPMN diagrams and bottleneck heatmaps in one day. https://www.stride.page/use-cases/legacy-modernization https://www.stride.page/api/og?title=Legacy%20modernization&subtitle=AI%20reads%20decades-old%20code%20so%20your%20modernization%20plan%20stops%20being%20a%20guess.&eyebrow=Use%20case Legacy modernization Modernizing legacy systems (COBOL, mainframe, old .NET) is one of the highest-stakes engineering investments. Stride's Legacy Intelligence reads the legacy code, extracts implicit requirements, generates a phased modernization roadmap, and computes payback math grounded in real LOC and complexity. https://www.stride.page/use-cases/architecture-decisions https://www.stride.page/api/og?title=Architecture%20decisions&subtitle=AI-scored%20architecture%20options%2C%20ADRs%20with%20rationale%2C%20and%20a%20tech%20radar%20that%20updates%20as%20decisions%20ship.&eyebrow=Use%20case Architecture decisions Most engineering organisations make a hundred architecture decisions a year, document maybe ten, and re-litigate the same trade-offs every 18 months. Stride's Design module generates 3-5 scored alternatives per decision, captures the chosen option as an ADR, and maintains a living tech radar. https://www.stride.page/use-cases/ai-test-generation https://www.stride.page/api/og?title=AI%20test%20generation&subtitle=Test%20cases%20written%20by%20AI%20from%20your%20stories%20%E2%80%94%20with%20traceability%20that%20maintains%20itself.&eyebrow=Use%20case AI test generation Test management as a separate discipline (TestRail + Jira + spreadsheets) was a workaround for tools that couldn't see across stories and tests. Stride generates test cases from AC at story-creation time, maintains the traceability matrix automatically, and predicts which areas are likely to regress. https://www.stride.page/use-cases/defect-prediction https://www.stride.page/api/og?title=Defect%20prediction&subtitle=Know%20which%20areas%20of%20the%20codebase%20are%20likely%20to%20break%20before%20they%20do.&eyebrow=Use%20case Defect prediction Defects don't distribute uniformly — most defects cluster in a small fraction of modules. Stride's defect-prediction model scores every module by risk and tells reviewers which PRs deserve careful eyes. It's the same model that's used to surface 'review carefully' at PR time and to plan regression-test investments. https://www.stride.page/use-cases/release-notes-automation https://www.stride.page/api/og?title=Release%20notes%20automation&subtitle=Release%20notes%20written%20from%20the%20stories%20actually%20shipped%20%E2%80%94%20not%20from%20memory.&eyebrow=Use%20case Release notes automation Release notes are typically written by someone reading through closed Jira tickets and rephrasing them into user-friendly language. Stride does the rephrasing automatically: every release surfaces a draft from the merged stories, in your team's voice, with the option to edit before shipping. https://www.stride.page/use-cases/team-onboarding https://www.stride.page/api/og?title=Team%20onboarding&subtitle=New%20engineers%20ramp%20in%20days%2C%20not%20weeks%20%E2%80%94%20by%20reading%20the%20graph%2C%20not%20Slack%20history.&eyebrow=Use%20case Team onboarding New engineers spend their first month searching Slack history for 'why does this work this way?' and asking senior engineers who'd rather be coding. Stride lets the AI answer those questions from the actual project graph — ADRs, stories, dependencies, and decisions — instead of from your senior engineers' time. https://www.stride.page/use-cases/quality-gates https://www.stride.page/api/og?title=Quality%20gates&subtitle=Definition%20of%20Done%20enforced%20by%20the%20tool%2C%20not%20by%20team%20memory.&eyebrow=Use%20case Quality gates Most teams have a Definition of Done that lives on a Confluence page nobody reads. Stride enforces it: stories can't transition to Done until AC are verified, tests pass, code is reviewed, and any other team-specific gates are met. Drift between intent and reality drops to zero. https://www.stride.page/learn/sprint-planning https://www.stride.page/api/og?title=Sprint%20planning&subtitle=Plan%2C%20run%2C%20and%20improve%20sprints%20with%20AI%20in%20the%20loop.&eyebrow=Learn Sprint planning Everything teams need to plan, run, and improve sprints — capacity, story sizing, sprint goals, retrospectives, and burndown. https://www.stride.page/learn/sprint-planning/capacity-planning https://www.stride.page/api/og?title=Capacity%20planning%20that%20survives%20reality&subtitle=Naive%20capacity%20is%20team-size%20%C3%97%20sprint-days.%20Realistic%20capacity%20is%2050-65%25%20of%20that.%20Why%2C%20and%20how%20to%20compute%20it%20for%20your%20team.&eyebrow=Learn Capacity planning that survives reality Naive capacity is team-size × sprint-days. Realistic capacity is 50-65% of that. Why, and how to compute it for your team. https://www.stride.page/learn/sprint-planning/story-sizing https://www.stride.page/api/og?title=Story%20sizing%20without%20flame%20wars&subtitle=Fibonacci%20vs%20t-shirt%2C%20when%20to%20estimate%2C%20when%20to%20stop%2C%20and%20how%20AI%20helps%20without%20taking%20over%20the%20room.&eyebrow=Learn Story sizing without flame wars Fibonacci vs t-shirt, when to estimate, when to stop, and how AI helps without taking over the room. https://www.stride.page/learn/sprint-planning/sprint-goals https://www.stride.page/api/og?title=Sprint%20goals%20worth%20committing%20to&subtitle=The%20difference%20between%20'complete%20these%2012%20stories'%20and%20'deliver%20the%20multi-tenant%20CSV%20export'.%20Goals%20teams%20actually%20care%20about.&eyebrow=Learn Sprint goals worth committing to The difference between 'complete these 12 stories' and 'deliver the multi-tenant CSV export'. Goals teams actually care about. https://www.stride.page/learn/sprint-planning/retrospectives https://www.stride.page/api/og?title=Retrospectives%20that%20change%20behavior&subtitle=Formats%20that%20work%20(Mad%2FSad%2FGlad%2C%20Sailboat%2C%204Ls%2C%20Lean%20Coffee)%2C%20formats%20that%20don't%2C%20and%20the%20action-item%20discipline%20that%20turns%20retros%20into%20actual%20change.&eyebrow=Learn Retrospectives that change behavior Formats that work (Mad/Sad/Glad, Sailboat, 4Ls, Lean Coffee), formats that don't, and the action-item discipline that turns retros into actual change. https://www.stride.page/learn/sprint-planning/burndown-charts https://www.stride.page/api/og?title=Burndown%20charts%20and%20what%20they%20actually%20tell%20you&subtitle=The%20false-positive%20trap%2C%20the%20right%20metrics%20next%20to%20burndown%2C%20and%20what%20burndown%20does%20NOT%20show.%20Plus%20the%20patterns%20that%20mean%20something.&eyebrow=Learn Burndown charts and what they actually tell you The false-positive trap, the right metrics next to burndown, and what burndown does NOT show. Plus the patterns that mean something. https://www.stride.page/learn/code-review https://www.stride.page/api/og?title=Code%20review&subtitle=Catch%20bugs%20without%20slowing%20the%20team%20down.&eyebrow=Learn Code review Checklists, SLOs, async patterns, mob review for high-stakes changes, and AI-assisted review — the practices that make code review effective without becoming the cycle-time bottleneck. https://www.stride.page/learn/code-review/review-checklists https://www.stride.page/api/og?title=Code-review%20checklists%20that%20actually%20catch%20bugs&subtitle=Most%20checklists%20are%20decorative.%20The%20five%20questions%20that%20find%20real%20defects%2C%20and%20why%20everything%20else%20belongs%20in%20the%20linter.&eyebrow=Learn Code-review checklists that actually catch bugs Most checklists are decorative. The five questions that find real defects, and why everything else belongs in the linter. https://www.stride.page/learn/code-review/async-code-review https://www.stride.page/api/og?title=Async%20code%20review%20without%2024-hour%20latency&subtitle=Two-touch%20SLO%2C%20structural%20defaults%2C%20comment%20templates.%20How%20distributed%20teams%20keep%20review%20latency%20under%204%20hours%20without%20forcing%20synchronous%20meetings.&eyebrow=Learn Async code review without 24-hour latency Two-touch SLO, structural defaults, comment templates. How distributed teams keep review latency under 4 hours without forcing synchronous meetings. https://www.stride.page/learn/code-review/mob-review https://www.stride.page/api/og?title=Mob%20review%20for%20high-stakes%20changes&subtitle=When%20one%20reviewer%20isn't%20enough%20and%20async%20is%20too%20slow.%20The%2030-60%20minute%20synchronous%20format%20for%20auth%2C%20payments%2C%20schema%2C%20and%20core%20architecture%20changes.&eyebrow=Learn Mob review for high-stakes changes When one reviewer isn't enough and async is too slow. The 30-60 minute synchronous format for auth, payments, schema, and core architecture changes. https://www.stride.page/learn/code-review/review-slos https://www.stride.page/api/og?title=Service-level%20objectives%20for%20code%20review&subtitle=Three%20numbers%20that%20make%20review%20effectiveness%20measurable%3A%20time-to-first-touch%2C%20time-to-merge%2C%20defect%20escape%20rate.%20Targets%2C%20measurement%2C%20and%20what%20to%20do%20when%20they%20slip.&eyebrow=Learn Service-level objectives for code review Three numbers that make review effectiveness measurable: time-to-first-touch, time-to-merge, defect escape rate. Targets, measurement, and what to do when they slip. https://www.stride.page/learn/code-review/ai-assisted-review https://www.stride.page/api/og?title=AI-assisted%20code%20review%20without%20losing%20rigor&subtitle=What%20AI%20catches%20well%20(style%2C%20simple%20bugs%2C%20security%20patterns)%3B%20what%20it%20misses%20(intent%2C%20architecture%2C%20tradeoffs).%20The%20division%20of%20labour%20that%20captures%20both%20speed%20and%20rigour.&eyebrow=Learn AI-assisted code review without losing rigor What AI catches well (style, simple bugs, security patterns); what it misses (intent, architecture, tradeoffs). The division of labour that captures both speed and rigour. https://www.stride.page/learn/test-management https://www.stride.page/api/og?title=Test%20management&subtitle=Keep%20the%20test%20suite%20useful%20as%20it%20grows%20past%2010%2C000%20cases.&eyebrow=Learn Test management Test-case design, traceability, regression strategy, exploratory testing, defect triage — the practices that keep a test suite a safety net rather than a maintenance tax. https://www.stride.page/learn/test-management/test-case-design https://www.stride.page/api/og?title=Test-case%20design%20that%20doesn't%20go%20stale&subtitle=Behaviour-anchored%20Gherkin%20survives%20refactors%20that%20break%20step-anchored%20UI%20tests.%20The%205%20components%20every%20good%20case%20has%2C%20and%20structural%20moves%20that%20age%20well.&eyebrow=Learn Test-case design that doesn't go stale Behaviour-anchored Gherkin survives refactors that break step-anchored UI tests. The 5 components every good case has, and structural moves that age well. https://www.stride.page/learn/test-management/traceability-matrix https://www.stride.page/api/og?title=Traceability%20matrix%20without%20spreadsheet%20hell&subtitle=Manual%20spreadsheets%20drift%20within%20weeks.%20The%20derived-matrix%20approach%20%E2%80%94%20auto-generated%20from%20the%20entity%20graph%20%E2%80%94%20stays%20accurate%20and%20pays%20back%20for%20audit-grade%20compliance.&eyebrow=Learn Traceability matrix without spreadsheet hell Manual spreadsheets drift within weeks. The derived-matrix approach — auto-generated from the entity graph — stays accurate and pays back for audit-grade compliance. https://www.stride.page/learn/test-management/regression-strategy https://www.stride.page/api/og?title=Regression%20strategy%20that%20scales%20past%2010%2C000%20tests&subtitle=At%2010k%2B%20tests%2C%20%22run%20everything%22%20stops%20being%20a%20strategy.%20The%204-tier%20approach%20(smoke%20%2F%20affected%20%2F%20full%20nightly%20%2F%20pre-release)%20keeps%20iteration%20fast%20without%20sacrificing%20coverage.&eyebrow=Learn Regression strategy that scales past 10,000 tests At 10k+ tests, "run everything" stops being a strategy. The 4-tier approach (smoke / affected / full nightly / pre-release) keeps iteration fast without sacrificing coverage. https://www.stride.page/learn/test-management/exploratory-testing https://www.stride.page/api/og?title=Exploratory%20testing%20alongside%20automation&subtitle=Charters%2C%20time-boxes%2C%20observed%20defect%20rates.%20The%20structured%20discipline%20that%20finds%20the%20bugs%20automation%20never%20catches%20%E2%80%94%20UX%20issues%2C%20unexpected%20combinations%2C%20real-world%20data%20quirks.&eyebrow=Learn Exploratory testing alongside automation Charters, time-boxes, observed defect rates. The structured discipline that finds the bugs automation never catches — UX issues, unexpected combinations, real-world data quirks. https://www.stride.page/learn/test-management/defect-triage https://www.stride.page/api/og?title=Defect%20triage%20that%20doesn't%20drown%20the%20team&subtitle=Severity%20%C3%97%20frequency%20%C3%97%20impact%2C%20with%20explicit%20non-fix%20criteria%20and%20SLAs%20per%20severity%20tier.%20The%20process%20that%20prevents%20the%20backlog%20from%20growing%20to%20400%2B%20untriaged%20items.&eyebrow=Learn Defect triage that doesn't drown the team Severity × frequency × impact, with explicit non-fix criteria and SLAs per severity tier. The process that prevents the backlog from growing to 400+ untriaged items. https://www.stride.page/research/engineering-burnout-and-process-debt-2026 https://www.stride.page/api/og?variant=burnout-prevalence-trend&title=Engineering%20Burnout%20%26%20Process%20Debt%202026&subtitle=Engineering%20burnout%20has%20tripled%20since%202019%20by%20some%20measures.%20The%20clinical%20literature%20names%20one%20mechanism%20most%20engineering%20surveys%20miss%3A%20process%20debt.&eyebrow=RESEARCH%20%C2%B7%20WELL-BEING&v=2026-05 Engineering Burnout & Process Debt 2026 Engineering burnout has tripled since 2019 by some measures. The clinical literature names one mechanism most engineering surveys miss: process debt. https://www.stride.page/research/dora-metrics-in-practice-2026 https://www.stride.page/api/og?variant=dora-quartile-distribution&title=DORA%20Metrics%20in%20Practice%202026&subtitle=Seven%20years%20of%20DORA%20Accelerate%20data%2C%20synthesised.%20Plus%20the%20pre-registered%20design%20for%20an%20800-engineering-leader%20segmented%20refresh.&eyebrow=RESEARCH%20%C2%B7%20DELIVERY%20METRICS&v=2026-05 DORA Metrics in Practice 2026 Seven years of DORA Accelerate data, synthesised. Plus the pre-registered design for an 800-engineering-leader segmented refresh. https://www.stride.page/research/sprint-estimation-reality-2026 https://www.stride.page/api/og?variant=sprint-cone-of-uncertainty&title=Sprint%20Estimation%20Reality%202026&subtitle=Forty-three%20years%20of%20estimation%20research%2C%20synthesised.%20Plus%20the%20pre-registered%20design%20for%20a%20500-person%20study%20of%20AI-era%20sprint%20calibration.&eyebrow=RESEARCH%20%C2%B7%20ESTIMATION%202026&v=2026-05 Sprint Estimation Reality 2026 Forty-three years of estimation research, synthesised. Plus the pre-registered design for a 500-person study of AI-era sprint calibration. https://www.stride.page/research/state-of-ai-software-delivery-2026 https://www.stride.page/api/og?variant=research-effect-range&title=State%20of%20AI%20Software%20Delivery%202026&subtitle=What%20the%20existing%20public%20studies%20(DORA%2C%20METR%2C%20Octoverse%2C%20Stack%20Overflow)%20tell%20us%20%E2%80%94%20and%20what%20the%20Stride%202026%20study%20will%20measure%20next.&eyebrow=RESEARCH%202026&v=2026-05 State of AI Software Delivery 2026 What the existing public studies (DORA, METR, Octoverse, Stack Overflow) tell us — and what the Stride 2026 study will measure next.