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/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/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/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/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/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/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/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/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/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/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/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/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/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-pair-programming https://www.stride.page/api/og?title=AI%20pair%20programming&subtitle=AI%20pair%20programming%20is%20the%20practice%20of%20working%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%20comple&eyebrow=Glossary AI pair programming AI pair programming is the practice of working alongside an AI coding assistant (Claude, Copilot, Cursor, Continue) as a continuous collaborator on coding tasks — suggesting completions, generating te 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/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/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/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%20is%20the%20practice%20of%20estimating%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.%20C&eyebrow=Glossary Capacity planning Capacity planning is the practice of estimating 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 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%20is%20the%20practice%20of%20deliberately%20injecting%20failures%20into%20production%20(or%20production-like)%20systems%20to%20validate%20they%20recover%20gracefully.%20Pioneered%20by%20Netflix%20with%20Cha&eyebrow=Glossary Chaos engineering Chaos engineering is the practice of deliberately injecting failures into production (or production-like) systems to validate they recover gracefully. Pioneered by Netflix with Chaos Monkey in 2010, t 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/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%20is%20the%20practice%20of%20having%20another%20engineer%20evaluate%20proposed%20changes%20before%20they%20merge.%20It%20catches%20bugs%2C%20enforces%20style%20consistency%2C%20distributes%20knowledge%20across%20the%20te&eyebrow=Glossary Code review Code review is the practice of having another engineer evaluate proposed changes before they merge. It catches bugs, enforces style consistency, distributes knowledge across the team, and surfaces des 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%20the%20lifecycle%20of%20a%20software%20project%2C%20first%20articulated%20by%20Barry%20Boehm%20in%20his%201981%20book%20Software%20Engineering%20Economics&eyebrow=Glossary Cone of Uncertainty The Cone of Uncertainty is a model of estimation variance over the lifecycle of a software project, first articulated by Barry Boehm in his 1981 book Software Engineering Economics. Estimates made at 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-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/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/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/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/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/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/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/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/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/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/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/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-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/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/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/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/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/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/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/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/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/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/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/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/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/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%2C%20developed%20by%20Noriaki%20Kano%20in%201984%2C%20is%20a%20framework%20for%20categorising%20product%20features%20by%20their%20non-linear%20relationship%20to%20customer%20satisfaction.%20The%20five%20categories%3A%20&eyebrow=Glossary Kano model The Kano model, developed by Noriaki Kano in 1984, is a framework for categorising product features by their non-linear relationship to customer satisfaction. The five categories: Basic (expected — ab 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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/shape-up https://www.stride.page/api/og?title=Shape%20Up&subtitle=Shape%20Up%20is%20Basecamp's%20product-development%20methodology%2C%20published%20as%20a%20free%20book%20by%20Ryan%20Singer%20in%202019.%20The%20cycle%20has%20three%20phases%3A%20shaping%20(a%20senior%20PM%20or%20designer%20scopes%20a%206-wee&eyebrow=Glossary Shape Up Shape Up is Basecamp's product-development methodology, published as a free book by Ryan Singer in 2019. The cycle has three phases: shaping (a senior PM or designer scopes a 6-week project with hard 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%2C%20originated%20at%20Google%20around%202003%20and%20codified%20in%20the%202016%20SRE%20book%2C%20that%20applies%20software-engineering%20practices%20to%20operations.%20R&eyebrow=Glossary Site reliability engineering Site reliability engineering (SRE) is a discipline, originated at Google around 2003 and codified in the 2016 SRE book, that applies software-engineering practices to operations. Rather than treating 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/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/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%20is%20an%20organisational%20structure%20for%20engineering%20teams%20%E2%80%94%20described%20in%20two%202012%20papers%20by%20Henrik%20Kniberg%20and%20Anders%20Ivarsson%20%E2%80%94%20that%20arranges%20engineers%20into%20Squads%20(c&eyebrow=Glossary Spotify model The Spotify model is an organisational structure for engineering teams — described in two 2012 papers by Henrik Kniberg and Anders Ivarsson — that arranges engineers into Squads (cross-functional 6-12 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/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%20is%20the%20practice%20of%20breaking%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%20&eyebrow=Glossary Story splitting Story splitting is the practice of breaking 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 e https://www.stride.page/glossary/swarm-pattern https://www.stride.page/api/og?title=Swarm%20pattern&subtitle=Swarming%20is%20the%20practice%20of%20having%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%20&eyebrow=Glossary Swarm pattern Swarming is the practice of having 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 stori 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/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%2C%20codified%20in%20the%202019%20book%20by%20Matthew%20Skelton%20and%20Manuel%20Pais%2C%20is%20a%20framework%20for%20organising%20engineering%20teams%20using%20four%20team%20types%20and%20three%20interaction%20modes.%20Te&eyebrow=Glossary Team Topologies Team Topologies, codified in the 2019 book by Matthew Skelton and Manuel Pais, is a framework for organising engineering teams using four team types and three interaction modes. Team types: stream-ali 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/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/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/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/user-story-mapping https://www.stride.page/api/og?title=User-story%20mapping&subtitle=User-story%20mapping%2C%20formalised%20by%20Jeff%20Patton%20in%20his%202014%20book%20of%20the%20same%20name%2C%20is%20a%20workshop%20technique%20for%20organising%20product%20backlogs%20around%20the%20user's%20journey%20rather%20than%20as%20a%20&eyebrow=Glossary User-story mapping User-story mapping, formalised by Jeff Patton in his 2014 book of the same name, is a workshop technique for organising product backlogs around the user's journey rather than as a flat list. The map 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/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-slicing https://www.stride.page/api/og?title=Vertical%20slicing&subtitle=Vertical%20slicing%20is%20the%20practice%20of%20breaking%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%20deliv&eyebrow=Glossary Vertical slicing Vertical slicing is the practice of breaking work into thin slices that cut through every layer of the architecture — UI, business logic, data, infrastructure — so each slice delivers end-user value i 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/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/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.