Customer Milestone 1 Report

Customer Milestone 1

This is the first milestone report for the bounswe2024group11 team. It includes a summary of what we have done so far, our project plan in a detailed manner, work done by each team member, and the tools we have benefitted.

1. Executive Summary

• We have decided our project domain as comics.
• We have prepared and asked some requirement elicitation questions.
• We have documented the requirements.
• We have created 5 different scenarios.
• We have created

1.a) Summary & Status

Currently, we have settled on the domain Comics. The elicitation questions are identified and requirements are specified. We created our scenarios and mock-ups.

1.b) Deliverables

• Our Wiki is in a well-established and well-navigatable state. We have a functioning Sidebar and a descriptive landing page.
• We have our Communication Plan, Project Plan, Requirements, Mockups, Scenarios, and Meeting Notes ready to review and evaluate.
• We have more than 100 issues opened, of which 90 are closed. Our issues have a standard form where we try to describe the problem in a succinct manner

1.c) Decisions

• Simplicity of issue and issue templates. We want to be direct and succinct.
• Weekly meetings on Google Meet, and subgroup meetings on Discord. Separation of concerns.
• Comics over Chess: We have checked WikiData and changed our domain to Comics because of WikiData searchability, and content richness.
• Only desktop flows: We used a mobile-first approach to designs so that our customers can easily extrapolate what they see in a desktop view to a mobile view.
• Reviewer: We decided to assign at least one reviewer to further issues besides the assignees.

1.d) Challenges met

• The first domain is not rich enough in terms of WikiData content. Domain change required double work on most of the ends such as requirements, and user scenarios.
• Understanding semantic search, its use cases, and its implications for our project.
• The false idea that we all have to be in every meeting hindered us
• Meetings taking too much time
• Trying to "glue" 5 user scenarios and mockups was an exhausting task.

---

2. Project Plan

We have created our project plan in ProjectLibre and displayed it in our Wiki. It can be found in this link.

Our project plan consists of ...

---

3. Personal Efforts

You can view each student's personal efforts page here

Arda Vural
Task
Task

Ceydanur Şen
Task
Task

Emre Kılıç
Task
Task

Hasan Kerem Şeker
Task
Task

Muhammed Emin Arayıcı
Task
Task

Muhammet Emin Çiftçi
Task
Task

Mücahit Erdoğan Ünlü
Task
Task

Ozan Oytun Karakaya
Task
Task

Ümit Can Evleksiz
Created issue templates and template configurator
Created a readme page in the repository, summarized the team and the project
Created Wiki home page (landing page) and modified as we progress. i.e. add team members' bio and efforts
Created image assets for the Wiki

Yunus Kağan Aydın
Task
Task

---

4. Evaluation of Tools and Processes

Tools Used:

• WhatsApp

  • We used WhatsApp to do our spontaneous discussions, created polls, or shared links.

• Discord

  • We used Discord to carry out our subgroup meetings. The topics of these subgroup meetings include the creation of scenarios, elicitation of requirements, and creation of the project plan.

• Google Drive

  • We used Google Drive to share folders and draft files.

• Google Meet

  • We used Google Meet to do weekly meetings in which current tasks are assigned to subgroups. These meetings allowed us to synchronize our progress.

• GitHub

  • The deliverables of the project are located on GitHub. It has issues with tasks, documentation of research, scenarios, mock-ups, plans, and wiki.

• Project Libre

  • It is used to create the project plan.

• Google Sheets

  • We used Google Sheets to save draft meeting notes.

• Figma

  • It is used to create mock-ups.

Workflow:

Problem Occurrence → Create Issue → Assign Someone → Review

See Communication Plan for details

Retrospective

We didn't make use of peer reviews at its full capacity for the first portion of this milestone. We also did our meeting as a whole instead of multiple submeetings in the first portion of this milestone.