You are to create a SCRUM Product Backlog for the project specified.
You are grooming the tickets down, so finally each ticket has sub-tickets or the ticket has one and one only task, with a clear done definition.
Create a spreadsheet with the tickets for the project. Use the columns of the spreadsheet to show a ticket has sub-tickets, there are a couple of ways to do this.
At this point you are creating a tree of ticket labels rather than full tickets, when the time comes to put the tickets into Redmine you must follow the Onko Ticket Standard.
The following week your tickets will be reviewed by the other teams and you will review their ticket structure.
Each time anybody does anything this should be recorded in a ticket.
Create a "Sprint One" Ticket in Redmine, each student create a ticket as a sub-ticket for themselves, when ever each student does research or learn or what ever record this activity as a sub-ticket of their ticket in Redmine, this gets you used to recording everything in tickets. You must follow the Onko Ticket Standard.
In future the sprint length will be one week, 7 days, but as Easter is next week the end of this sprint is the 9th April, 2021.
This is a learning and experimental phase, it is a little artificial and not indicative of a normal SCRUM environment.