Skip to content

Performance

During the course of Smart Cities we are measuring your performance.

We will measure your performance based on the following criteria:

  • How many commits you make to your Gitlab projects.
  • How many tasks you complete in the group project.
  • How many merge requests you create in the group project.
  • How many merge requests you review in the group project.
  • How many hours to spend on the project(s).
  • How much documentation you write for your project(s) in markdown files.

Performance view from DLO

Commits

Every day you work on different parts of your project where you make multiple commits. We expect you to make professional commits on each day you work on one or more parts of your project(s).

A profesional commit is:

  • A commit should be around a function, subject or other small piece of your project you worked on.
  • Should be complete; not only once sentence but also not your whole project at once.
  • Commit message is well written in such a way it’s understandable what the changes are about.
  • The commit is pushed from your own HvA-account.
  • Push your commits to the remote server directly, don’t collect them and push them at once.

Tasks

In your group project you and your teammates are working on User Stories which include Tasks. You are expected to be assigned to tasks and to complete them.

Merge Requests

Each User Story has one Merge Request associated with it. You are expected to create a Merge Request when you get assigned to this User Story. The Merge Request takes care of creating a branch for you which you, or teammates, can use to work on the User Story.

For the Merge Request to count as reviewed by you, you should:

  • Assign yourself to the Merge Request, only one assignee is allowed.
  • Close/Merge the Merge Request by yourself.

Hours

Most likely you will be working on different project(s) during the course. To keep track of the hours you spend on the project(s), you are checking-in and out of the project(s) in DLO.

  • Check-in the project(s) you are working on.
  • Check-out the project(s) you are not working on.

Check-in’s will be automatically closed after 8 hours of inactivity with zero hours being logged.