Skip to content
BoKSA

Delivering your work

Delivering your work

Everything you deliver goes into one of two systems. There is no third place, and nothing is delivered by email, chat or a shared drive.

GitLab Portflow
What goes here The team's work on the project Your personal portfolio
Examples Code, the Issue Board, user stories and learning stories, technical documents, research reports, client meeting minutes, meeting reports, retro reports Collaboration contract, SMART learning goals, personal reflections, self-evaluations, all feedback you receive
Whose is it The team's — shared, versioned, reviewed Yours — personal, individual, assessed

The rule of thumb: work on the project ends up in GitLab. Anything personal — reflection, your learning goal, the collaboration contract, feedback you received — is delivered directly in Portflow.

The two are linked, not separated. When project work in GitLab is also evidence for one of your learning outcomes, you do not copy it into Portflow. You add it in Portflow as evidence of the type Add link, using a GitLab permalink, so the exact version stays attached.

Use a permalink, not a branch URL

A link to a file on main changes as soon as someone commits. In GitLab, open the file, press y, and copy the URL from the address bar — that URL points at one fixed commit and will still show the same version months later, when the assessment committee looks at your portfolio.

Set up Portflow

Do this in the first days of the semester. Without this your teachers cannot see your work and cannot give you feedback that counts.

  • Import the template using the template ID your teachers give you. Do not create your own sections, collections or goals — stick to the template.
  • Invite your teachers: tick share entire portfolio, tick feedback visibility, and set automatically revoke access after to academic year so access survives a possible resit. See Invite teachers.
  • Know which collections you use. In the studios these are Project Group, Learning Group and Individual — group project evidence goes in Project Group.
  • Know what goals and sub-goals mean: goals are the learning outcomes, sub-goals are the success criteria you link your feedback to. See Terminology.

Adding evidence

  • Give each evidence item a clear, version-independent name — "Collaboration contract project group X", not "Collaboration contract v2".
  • Add a description: what you made, why, and what you learned from it.
  • Link the evidence to the learning outcome (goal) it belongs to.
  • One piece of work is one evidence item. Do not create a separate item per file; bundle the work and use Portflow's versioning, adding a version note that explains what changed.

Evidence can be a link to GitLab, an uploaded file, an assignment imported from the DLO, or free text. Free text fits things without a product behind them, such as a SMART learning goal or a short reflection — do not write full reports there. See Collecting evidence.

Recording feedback

You write feedback down yourself; that is how you show what you learned from it.

  1. Have the evidence item ready in Portflow before you ask for feedback.
  2. Take notes while you discuss your work.
  3. Write the feedback next to the evidence item with Add Comment — what went well, what can be better, and the follow-up action you will take.
  4. Link the feedback to the sub-goals (success criteria) it is about. Keep the number small; if it fits no sub-goal, link it to the goal, but never to both at once.
  5. Send a Request Comment Validation to the person who gave the feedback, so they can confirm you recorded it correctly.

See Gathering feedback.

Peer feedback

To have a fellow student review your work, share the collection that contains the evidence — never your whole portfolio. Keep the access duration as short as needed, in days rather than weeks, and decide deliberately whether feedback from others is visible to them (by default it is not). See Peer feedback.

Later in the semester

  • Progress Review — when you are to be assessed you do not send a feedback request but a Progress Review request. Name it after the moment, e.g. "Sprint Review - Sprint 3", choose With levels and the scale Numeric 1 - 4 (4 levels), and send it only to the relevant teachers. A teacher cannot assess you without it.
  • Self-evaluation — a Progress Review request where you pick self review instead of a reviewer, and assess yourself on the learning outcomes. See Self-evaluation.
  • Snapshot — at the end of the semester you submit a snapshot of your portfolio for the assessment committee, via Assignments in the DLO. Select all collections and all evidence of the semester.

Full Portflow documentation