It’s February and time for a new iteration. This month’s projected goal was to finish up the riverboat problems and code the assessment policy. This breaks down into the following stories:
- Implement 2 more riverboat problems as instructional units. The current riverboat lesson only has one type of problem supported.
- Implement middleware to calculate a score average and update the user’s score total for the last 10 problems, hardcoded. (This would probably be more in real life, but we’re limiting to 10 scores evaluated for easier testing and verification).
- Implement the middleware in previous story to access the DB.
Although these stories will encompass the projected features for this month, I wanted to add some stretch goals to ease next month’s iteration, if possible. They are:
- Determine and display the user’s mastery status for each instructional unit in the class view.
- Determine and display each student’s mastery status to admins in the lesson view.
