Hi everyone
In this last sprint I have worked on developing the user stories for the student experience project: Do a Course
The 3 main areas of improvement for the "Do a Course" project are:
- Complete course activities more easily
- Understand my progress in activities and courses
- Show me what I need to do next
- Complete course activities more easily
- Understand my progress in activities and courses
- Show me what I need to do next
The first area is explained here in more detail and will be the first part of the project.
- Complete course activities more easily
- Complete course activities more easily
This entails the following points of friction in the user journey:
1. It is difficult to know which course activity/s I need to complete when they are restricted by another activity/s.
As you can see, this layout and interaction does not look very nice for the student!
There are 5 ways an activity can be restricted and this story will only be looking at the use case where an activity/s is restricted by activity completion.
2. Allow students to mark an activity as complete from within the activity.
Currently students can only mark an activity as complete on the course page level. So we would like to allow students to interact with the same functionality on the activity level. This scenario is only applicable IF manual completion is enabled for the course.
User story links below: