You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fred suggested a very good idea so putting it here - Feel free to elaborate more on this @FredericoCoelhoNunes!
One thing we can do to increase the learning curve for the students is to provide personalized feedback immediately after the presentations and discuss what they have done correctly or what could have done better. At the moment, they don't receive any feedback and it'd be hard to know what to improve. Even though we have always encouraged them to seek feedback, from my experience, not many of them have done so. So instead of relying on the students to take the initiative, I really think that we should allocate a time box to provide feedback to all the teams.
Now, a few discussion points:
How should we provide feedback? e.g. in public or 1-on-1 with the team?
How we can allocate time for this? E.g. One thing we can do is to (1) have a clear criterion on Hackathon grading (See linked issue) and therefore (2) be able to divide students in 2 rooms without compromising grading's objectivity and fairness
The text was updated successfully, but these errors were encountered:
Fred suggested a very good idea so putting it here - Feel free to elaborate more on this @FredericoCoelhoNunes!
One thing we can do to increase the learning curve for the students is to provide personalized feedback immediately after the presentations and discuss what they have done correctly or what could have done better. At the moment, they don't receive any feedback and it'd be hard to know what to improve. Even though we have always encouraged them to seek feedback, from my experience, not many of them have done so. So instead of relying on the students to take the initiative, I really think that we should allocate a time box to provide feedback to all the teams.
Now, a few discussion points:
The text was updated successfully, but these errors were encountered: