SPEED-BOK v1.4.7

Know SPEED

SPEED — Structured Parallel Engineering for Evolved Deployment — is a way of delivering software in which the specification is authoritative, quality is enforced mechanically, and cooperating roles coordinate through explicit boundaries. This is the map. Every area is a hub; every hub links to what to read, reference, and practice next.

The methodology, mapped

The SPEED Big Picture

Seven knowledge areas, one delivery pipeline. Every element links to tutorials, references, exercises, and field notes — start anywhere and follow the flow.

SPEED-BOK v1.4.7

The forward pipeline

Canon ManagementPreserving and evolving authoritative truth.
CanonicalizationCanon reviewDecision captureGlossary maintenanceCross-reference verification
17 linked piecesExplore
Spec EngineeringProducing specifications at every tier with quality.
Tell authorshipScopingDraftingLinkingValidation framingLifecycle stewardship
20 linked piecesExplore
Flight ExecutionRunning bounded delivery cycles that end with committed work shipped.
Cycle planningDaily synchronizationProgress trackingCycle reviewRetrospection
25 linked piecesExplore
Quality ArbitrationDesigning and running the gates that catch defects early.
Gate specificationGate implementationGate operationFailure analysisGate maintenance
7 linked piecesExplore
Release and DeploymentPromoting validated artifacts safely into live environments.
Release planningEnvironment promotionRelease executionPost-release observationRollback operation
8 linked piecesExplore

The governance & learning loop

Governance and ComplianceMaintaining the records, decisions, and accountability the program requires.
Decision-record maintenanceSteering-file disciplineCanonical-drift monitoringCompliance attestationAccess and authority accounting
9 linked piecesExplore
Observability and Run EventsProducing the operational signal that feeds back into the foundation.
Event specificationSignal captureBaseline establishmentAnomaly detectionFeedback distribution
9 linked piecesExplore
Explore the full Big PictureStart with Spec Engineering

From knowing to running

This map teaches the methodology. Turning it into a running program — a live canon, real gates, a working pipeline — is what the implementor path is for. Start where the practice begins.

Begin the implementor path