Weekly Tasks

Weekly Progress Report

Report your team’s weekly progress in the “Discussions” of your project’s repository in GitHub in blog style – i.e., one blog post per week:

o Each blog contains a description of what you have learned in this week, and links to your project artifacts, such as UML drawing, use case description, burndown chart, Kanban board, etc.
o The post should be published before the next lecture and give other teams enough time to review before the next lecture.
o 1 point per post in time.
o Example.

Peer Reviews

Provide comments on at least two other teams’ posts every week:

o Provide other teams feedback on their blog posts. Please review those who have less than 2 comments.
o 1 point of two reviews in time.
o A full list of all the project blogs will be available in SE-TINF22B6/for-allteams after all of you set up yours.