A Modernization Approach Built for Governance
BBS modernizes legacy training products in review-ready increments—preserving approvals, traceability, and documentation while enabling disciplined delivery.
Why This Approach Works
Every training product touches readiness—and modernization succeeds when the work is reviewable, traceable, and built to sustain.
BBS is designed to help teams:
- Refresh legacy content while preserving review gates and approvals
- Reduce avoidable rework by validating early and often
- Produce consistent artifacts (not just "updated slides")
- Package for LMS delivery with documentation that supports acceptance
"This isn't a shortcut. It's a governed production workflow."
Intake-to-TOMA™ Workflow Preview
A structured workflow that produces artifacts at every phase. Click to explore each phase.
EMBRACE
Scope & Inventory
Confirm what exists, what must change, and how review gates will work. Establish the backlog and the governance plan before production.
Key Artifacts
- Gap Analysis
- Learning Solution Recommendation (LSR)
- Inventory + Baseline (modules, sources, versions)
- Governance + Review Plan (who reviews what, when)
- ATIS Documentation Review (requirements + structure)
- Prioritized Backlog (what gets modernized first)
ENHANCE
Build & Validate
Iterate in reviewable increments. SMEs validate evolving drafts and prototypes while QA/QC and version control run in parallel.
Key Artifacts
- IMPD (updated)
- Living Storyboards (iterative, SME-validated)
- Prototypes / sample builds (as appropriate to scope)
- Assessment Strategy + item plan
- SME Validation Records (feedback captured + disposition)
EXECUTE
Package & Deliver
Finalize builds, package for deployment, and deliver documentation sets that support review, acceptance, and sustainment.
Key Artifacts
- Final builds + source files
- SCORM/xAPI Packages + deployment notes
- QA/QC Logs + issue disposition
- ATIS-aligned documentation package
- Release Notes + Version History
- 508 compliance documentation (as applicable)
How We Run Modernization (Sprint-Based, Governed)
Modernization is executed through structured builds with defined acceptance checks and stakeholder touchpoints.
What to expect in each cycle:
- Sprint planning with clear acceptance criteria
- Reviewable increments (as appropriate to scope)
- Structured SME validation touchpoints (not endless loops)
- QA/QC + revision control captured continuously
- Release notes and version history maintained for each delivery package
(This describes a method—not a promise of speed.)
Deliverables & Review Gates
Each phase produces specific artifacts with defined sign-offs to reduce rework and support confident acceptance.
| Phase | Primary Outputs | Reviews / Sign-offs |
|---|---|---|
| EMBRACE | Gap Analysis, LSR, Inventory/Baseline, Backlog, Governance Plan | PM/COR + SMEs |
| ENHANCE | IMPD, Living Storyboards, Prototypes, Assessment Strategy | SME validation cycles |
| EXECUTE | Final builds, SCORM/xAPI packages, QA/QC logs, ATIS documentation, Release notes | Acceptance checks |
| SUSTAIN | Change-impact briefs, updated packages, lessons learned | Quarterly reviews (or as required) |
Roles (Who Does What)
BBS
Production + Governance Support
Builds, documents, packages, tracks changes, manages QA/QC.
Government / Customer Team
Direction + Approval
Sets priorities, validates requirements, approves releases.
SMEs
Content Validation
Validate accuracy and operational relevance (SMEs validate—never rewrite).
KO/CO/COR/PM
Contract Oversight
Confirms scope, reviews documentation sets, accepts deliverables per contract terms.
Change Control + Traceability
Modernization succeeds when decisions are visible and auditable.
BBS uses:
- Version control with release notes and baselines
- Decision tracking (what changed, why, when, who validated)
- Issue logs with disposition (accept / revise / defer)
- Documentation packages that support acceptance and sustainment
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."
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."
Ready to Start?
Not sure what to modernize first? Start with an Intake Sprint to clarify scope, inventory assets, and build a prioritized backlog with review gates.