CEPD · Module 1 — Production systems and SAM sprints
Allen's Successive Approximation Model is a production rhythm. ADDIE remains a useful checklist. Prototypes exist to make decisions.
About 18 min
Practice in the lesson player
Sorting, matching, quizzes, and the module gate stay behind a free account so scored answers are not public. The teaching notes below are the same cited curriculum.
01
ADDIE as vocabulary: Names the activities: analyse, design, develop, implement, evaluate. · Often run as a waterfall with sign-off at each phase. · Useful checklist that nothing was skipped.
02
Sprint | Output | Decision it supports
0: Savvy start (2 days) | Action map, format log, two-screen prototype | Is this the right practice?
1 (1 week) | Design proof: one complete lesson, both languages | Is the look, voice and RTL layout right?
2 (1 to 2 weeks) | Alpha: all lessons, functional | Is the content correct and complete?
3 (1 week) | Beta and gold: fixes, QC, accessibility report, SCORM | Is it ready to release?
03
Teams often prototype the title screen and the menu because they are easy. That tests nothing. Prototype the screen most likely to fail: the branching scenario no one has written before, the Arabic layout of a complex table, the drag activity on a phone. Michael Allen's point is that prototypes are for decisions. A prototype that confirms what everyone already agreed is a cost with no decision attached.
04
Write a sprint plan for your course using the table on slide 3. Name the riskiest screen and schedule it for sprint 0. Add the plan to your production plan.