This English version of the course material has been machine translated from the Finnish original and may contain errors. If something is unclear, check the Finnish version of this page.
Mini project grading criteria
- Grading criteria for the first sprint
- Grading criteria for the second sprint
- Grading criteria for the third sprint
- Grading criteria for the fourth sprint
- Final steps
You can get at most 11 course points from the mini project according to the following criteria and principles:
- For each sprint, the group can get 2.5 course points, i.e. at most 10 points from the four sprints
- The primary grading criteria are following the process, steady progress and the quality of the features implemented in the program
- The process also includes the ground rules and the retrospectives. What is assessed is that they have been done properly, not what has been decided in them.
- The number of implemented features matters fairly little in the grading, but not zero, i.e. you need to write some code too
- More detailed sprint-specific grading criteria below
- Individual performance is worth -1p … 1p; in exceptional cases -2p or 2p is possible
- The points for individual performance are based on the peer review done at the end and on the “digital footprint” visible in the group’s repository and backlogs
- When assessing individual performance, the following are valued:
- Physical and mental presence
- An active approach
- Reliability
- Smooth group work
- Steady work
- Raising problems constructively and helping others
- Contribution to the group’s outputs (code, tests, deployment pipeline, backlogs)
- Hero coding cannot compensate for otherwise deficient group work
- Also take the working time of about 6 hours per sprint seriously. Going well over the working time does not bring “extra points”, rather the opposite.
Unjustified non-participation in any sprint leads to failing the mini project.
Grading criteria for the first sprint
The project must be registered in the submission app https://study.cs.helsinki.fi/stats/courses/ohtu-2026.
- One group member logs in to the system and goes to the miniprojects tab
- Creates the project with the form opened by the create project button
- And shares the id of the created project with the other group members
- The other group members log in to the system and join the group using the id with the form opened by the join project button
Every group member must be registered in the project by the customer meeting held at the end of the first sprint at the latest.
- Group members who have not registered by the customer meeting of the first sprint do not get the group’s points for the sprint
Links to the project’s backlogs and other documents (and the whole world must have read access to them), and to GitHub Actions (or another CI service in use) must be put in the README of the project’s GitHub repository!
Points are awarded for the following:
- (0.25p) GitHub README:
- The README contains a link to the group’s ground rules (the file
pelisaannot.md, see tips for group work)- Only the fact that the ground rules have been drawn up is assessed, not their content
- The README contains a link to the backlogs (and the whole world has read access to them)
- The definition of done is written down explicitly
- A link to the application running on the OKD cluster (it is enough that the boilerplate or the first story of the sprint works there)
- The README contains a link to the group’s ground rules (the file
- (0.25p) product backlog
- The backlog is DEEP (the stories do not need to be estimated)
- (0.25p) sprint 1 backlog
- The user stories selected for the sprint are split into technical-level tasks
- The progress of the sprint is tracked based on the finished tasks with a burndown or burnup chart
- The chart can be, e.g., one drawn automatically by GitHub Projects
- Each task shows who is working on it
- The status of each task is visible (e.g. todo, doing, done)
- (0.25p) the acceptance criteria of the user stories selected for sprint 1 are written down
- (0.25p) testing
- The project has at least one Robot test written by the group itself (the ready-made tests of the boilerplate do not count)
- (0.25p) continuous integration
- The project’s code is on GitHub
- GitHub Actions runs the tests and they pass
- (0.25p) implementation
- At least one of the stories agreed for the sprint goal is implemented at the level required by the definition of done
- the stories are assessed in the version running on the OKD cluster: if the application does not work in OKD, you get at most half of the points for this item (0.125p)
- (0.25p) the work has been done steadily
- All the work must not have been done on a single day
- (0.25p) GitHub has a sensibly defined .gitignore and the repository contains no files that do not belong there
- (0.25p) the group has prepared properly for the sprint review
- The person running the review has been agreed on and the necessary preparations have been made in advance
- During the review, the user stories selected for the sprint that have been implemented according to their acceptance criteria are demonstrated to the customer
The maximum for the sprint is 2.5 points.
Retrospective
- A retrospective must be held at the end of sprint 1
- Instructions for holding a retrospective can be found in the mini project instructions
- Short notes on the retrospective must be written in the file
retro.mdplaced in the root of the project repository - Based on the observations of the retrospective, at least three concrete improvements must be identified, i.e. things in which the team improves its way of working in the next sprint
- it must be possible to check at the end of the sprint whether an improvement was carried out: e.g. every pull request is reviewed before merging rather than we communicate better
- the improvements are written down in the notes and added to the backlog of the next sprint as tasks of their own, each with a person responsible
- At the beginning of each retrospective, the improvements from the previous retrospective are reviewed, and the notes record how each one was carried out (yes / partly / no) and why
- Based on the retrospective, it is also a good idea to update the group’s ground rules when needed
- The retrospective affects the scoring of sprint 2
Grading criteria for the second sprint
Points are awarded for the following:
- (0.25p) product backlog
- The backlog is DEEP (the stories do not need to be estimated)
- (0.25p) sprint 2 backlog
- The user stories selected for the sprint are split into technical-level tasks
- The progress of the sprint is tracked based on the finished tasks with a burndown or burnup chart
- Each task shows who is working on it
- (0.25p) the acceptance criteria of the stories selected for sprint 2 are written down
- (0.25p) at least some of the stories are tested at the story level (with Robot Framework)
- (0.25p) the application has at least one unit test written by the group itself (the ready-made tests of the boilerplate do not count)
- like in the boilerplate, the tests can be written with the unittest library, and they are run with pytest
- you should read this note on testing
- (0.25p) continuous integration
- The CI service runs the tests
- the main branch is not broken at the end of the sprint
- (0.125p) sensible Pylint rules have been defined for the project and they are checked by CI
- (0.25p) most of the user stories of the sprint are implemented at the level required by the definition of done
- the stories are assessed in the version running on the OKD cluster: if the application does not work in OKD, you get at most half of the points for this item (0.125p)
- (0.125p) a release has been created on GitHub of the working version shown in the demo.
- the release must have a sensible name and description, see an example e.g. here
- (0.125p) A retrospective has been held at the end of sprint 1, proper notes have been made of it, and they contain at least three concrete improvements
- (0.25p) The improvements from the sprint 1 retrospective are tasks in the sprint 2 backlog, and the team has acted on them
- (0.125p) the group has prepared properly for the sprint review
- The review is run by a different person than in the previous review
- The person running the review has been agreed on and the necessary preparations have been made in advance
- During the review, the customer is shown that each user story selected for the sprint has been implemented according to its acceptance criteria
- Hold a retrospective at the end of the sprint; the points for the retrospective are given in the grading of sprint 3, see the instructions
The maximum for the sprint is 2.5 points.
Grading criteria for the third sprint
Coming later!
Grading criteria for the fourth sprint
Coming later!
Final steps
Coming later!
Make sure that your commits show up correctly on GitHub
Since the number (and quality) of the commits made to GitHub affects your individual points, make sure that you have configured your email address in Git (see exercise 2 of the week 1 exercises), that your username shows up correctly in the repository’s commit list when you commit to your group’s repository, and that your username appears in the repository’s contributors list.
It is recommended that everyone makes one test commit (from their own machine) right at the start and checks that Git has been configured correctly.
Pair programming and commits
If you pair program (you should!), you can make the commits show up for both of you by following these instructions.
Missing commits
If your commit shows (despite configuring Git’s email address) a grey symbol like the lower one of the following

Click the name of the grey commit to see the email address that is attached to the commit but that GitHub does not recognise as yours.

Add the address in the settings menu:
