Project Development Weekly Progress Report

This template will be used to create a weekly progress report for your project. The report should be submitted at the end of the lab session unless mentioned otherwise. The report should be written in Markdown format and saved as lab_report_<week_number>.md in the reports folder of your team's repository. You should always refer to previously created issues, action items, pull requests and other project development artifacts when writing the report. In short, the report provide a summary of the week's activities and a plan for the following week. These activities should always be linked to the relevant unique project development artifact.

This report will evaluate your understanding of the development process of a project, and your ability to plan and manage a project. The report will also be used to evaluate your progress and provide feedback. The report will be evaluated based on the following criteria:

• Completeness: The report should be complete and include all the required information that are linked to the relevant artifacts.
• Consistency: The report should be consistent with the project plan and reports of previous weeks.
• Feasibility: The report should be feasible and realistic. The action items should be achievable in the upcoming week.

---

Team Name: [Team Name]
Date: [Date]

Progress Summary

Provide a high-level overview of your progress during the week. Mention any significant achievements, challenges, changes in the project plan, and write the main objective for the following week (not more than five sentences; you should be able to tell it to someone in 30 seconds in an elevator).

What was planned for the week? How did it go?

List the tasks that you planned to complete during the week. These should be based on the project plan and progress reports of previous weeks. If they are complete, include a reference to the related project development artifact.

Completed tasks that were not planned for the week

List the tasks that you did not anticipate in the project plan or in the previous week's report but completed anyway.

Planned vs. Actual

Describe any discrepancies between the project plan and the actual progress. Did tasks take as much time as expected, or shorter/longer? Did you accomplish all the tasks planned for the week? Describe any new issues that you encountered during the week, which were not planned for. These could be technical or non-technical issues. Explain how you plan to address these issues in the upcoming week(s).

Your plans for the next week

List the specific tasks or actions you plan to take in the upcoming week. These should be based on the project plan and the issues discussed earlier. All action items should be linked to the relevant issues.

Risks

Identify any risks that you anticipate in the upcoming week(s), and explain how you plan to mitigate them.

Participants

Team members that attended this session.

• Burak Eren
• Elif Kızılkaya
• Fatma Sena Alçı
• Furkan Ülke
• Hakan Karakuş
• Hatice Erk
• Kardelen Erdal
• Melih Gezer
• Muhammet Tayyip Kamiloğlu
• Ömer Şafak Bebek
• Yunus Emre Altuğ

Additional Notes

Include any other relevant information or comments regarding the week's progress or any additional insights you want to share. This section is optional.