Course Development Objectives
The Course Development Process is intended to satisfy the needs of different constituents before a course is added to the library
- Is there demand for the course?
- Do students find the course interesting?
- Does the course meet the SANS standard for quality?
- Can the course run in all delivery modes?
- Is the course easy to teach?
Course Development Process
Proposal - Check Process
- Curriculum Lead
- Advocates for the course idea
- Coaches development of the Proposal
- Curriculum Director
- Advocates for the course idea
- Curriculum Review
- Reviews proposal to ensure completeness and identify gaps
- SANS Leadership
- Reviews proposal before next phase begins
Demonstrate Stability
Beta 1
Steady State
Course Proposal
Convert an Idea into the concept for a Course
First exposure of the course to students
- No significant content changes (revision-level changes only)
- 5 runs
- Capped at 25 students paying full fees
- Taught by both the Author and the Instructor
- Run outside NA to test with an international audience
- Does the course perform as expected?
- Taught by the Author. Observed by Instructor.
- Review by SME
- Capped at 15 students paying 50% fees
- Lab-by-Lab evaluations
- Opportunity for development instructor(s) to observe
- OLT readiness evaluation
- Develop action plan to address issues exposed in Beta 1. Ensure all actions can be corrected before Beta 2.
- Author works with Curriculum Lead and Curriculum Director
- Write the course description
- Identify the target audience and value for students
- Create the course outline and learning objectives
- Detail the topics covered in the course
- Identify labs needed to support the learning objectives
- Identify support needed during course development
Writing
Decide to Release
Beta 2
Develop all the materials for the Course
Refine the course and resolve problems from Beta 1
- Write slides and notes to support the learning objectives
- Create the labs to support the learning objectives
- Need detailed testing (QA testing) to ensure labs:
- Function properly
- Challenge students appropriately (qualitative testing)
- Operate robustly
- Peer review of content to check industry interest
- Bi-weekly check-in by CL
- Progressing along timeline toward Beta 1
- Taught by Instructor. Observed by Author.
- Reviewed by SME
- Capped at 20 students paying 75% fees
- Lab-by-Lab evaluations
- Opportunity for development instructors to observe
- Expect better results than Beta 1
- Validation of corrections made
- More fine-tuning, no major issues