Study guide

9.2 SAM, Agile Development and Prototypes

BCSP CIT Certified Instructional Trainer Study Guide 2026

Track your progress as you read

Finished sections get a check mark.

1 Credential and Training Standards

1.1 BCSP CIT Credential Scope, Exam Logistics & Recertification 1.2 ANSI/ASSP Z490 Criteria for Accepted EHS Training Practices

2 Adult Learning and Learning Access

2.1 Foundations of Andragogy: Knowles' Adult Learning Assumptions in Safety 2.2 Learner Literacy, ESL Accommodations & Plain Language Compliance 2.3 Opening a Course: Administrative Items and Learning Expectations

3 Communication and Facilitation

3.1 Verbal & Nonverbal Facilitation Techniques in Safety Training 3.2 Active Listening, Socratic Questioning & Teach-Back Verification 3.3 Feedback Frameworks, Corrective Coaching & Psychological Safety

4 Conflict and Instructional Technology

4.1 Managing Challenging Classroom Dynamics, Resistance & Conflict 4.2 Instructional Media, Presentation Tools & Technology Contingencies

5 Performance Needs and Existing Training

5.1 Performance Gaps and Training Necessity 5.2 Evaluating Existing Training and Interventions

6 Organizational, Task and Hazard Analysis

6.1 Organizational and Job Task Analysis 6.2 Hazard Analysis, KSAs and Task Evidence

7 Audience, Baseline and Prerequisites

7.1 Defining the Audience and Its Learning Needs 7.2 Baseline Knowledge and Prior-Learning Credit 7.3 Verifying Prerequisites and Readiness for Training

8 Applicable Training Requirements

8.1 OSHA Training Frameworks, General Duty Clause & Consensus Standards 8.2 Mandated Safety Programs: Lockout/Tagout, Confined Space & Fall Protection 8.3 Chemical & Biological Hazards: HazCom, Bloodborne & Respiratory Protection

9 Systematic and Iterative Design

9.1 ADDIE and the Systematic Approach to Training 9.2 SAM, Agile Development and Prototypes

10 Objectives and Learning Outcomes

10.1 Writing Observable ABCD Objectives 10.2 SMART, Objective Hierarchies and Stakeholder Consensus

11 Learning Domains and Practice

11.1 Cognitive Learning and Revised Bloom Taxonomy 11.2 Psychomotor, Affective and Constructive Alignment 11.3 Experiential Learning Cycles (Kolb), Adult Discovery & Instructional Scaffolding

12 Delivery Choices and Program Economics

12.1 Modality Matrix: Classroom ILT, E-Learning, Microlearning, Hands-On & OJT 12.2 Cost Classification and Worked Budgets 12.3 Resource Feasibility and Cost-Benefit Decisions

13 Developing and Validating Course Components

13.1 Lesson Plan Architecture: Components of Comprehensive Trainer & Participant Guides 13.2 Job Aids and Performance Support 13.3 SME Selection, Credible Sources and Validation

14 Development Planning and External Providers

14.1 Implementing the Instructional Development Plan 14.2 Deciding When and How to Outsource Development

15 Pilots and Recoverable Records

15.1 Representative Pilots and Course Revision 15.2 Record Retention, Privacy and Recovery

16 Implementation Environments and Logistics

16.1 Physical Classroom Design, Seating Arrangements, Ergonomics & Environmental Controls 16.2 Field, Shop & Hands-On Training: Safety Briefings, PPE Verification & Live Demonstration Safety 16.3 Virtual Instructor-Led Training (VILT), Technical Contingency Planning & Remote Engagement 16.4 Scheduling, Logistics and Course Time Management

17 Assessment and Remediation

17.1 Formative and Summative Assessment Tools 17.2 Assessment Criteria, Alignment and Remediation

18 Items, Performance and Standards

18.1 Writing Clear Items and Plausible Distractors 18.2 Item Analysis and Assessment Data 18.3 Performance Checklists and Evaluator Calibration 18.4 Standard Setting and the Angoff Calculation

19 Evaluation Models, Surveys and Learning Data

19.1 Evaluation Models and Feedback Surveys 19.2 Learning Outcomes and Evaluation Data

20 Transfer and Behavior Evidence

20.1 Transfer of Learning and Work Conditions 20.2 Behavior Observations and Change Reporting

21 Results, ROI and Improvement Reports

21.1 Organizational Results and Causal Limits 21.2 ROI, Course Improvement and Training Reports

9.2 SAM, Agile Development and Prototypes

Key Takeaways Explain This Topic AI

SAM uses preparation, iterative design and iterative development.

Agile increments need acceptance criteria linked to outcomes and risk.

Rapid iteration preserves technical validation and safe release decisions.

Last updated: October 2026

Agile Alternatives: Allen's Successive Approximation Model (SAM)

Iterative development is useful when the team needs early evidence about learner experience or a design alternative. It can be used within ADDIE as well as in other models. Model names alone do not determine speed, documentation quality or regulatory suitability.

To overcome lot delay and late-stage design failure, Dr. Michael Allen introduced the Successive Approximation Model (SAM) . SAM applies agile software development principles to instructional design, prioritizing rapid prototyping, cyclical iteration, and continuous SME collaboration over rigid, sequential handoffs. SAM2 Extended Architecture:

  • [ PREPARATION PHASE ]
  • Information Gathering ===> [ SAVVY START ] (Collaborative Brainstorming & Rapid Sketching)
  • |
  • v
  • [ ITERATIVE DESIGN PHASE ]
  • +---> Prototype Design ===> Review ===> Refine Prototype ---+
  • | |
  • +----------------- (Cycle 3 Times) <-------------------------+
  • |
  • [ Design Proof Frozen ]
  • |
  • v
  • [ ITERATIVE DEVELOPMENT PHASE ]
  • +---> Alpha Build ===> Beta Build ===> Gold Release ---------+
  • | (Usability) (Remediation) (Final Rollout) |
  • +----------------- (Cycle 3 Times) <-------------------------+
  • SAM1: The Compact Cyclical Model

SAM1 is engineered for small, single-designer projects or discrete, low-complexity safety topics (such as an annual 20-minute hazard communication update). SAM1 operates across three perpetual, interconnected steps repeated in rapid micro-sprints:

Evaluate : Review current worker behaviors, error reports, and baseline capabilities.

Design : Immediately brainstorm and sketch a lean instructional intervention.

Develop : Build a rough, functional prototype (e.g., a paper mock-up of a chemical labeling guide) and put it into workers' hands immediately for feedback.

SAM2: The Extended Enterprise Framework

For complex, organization-wide safety initiatives—such as commissioning an entirely new robotic manufacturing line or rolling out an enterprise-wide process safety management (PSM) program—SAM2 provides a structured, eight-step process divided across three operational phases:

Preparation Phase :

Information Gathering : Rapid collection of existing safety procedures, incident logs, and regulatory standards.

The Savvy Start : An intensive, multi-disciplinary kickoff sprint. Rather than spending weeks writing an analysis report in isolation, the instructional designer convenes safety engineers, frontline supervisors, maintenance craftspeople, and equipment operators in a single room. The team actively sketches ideas, challenges operational assumptions, and creates multiple competing rough prototypes.

Iterative design: Build and review prototypes with relevant stakeholders and learners. Use feedback to refine activities and evidence of learning. The number of iterations is determined by the project; there is no universal requirement for exactly three cycles.

Iterative development: Produce increasingly complete versions, validate technical and instructional quality, test representative use, and resolve defects before release. Define what each release must demonstrate instead of assuming that naming it alpha or beta establishes readiness.

Rapid Prototyping and Lot Delay Elimination

Rooted in Tripp and Bichelmeyer's design research, Rapid Prototyping integrates the concurrent execution of analysis and design. In conventional ADDIE, a designer might spend two months drafting technical storyboards before discovering during implementation that the chosen simulator interface is unusable for workers wearing heavy chemical gloves. Rapid prototyping circumvents this catastrophic failure by creating early, low-fidelity mockups (paper prototypes, wireframes, tabletop simulation cards) within days of project initiation.

Note

Rapid prototyping does not discard rigorous needs analysis; rather, it uses the physical prototype as the primary diagnostic instrument to elicit hidden technical requirements from subject matter experts who struggle to articulate nuances on theoretical interview forms.

ISD Model Comparison: Selecting the Optimal Framework

Selecting the correct ISD framework is not an ideological preference; it is a calculated risk-management decision based on project parameters, regulatory oversight, and organizational velocity.

  • Design approach Useful decision principle
  • ADDIE or SAT Trace analysis through design, development, implementation and evaluation
  • SAM Use purposeful design/prototype/review iterations
  • Agile development Prioritize small increments and inspect evidence frequently

All approaches need appropriate validation, documentation and release criteria.

Important

Iteration should preserve applicable requirements, technical validation and evidence of the approved performance. Maintain appropriate decisions and references as the course develops, rather than treating a model name as a compliance guarantee.

Agile work without losing validation

An Agile approach uses small increments, frequent inspection and adaptation. In instructional development, an increment might be a working scenario with feedback, a usable performance checklist or an accessible lesson prototype. A prioritized backlog identifies what to develop next; its items should connect to the learner outcome and identified risk. A finished animation that does not support an objective is not necessarily the most valuable next increment.

Define acceptance criteria before reviewing the increment. For a branching case, criteria can include technically valid decisions, useful feedback, accessible navigation and evidence that representative learners understand the prompt. Test those criteria rather than accepting the work solely because stakeholders like its appearance. Record unresolved issues and decide whether they block release.

  • Prototype evidence Possible design decision
  • Learners misread a critical cue Revise cueing and test again
  • Activity cannot fit the schedule Change scope or timing without losing the objective
  • Reviewer disputes the approved procedure Resolve the source conflict before release
  • Screen-reader use fails Correct access and repeat the relevant check

SAM and Agile do not authorize releasing hazardous misinformation to see whether it works. Technical review, safe pilot conditions and required approvals remain necessary. A smaller reviewable increment can expose an error earlier, but it still needs the right reviewer. Documentation can be maintained alongside each iteration rather than postponed until the final course.

Allen Interactions' SAM process describes preparation, iterative design and iterative development.

Key takeaways

SAM uses preparation, iterative design and iterative development.

Agile increments need acceptance criteria linked to outcomes and risk.

Rapid iteration preserves technical validation and safe release decisions.