Productized Services for Training Modernization
Agile, sprint-based delivery that produces reviewable increments—while preserving governance, review gates, and documentation.
What's Changing (and How BBS Helps)
Acquisition reform is shifting expectations toward modular delivery, right-sized risk, and sustainment-ready outputs. BBS aligns modernization work to that intent—without sacrificing documentation discipline.
| What's Changing | What It Means for Training | How BBS Supports (GovCon-safe) |
|---|---|---|
| Speed-to-need cycles | Shorter windows for usable increments | 90–150 day sprint planning + release-based delivery packages (scope-dependent) |
| Right-sized thresholds | Simplify where risk is low | CO/COR-friendly documentation sets + audit-ready evidence trails |
| Modular / MOSA thinking | Build for sustainment + swap/upgrade | Modular course architecture (SCORM/xAPI-ready), reusable components |
| Workforce capability | Upskilling + continuous learning | Modern learning design + workforce development support |
| Agile workforce development | Continuous learning at speed | Sprint-based delivery with PSP 6 & 7 integration; workforce enablement playbooks |
Note: Planning ranges describe a method and typical structuring approach—not a promise of cycle time.
Design & Development Artifacts (TDC + ATIS)
BBS produces training development artifacts aligned to TDC workflows and structured to support ATIS documentation needs.
| Artifact | Purpose | Phase |
|---|---|---|
| Gap Analysis | Identifies delta between current training state and doctrine/mission requirements | EMBRACE |
| Learning Solution Recommendation (LSR) | Documents recommended approach, modality, and delivery strategy | EMBRACE |
| IMPD | Defines media requirements, interactions, and technical specifications | EMBRACE / ENHANCE |
| Living Storyboards | Iterative storyboard artifacts evolving through SME validation | ENHANCE |
| Assessment Strategy | Defines evaluation approach, test items, and performance measures | ENHANCE |
| SCORM/xAPI Packages | LMS-ready deliverables with deployment notes and tracking guidance | EXECUTE |
| QA/QC Logs | Documented quality checks, issue disposition, and remediation tracking | EXECUTE |
| ATIS Documentation | Artifacts formatted and structured to support ATIS documentation requirements | EXECUTE |
Service Packages
Choose the package that matches your starting point. Each package is designed to produce clear deliverables, traceable documentation, and predictable review touchpoints.
Purpose: Establish a clear modernization baseline—what exists, what's outdated, what's missing, and what should be prioritized—so stakeholders can make scoped, low-risk decisions before build work begins.
In Scope
- Intake kickoff + stakeholder alignment (governance, constraints, review cadence)
- Content and asset inventory (modules, lessons, media, assessments, source files)
- Baseline documentation review (as provided) to identify gaps and update needs
- Gap analysis against current requirements (doctrine/policy/mission requirements as applicable)
- Learning Solution Recommendation (LSR) development/refinement (as applicable)
- Initial modernization backlog (prioritized work items with assumptions + dependencies)
- Definition of Done (DoD) + acceptance criteria draft for modernization deliverables
- QA/QC + revision control approach (issue log structure, versioning, traceability)
- 508-aware posture review (process-level; identify likely remediation needs)
Deliverables
- Modernization Intake Summary (Word)
- Inventory + Asset Register (Excel/Sheets)
- Gap Analysis (Word)
- Learning Solution Recommendation (LSR) (Word) (if required by scope)
- Prioritized Backlog + Release Plan (Excel/Sheets)
- Governance + Review Plan (Word)
- Definition of Done + Acceptance Criteria (Word)
- QA/QC + Revision Control Checklist (Word)
- 508-Aware Considerations Memo (Word)
Agile Element: Time-boxed intake delivered as a structured sprint, producing a reviewable baseline package and an executable backlog.
Acceptance Checks
- Inventory captures all known modules/assets with location, format, and version notes
- Gap analysis identifies what must change and why (in stakeholder language)
- Backlog is prioritized and includes assumptions/dependencies and proposed review gates
- Governance plan defines who reviews what, when, and how changes are approved
- Acceptance criteria and Definition of Done are documented for future execution
Purpose: Modernize a defined batch of lessons/modules into reviewable, LMS-ready releases—while preserving governance, documentation, and SME validation.
In Scope
- Update or create IMPD for the batch (as applicable)
- Develop Living Storyboards through structured SME validation touchpoints
- Update scripts/narration text (as required by scope)
- Rebuild or refresh content in Articulate Rise/Storyline (source files maintained)
- Refresh/update media assets where required (graphics, audio, video)
- Build/update assessments and feedback logic (as applicable)
- Maintain QA/QC logs, issue disposition, and revision control
- Integrate 508-aware practices during development (documented)
- Create SCORM/xAPI packaging and deployment notes
- Produce ATIS-aligned documentation package (as scoped)
Deliverables
- Updated IMPD (Word/PDF as required)
- Final Living Storyboards + SME validation records
- Updated Rise/Storyline source files + publish outputs
- SCORM/xAPI packages + deployment notes (ZIP + Word)
- QA/QC log + change log/version history
- 508 documentation notes (remediation actions and checks performed)
- ATIS-aligned documentation set for the release/batch
Agile Element: Work delivered in time-boxed sprints (e.g., 2-week increments as appropriate to scope), with planned SME validation gates and review-ready increments at each checkpoint.
Acceptance Checks (deliverable-based)
- Scope baseline and batch list confirmed (lessons/modules, versions, priorities)
- Storyboards validated by SMEs with recorded disposition of comments (SMEs validate—never rewrite)
- QA/QC log completed for the batch, with defects dispositioned and tracked to closure
- Accessibility checks documented (508-aware practices applied and recorded)
- Packages produced and verified against agreed pre-deployment checks (LMS-ready packaging + notes)
- Release notes/version history delivered with the final package set
Purpose: Keep training current through a repeatable sustainment rhythm—monitor changes, assess impact, execute prioritized updates, and maintain traceability and packaging readiness.
In Scope
- Change-impact monitoring inputs (provided by customer or mutually defined sources)
- Change-impact analysis (what changed, what it affects, recommended update actions)
- Backlog grooming + prioritization for the update cycle (scope, sequencing, dependencies)
- Targeted lesson/module updates (content, interactions, assessments as scoped)
- Structured SME validation touchpoints (review package + feedback disposition)
- QA/QC log maintenance + issue disposition tracking
- Version control + release notes + baseline management
- 508-aware remediation activities aligned to update scope
- Packaging support (SCORM/xAPI-ready outputs where applicable) + deployment notes
- Lessons learned capture and feed-forward into the next cycle (PSP 7)
Deliverables
- Quarterly Change-Impact Brief (Word/PPT)
- Updated Backlog + Release Plan (Excel/Sheets)
- Updated Lesson/Module Packages + Source Files (as applicable)
- SME Review Package + Validation Record (PPT/Word)
- QA/QC Log + Issue Disposition Report (Excel/Word)
- Release Notes + Version History (Word)
- 508 Remediation Notes/Checklist (Word)
- Deployment Notes (Word)
- Lessons Learned Summary (PSP 7-aligned) (Word)
Agile Element: Quarterly cadence built around a prioritized backlog and increment-based delivery—each cycle produces a reviewable release package and an updated baseline.
Acceptance Checks
- Change-impact brief is delivered and reviewed (what changed + recommended actions)
- Update backlog is approved for the cycle with defined scope boundaries
- SME validation is documented (what was reviewed, feedback disposition, approvals)
- QA/QC log shows checks performed and issues resolved or deferred with rationale
- Release notes and version history reflect all updates made during the cycle
- Packages and deployment notes are provided in agreed formats where applicable
Agile Delivery + Continuous Improvement
BBS uses sprint-based delivery with structured stakeholder/SME touchpoints. Each sprint produces a reviewable increment, followed by a retrospective that feeds improvements into the next cycle.
Continuous Improvement (PSP 6 & PSP 7)
PSP 6 — Implement
Deploy the training, execute the release plan, confirm adoption steps.
PSP 7 — Evaluate
Measure effectiveness, capture findings, and identify gaps.
Feed Forward
Lessons learned roll into the backlog for the next sprint/update cycle.
Sprints produce reviewable increments; PSP 7 feeds improvements forward.
Human-Led. AI-Assisted. Governance Preserved.
"Human-led, AI-assisted; human review maintained; AI accelerates drafting/consistency checks and QA support; does not replace SMEs or approval authorities; does not provide source-selection influence."
Ready to Start?
Not sure which package fits? Start with an Intake Sprint to clarify scope and build a prioritized backlog.
🎯 Low-Risk Entry Point
Test us with 1–2 lessons. We'll modernize a sample lesson from your existing curriculum—so you can evaluate our approach, quality, and turnaround before committing to a full engagement.
Ideal for risk-conscious buyers who want proof of capability before scaling.