14th Meeting 30.12.2020

Time & Location

• December 30th 2020, 20:30
• Zoom

Attendees

• Alperen Bağ
• Berkay Alkan
• Berke Can Gürer
• Burak Çuhadar
• Çağrı Çiftçi
• Emre Girgin
• Eylül Yalçınkaya
• Koray Çetin
• Mehmet Erdinç Oğuz
• Meriç Üngör
• Muhammed Olcayto Türker
• Veli Can Ünal

Agenda

1. We will talk about the tasks of milestone 2 Report.

Discussion

1. Table of content.
2. Executive Summary: Summary of project status and any changes that are planned for moving forward.
3. List and status of deliverables.
4. Evaluation of the status of deliverables and their impact on the plan.
5. A summary of coding work done by each team member (in tabular format).
6. Each team member should explain the unit tests committed by him/her by referring to the commit SHA (in a separate subsection for each member under the Unit Tests Section).
7. A detailed explanation of the challenges you met during the deployment, dockerizing, and CI/CD processes.
8. API documentation (Do not just put the link to your documentation. You need to document within the report.).
9. Project plan (in tabular format; you may omit Gantt timelines and display dates/durations/assignees/predecessors only as a text for readability. Unreadable plans will NOT be graded.).
10. User scenarios you presented during the milestone presentation.
11. Issues will be inspected online and will not be in the delivered report.
12. Meetings will be inspected online and will not be in the delivered report.
13. The wiki page will be inspected online and will not be in the delivered report (don't forget to keep your Wiki page up to date). Note that we are expecting every available information regarding your project available on your wiki page.
14. The code will be inspected online and will not be in the delivered report. However, the code structure and group process should be documented, for example, if each feature is a branch and what are the branches, how are pull requests used, etc.
15. Evaluation of tools and managing the project. This is a lesson learned from the project development decisions made so far. Tools are for planning, IDE, frameworks, and everything. The management is the process used by the team, including how the tools are being effectively utilized. If there are some aspects that are not working out, what kind of changes are planned.
16. Assessment of the customer presentation. What did you learn from your interaction about the status and direction of your project? Also, did you learn anything about presenting? Difficulties? What went well, what needs improvement for next time.

Action Items

Task No.	Person	Task	Deadline	Completion time
0	Çağrı Çiftçi	Taking meeting notes.	30.12.2020 Wednesday@23.59	30.12.2020 Wednesday@22.45
1	Mehmet Erdinç Oğuz	Table of content.	05.01.2021 Tuesday@17.00
2	Eylül Yalçınkaya	Executive Summary: Summary of project status and any changes that are planned for moving forward.	04.01.2021 Monday@17.00	04.01.2020 Monday @12:00
3	Burak Çuhadar, Mehmet Erdinç Oğuz, Emre Girgin	List and status of deliverables	04.01.2021 Monday@17.00	Burak Çuhadar: 05.01.2021 Tuesday@10.36
4	Burak Çuhadar, Mehmet Erdinç Oğuz, Emre Girgin	Evaluation of the status of deliverables and their impact on the plan	04.01.2021 Monday@17.00	Burak Çuhadar: 05.01.2021 Tuesday@10.36
5	Everyone	A summary of coding work done by each team member (in tabular format)	04.01.2021 Monday@17.00
6	Muhammed Olcayto Türker, Mehmet Erdinç Oğuz, Koray Çetin, Veli Can Ünal	Each team member should explain the unit tests committed by him/her by referring to the commit SHA (in a separate subsection for each member under the Unit Tests Section).	04.01.2021 Monday@17.00	04.01.2021 Monday
7	Meriç Üngör, Koray Çetin	A detailed explanation of the challenges you met during the deployment, dockerizing, and CI/CD processes.	04.01.2021 Monday@17.00
8	Muhammed Olcayto Türker	API documentation (Do not just put the link to your documentation. You need to document within the report.)	04.01.2021 Monday@17.00
9	Çağrı Çiftçi	Project plan (in tabular format; you may omit Gantt timelines and display dates/durations/assignees/predecessors only as a text for readability. Unreadable plans will NOT be graded.).	04.01.2021 Monday@17.00	05.01.2020 Tuesday@21:00
10	Berke Can Gürer, Çağrı Çiftçi	User scenarios you presented during the milestone presentation.	04.01.2021 Monday@17.00	Çağrı Çiftçi - 05.01.2020 Tuesday@21:00
11	Çağrı Çiftçi ,Eylül Yalçınkaya , Koray Çetin	The code will be inspected online and will not be in the delivered report. However, the code structure and group process should be documented, for example, if each feature is a branch and what are the branches, how are pull requests used, etc	04.01.2021 Monday@17.00	Eylül Yalçınkaya - 04.01.2020 Monday @12:00 Çağrı Çiftçi - 05.01.2020 Tuesday@21:00
12	Meriç Üngör, Berkay Alkan, Veli Can Ünal	Evaluation of tools and managing the project. This is a lesson learned from the project development decisions made so far. Tools are for planning, IDE, frameworks, and everything. The management is the process used by the team, including how the tools are being effectively utilized. If there are some aspects that are not working out, what kind of changes are planned.	04.01.2021 Monday@17.00	04.01.2021 Monday
13	Alperen Bağ	Assessment of the customer presentation. What did you learn from your interaction about the status and direction of your project? Also, did you learn anything about presenting? Difficulties? What went well, what needs improvement for next time.	04.01.2021 Monday@17.00