A manageable place to start

Technical Sprints. Five focused ways to start.

Start with a focused 5–10-business-day engagement to test an idea, check a result, or plan the next system change. Broader engineering work is scoped separately.

Compare the Sprints

Choose the question you need answered.

Each Sprint delivers the agreed technical outputs, documented findings, known limitations, and a recommendation for the next step.

Download Sprints overview (PDF)
00Flexible technical prototype

Rapid Prototype Sprint

Test one important technical idea before committing to the larger system.

A tested prototype and a documented next decisionExplore this Sprint
01Models & simulation

Model and Simulation Verification Sprint

Check a model's implementation, assess its assumptions, and document where the results support the intended decision.

Verification findings and a decision memoExplore this Sprint
02AI-enabled systems

AI Evaluation and Test Harness Sprint

Define failure modes, implement an executable evaluation harness, and establish measurable performance.

A reusable test harness and documented readiness findingsExplore this Sprint
03RF & technical data

RF and Technical Data Analytics Sprint

Turn radio-frequency (RF), sensor, laboratory, or operational data into a reproducible analytical workflow.

A repeatable workflow and findings packageExplore this Sprint
04OT/ICS, FRCS & cyber-physical systems

Cyber-Physical Systems Assurance Sprint

Assess one system's interfaces, hazards, and security requirements, then prioritize the verification work needed before a change.

A prioritized assurance and verification planExplore this Sprint

Example deliverables

What you receive.

These examples show how a deliverable is organized. They are not customer work. Your package follows the agreed question, scope, and required evidence.

01

Verification evidence package

A reviewable package for a model, simulation, analytical method, or technical workflow.

See what is included
Controlled baseline
Inputs, configuration, intended use, assumptions, and acceptance criteria
Evidence
Reproducible checks, test results, known failure conditions, and sensitivity findings when scoped
Decision handoff
Supported findings, explicit limitations, and a proceed, revise, or stop recommendation
See the verification Sprint
02

Technical prototype handoff

A testable prototype for one technical question before a larger commitment.

See what is included
Working asset
An evaluable prototype tied to one primary workflow and agreed success measures
Technical boundary
Architecture, approved inputs, interfaces, configuration, and known limitations
Next decision
Demonstration results and a documented recommendation to proceed, revise, or stop
See the prototype Sprint

Shared engagement format

Agree the scope before work begins.

Window
5–10 business days after authorization and usable inputs
Focus
One decision, one primary workflow, written acceptance criteria
Handoff
Agreed deliverables, findings, limitations, and a next-step recommendation

Start with the decision

What decision needs credible evidence?

Discuss a Sprint