Industrial Project: course site proposal

The 15-minute tour

One semester, followed through the people who live it. Each step below was recorded by a browser script on the live prototype at the checkpoint named, logged in as that person. Where a step shows a form being filled in, it was really submitted.

To see a step yourself, ask for the site to be switched to its checkpoint, then log in as the person shown (see Try it).

1. Customer submits a proposal; the AI review; revisions

Checkpoint: call-open
Video of the whole step
A customer fills in the proposal form in the portal
customer-1 (Greta Olsen): A customer fills in the proposal form in the portal
The customer's own proposals, with their review status
customer-1 (Greta Olsen): The customer's own proposals, with their review status
The museum's proposal in the portal, after three review rounds
customer-4 (Clara Moreau): The museum's proposal in the portal, after three review rounds
The coordinator's view: the AI review comments and the customer's replies, round by round
coordinator (Ruth Ellison): The coordinator's view: the AI review comments and the customer's replies, round by round

2. Brief beside sealed specification; a student is refused

Checkpoint: pitch-day
The public brief of project P4
coordinator (Ruth Ellison): The public brief of project P4
Its sealed specification: requirements tagged by how a student can find them
coordinator (Ruth Ellison): Its sealed specification: requirements tagged by how a student can find them
A student sees the brief in the project catalogue
student-9 (Nora Lindqvist): A student sees the brief in the project catalogue
The same student asking the API directly for the sealed specification: refused (403)
student-9 (Nora Lindqvist): The same student asking the API directly for the sealed specification: refused (403)

3. Student ranks projects; the assignment, a swap and an appeal

Checkpoint: pitch-day
Video of the whole step
A student ranks three projects; the avoid list is private to the coordinator
student-9 (Nora Lindqvist): A student ranks three projects; the avoid list is private to the coordinator
The solver's result: rules, seed, satisfaction statistics, and the avoid list that mattered
coordinator (Ruth Ellison): The solver's result: rules, seed, satisfaction statistics, and the avoid list that mattered
Requests after the results: a swap both sides asked for (granted) and an appeal (declined, with a reason)
coordinator (Ruth Ellison): Requests after the results: a swap both sides asked for (granted) and an appeal (declined, with a reason)

4. Weekly report, returned by the customer, and the sign-off trail

Checkpoint: week-2
Video of the whole step
Week 2 report in the student portal: resubmitted after the customer returned it
student-9 (Nora Lindqvist): Week 2 report in the student portal: resubmitted after the customer returned it
The team writes its week 3 report and submits it for sign-off
student-9 (Nora Lindqvist): The team writes its week 3 report and submits it for sign-off
The customer asks for changes from the sign-off form (one click from the e-mail)
customer-4 (Clara Moreau): The customer asks for changes from the sign-off form (one click from the e-mail)
The mentor's view: the report is back with the team (state: Changes Requested)
mentor-4 (Paul Mercer): The mentor's view: the report is back with the team (state: Changes Requested)
Every sign-off is its own record: who, when, round, decision and comment
mentor-4 (Paul Mercer): Every sign-off is its own record: who, when, round, decision and comment

5. Course manager: the dashboard in week 6

Checkpoint: week-6
Video of the whole step
The course dashboard in week 6
manager (Martin Ekdahl): The course dashboard in week 6
All teams by week: on time or late, mentor and customer sign-off (✓ signed, ✗ changes requested, – no response)
manager (Martin Ekdahl): All teams by week: on time or late, mentor and customer sign-off (✓ signed, ✗ changes requested, – no response)
Needs attention: every item links to its source record
manager (Martin Ekdahl): Needs attention: every item links to its source record
Into the team that is behind: its milestones on the Gantt
manager (Martin Ekdahl): Into the team that is behind: its milestones on the Gantt
Its weekly digests for the mentor
manager (Martin Ekdahl): Its weekly digests for the mentor

6. Presentation day: briefing, score, merged feedback

Checkpoint: mid-semester
Video of the whole step
Mentor of T1 and T9 reads the briefing on T4, with questions per student
mentor-1 (Karin Holm): Mentor of T1 and T9 reads the briefing on T4, with questions per student
Scoring T4 on the presentation day: the same short form for every mentor
mentor-1 (Karin Holm): Scoring T4 on the presentation day: the same short form for every mentor
Presentation-day board: order, room and scores received out of eight
manager (Martin Ekdahl): Presentation-day board: order, room and scores received out of eight
T4's mentor sees the merged feedback draft, edits it and approves it; it goes to the students as a PDF
mentor-4 (Paul Mercer): T4's mentor sees the merged feedback draft, edits it and approves it; it goes to the students as a PDF

7. Decision sheet and calibration

Checkpoint: final-day
Decision sheet for T3: every source linked
manager (Martin Ekdahl): Decision sheet for T3: every source linked
Calibration: one mentor scores about 1.5 points lower on every team
manager (Martin Ekdahl): Calibration: one mentor scores about 1.5 points lower on every team
Grade records: the mentor recommends, the course manager decides and notes why
manager (Martin Ekdahl): Grade records: the mentor recommends, the course manager decides and notes why

Closing: what the system caught

See the planted situations: every one of them is checked by script after every checkpoint.