Agile Engagement Model

Capability Delivery Sprints

Set the scope, agree on the price, and RDS delivers. Two domain tracks — Enterprise IT and DoD Programs — organized into fixed-cost, customer-steered increments of 2–4 weeks. Your review and approval after every sprint set the course for the next.

2 Domain Tracks Enterprise IT: 22 Sprints / 6 Packages DoD Programs: 30 Sprints / 8 Packages $40K Pilot — $9M+ End-to-End Fixed-Cost CDRL-Mappable

Enterprise IT Catalog (PDF) Defense Programs Catalog (PDF)

Two Domain Tracks — You Steer Every Sprint

Capability Delivery Sprints are organized into two domain tracks, each with its own lifecycle, sprint catalog, and engagement packages. Both tracks share the same core delivery model: RDS delivers working, decision-grade outcomes in focused 2-to-4 week increments, every sprint closes with your review and approval, and your feedback directly shapes what comes next.

Fixed cost per sprint keeps budgeting predictable. Customer-steered scope keeps delivery aligned to enterprise outcomes and mission needs as they evolve — every funding decision rests on delivered results rather than projections.

Enterprise IT Track

Nine-phase lifecycle anchored to TOGAF ADM, ITIL 4, and DevSecOps. Designed for enterprise and civilian-agency IT leaders driving modernization, adoption, and continual improvement.

22 sprint types across 9 phases
6 engagement packages — Capability Pilot through End-to-End
Frameworks: TOGAF ADM, ITIL 4, DevSecOps, BPMN

IT Modernization capabilities →

DoD Programs Track

Ten-phase lifecycle aligned to the DoD Adaptive Acquisition Framework (AAF), the SE “Vee”, the DoD Mission Engineering Guide, and Digital Engineering. Designed for program offices and mission-engineering teams.

30 sprint types across 10 phases
8 engagement packages — Capability Pilot through End-to-End
Frameworks: AAF, SE Vee, Mission Engineering Guide, Digital Engineering, MBSE (SysML v2, UAF, DoDAF)

Defense Programs capabilities →

The Sprint Loop

▶

Deliver in increments

Each sprint produces a defined, working deliverable in 2–4 weeks, measured against acceptance criteria agreed up front.

▶

Review and approve

Every sprint closes with your review of delivered outcomes. You accept the work and confirm direction before the next sprint begins.

▶

Pivot with confidence

Your feedback and approval set the scope of the next sprint. Reprioritize, redirect, or accelerate — the model is built for the true pivot, sprint to sprint.

▶

See value early

Decision-grade outcomes arrive from week two onward, so every funding and milestone decision rests on delivered results rather than projections.

How RDS Delivers — Three Layers in Concert

▶

The Frame — Capability-First Management

A capability map anchors every sprint across both tracks. Business capability decomposition drives architecture, design, code, tests, and deployment. Capability-thread traceability is maintained continuously throughout the engagement.

▶

The Disciplines — Architecture, Design, MBSE

TOGAF ADM, ITIL 4, DevSecOps, BPMN (Enterprise IT) and the SE “Vee”, AAF, DoD Mission Engineering Guide, Digital Engineering, SysML v2, UAF, DoDAF, and MBSE (DoD Programs) — the formalized disciplines that keep capability-thread traceability enforceable in practice. The same senior-led team carries the work from mission analysis through to working capability with full continuity.

▶

The Substrate — AI-Native Tooling, Harnesses, and Process

RDS uses AI in every aspect of the business: internal operations, customer delivery, and delivered products. Collaborative Machines (31-role multi-agent reasoning platform), Cognitive Mesh (mesh coordination harness), a 1,750-clause FAR/DFARS/HHSAR/VAAR library, and a 7-domain enterprise knowledge base — the substrate that makes fixed-cost delivery viable on federal schedules.

Sample packages and price bands are discussion anchors. Final scope, deliverables, and price for any engagement are defined together with the customer before sprint initiation.

Sprint Catalog

Each sprint produces a defined deliverable traceable to the capability map, executed against acceptance criteria agreed before sprint initiation. Mix and match to fit your mission timeline and procurement cadence.

Enterprise IT Track — 22 Sprints across 9 Phases

TOGAF ADM · ITIL 4 · DevSecOps · BPMN. Phases 4–8 iterate per release; governance and management run continuously. See IT Modernization for the full capability view.

Sprint	Phase	Typical Cadence
RDS Validation Sprint	Engage	~2 weeks (min)
Business Architecture Sprint	Vision & Scope	2–4 weeks
Management Sprint	Plan & Govern (continuous overlay)	1–4 weeks, recurring
Planning Sprint	Plan & Govern	1–2 weeks
Program Increment Planning Sprint	Plan & Govern	1–4 days
Contract Delivery Planning Sprint	Plan & Govern	1–4 days
Business Capability & Process Modeling Sprint	Architecture & Design	2–4 weeks
Technical Architecture Sprint	Architecture & Design	2–4 weeks
Solution Architecture Sprint	Architecture & Design	2–4 weeks
Technical Design & Modeling Sprint	Architecture & Design	2–4 weeks
Technical Lead Planning Sprint	Architecture & Design	2–4 weeks
Implementation Sprint	Build & Integrate	2–4 weeks
Configuration Sprint	Build & Integrate	2–4 weeks
Deployment Sprint	Release & Deploy	1–3 weeks
Operational Validation Sprint	Validate & Document	2–4 weeks
Documentation Sprint	Validate & Document	1–3 weeks
Adoption Sprint	Adopt, Operate & Improve	2–4 weeks
Sustainment Sprint	Adopt, Operate & Improve	2–4 weeks, recurring
Maintenance Sprint	Adopt, Operate & Improve	2–4 weeks, recurring
Security Event Sprint	Adopt, Operate & Improve	4 extended days (on demand)
Handover Sprint	Transition & Close	1–3 weeks
After Action Review Sprint	Transition & Close	1–2 weeks

DoD Programs Track — 30 Sprints across 10 Phases

DoD Adaptive Acquisition Framework (AAF) · SE “Vee” · DoD Mission Engineering Guide · Digital Engineering · MBSE (SysML v2, UAF, DoDAF). Formally gated, with sprints mapping to milestone reviews (MCR / SRR / SFR / PDR / CDR / TRR / SVR / OTRR / PRR / ORR) where applicable. See Defense Programs for the full capability view.

Phase 2 — Mission Engineering & Analysis — includes eight dedicated mission engineering sprints, making it procurable as a standalone decision-support study or as part of a full program engagement.

Sprint	Phase	Typical Cadence
RDS Validation Sprint	Engage	~2 weeks
Mission Problem Framing Sprint	Mission Engineering & Analysis	1–2 weeks
Mission Characterization Sprint	Mission Engineering & Analysis	2–4 weeks
Mission Thread Development Sprint	Mission Engineering & Analysis	2–4 weeks
Mission Engineering Thread Sprint	Mission Engineering & Analysis	2–4 weeks
Mission Architecture Sprint	Mission Engineering & Analysis	2–4 weeks
Mission Analysis Design Sprint	Mission Engineering & Analysis	1–3 weeks
Mission Engineering Analysis Sprint	Mission Engineering & Analysis	2–4 weeks
Results & Recommendations Sprint	Mission Engineering & Analysis	1–2 weeks
Management Sprint	Program Planning & Control (continuous overlay)	1–4 weeks, recurring
Planning Sprint	Program Planning & Control	1–2 weeks
Program Increment Planning Sprint	Program Planning & Control	1–4 days
Contract Delivery Planning Sprint	Program Planning & Control	1–4 days
Capability Requirements Sprint	Requirements & Capability Definition	2–4 weeks
Operational Activity Modeling Sprint	Requirements & Capability Definition	2–4 weeks
System Architecture Sprint	Architecture & System Design	2–4 weeks
System Design Sprint	Architecture & System Design	2–4 weeks
Detailed Design & MBSE Sprint	Architecture & System Design	2–4 weeks
Implementation Planning Sprint	Architecture & System Design	2–4 weeks
Implementation Sprint	Implementation & Integration	2–4 weeks
Integration Sprint	Implementation & Integration	2–4 weeks
Operational Validation Sprint	Verification, Validation & Test	2–4 weeks
Documentation Sprint	Verification, Validation & Test	1–3 weeks
Deployment Sprint	Production, Deployment & Fielding	1–3 weeks
Fielding & Training Sprint	Production, Deployment & Fielding	2–4 weeks
Sustainment Sprint	Operations & Sustainment	2–4 weeks, recurring
Maintenance Sprint	Operations & Sustainment	2–4 weeks, recurring
Security Event Sprint	Operations & Sustainment	4 extended days (on demand)
Handover Sprint	Transition & Closeout	1–3 weeks
After Action Review Sprint	Transition & Closeout	1–2 weeks

Milestone review support: MCR (Mission Architecture Sprint) · SRR (System Architecture Sprint) · SFR (System Architecture Sprint) · PDR (System Design Sprint) · CDR (Detailed Design & MBSE Sprint) · TRR · SVR/FCA · OTRR (Operational Validation Sprint) · PRR · ORR (Deployment Sprint).

Sample Engagement Packages

Packages assemble sprint sets into common procurement shapes. Banded price anchors are starting points for vehicle selection; final price is negotiated within the band based on agreed scope and deliverables.

Enterprise IT Track — 6 Packages

Package	Composition	Duration	Price Band
Capability Pilot	RDS Validation Sprint · light-touch Management Sprint	2–3 weeks	$40K–$100K
Discovery Package	Planning · Business Architecture · Technical Architecture · Management	3–12 weeks	$75K–$425K+
Design Package	Planning · Solution Architecture · Technical Design & Modeling · Technical Lead Planning · Management	6–24+ weeks	$149K–$3.4M+
Delivery Package	Planning · Implementation · Configuration · Deployment · Operational Validation · Management	6–48+ weeks	$149K–$9M+
Adopt & Sustain Package	Planning · Adoption · Sustainment · Maintenance · Management	6–48+ weeks	$149K–$7M+
End-to-End Capability Delivery	All sprint types across one or more capability increments	10–48+ weeks	$249K–$9M+

The Capability Pilot is the lowest-commitment entry point — it validates the approach and supports a confident decision on a larger follow-on. Discovery and Design Packages prepare a program for execution. Delivery Package executes a bounded increment. Adopt & Sustain carries the delivered capability through operations and continual improvement.

DoD Programs Track — 8 Packages

Package	Composition	Milestone Support	Duration & Price
Capability Pilot	RDS Validation Sprint · light-touch Management Sprint	—	2–3 weeks · $40K–$100K
Mission Engineering Study	All eight Mission Engineering & Analysis sprints · Management	Informs Milestone A · MCR	6–24 weeks · $149K–$3.4M+
Program Mobilization	Management · Planning · Program Increment Planning · Contract Delivery Planning	—	2–4 weeks · $49K–$198K+
Requirements & Architecture	Planning · Capability Requirements · Operational Activity Modeling · System Architecture · Management	SRR · SFR	3–12 weeks · $75K–$550K+
System Design	Planning · System Design · Detailed Design & MBSE · Implementation Planning · Management	PDR & CDR baselines	6–24+ weeks · $149K–$3.4M+
Build, Integrate & Test	Planning · Implementation · Integration · Operational Validation · Deployment · Documentation · Management	TRR · SVR · PRR	8–48 weeks · $249K–$9M+
Operations & Sustainment	Planning · Fielding & Training · Sustainment · Maintenance · Management	ORR	6–48+ weeks · $149K–$7M+
End-to-End Capability Delivery	All sprint types across one or more capability increments, including the Mission Engineering & Analysis phase	Full milestone cadence	10–48+ weeks · $249K–$9M+

The Mission Engineering Study is procurable as a standalone Milestone A decision-support effort. Program Mobilization is the post-award stand-up package. Sprint price is driven by scope and the resources required to deliver that scope; banded anchors are published per package and the final price is negotiated within the band.

Variants & Modifiers

Compliance environment, joint-delivery, and cadence framework options can be applied to any sprint or package without changing the catalog or pricing model.

Compliance Environment Variants

Any sprint can be executed in a compliance-aware variant when contract context requires it. Variants don't change scope or deliverables — they change the execution environment, evidence collection rigor, and chain-of-custody posture.

CUI / ITAR Variant. Azure GCC High enclave (CMMC L2, C3PAO-assessed via Ariento Corp.). 32 CFR Part 2002 marking compliance on outputs.
CMMC L2 Variant. 110+ NIST SP 800-171 controls operational. Control-mapping summaries for sprint outputs.
DCAA-Audit-Ready Variant. DCAA-ready accounting, timekeeping, and project cost. SF 1408-criteria evidence.

Mentor-Protégé Joint Delivery

Any sprint or package can be executed jointly with a Tier-1 prime mentor under DoD MPP or SBA All Small. Sprint structure and deliverables remain unchanged; resource allocation between mentor and protégé is governed by the mentor-protégé agreement.

Joint sprint outputs carry both mentor and protégé attribution and are eligible for mentor-protégé development credit.

Cadence Framework Selection

The catalog is cadence-framework agnostic. Customer selects the framework that fits their procurement, program rhythm, and team operating model. RDS adapts sprint structure, ceremonies, and deliverable formats accordingly.

• SAFe (Program Increment-aware planning, ART coordination)
• Scaled Scrum (scrum-of-scrums, synchronized sprint reviews)
• DoD Adaptive Acquisition Framework (AAF milestone cadence)
• Traditional SE Vee (SRR / PDR / CDR / TRR phase gates)
• Digital Engineering / MBSE-centric (SysML v2, UAF authoritative models)
• Hybrid (custom blends for prime-led programs)

Commercial Model

▶

Pricing Approach

Fixed cost. Each sprint and package is priced against defined objectives, deliverables, and acceptance criteria. Banded price anchors are published per package; final price is negotiated within band based on agreed scope. Compliance variants may carry an environment premium. Multi-sprint packages may be bundled with package discounts.

▶

Supported FAR Contract Types

Firm Fixed Price (FAR 16.202) is the primary model. RDS also supports Time and Materials (FAR 16.601), Labor Hour (FAR 16.602), Cost-Plus Fixed Fee (FAR 16.306), Cost-Plus Award Fee (FAR 16.405-2), and Performance-Based Acquisition (FAR 37.6) when customer procurement context requires.

▶

Acquisition Pathways

VA Vets First sole source (38 U.S.C. 8127(d), VAAR Subpart 819.70 — up to the $5M services threshold), Simplified Acquisition Procedures (FAR Part 13), VOSB or SDVOSB set-aside competition, GSA Multiple Award Schedule (SIN 54151S, application targeted Q3 2026), prime subcontract under FAR 19.704 with VOSB credit toward the prime's subcontracting plan, and mentor-protégé arrangements.

▶

Customer Assumptions

Customer provides timely access to stakeholders, existing artifacts, and required systems or information. Acceptance criteria are agreed before sprint initiation. Out-of-scope requests are handled through formal change control. Compliance variants and cadence framework are agreed at engagement start.

FFP (FAR 16.202) T&M (FAR 16.601) LH (FAR 16.602) CPFF (FAR 16.306) CPAF (FAR 16.405-2) PBA (FAR 37.6) VA Vets First Sole Source FAR Part 13 SAP

Let's Talk Through the Right Entry Point

Initial conversations cover: mission need or business objective; the capability question that needs answering first; the domain track (Enterprise IT or DoD Programs); the procurement vehicle and contract type that fit; compliance environment requirements (CUI, ITAR, CMMC L2, DCAA); cadence framework preference; and whether mentor-protégé joint delivery applies.

The Capability Pilot ($40K–$100K, 2–3 weeks) is the lowest-commitment entry point — it produces a decision-grade deliverable that validates the approach and supports a confident decision on the path forward.

Start a Conversation Procurement Pathways