Grading policy #

Points distribution:

Weekly progress — 72 points (6 weeks x 12 points)
- Report — 4 points
- Implementation with noticeable progress — 4 points
- Personal contribution — 4 points
Final presentation — 28 points
Project deployment — Extra 5 points

Grades distribution:

D - [0, 60]
C - [60, 75]
B - [75, 90]
A - [90, +inf]

Weekly progress evaluation #

The report should be written simply and clearly, imagine that you are writing instructions on how to create your project from scratch, describe your decisions and how you came to them.
Each report should contain:
- A full description of the contribution of each participant with artifacts of the work (pull requests, commits, links to files in the repository or other relevant artifact)
- Detailed plans for the next week (what are you going to do next week)
- Description of the solution of weekly tasks

Your master branch must contain working code at any point in time. Make sure to put your solution in docker container, or make a proper documentation to run it simple way. If TA is not able to reproduce your solution (locally, in google colab or other), then it is considered as not working and you get 0 points for the implementation part.
The progress for the week should correspond to the number of participants in your team. There should be no participants who have not done anything in a week.

In the report and at the weekly meeting with TA, each participant must clearly explain their contribution for the week. The absence of work artifacts will result in 0 points for this part.

Your presentation should be organized and structured in a way that describes the development process and narrates a story of how you identified the problem and how you solved it.
Avoid overloading your audience with text. Your presentation should be clear and concise, with illustrations and short accompanying text.
People like stories, so tell yours! Share the challenges you faced, the mistakes you made, and the lessons you learned. This will show that you are a team that is willing to learn and adapt.
Use the talents of your team members to create a dynamic and engaging presentation. For example, if you have someone on your team who is passionate about frontend development, let them tell the part of the story that covers frontend development.
Your presentation should be short, only 10 minutes long. This means that you will need to be selective about what you include - choose the most important parts of your story and leave the rest.

The deadline for the submission of the reports is Wednesday 23:59:59.

Late submission policy:

every one hour after the deadline cost 5 percent of the whole week grade
- for example, if you submit the report at Thursday 00:00:00, you will lose 5% of the grade
- if you submit the report at Thursday 01:00:00, you will lose 10% of the grade
- and so on
after 20 hours (Thursday 19:00:00) - you loose all points

If you have any questions, please, contacts us in telegram.

Best regards,

The Capstone Project Team