Mastery Evaluations

Stages of Backwards Design

1. Identify desired results
   • Program goal
   • Learning objectives
2. Determine assessment evidence
   • Mastery evaluations
   • Interactive quizzes
3. Plan learning experiences and instruction
   • Content
   • Formative assessments

(i.e. drills, mini-projects, etc)

#Goals

Uniformity, Transparency, Accountability

• Reduce admin extensions related to capstone confusion
• Reduce/exterminate instances of students who reach month 6 without the skills to graduate
• Pinpoint weak spots in the curriculum

Uniformity

• Why?
  • Reusable infrastructure
  • Ease of generating new evals
  • Predictable evals are more transparent*
• How?
  • All evals (regardless of program) will have two components
    • Project
    • Question set
  • Implementation will differ depending on the constraints of the eval call

Transparency

• Why?
  • Reduce student anxiety
  • Empower students and mentors
  • Reduce admin extensions related to capstone confusion
• How?
  • Provide specific breakdowns of how students will be scored on each section of the eval
  • Provide specific project rubrics

Accountability

• Why?
  • Students need to know how they're doing in order to grow
  • Reduce/eliminate instances of students who reach month 6 without the skills to graduate
• How?
  • Decrease time to feedback to enforce blocks on moving forward
  • Students must PASS not just take mock interviews

Rollout Schedule

• WEB-DEV-001: Rolled out in Oct
• WEB-DEV-002/Git: Rolled out in Nov
• DATA-201-PREP: Rolled out in Nov
• REACT-001: Done, shipping this week
• NODE-001: In progress, shipping this week

Updates

• We shipped quizzes for Git!
• Quizzes in progress for the rest of Web Dev
• New eval for React
• Final capstone moving to React
• New onboarding materials for interviewers