From 08e5b150520933a3162d25fa2fb77fdcc272c340 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Sat, 31 May 2025 15:20:29 +0300 Subject: [PATCH 01/70] updated the communication file --- collaboration/communication.md | 50 +++++++++++++++++++--------------- 1 file changed, 28 insertions(+), 22 deletions(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index bdf6d3730..d6299bfb2 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -4,7 +4,7 @@ Careful! be sure to protect your privacy when filling out this document everything you write here will be public so share only what you are comfortable sharing online - you can share the rest in confidence with you group by another channel + you can share the rest in confidence with your group by another channel --> # Communication @@ -13,17 +13,19 @@ ## Communication Schedule -| Day | How | The topic of discussion | | --- | :-: | ----------------------- | -| | | | +| Day | How | The topic of discussion | +|---------- |:----------:|----------------------------------------------- | +| As needed | Slack | General communication and coordination | +| Weekly | Google Meet| Team meetings and check-ins | +| As needed | GitHub | Task-related discussions (Issues, PR reviews) | ## Communication Channels -how often will we get in touch on each channel, and what we will discuss there: +How often will we get in touch on each channel, and what we will discuss there: -- **Issues**: -- **Pull Requests**: -- **Slack/Discord**: -- **Video Calls**: +- **Issues and Pull Requests**: Used for task-specific discussions and reviewing submitted code. Helps in learning how to manage GitHub collaboration. We should establish clear norms on when to close issues and accept PRs. +- **Slack**: Preferred for daily communication, quick questions, and coordination. +- **Video Calls**: Held on Google Meet. Used for meetings. Weekly or as needed. --- @@ -31,24 +33,28 @@ how often will we get in touch on each channel, and what we will discuss there: ### Availability for calling/messaging -| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | | -| ------ | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: | --- | -| _name_ | | | | | | | | +| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | +|--------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| +| Ammar | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | +| Banu | 12–4PM | 2–4PM | 2–4PM | 12–4PM | 12–4PM | 12–4PM | 12–4PM | +| Amro | ❌ | 9–3PM | ❌ | 9–3PM | 9–3PM | 9–3PM | 9–3PM | +| Azza | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 5–7AM | 5–7AM | 3–5AM, 12–2PM | + +> Note: Times are in EST. Availability may vary slightly due to personal commitments. ### How many hours everyone has per day -- name: _5h_; -- name: _6h_; -- name: _5h_; -- name: _4h_; -- name: _3h_; +- Ammar: _2h_ +- Banu: _2–3h_ +- Amro: _2–3h_ +- Azza: _2-3h and Emergency_ + +--- ## Asking for Help -There's a fine line between confidently learning from your mistakes, and -stubbornly getting no where. Here is a general guide for when to ask for help -based on how long you've been stuck on the same problem: +There's a fine line between confidently learning from your mistakes, and stubbornly getting nowhere. Here is a general guide for when to ask for help based on how long you've been stuck on the same problem: -1. _0 -> 30 min_: Try on your own -1. _30 -> 60 min_: Ask your group for help -1. _60+ min_: Tag your coaches in Slack or GitHub +1. _0 → 30 min_: Try on your own +2. _30 → 60 min_: Ask your group for help +3. _60+ min_: Tag your coaches in Slack or GitHub From 851ee7f8e27216e1e07b7a6f3e4505168fbd75aa Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sat, 31 May 2025 15:24:56 +0300 Subject: [PATCH 02/70] draft --- collaboration/learning_goals.md | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index 11c583d2b..8de2f888d 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -1,5 +1,37 @@ # Learning Goals +What we Aim to learn in each and every step of the Project + ## Collective +The team aims to collaboratively master problem scoping, data collection, analysis, +and insights communication using GitHub, while developing technical and teamwork +skills for effective data science project execution." + ## Individual + +Milestone 0: Cross-Cultural Collaboration + +-AmroMohamed: + +1-Awareness: Recognize cultural differences in work styles, communication, +and problem-solving approaches. + +2-Communication: Practice inclusive and clear communication to mitigate misunderstandings. + +3-Collaboration Tools: Use GitHub to document decisions transparently +and ensure equitable participation. + +4-Conflict Resolution: Address challenges constructively by adapting to diverse viewpoints. + +-Member2 + +-Member3 + +-Member4 + +-Member5 + +-Member6 + +-Member7 From f426a7b2971a68fe86811796e9296277c159289a Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sat, 31 May 2025 15:57:20 +0300 Subject: [PATCH 03/70] file structure --- .../0_domain_study}/README.md | 0 .../0_domain_study}/guide.md | 0 {1_datasets => 1_Problem_Identification/1_datasets}/README.md | 0 {1_datasets => 1_Problem_Identification/1_datasets}/guide.md | 0 .../2_data_preparation}/README.md | 0 .../2_data_preparation}/guide.md | 0 .../3_data_exploration}/README.md | 0 .../3_data_exploration}/guide.md | 0 {5_communication_strategy => 5_Communicating_Results}/README.md | 0 {5_communication_strategy => 5_Communicating_Results}/guide.md | 0 10 files changed, 0 insertions(+), 0 deletions(-) rename {0_domain_study => 1_Problem_Identification/0_domain_study}/README.md (100%) rename {0_domain_study => 1_Problem_Identification/0_domain_study}/guide.md (100%) rename {1_datasets => 1_Problem_Identification/1_datasets}/README.md (100%) rename {1_datasets => 1_Problem_Identification/1_datasets}/guide.md (100%) rename {2_data_preparation => 2_Data_Collection/2_data_preparation}/README.md (100%) rename {2_data_preparation => 2_Data_Collection/2_data_preparation}/guide.md (100%) rename {3_data_exploration => 2_Data_Collection/3_data_exploration}/README.md (100%) rename {3_data_exploration => 2_Data_Collection/3_data_exploration}/guide.md (100%) rename {5_communication_strategy => 5_Communicating_Results}/README.md (100%) rename {5_communication_strategy => 5_Communicating_Results}/guide.md (100%) diff --git a/0_domain_study/README.md b/1_Problem_Identification/0_domain_study/README.md similarity index 100% rename from 0_domain_study/README.md rename to 1_Problem_Identification/0_domain_study/README.md diff --git a/0_domain_study/guide.md b/1_Problem_Identification/0_domain_study/guide.md similarity index 100% rename from 0_domain_study/guide.md rename to 1_Problem_Identification/0_domain_study/guide.md diff --git a/1_datasets/README.md b/1_Problem_Identification/1_datasets/README.md similarity index 100% rename from 1_datasets/README.md rename to 1_Problem_Identification/1_datasets/README.md diff --git a/1_datasets/guide.md b/1_Problem_Identification/1_datasets/guide.md similarity index 100% rename from 1_datasets/guide.md rename to 1_Problem_Identification/1_datasets/guide.md diff --git a/2_data_preparation/README.md b/2_Data_Collection/2_data_preparation/README.md similarity index 100% rename from 2_data_preparation/README.md rename to 2_Data_Collection/2_data_preparation/README.md diff --git a/2_data_preparation/guide.md b/2_Data_Collection/2_data_preparation/guide.md similarity index 100% rename from 2_data_preparation/guide.md rename to 2_Data_Collection/2_data_preparation/guide.md diff --git a/3_data_exploration/README.md b/2_Data_Collection/3_data_exploration/README.md similarity index 100% rename from 3_data_exploration/README.md rename to 2_Data_Collection/3_data_exploration/README.md diff --git a/3_data_exploration/guide.md b/2_Data_Collection/3_data_exploration/guide.md similarity index 100% rename from 3_data_exploration/guide.md rename to 2_Data_Collection/3_data_exploration/guide.md diff --git a/5_communication_strategy/README.md b/5_Communicating_Results/README.md similarity index 100% rename from 5_communication_strategy/README.md rename to 5_Communicating_Results/README.md diff --git a/5_communication_strategy/guide.md b/5_Communicating_Results/guide.md similarity index 100% rename from 5_communication_strategy/guide.md rename to 5_Communicating_Results/guide.md From f6d3abf8f24c9330d1caa84f51de2ea2ccebe1d4 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sat, 31 May 2025 15:59:10 +0300 Subject: [PATCH 04/70] file structure --- {4_data_analysis => 3_Data_Analysis}/README.md | 0 {4_data_analysis => 3_Data_Analysis}/guide.md | 0 {5_Communicating_Results => 4_Communicating_Results}/README.md | 0 {5_Communicating_Results => 4_Communicating_Results}/guide.md | 0 {6_final_presentation => 5_Final_Presentation}/README.md | 0 {6_final_presentation => 5_Final_Presentation}/guide.md | 0 6 files changed, 0 insertions(+), 0 deletions(-) rename {4_data_analysis => 3_Data_Analysis}/README.md (100%) rename {4_data_analysis => 3_Data_Analysis}/guide.md (100%) rename {5_Communicating_Results => 4_Communicating_Results}/README.md (100%) rename {5_Communicating_Results => 4_Communicating_Results}/guide.md (100%) rename {6_final_presentation => 5_Final_Presentation}/README.md (100%) rename {6_final_presentation => 5_Final_Presentation}/guide.md (100%) diff --git a/4_data_analysis/README.md b/3_Data_Analysis/README.md similarity index 100% rename from 4_data_analysis/README.md rename to 3_Data_Analysis/README.md diff --git a/4_data_analysis/guide.md b/3_Data_Analysis/guide.md similarity index 100% rename from 4_data_analysis/guide.md rename to 3_Data_Analysis/guide.md diff --git a/5_Communicating_Results/README.md b/4_Communicating_Results/README.md similarity index 100% rename from 5_Communicating_Results/README.md rename to 4_Communicating_Results/README.md diff --git a/5_Communicating_Results/guide.md b/4_Communicating_Results/guide.md similarity index 100% rename from 5_Communicating_Results/guide.md rename to 4_Communicating_Results/guide.md diff --git a/6_final_presentation/README.md b/5_Final_Presentation/README.md similarity index 100% rename from 6_final_presentation/README.md rename to 5_Final_Presentation/README.md diff --git a/6_final_presentation/guide.md b/5_Final_Presentation/guide.md similarity index 100% rename from 6_final_presentation/guide.md rename to 5_Final_Presentation/guide.md From 14ebbbb9bda31f860721e444932cf348ec3b1b3b Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Sat, 31 May 2025 16:20:39 +0300 Subject: [PATCH 05/70] updated communication file, added Muhammad's and edited Azza's --- collaboration/communication.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index d6299bfb2..81866ab48 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -38,7 +38,8 @@ How often will we get in touch on each channel, and what we will discuss there: | Ammar | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | | Banu | 12–4PM | 2–4PM | 2–4PM | 12–4PM | 12–4PM | 12–4PM | 12–4PM | | Amro | ❌ | 9–3PM | ❌ | 9–3PM | 9–3PM | 9–3PM | 9–3PM | -| Azza | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 5–7AM | 5–7AM | 3–5AM, 12–2PM | +| Azza | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 3–5AM, 12–2PM | ❌ | 5–7AM | 3–5AM, 12–2PM | +|Muhammad| 12–2PM | 12–2PM | 12–2PM | 12–2PM | ❌ | ❌ | 12–2PM | > Note: Times are in EST. Availability may vary slightly due to personal commitments. @@ -48,6 +49,7 @@ How often will we get in touch on each channel, and what we will discuss there: - Banu: _2–3h_ - Amro: _2–3h_ - Azza: _2-3h and Emergency_ +- Muhammamd: 2h --- From 48638b1a337c847a0e7e84a514837c04c845ddb9 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Sat, 31 May 2025 16:27:30 +0300 Subject: [PATCH 06/70] updated Ammar's availability --- collaboration/communication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index 81866ab48..e27a918ea 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -35,7 +35,7 @@ How often will we get in touch on each channel, and what we will discuss there: | Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |--------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| -| Ammar | ✅ | ✅ | ✅ | ✅ | ❌ | ✅ | ✅ | +| Ammar | 12–3PM | 12–3PM | 12–3PM | 12–3PM | ❌ | 12–3PM | 12–3PM | | Banu | 12–4PM | 2–4PM | 2–4PM | 12–4PM | 12–4PM | 12–4PM | 12–4PM | | Amro | ❌ | 9–3PM | ❌ | 9–3PM | 9–3PM | 9–3PM | 9–3PM | | Azza | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 3–5AM, 12–2PM | 3–5AM, 12–2PM | ❌ | 5–7AM | 3–5AM, 12–2PM | From 209c8434398c3731693bffee5bb1610d311c27e7 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Sat, 31 May 2025 12:48:28 -0400 Subject: [PATCH 07/70] docs: add group norms to collaboration readme --- collaboration/README.md | 60 +++++++++++++++++++++++++++++++++++++++-- 1 file changed, 58 insertions(+), 2 deletions(-) diff --git a/collaboration/README.md b/collaboration/README.md index 20889b951..7062b93bb 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -1,5 +1,61 @@ # Collaboration - +## Group Norms 📜 - +As a team, we are committed to working collaboratively, respectfully, and efficiently. +Our group norms are designed to ensure **clear communication**, **equal +contribution**, **accountability**, and a **supportive environment** where all +members can thrive and deliver high-quality work. These norms will guide our interactions, +help us resolve conflicts, and keep our project on track: + +--- + +### 1. Respectful Communication 🤝 + +We actively listen to each other, value all contributions, and speak respectfully +at all times. + +### 2. Equal Participation ⚖️ + +Everyone is expected to contribute equally to discussions, code, and documentation +unless otherwise agreed upon. + +### 3. Clear and Timely Communication ⏰ + +We use our group chat, video meetings and GitHub issues to keep each other informed. +If someone will be unavailable, they inform the team in advance. + +### 4. Commitment to Deadlines 📅 + +We agree on realistic deadlines and take responsibility for meeting them. +We support each other when someone falls behind. + +### 5. Constructive Feedback 💬 + +We give and receive feedback with the goal of improving our work, not criticizing +individuals. + +### 6. Decision Making by Consensus 🧠 + +Major decisions are made as a group, and everyone’s voice is heard before reaching +agreement. + +### 7. Use of GitHub 🔀 + +All code is pushed to GitHub with meaningful commit messages. +Pull requests are used for all major changes and must be reviewed by at least +two team member. + +### 8. Code Quality and Documentation 🧑‍💻 + +We follow agreed coding conventions and document our work clearly so others can +understand and build on it. + +### 9. Problem Solving Together 🤔 + +We discuss blockers or confusion openly and help each other resolve problems. + +### 10. Accountability and Ownership 🙋 + +Each member is responsible for their tasks and follows through on commitments. +If issues arise, we communicate honestly and seek support. From 796a00a4541af8102ec3289463181d0014a1ebaf Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Sat, 31 May 2025 13:50:41 -0400 Subject: [PATCH 08/70] docs: update collaboration README with intro and file summaries - Added a short introduction explaining the purpose of the collaboration folder - Listed and described the contents: communication.md, constraints.md, learning_goals.md, and retrospective.md - Clarified how these documents support teamwork and project alignment --- collaboration/README.md | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/collaboration/README.md b/collaboration/README.md index 7062b93bb..17f77ecb5 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -1,5 +1,31 @@ # Collaboration +This folder contains key documents that support our team's collaboration, planning, +and continuous improvement. Each file is designed to help us stay aligned, communicate +effectively, and reflect on our progress throughout the project. It also includes +the shared group norms that guide how we work together as a team. + +## Files Included 🗃️ + +- [**communication.md**](communication.md) + Details how and when we communicate, including preferred channels, weekly check-ins, + availability, and when to ask for help. + +- [**constraints.md**](constraints.md) + Lists any known limitations such as deadlines, availability, scope boundaries, + or technical issues. + +- [**learning_goals.md**](learning_goals.md) + Defines what each team member hopes to learn during the project, both technically + and collaboratively. + +- [**retrospective.md**](retrospective.md) + A place for team reflection at several points in the project, such as what went + well, what didn't, and how to do it differently next time. + +Keeping these documents up to date helps us stay transparent, focused, goal-oriented, +and flexible as the project evolves. 🚀 + ## Group Norms 📜 As a team, we are committed to working collaboratively, respectfully, and efficiently. From 756b55a35946deba04afeb882e3fb1a27ee89161 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Sat, 31 May 2025 14:21:19 -0400 Subject: [PATCH 09/70] docs: update group norms intro for smoother transition --- collaboration/README.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/collaboration/README.md b/collaboration/README.md index 17f77ecb5..2572f2ee5 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -28,13 +28,11 @@ and flexible as the project evolves. 🚀 ## Group Norms 📜 -As a team, we are committed to working collaboratively, respectfully, and efficiently. -Our group norms are designed to ensure **clear communication**, **equal -contribution**, **accountability**, and a **supportive environment** where all -members can thrive and deliver high-quality work. These norms will guide our interactions, -help us resolve conflicts, and keep our project on track: - ---- +To support the documents above and ensure smooth teamwork, we have established +a set of shared norms. These norms guide how we collaborate each day by encouraging +clear communication, mutual respect, and shared ownership. They help us navigate +challenges, stay on track, and create a supportive environment where everyone +can do their best work. ### 1. Respectful Communication 🤝 From e2b625a152fdbc42872df4ea081b01354a72cb45 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Sat, 31 May 2025 14:46:25 -0400 Subject: [PATCH 10/70] docs: add README.md as the first item in the Files included section --- collaboration/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/collaboration/README.md b/collaboration/README.md index 2572f2ee5..77ec4f767 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -7,6 +7,9 @@ the shared group norms that guide how we work together as a team. ## Files Included 🗃️ +- [**README.md**](README.md) + Contains an introduction of the collaboration process and group norms. + - [**communication.md**](communication.md) Details how and when we communicate, including preferred channels, weekly check-ins, availability, and when to ask for help. From 18a5863ca6cf3d454e1103351aa2b395c702ff97 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Sat, 31 May 2025 15:21:11 -0400 Subject: [PATCH 11/70] fix the markdown formatting error --- 1_datasets/guide.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/1_datasets/guide.md b/1_datasets/guide.md index eadf53553..5a87226b3 100644 --- a/1_datasets/guide.md +++ b/1_datasets/guide.md @@ -35,13 +35,13 @@ one. The kind of data you choose impacts: Below is an overview of different kinds of dataset you will encounter: -1. [Classification by Data Type](#classification-by-data-type) -2. [Classification by Structure](#classification-by-structure) -3. [Classification by Collection Method](#classification-by-collection-method) -4. [Classification by Size and Complexity](#classification-by-size-and-complexity) -5. [Classification by Access Type](#classification-by-access-type) -6. [Classification by Purpose](#classification-by-purpose) -7. [Classification by Format](#classification-by-format) +1. [Classification by Data Type](classification-by-data-type) +2. [Classification by Structure](classification-by-structure) +3. [Classification by Collection Method](classification-by-collection-method) +4. [Classification by Size and Complexity](classification-by-size-and-complexity) +5. [Classification by Access Type](classification-by-access-type) +6. [Classification by Purpose](classification-by-purpose) +7. [Classification by Format](classification-by-format) ### Quantitative (Numerical) Data From 52c821bdaa736cee86db0c31b6291b7b948bfb4f Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Sat, 31 May 2025 15:27:19 -0400 Subject: [PATCH 12/70] fix the markdown formatting error --- guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide.md b/guide.md index 75029ea6a..53b8877d0 100644 --- a/guide.md +++ b/guide.md @@ -8,7 +8,7 @@ designed to help you do **reproducible** research. If your research process is well organized, others should be able to clone it, run all scripts (without errors!), and evaluate your conclusions for themselves. -``` +```text / ├── README.md # Project overview and main findings ├── /collaboration/ # Team norms, strategies, and retrospectives From f5b3c554181df0e76a5f8cf98c01d9e74edd2ceb Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 13:50:12 +0300 Subject: [PATCH 13/70] learning-goals --- collaboration/learning_goals.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index 8de2f888d..cfabef897 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -24,7 +24,17 @@ and ensure equitable participation. 4-Conflict Resolution: Address challenges constructively by adapting to diverse viewpoints. --Member2 +-AzzaOmer + +1-Navigate and manage conflicts in group settings to strengthen collaboration. + +2-Build relationships that support professional growth within and outside the team. + +3-Strengthen team connections for future opportunities and collaborations. + +4-Apply the full data science lifecycle in a real project . + +5-Implement good coding practices. -Member3 From 08d0927ed41c143dfd0fa94f023425f723b8a703 Mon Sep 17 00:00:00 2001 From: AzzaOmer1 <103028535+AzzaOmer1@users.noreply.github.com> Date: Sun, 1 Jun 2025 13:54:44 +0300 Subject: [PATCH 14/70] Refined constraints.md with structured team constraints --- collaboration/constraints.md | 82 +++++++++++++++++++++++++----------- 1 file changed, 57 insertions(+), 25 deletions(-) diff --git a/collaboration/constraints.md b/collaboration/constraints.md index 24079505c..85d581b98 100644 --- a/collaboration/constraints.md +++ b/collaboration/constraints.md @@ -1,34 +1,66 @@ +# 🚧 Constraints -# Constraints +Some boundaries around our project to guide effective collaboration and planning. -Some boundaries around our project. +--- -## External +## 🔒 Project Boundaries & Constraints - +To ensure efficiency and balanced contributions, the project should have clear boundaries: -## Internal: Involuntary +- 👥 Roles and responsibilities should be well-defined to prevent overlapping efforts. +- 🎯 Expectations should be set for balanced contributions, +considering members' constraints. +- 💬 A culture of constructive feedback and solution-focused discussions +should be established. +- 🧩 A clear process for resolving conflicts is essential. - +These boundaries aim to create a productive and supportive environment for the team. -## Internal: Voluntary +--- - +## 🌍 External Constraints + +The team faces several external constraints impacting collaboration: + +- 🕒 **Timezones:** Remote work across different timezones can be challenging. +- 👨‍👩‍👧‍👦 **Family & Work Responsibilities:** Some members are constrained by +family and work commitments. +- ⏳ **Strict Deadline:** We must meet a strict project deadline. +- 📚 **Learning Curve:** We need to learn and share a large amount of new +material in a limited time. +- 📵 **Real-time Communication:** Significant timezone differences make +real-time coordination difficult. + +--- + +## ⚙️ Internal Involuntary Constraints + +These are constraints from within the team that are beyond individual control: + +1. 🧠 **Limited Git/GitHub knowledge** – some members are still building proficiency. +2. ⌚ **Time availability** – team members have limited hours during the week. +3. 📅 **Scheduling conflicts** due to personal commitments. +4. 🔄 **Progress dependencies** – tasks sometimes rely on others' input or decisions. +5. 💻 **Limited programming or data analysis experience** in some team members. + +These constraints may create hurdles in both skill development and collaboration. + +--- + +## 🛠️ Internal Voluntary Constraints + +These are commitments the team has voluntarily agreed to: + +- 📆 **Daily Progress Updates:** Team members commit to reporting progress consistently. +- 💻 **Asynchronous Communication:** Emphasis on GitHub issues, pull requests, and +other async tools. +- 🔁 **Flexible Availability:** Members with unpredictable schedules are +willing to adapt to contribute meaningfully. +- 🚀 **Skill Development Commitment:** Everyone is committed to improving their +technical and collaborative skills. +- 🌱 **Learning Mindset:** Despite limited experience, members view this as +an opportunity to grow. + +--- From ede57f69b879c858ecad49721a07599c98ce8b18 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 16:22:39 +0300 Subject: [PATCH 15/70] learning-goals --- collaboration/communication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index bdf6d3730..fa451be4b 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -33,7 +33,7 @@ how often will we get in touch on each channel, and what we will discuss there: | Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | | | ------ | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: | --- | -| _name_ | | | | | | | | +| _name_ | | | | ### How many hours everyone has per day From 8cd6a2e9fa3d17d4aff374dd1bb0c772669bbd97 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 16:27:46 +0300 Subject: [PATCH 16/70] file --- collaboration/learning_goals.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index cfabef897..fe16b0cd6 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -43,5 +43,3 @@ and ensure equitable participation. -Member5 -Member6 - --Member7 From b8f503e6ce6c905c7e0a8d3962e8c3dc33b66a64 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 16:32:42 +0300 Subject: [PATCH 17/70] file --- .../0_domain_study => 0_domain_study}/README.md | 0 .../0_domain_study => 0_domain_study}/guide.md | 0 {1_Problem_Identification/1_datasets => 1_datasets}/README.md | 0 {1_Problem_Identification/1_datasets => 1_datasets}/guide.md | 0 .../2_data_preparation => 2_data_preparation}/README.md | 0 .../2_data_preparation => 2_data_preparation}/guide.md | 0 .../3_data_exploration => 3_data_exploration}/README.md | 0 .../3_data_exploration => 3_data_exploration}/guide.md | 0 8 files changed, 0 insertions(+), 0 deletions(-) rename {1_Problem_Identification/0_domain_study => 0_domain_study}/README.md (100%) rename {1_Problem_Identification/0_domain_study => 0_domain_study}/guide.md (100%) rename {1_Problem_Identification/1_datasets => 1_datasets}/README.md (100%) rename {1_Problem_Identification/1_datasets => 1_datasets}/guide.md (100%) rename {2_Data_Collection/2_data_preparation => 2_data_preparation}/README.md (100%) rename {2_Data_Collection/2_data_preparation => 2_data_preparation}/guide.md (100%) rename {2_Data_Collection/3_data_exploration => 3_data_exploration}/README.md (100%) rename {2_Data_Collection/3_data_exploration => 3_data_exploration}/guide.md (100%) diff --git a/1_Problem_Identification/0_domain_study/README.md b/0_domain_study/README.md similarity index 100% rename from 1_Problem_Identification/0_domain_study/README.md rename to 0_domain_study/README.md diff --git a/1_Problem_Identification/0_domain_study/guide.md b/0_domain_study/guide.md similarity index 100% rename from 1_Problem_Identification/0_domain_study/guide.md rename to 0_domain_study/guide.md diff --git a/1_Problem_Identification/1_datasets/README.md b/1_datasets/README.md similarity index 100% rename from 1_Problem_Identification/1_datasets/README.md rename to 1_datasets/README.md diff --git a/1_Problem_Identification/1_datasets/guide.md b/1_datasets/guide.md similarity index 100% rename from 1_Problem_Identification/1_datasets/guide.md rename to 1_datasets/guide.md diff --git a/2_Data_Collection/2_data_preparation/README.md b/2_data_preparation/README.md similarity index 100% rename from 2_Data_Collection/2_data_preparation/README.md rename to 2_data_preparation/README.md diff --git a/2_Data_Collection/2_data_preparation/guide.md b/2_data_preparation/guide.md similarity index 100% rename from 2_Data_Collection/2_data_preparation/guide.md rename to 2_data_preparation/guide.md diff --git a/2_Data_Collection/3_data_exploration/README.md b/3_data_exploration/README.md similarity index 100% rename from 2_Data_Collection/3_data_exploration/README.md rename to 3_data_exploration/README.md diff --git a/2_Data_Collection/3_data_exploration/guide.md b/3_data_exploration/guide.md similarity index 100% rename from 2_Data_Collection/3_data_exploration/guide.md rename to 3_data_exploration/guide.md From 313a63a869c46d959e134464db24c33229df9744 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 16:35:03 +0300 Subject: [PATCH 18/70] file --- {3_Data_Analysis => 4_data_analysis}/README.md | 0 {3_Data_Analysis => 4_data_analysis}/guide.md | 0 {4_Communicating_Results => 5_communication_strategy}/README.md | 0 {4_Communicating_Results => 5_communication_strategy}/guide.md | 0 {5_Final_Presentation => 6_final_presentation}/README.md | 0 {5_Final_Presentation => 6_final_presentation}/guide.md | 0 6 files changed, 0 insertions(+), 0 deletions(-) rename {3_Data_Analysis => 4_data_analysis}/README.md (100%) rename {3_Data_Analysis => 4_data_analysis}/guide.md (100%) rename {4_Communicating_Results => 5_communication_strategy}/README.md (100%) rename {4_Communicating_Results => 5_communication_strategy}/guide.md (100%) rename {5_Final_Presentation => 6_final_presentation}/README.md (100%) rename {5_Final_Presentation => 6_final_presentation}/guide.md (100%) diff --git a/3_Data_Analysis/README.md b/4_data_analysis/README.md similarity index 100% rename from 3_Data_Analysis/README.md rename to 4_data_analysis/README.md diff --git a/3_Data_Analysis/guide.md b/4_data_analysis/guide.md similarity index 100% rename from 3_Data_Analysis/guide.md rename to 4_data_analysis/guide.md diff --git a/4_Communicating_Results/README.md b/5_communication_strategy/README.md similarity index 100% rename from 4_Communicating_Results/README.md rename to 5_communication_strategy/README.md diff --git a/4_Communicating_Results/guide.md b/5_communication_strategy/guide.md similarity index 100% rename from 4_Communicating_Results/guide.md rename to 5_communication_strategy/guide.md diff --git a/5_Final_Presentation/README.md b/6_final_presentation/README.md similarity index 100% rename from 5_Final_Presentation/README.md rename to 6_final_presentation/README.md diff --git a/5_Final_Presentation/guide.md b/6_final_presentation/guide.md similarity index 100% rename from 5_Final_Presentation/guide.md rename to 6_final_presentation/guide.md From b0348e69fa11b3a2c1e6752faf88cb3c2599b752 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 16:48:19 +0300 Subject: [PATCH 19/70] file --- 1_datasets/guide.md | 2 ++ collaboration/communication.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/1_datasets/guide.md b/1_datasets/guide.md index eadf53553..713532986 100644 --- a/1_datasets/guide.md +++ b/1_datasets/guide.md @@ -43,6 +43,8 @@ Below is an overview of different kinds of dataset you will encounter: 6. [Classification by Purpose](#classification-by-purpose) 7. [Classification by Format](#classification-by-format) +### Classification by Data Type + ### Quantitative (Numerical) Data Data that represents quantities and can represented as numbers. diff --git a/collaboration/communication.md b/collaboration/communication.md index fa451be4b..bdf6d3730 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -33,7 +33,7 @@ how often will we get in touch on each channel, and what we will discuss there: | Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | | | ------ | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: | --- | -| _name_ | | | | +| _name_ | | | | | | | | ### How many hours everyone has per day From 92f4d84366e746efbde8ff4d7a68edd2c676e950 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 17:15:06 +0300 Subject: [PATCH 20/70] file --- guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide.md b/guide.md index 75029ea6a..53b8877d0 100644 --- a/guide.md +++ b/guide.md @@ -8,7 +8,7 @@ designed to help you do **reproducible** research. If your research process is well organized, others should be able to clone it, run all scripts (without errors!), and evaluate your conclusions for themselves. -``` +```text / ├── README.md # Project overview and main findings ├── /collaboration/ # Team norms, strategies, and retrospectives From 3e156a419cd88cdef946410f6bf386e6bc92def0 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 17:25:15 +0300 Subject: [PATCH 21/70] file --- collaboration/communication.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index bdf6d3730..98d0ac116 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -31,9 +31,9 @@ how often will we get in touch on each channel, and what we will discuss there: ### Availability for calling/messaging -| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | | -| ------ | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: | --- | -| _name_ | | | | | | | | +| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday| +| ------ | :----: | :-----: | :-------: | :------: | :----: | :------: | :----:| +| _name_ | | | | | | | | ### How many hours everyone has per day From 4986b6b89722a5acdf64e079915b8164be29dfa6 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 18:17:40 +0300 Subject: [PATCH 22/70] file --- collaboration/learning_goals.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index fe16b0cd6..2fe9b5bfc 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -36,7 +36,15 @@ and ensure equitable participation. 5-Implement good coding practices. --Member3 +-BanuÖzyılmaz + +1-Be a Supportive Team Member and Be a Supportive Team Member + +2-learn how to work well with people from different backgrounds, +being open to new ideas and perspectives. + +3-It’s important for me to communicate clearly and respectfully +so we can collaborate smoothly as a team. -Member4 From b27a1b70020c9f11b0d4b5b006d5e945dfd3ca2a Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Sun, 1 Jun 2025 19:19:56 +0300 Subject: [PATCH 23/70] file --- collaboration/learning_goals.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index 2fe9b5bfc..db06cad16 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -46,7 +46,11 @@ being open to new ideas and perspectives. 3-It’s important for me to communicate clearly and respectfully so we can collaborate smoothly as a team. --Member4 +-MuhammadShahroz + +1-Aim to work supportively and openly with teammates from diverse backgrounds, + +2-ensuring clear and respectful communication. -Member5 From 0f34bce0d61300174ebb8fdc5e8c16ee210b77b5 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Sun, 1 Jun 2025 15:24:46 -0400 Subject: [PATCH 24/70] fix md formatting --- 1_datasets/guide.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/1_datasets/guide.md b/1_datasets/guide.md index 5a87226b3..713532986 100644 --- a/1_datasets/guide.md +++ b/1_datasets/guide.md @@ -35,13 +35,15 @@ one. The kind of data you choose impacts: Below is an overview of different kinds of dataset you will encounter: -1. [Classification by Data Type](classification-by-data-type) -2. [Classification by Structure](classification-by-structure) -3. [Classification by Collection Method](classification-by-collection-method) -4. [Classification by Size and Complexity](classification-by-size-and-complexity) -5. [Classification by Access Type](classification-by-access-type) -6. [Classification by Purpose](classification-by-purpose) -7. [Classification by Format](classification-by-format) +1. [Classification by Data Type](#classification-by-data-type) +2. [Classification by Structure](#classification-by-structure) +3. [Classification by Collection Method](#classification-by-collection-method) +4. [Classification by Size and Complexity](#classification-by-size-and-complexity) +5. [Classification by Access Type](#classification-by-access-type) +6. [Classification by Purpose](#classification-by-purpose) +7. [Classification by Format](#classification-by-format) + +### Classification by Data Type ### Quantitative (Numerical) Data From 3a5417135fad0e190967b7c50db5618b449700ca Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Sun, 1 Jun 2025 15:47:36 -0400 Subject: [PATCH 25/70] docs: add GitHub project board usage based on feedback --- collaboration/README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/collaboration/README.md b/collaboration/README.md index 77ec4f767..d933f23a3 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -69,9 +69,13 @@ agreement. ### 7. Use of GitHub 🔀 -All code is pushed to GitHub with meaningful commit messages. +All code is pushed to GitHub with meaningful commit messages. Pull requests are used for all major changes and must be reviewed by at least -two team member. +two team member. +We also use GitHub Project Boards to organize tasks, track +progress, and ensure transparency. Each task is represented as a card and moves +through stages like _To Do, In Progress,_ and _Done_. Team members are responsible +for updating the status of their tasks regularly. ### 8. Code Quality and Documentation 🧑‍💻 From 537549bfeb9828a8e4c6c624ae44e94d87f4c067 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Mon, 2 Jun 2025 00:04:39 +0300 Subject: [PATCH 26/70] fixed typo in line 52 --- collaboration/communication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index e27a918ea..96479bf0b 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -49,7 +49,7 @@ How often will we get in touch on each channel, and what we will discuss there: - Banu: _2–3h_ - Amro: _2–3h_ - Azza: _2-3h and Emergency_ -- Muhammamd: 2h +- Muhammad: 2h --- From 28ffa447262631e35a00d51306f6d151d223980e Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Mon, 2 Jun 2025 04:17:52 +0300 Subject: [PATCH 27/70] goals --- collaboration/learning_goals.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index db06cad16..6ae6472d3 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -52,6 +52,11 @@ so we can collaborate smoothly as a team. 2-ensuring clear and respectful communication. --Member5 +-AmmarIbrahim + +1-Learn how to work effectively as part of a team. + +2-communicating efficiently and putting in effort for the team’s +success—not just individual progress. -Member6 From 245620a9a315e8330332370d8ad022c53b045f68 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Mon, 2 Jun 2025 05:16:31 +0300 Subject: [PATCH 28/70] fixed line lengths and ignoerd it for the table --- collaboration/communication.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/collaboration/communication.md b/collaboration/communication.md index 96479bf0b..decdc4536 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -23,7 +23,10 @@ How often will we get in touch on each channel, and what we will discuss there: -- **Issues and Pull Requests**: Used for task-specific discussions and reviewing submitted code. Helps in learning how to manage GitHub collaboration. We should establish clear norms on when to close issues and accept PRs. +- **Issues and Pull Requests**: Used for task-specific discussions +and reviewing submitted code. +Helps in learning how to manage GitHub collaboration. +We should establish clear norms on when to close issues and accept PRs. - **Slack**: Preferred for daily communication, quick questions, and coordination. - **Video Calls**: Held on Google Meet. Used for meetings. Weekly or as needed. @@ -32,7 +35,7 @@ How often will we get in touch on each channel, and what we will discuss there: ## Availability ### Availability for calling/messaging - + | Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |--------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| | Ammar | 12–3PM | 12–3PM | 12–3PM | 12–3PM | ❌ | 12–3PM | 12–3PM | @@ -42,7 +45,7 @@ How often will we get in touch on each channel, and what we will discuss there: |Muhammad| 12–2PM | 12–2PM | 12–2PM | 12–2PM | ❌ | ❌ | 12–2PM | > Note: Times are in EST. Availability may vary slightly due to personal commitments. - + ### How many hours everyone has per day - Ammar: _2h_ @@ -55,7 +58,10 @@ How often will we get in touch on each channel, and what we will discuss there: ## Asking for Help -There's a fine line between confidently learning from your mistakes, and stubbornly getting nowhere. Here is a general guide for when to ask for help based on how long you've been stuck on the same problem: +There's a fine line between confidently learning from your mistakes, +and stubbornly getting nowhere. +Here is a general guide for when to ask for help +based on how long you've been stuck on the same problem: 1. _0 → 30 min_: Try on your own 2. _30 → 60 min_: Ask your group for help From 21477ec1d39a021e193910d101cada4a993e67e3 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Mon, 2 Jun 2025 05:25:07 +0300 Subject: [PATCH 29/70] Add comment for ignoring table line length --- collaboration/communication.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/collaboration/communication.md b/collaboration/communication.md index decdc4536..55fbc9b85 100644 --- a/collaboration/communication.md +++ b/collaboration/communication.md @@ -36,6 +36,8 @@ We should establish clear norms on when to close issues and accept PRs. ### Availability for calling/messaging + + | Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |--------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| | Ammar | 12–3PM | 12–3PM | 12–3PM | 12–3PM | ❌ | 12–3PM | 12–3PM | From a26ec6f0ff224d63f5778d310228a29b9415e667 Mon Sep 17 00:00:00 2001 From: AmroMohamed Date: Mon, 2 Jun 2025 14:43:50 +0300 Subject: [PATCH 30/70] see if the errors are gone --- 1_datasets/guide.md | 2 ++ guide.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/1_datasets/guide.md b/1_datasets/guide.md index eadf53553..713532986 100644 --- a/1_datasets/guide.md +++ b/1_datasets/guide.md @@ -43,6 +43,8 @@ Below is an overview of different kinds of dataset you will encounter: 6. [Classification by Purpose](#classification-by-purpose) 7. [Classification by Format](#classification-by-format) +### Classification by Data Type + ### Quantitative (Numerical) Data Data that represents quantities and can represented as numbers. diff --git a/guide.md b/guide.md index 75029ea6a..53b8877d0 100644 --- a/guide.md +++ b/guide.md @@ -8,7 +8,7 @@ designed to help you do **reproducible** research. If your research process is well organized, others should be able to clone it, run all scripts (without errors!), and evaluate your conclusions for themselves. -``` +```text / ├── README.md # Project overview and main findings ├── /collaboration/ # Team norms, strategies, and retrospectives From 62f9150549031b09376bc2dc10295ed53ec344de Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Tue, 3 Jun 2025 01:20:40 -0400 Subject: [PATCH 31/70] docs: create a draft for milestone 0 retrospective --- collaboration/retrospective.md | 106 ++++++++++++++++++++++++++++----- 1 file changed, 90 insertions(+), 16 deletions(-) diff --git a/collaboration/retrospective.md b/collaboration/retrospective.md index c24b796a7..d642563f2 100644 --- a/collaboration/retrospective.md +++ b/collaboration/retrospective.md @@ -1,31 +1,105 @@ - - # Retrospective -## Stop Doing +This document is a team retrospective — a reflective summary of our process, collaboration, +and outcomes during the phases of our project. It serves to identify what +went well, what could be improved, and what lessons we’ve learned to carry forward +into the next milestone. -## Continue Doing +--- -## Start Doing +## Milestone 0: Cross-Cultural Collaboration -## Lessons Learned +This part summarizes our team’s experience and reflections from +Milestone 0, focused on Cross-Cultural Collaboration. The primary goal of this milestone +was to establish the foundations for effective teamwork by exploring cross-cultural +communication, design thinking, and innovation methodologies. ---- +During this phase (May 27 – June 2), we got to know our teammates, defined our collaboration +strategy, and prepared our GitHub repository and shared documents. Below is our +collective reflection on what went well, what we can improve, and what we’ve learned +from working together so far. -## Strategy vs. Board +### 🔴 Stop Doing -### What parts of your plan went as expected? +- Overthinking or overplanning that slows down actual work progress. +- Spending too much time on planning instead of taking action. +- Being inactive for long periods without informing the team in advance, which +can unintentionally disrupt collaboration. + +### 🟢 Continue Doing -### What parts of your plan did not work out? +- Communicating clearly and respectfully across time zones and cultures. +- Using collaborative tools like GitHub Projects and shared documents to stay organized. +- Using a shared space (like a Slack channel or Discord) for quick questions and +updates. +- Supporting each other in setting up the repository and assigning roles. +- Having open discussions for project process. -### Did you need to add things that weren't in your strategy? +### 🟡 Start Doing -### Or remove extra steps? +- Establishing a regular check-in schedule to keep everyone aligned. +- Inform the group in advance if you expect to be unavailable or less responsive, +so the team can adjust plans accordingly. +- Adding brief summaries after each meeting to make sure we’re all on the same page. ---- +### 💡 Lessons Learned + +- Cross-cultural collaboration requires patience and active listening, especially +early on. +- Setting up solid foundations (norms, communication plans, etc.) helps avoid +misunderstandings later. +- Effective communication is essential for successful collaboration. +- Having structure (like milestones and a project board) from the beginning helps +reduce stress. + +### 📊 Strategy vs. Board + +1.What parts of our plan went as expected? + +- We successfully met our group and set up the foundational structure of our project +repository on GitHub. +- We created and agreed upon key collaboration documents: group norms, communication +plan, constraints, and learning goals. +- The project board was organized with the required milestones and basic task cards, +as planned. + +2.What parts of our plan did not work out? + +- Coordinating schedules across time zones was more difficult than anticipated. +- Roles were not fully assigned effectively, and not every member was able to contribute +to the tasks due to other personal commitments. + +3.Did you need to add things that weren't in your strategy? -## Individual Rerospectives + ... + +4.Or remove extra steps? -### Name +... - +### 👤 Individual Retrospectives + +Member 1: Banu Özyılmaz + +- Contributions + + - Participated actively in initial group meetings and discussions. + - Contributed to drafting the group norms and retrospective file. + - Provided feedback and edits to team members’ contributions in shared docs. + +- Challenges + + - Adjusting to different time zones and response times. + - Balancing this milestone with other responsibilities required extra planning. + +- Progress + + - Gained a better understanding of the value of defining constraints and + expectations early. + - Improved skills in async collaboration and version control using GitHub. + - Felt more confident in working across cultures and establishing shared goals + with a diverse team. + +Member 2: + +--- From b9d9f7287952c34e52c7f3aba1cdf04b9ea5a59f Mon Sep 17 00:00:00 2001 From: Gennadii Ershov Date: Tue, 3 Jun 2025 02:32:06 -0400 Subject: [PATCH 32/70] docs: update main README --- README.md | 122 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 122 insertions(+) diff --git a/README.md b/README.md index e69de29bb..97ffd98bc 100644 --- a/README.md +++ b/README.md @@ -0,0 +1,122 @@ +# [Project Title] + +## Project Overview + +Briefly describe the goal and scope of this project. For example: + +- What problem are you trying to solve? +- What questions are you aiming to answer? +- Why is this analysis or application important? + +--- + +## Stack / Technologies Used + +- [Programming Language / Version] +- [Library / Framework] +- [Library / Framework] +- [Library / Framework] +- [Notebook / IDE] + +--- + +## Data + +### Dataset Source + +**Title:** [Name of dataset or link to source] +Provide a short description of when and how the data was collected, and why it’s +relevant to your project. + +Files included in this dataset (if applicable): + +- `[filename1.extension]` – brief description +- `[filename2.extension]` – brief description + +Specify which file(s) you chose to focus on and why. + +### Dataset Context + +Explain any background or contextual information that helps the reader understand: + +- The purpose of the dataset +- The population or scenario it represents +- Any known limitations or biases + +### Selected Columns + +| Column Name | Description | +|-------------------------|--------------------------------------------------| +| `[column_1]` | [Brief explanation of what this column means] | +| `[column_2]` | [Brief explanation of what this column means] | +| `[column_3]` | [Brief explanation of what this column means] | +| … | … | + +--- + +## Exploratory Data Analysis (EDA) + +### Key Analytical Questions + +1. [Question 1 about your data] +2. [Question 2 about your data] +3. [Question 3 about your data] +4. [Question 4 about your data] +5. [Any additional questions] + +--- + +## Methodology / Considerations + +Reflect on important aspects of the dataset and analysis, such as: + +- Sampling methods or biases +- Any relevant assumptions +- Data quality issues or missing values +- How these factors might affect your results + +Each bullet point should highlight a single consideration or constraint. + +--- + +## Summary / Key Findings + +Summarize the main takeaways from your analysis. Organize by topic or question: + +### 1. [Title for Finding 1] + +- Bullet point(s) summarizing the result or insight. + +### 2. [Title for Finding 2] + +- Bullet point(s) summarizing the result or insight. + +### 3. [Title for Finding 3] + +- Bullet point(s) summarizing the result or insight. + +…continue as needed. + +End with a brief paragraph on any broader implications or next steps. + +--- + +## Contributors + +List each team member (or yourself) and their role or focus area. For example: + +- **[Ammar Ibrahim](https://github.com/AmmarIbrahimTech)** + - [Responsibility or question addressed] + - [Responsibility or question addressed] +- **[Amro Mohamed](https://github.com/Elshikh-Amro)** + - [Responsibility or question addressed] + - [Responsibility or question addressed] +- **[Azza Omer](https://github.com/AzzaOmer1)** +- **[Banu Ozyilmaz](https://github.com/doctorbanu)** +- **[Gennadii Ershov](https://github.com/imwaymaran)** +- **[Muhammad Shahroz](https://github.com/Shahroz657)** +- **[Ramon Colmenares](https://github.com/RamonColmenares)** + +## Acknowledgments + +Special thanks to the **MIT Emerging Talent Program** for their guidance and feedback. From 9af9f816fa321686d50d4949e57c3e965af9601a Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Tue, 3 Jun 2025 21:35:19 -0400 Subject: [PATCH 33/70] docs: add contributions of 2 team members and collapse section for shorten document --- collaboration/retrospective.md | 85 ++++++++++++++++++++++++++++++++-- 1 file changed, 82 insertions(+), 3 deletions(-) diff --git a/collaboration/retrospective.md b/collaboration/retrospective.md index d642563f2..5feadb5ad 100644 --- a/collaboration/retrospective.md +++ b/collaboration/retrospective.md @@ -19,7 +19,13 @@ strategy, and prepared our GitHub repository and shared documents. Below is our collective reflection on what went well, what we can improve, and what we’ve learned from working together so far. -### 🔴 Stop Doing + + +
+📝 [ 𝗠𝗜𝗟𝗘𝗦𝗧𝗢𝗡𝗘 𝟬 | 𝗥𝗘𝗧𝗥𝗢𝗦𝗣𝗘𝗖𝗧𝗜𝗩𝗘𝗦 ] + +### 🔴 Stop Doing - Overthinking or overplanning that slows down actual work progress. - Spending too much time on planning instead of taking action. @@ -62,12 +68,17 @@ repository on GitHub. plan, constraints, and learning goals. - The project board was organized with the required milestones and basic task cards, as planned. +- Communication was open and respectful, enabling faster resolution of blockers. +- We maintained consistent stand-ups that helped sync progress and distribute + tasks evenly as possible. 2.What parts of our plan did not work out? - Coordinating schedules across time zones was more difficult than anticipated. - Roles were not fully assigned effectively, and not every member was able to contribute to the tasks due to other personal commitments. +- Some team members, including myself, struggled with balancing individual tasks + with team support. 3.Did you need to add things that weren't in your strategy? @@ -84,7 +95,8 @@ Member 1: Banu Özyılmaz - Contributions - Participated actively in initial group meetings and discussions. - - Contributed to drafting the group norms and retrospective file. + - Contributed to drafting and editing the collaboration readme file and + retrospective file. - Provided feedback and edits to team members’ contributions in shared docs. - Challenges @@ -100,6 +112,73 @@ Member 1: Banu Özyılmaz - Felt more confident in working across cultures and establishing shared goals with a diverse team. -Member 2: +Member 2: Muhammad Shahroz + +- Contributions + + - Broke the ice with teammates and made sure everyone was added to the group + chat and repo. + - Double-checked our GitHub setup and helped iron out any access issues. + +- Challenges + + - Figuring out everyone’s availability with the time differences took some back-and-forth. + - Needed to quickly learn new collaboration tools and adapt to the team’s workflow. + +- Progress + + - Started building a routine for team updates and keeping tasks transparent. + - Feel good about the team’s openness and ready to take on more technical work + in the next phase. + +Member 3: Amro Mohamed + +- Contributions + + - Adjusted repository settings to streamline workflow and maintain project organization. + - Contributed to drafting and editing the learning goals file. + - Collaborated effectively with team members. + - Planned and hosted the team video meetings. + +- Challenges + + - Occasional misalignment on task priorities caused rework and delays. + - Some team members, including myself, struggled with balancing individual tasks + with team support. + +- Progress + + - Learned to be more proactive in communicating. + - Improved at using tools like Git, and Slack for better team coordination. + - Gained a deeper appreciation for the diversity of skills within the team. + +Member 4: + +- Contributions + + - + +- Challenges + + - +- Progress + + - + +Member 5: + +- Contributions + + - + +- Challenges + + - +- Progress + + - + +
+ --- From 16a8d730932be6826da2a574713db3b28a9b7093 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Tue, 3 Jun 2025 21:50:52 -0400 Subject: [PATCH 34/70] docs: add contributions of a team member for individual retrospectives --- collaboration/retrospective.md | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/collaboration/retrospective.md b/collaboration/retrospective.md index 5feadb5ad..f380881f8 100644 --- a/collaboration/retrospective.md +++ b/collaboration/retrospective.md @@ -82,11 +82,13 @@ to the tasks due to other personal commitments. 3.Did you need to add things that weren't in your strategy? - ... +- Yes, we needed to create a more detailed schedule that includes task assignments + for each person and clear deadlines. This would help improve task ownership and + keep everyone aligned. 4.Or remove extra steps? -... +- There weren't any extra steps. ### 👤 Individual Retrospectives @@ -152,18 +154,29 @@ Member 3: Amro Mohamed - Improved at using tools like Git, and Slack for better team coordination. - Gained a deeper appreciation for the diversity of skills within the team. -Member 4: +Member 4: Azza Omer - Contributions - - + - Collaborated with the team by sharing my opinions, encouraging others in a + positive way. + - Actively attending meetings. + - Contributed to drafting and editing the constraints file. - Challenges - - + - There was no clear plan for task distribution or tracking, which made it + harder to know who was responsible for what. + - Time zone differences affected participation and limited the ability to share + feedback effectively. + - Felt the need to be more involved in team activities. + - Progress - - + - Became more comfortable using GitHub and VS Code. + - Found that having a clear plan helped reduce overthinking and anxiety. + - Improved in showcasing more of my skills . + - Became more open to listening to different perspectives from team members. Member 5: From 6ae70f7e4f1b3a04685af6780f1a819c0c425358 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Thu, 5 Jun 2025 16:13:40 -0400 Subject: [PATCH 35/70] updated and reorganized content to match the new retrospective folder structure --- .../0_cross_cultural_collaboration.md | 164 +++++++++++++++ collaboration/retrospectives/README.md | 31 ++- collaboration/retrospectives/_template.md | 198 ++---------------- 3 files changed, 210 insertions(+), 183 deletions(-) diff --git a/collaboration/retrospectives/0_cross_cultural_collaboration.md b/collaboration/retrospectives/0_cross_cultural_collaboration.md index e69de29bb..d94213bc6 100644 --- a/collaboration/retrospectives/0_cross_cultural_collaboration.md +++ b/collaboration/retrospectives/0_cross_cultural_collaboration.md @@ -0,0 +1,164 @@ +# Milestone 0: Cross-Cultural Collaboration + +This part summarizes our team’s experience and reflections from +Milestone 0, focused on Cross-Cultural Collaboration. The primary goal of this milestone +was to establish the foundations for effective teamwork by exploring cross-cultural +communication, design thinking, and innovation methodologies. + +During this phase (May 27 – June 2), we got to know our teammates, defined our collaboration +strategy, and prepared our GitHub repository and shared documents. Below is our +collective reflection on what went well, what we can improve, and what we’ve learned +from working together so far. + +## 🔴 Stop Doing + +- Overthinking or overplanning that slows down actual work progress. +- Spending too much time on planning instead of taking action. +- Being inactive for long periods without informing the team in advance, which +can unintentionally disrupt collaboration. + +## 🟢 Continue Doing + +- Communicating clearly and respectfully across time zones and cultures. +- Using collaborative tools like GitHub Projects and shared documents to stay organized. +- Using a shared space (like a Slack channel or Discord) for quick questions and +updates. +- Supporting each other in setting up the repository and assigning roles. +- Having open discussions for project process. + +## 🟡 Start Doing + +- Establishing a regular check-in schedule to keep everyone aligned. +- Inform the group in advance if you expect to be unavailable or less responsive, +so the team can adjust plans accordingly. +- Adding brief summaries after each meeting to make sure we’re all on the same page. + +## 💡 Lessons Learned + +- Cross-cultural collaboration requires patience and active listening, especially +early on. +- Setting up solid foundations (norms, communication plans, etc.) helps avoid +misunderstandings later. +- Effective communication is essential for successful collaboration. +- Having structure (like milestones and a project board) from the beginning helps +reduce stress. + +## 📊 Strategy vs. Board + +1.What parts of our plan went as expected? + +- We successfully met our group and set up the foundational structure of our project +repository on GitHub. +- We created and agreed upon key collaboration documents: group norms, communication +plan, constraints, and learning goals. +- The project board was organized with the required milestones and basic task cards, +as planned. +- Communication was open and respectful, enabling faster resolution of blockers. +- We maintained consistent stand-ups that helped sync progress and distribute + tasks evenly as possible. + +2.What parts of our plan did not work out? + +- Coordinating schedules across time zones was more difficult than anticipated. +- Roles were not fully assigned effectively, and not every member was able to contribute +to the tasks due to other personal commitments. +- Some team members, including myself, struggled with balancing individual tasks + with team support. + +3.Did you need to add things that weren't in your strategy? + +- Yes, we needed to create a more detailed schedule that includes task assignments + for each person and clear deadlines. This would help improve task ownership and + keep everyone aligned. + +4.Or remove extra steps? + +- There weren't any extra steps. + +## 👤 Individual Retrospectives + +Member 1: Banu Özyılmaz + +- Contributions + + - Participated actively in initial group meetings and discussions. + - Contributed to drafting and editing the collaboration readme file and + retrospective file. + - Provided feedback and edits to team members’ contributions in shared docs. + +- Challenges + + - Adjusting to different time zones and response times. + - Balancing this milestone with other responsibilities required extra planning. + +- Progress + + - Gained a better understanding of the value of defining constraints and + expectations early. + - Improved skills in async collaboration and version control using GitHub. + - Felt more confident in working across cultures and establishing shared goals + with a diverse team. + +Member 2: Muhammad Shahroz + +- Contributions + + - Broke the ice with teammates and made sure everyone was added to the group + chat and repo. + - Double-checked our GitHub setup and helped iron out any access issues. + +- Challenges + + - Figuring out everyone’s availability with the time differences took some back-and-forth. + - Needed to quickly learn new collaboration tools and adapt to the team’s workflow. + +- Progress + + - Started building a routine for team updates and keeping tasks transparent. + - Feel good about the team’s openness and ready to take on more technical work + in the next phase. + +Member 3: Amro Mohamed + +- Contributions + + - Adjusted repository settings to streamline workflow and maintain project organization. + - Contributed to drafting and editing the learning goals file. + - Collaborated effectively with team members. + - Planned and hosted the team video meetings. + +- Challenges + + - Occasional misalignment on task priorities caused rework and delays. + - Some team members, including myself, struggled with balancing individual tasks + with team support. + +- Progress + + - Learned to be more proactive in communicating. + - Improved at using tools like Git, and Slack for better team coordination. + - Gained a deeper appreciation for the diversity of skills within the team. + +Member 4: Azza Omer + +- Contributions + + - Collaborated with the team by sharing my opinions, encouraging others in a + positive way. + - Actively attending meetings. + - Contributed to drafting and editing the constraints file. + +- Challenges + + - There was no clear plan for task distribution or tracking, which made it + harder to know who was responsible for what. + - Time zone differences affected participation and limited the ability to share + feedback effectively. + - Felt the need to be more involved in team activities. + +- Progress + + - Became more comfortable using GitHub and VS Code. + - Found that having a clear plan helped reduce overthinking and anxiety. + - Improved in showcasing more of my skills . + - Became more open to listening to different perspectives from team members. diff --git a/collaboration/retrospectives/README.md b/collaboration/retrospectives/README.md index 08d9b0582..4d0c8209d 100644 --- a/collaboration/retrospectives/README.md +++ b/collaboration/retrospectives/README.md @@ -1,3 +1,32 @@ # Retrospectives -Retrospective documents for each milestone of the CDSP. +> *“We do not learn from experience... we learn from reflecting on +> experience.”* +> — John Dewey + +This folder contains our team’s retrospectives, written at the end of each milestone +to reflect on our progress, collaboration, and learning process. + +Retrospectives are a critical part of our workflow. They allow us to step back, +evaluate what went well, what could be improved, and identify actionable lessons +that can strengthen our performance in the next phase. By documenting both individual +and collective insights, we aim to build a more adaptive, communicative, and +efficient team culture. + +--- + +## Contents 📂 + +| Milestone | File | Description | +|----------|------|-------------| +| 0️⃣ | [0_cross-cultural_collaboration.md](0_cross-cultural_collaboration.md) | Reflections on early team formation and intercultural collaboration. | +| 1️⃣ | [1_problem_identification.md](1_problem_identification.md) | Thoughts on defining the problem space based on personal experience. | +| 2️⃣ | [2_data_collection.md](2_data_collection.md) | Insights from planning and executing our data collection process. | +| 3️⃣ | [3_data_analysis.md](3_data_analysis.md) | Observations during data cleaning, exploration, and analysis. | +| 4️⃣ | [4_communicating_results.md](4_communicating_results.md) | Reflections on how we prepared to share our findings. | +| 5️⃣ | [5_final_presentation.md](5_final_presentation.md) | Final thoughts on presenting and wrapping up the project. | + +--- + +📌 *This retrospective folder helps us track not only what we built, but how we +built it — together.* diff --git a/collaboration/retrospectives/_template.md b/collaboration/retrospectives/_template.md index f380881f8..c24b796a7 100644 --- a/collaboration/retrospectives/_template.md +++ b/collaboration/retrospectives/_template.md @@ -1,197 +1,31 @@ -# Retrospective - -This document is a team retrospective — a reflective summary of our process, collaboration, -and outcomes during the phases of our project. It serves to identify what -went well, what could be improved, and what lessons we’ve learned to carry forward -into the next milestone. - ---- - -## Milestone 0: Cross-Cultural Collaboration - -This part summarizes our team’s experience and reflections from -Milestone 0, focused on Cross-Cultural Collaboration. The primary goal of this milestone -was to establish the foundations for effective teamwork by exploring cross-cultural -communication, design thinking, and innovation methodologies. - -During this phase (May 27 – June 2), we got to know our teammates, defined our collaboration -strategy, and prepared our GitHub repository and shared documents. Below is our -collective reflection on what went well, what we can improve, and what we’ve learned -from working together so far. - - - -
-📝 [ 𝗠𝗜𝗟𝗘𝗦𝗧𝗢𝗡𝗘 𝟬 | 𝗥𝗘𝗧𝗥𝗢𝗦𝗣𝗘𝗖𝗧𝗜𝗩𝗘𝗦 ] - -### 🔴 Stop Doing - -- Overthinking or overplanning that slows down actual work progress. -- Spending too much time on planning instead of taking action. -- Being inactive for long periods without informing the team in advance, which -can unintentionally disrupt collaboration. - -### 🟢 Continue Doing - -- Communicating clearly and respectfully across time zones and cultures. -- Using collaborative tools like GitHub Projects and shared documents to stay organized. -- Using a shared space (like a Slack channel or Discord) for quick questions and -updates. -- Supporting each other in setting up the repository and assigning roles. -- Having open discussions for project process. - -### 🟡 Start Doing - -- Establishing a regular check-in schedule to keep everyone aligned. -- Inform the group in advance if you expect to be unavailable or less responsive, -so the team can adjust plans accordingly. -- Adding brief summaries after each meeting to make sure we’re all on the same page. - -### 💡 Lessons Learned - -- Cross-cultural collaboration requires patience and active listening, especially -early on. -- Setting up solid foundations (norms, communication plans, etc.) helps avoid -misunderstandings later. -- Effective communication is essential for successful collaboration. -- Having structure (like milestones and a project board) from the beginning helps -reduce stress. - -### 📊 Strategy vs. Board - -1.What parts of our plan went as expected? - -- We successfully met our group and set up the foundational structure of our project -repository on GitHub. -- We created and agreed upon key collaboration documents: group norms, communication -plan, constraints, and learning goals. -- The project board was organized with the required milestones and basic task cards, -as planned. -- Communication was open and respectful, enabling faster resolution of blockers. -- We maintained consistent stand-ups that helped sync progress and distribute - tasks evenly as possible. - -2.What parts of our plan did not work out? + -- Coordinating schedules across time zones was more difficult than anticipated. -- Roles were not fully assigned effectively, and not every member was able to contribute -to the tasks due to other personal commitments. -- Some team members, including myself, struggled with balancing individual tasks - with team support. - -3.Did you need to add things that weren't in your strategy? - -- Yes, we needed to create a more detailed schedule that includes task assignments - for each person and clear deadlines. This would help improve task ownership and - keep everyone aligned. - -4.Or remove extra steps? - -- There weren't any extra steps. - -### 👤 Individual Retrospectives - -Member 1: Banu Özyılmaz - -- Contributions - - - Participated actively in initial group meetings and discussions. - - Contributed to drafting and editing the collaboration readme file and - retrospective file. - - Provided feedback and edits to team members’ contributions in shared docs. - -- Challenges - - - Adjusting to different time zones and response times. - - Balancing this milestone with other responsibilities required extra planning. - -- Progress - - - Gained a better understanding of the value of defining constraints and - expectations early. - - Improved skills in async collaboration and version control using GitHub. - - Felt more confident in working across cultures and establishing shared goals - with a diverse team. - -Member 2: Muhammad Shahroz - -- Contributions - - - Broke the ice with teammates and made sure everyone was added to the group - chat and repo. - - Double-checked our GitHub setup and helped iron out any access issues. - -- Challenges - - - Figuring out everyone’s availability with the time differences took some back-and-forth. - - Needed to quickly learn new collaboration tools and adapt to the team’s workflow. +# Retrospective -- Progress +## Stop Doing - - Started building a routine for team updates and keeping tasks transparent. - - Feel good about the team’s openness and ready to take on more technical work - in the next phase. +## Continue Doing -Member 3: Amro Mohamed +## Start Doing -- Contributions - - - Adjusted repository settings to streamline workflow and maintain project organization. - - Contributed to drafting and editing the learning goals file. - - Collaborated effectively with team members. - - Planned and hosted the team video meetings. +## Lessons Learned -- Challenges - - - Occasional misalignment on task priorities caused rework and delays. - - Some team members, including myself, struggled with balancing individual tasks - with team support. +--- -- Progress - - - Learned to be more proactive in communicating. - - Improved at using tools like Git, and Slack for better team coordination. - - Gained a deeper appreciation for the diversity of skills within the team. +## Strategy vs. Board -Member 4: Azza Omer +### What parts of your plan went as expected? -- Contributions - - - Collaborated with the team by sharing my opinions, encouraging others in a - positive way. - - Actively attending meetings. - - Contributed to drafting and editing the constraints file. +### What parts of your plan did not work out? -- Challenges - - - There was no clear plan for task distribution or tracking, which made it - harder to know who was responsible for what. - - Time zone differences affected participation and limited the ability to share - feedback effectively. - - Felt the need to be more involved in team activities. - -- Progress - - - Became more comfortable using GitHub and VS Code. - - Found that having a clear plan helped reduce overthinking and anxiety. - - Improved in showcasing more of my skills . - - Became more open to listening to different perspectives from team members. +### Did you need to add things that weren't in your strategy? -Member 5: +### Or remove extra steps? -- Contributions - - - +--- -- Challenges - - - -- Progress - - - +## Individual Rerospectives -
- +### Name ---- + From 2265e56848ab0c88ce6e17176199eb4c83393802 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Mon, 9 Jun 2025 14:28:37 -0400 Subject: [PATCH 36/70] docs: add contribution guidelines to contributing.md --- CONTRIBUTING.md | 70 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 70 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e69de29bb..2d654eea6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -0,0 +1,70 @@ +# CONTRIBUTING.md + +Welcome to The Data Detectives, + +We are an international, interdisciplinary team working across time zones, cultures, +and communication styles. To ensure respectful, inclusive, and effective collaboration, +please follow these guidelines when contributing to this project. + +--- + +## 🌍 Be Culturally Respectful + +- Assume good intent — different expressions or tones may reflect cultural habits, + not rudeness. +- Avoid idioms, slang, or region-specific references unless you explain them. +- Be mindful of cultural holidays and differing weekend schedules. + +--- + +## 🕓 Respect Time Zones and Asynchronous Work + +- Don’t expect immediate responses. Allow some time for replies. +- Use clear timestamps (with time zones) when proposing meetings or deadlines. +- Document decisions in writing so team members in other zones stay informed. +- Assign tasks through the GitHub Project Board so everyone can follow the workflow. + +--- + +## 💬 Communicate Clearly + +- Keep messages concise and easy to understand. +- Use bullet points, visuals, or summaries to make complex ideas easier to follow. +- Ask for clarification when something is unclear, and be patient when others do + the same. + +--- + +## 🎯 Contribute Inclusively + +- Encourage input from all team members, especially those who may feel less + confident due to language or experience. +- Respect different work styles, speeds, and levels of expertise. +- Use shared documents and GitHub Issues to promote transparency and equal + participation. + +--- + +## 🛠 GitHub Contribution Process + +- Track tasks on the GitHub Project Board — this helps us coordinate across different + time zones and prevents duplicated effort. +- Open an **Issue** before making any significant changes. Use it to describe + your idea, get feedback, and confirm alignment with team priorities. +- Create **Pull Requests (PRs)** linked to existing issues. Include clear descriptions +- and screenshots (if applicable). +- Every PR must be reviewed by at least **two team members** before it is merged + — this - ensures shared understanding, quality, and accountability. +- Use **Draft PRs** if your work is still in progress but you'd like early feedback. + +--- + +## 🚀 Let’s Build Together + +This is a learning environment—everyone brings something valuable. +Let’s co-create a respectful and inclusive space where differences are strengths, +and feedback is welcomed as a tool for collective growth. + +--- + +Thank you for contributing 💙 From 8181f0be285663a7bea30c6d3842972717f9cd46 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Mon, 9 Jun 2025 15:36:47 -0400 Subject: [PATCH 37/70] fix: fix a broken link on retrospectives README --- collaboration/retrospectives/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/collaboration/retrospectives/README.md b/collaboration/retrospectives/README.md index 4d0c8209d..772d575a1 100644 --- a/collaboration/retrospectives/README.md +++ b/collaboration/retrospectives/README.md @@ -19,7 +19,7 @@ efficient team culture. | Milestone | File | Description | |----------|------|-------------| -| 0️⃣ | [0_cross-cultural_collaboration.md](0_cross-cultural_collaboration.md) | Reflections on early team formation and intercultural collaboration. | +| 0️⃣ | [0_cross_cultural_collaboration.md](0_cross_cultural_collaboration.md) | Reflections on early team formation and intercultural collaboration. | | 1️⃣ | [1_problem_identification.md](1_problem_identification.md) | Thoughts on defining the problem space based on personal experience. | | 2️⃣ | [2_data_collection.md](2_data_collection.md) | Insights from planning and executing our data collection process. | | 3️⃣ | [3_data_analysis.md](3_data_analysis.md) | Observations during data cleaning, exploration, and analysis. | From bf63e5bbba2cde50920e1a79ac40ced0e5074fec Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Mon, 9 Jun 2025 15:49:27 -0400 Subject: [PATCH 38/70] docs: update files included link for retrospectives section --- collaboration/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/collaboration/README.md b/collaboration/README.md index d933f23a3..300fc30a1 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -22,8 +22,8 @@ the shared group norms that guide how we work together as a team. Defines what each team member hopes to learn during the project, both technically and collaboratively. -- [**retrospective.md**](retrospective.md) - A place for team reflection at several points in the project, such as what went +- [**retrospectives**](retrospectives/) + A folder for team reflections at several points in the project, such as what went well, what didn't, and how to do it differently next time. Keeping these documents up to date helps us stay transparent, focused, goal-oriented, From c01e1aada025842ecbd65cd7e93c9d433031246f Mon Sep 17 00:00:00 2001 From: Banu Ozyilmaz Date: Thu, 12 Jun 2025 14:23:30 -0400 Subject: [PATCH 39/70] docs: update typos in CONTRIBUTING.md --- CONTRIBUTING.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2d654eea6..9a4c36ab9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,7 +3,7 @@ Welcome to The Data Detectives, We are an international, interdisciplinary team working across time zones, cultures, -and communication styles. To ensure respectful, inclusive, and effective collaboration, +and communication styles. To ensure respectful, inclusive, and effective collaboration, please follow these guidelines when contributing to this project. --- @@ -11,7 +11,7 @@ please follow these guidelines when contributing to this project. ## 🌍 Be Culturally Respectful - Assume good intent — different expressions or tones may reflect cultural habits, - not rudeness. +not rudeness. - Avoid idioms, slang, or region-specific references unless you explain them. - Be mindful of cultural holidays and differing weekend schedules. @@ -31,30 +31,30 @@ please follow these guidelines when contributing to this project. - Keep messages concise and easy to understand. - Use bullet points, visuals, or summaries to make complex ideas easier to follow. - Ask for clarification when something is unclear, and be patient when others do - the same. +the same. --- ## 🎯 Contribute Inclusively - Encourage input from all team members, especially those who may feel less - confident due to language or experience. +confident due to language or experience. - Respect different work styles, speeds, and levels of expertise. - Use shared documents and GitHub Issues to promote transparency and equal - participation. +participation. --- ## 🛠 GitHub Contribution Process - Track tasks on the GitHub Project Board — this helps us coordinate across different - time zones and prevents duplicated effort. +time zones and prevents duplicated effort. - Open an **Issue** before making any significant changes. Use it to describe - your idea, get feedback, and confirm alignment with team priorities. +your idea, get feedback, and confirm alignment with team priorities. - Create **Pull Requests (PRs)** linked to existing issues. Include clear descriptions -- and screenshots (if applicable). +and screenshots (if applicable). - Every PR must be reviewed by at least **two team members** before it is merged - — this - ensures shared understanding, quality, and accountability. + — this ensures shared understanding, quality, and accountability. - Use **Draft PRs** if your work is still in progress but you'd like early feedback. --- From 65ae8493878c3b26d604211cdc68ea91346ac8e1 Mon Sep 17 00:00:00 2001 From: Banu Ozyilmaz Date: Thu, 12 Jun 2025 14:28:10 -0400 Subject: [PATCH 40/70] Fix: md formatting fix for CONTRIBUTING.md --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9a4c36ab9..92b53ab8c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,7 +3,7 @@ Welcome to The Data Detectives, We are an international, interdisciplinary team working across time zones, cultures, -and communication styles. To ensure respectful, inclusive, and effective collaboration, +and communication styles. To ensure respectful, inclusive, and effective collaboration, please follow these guidelines when contributing to this project. --- From 66c64afb2a5827612247d4ed7ad2530953599af6 Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Thu, 12 Jun 2025 14:33:07 -0400 Subject: [PATCH 41/70] fix: fix md formatting error --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2d654eea6..8344f98fd 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -52,9 +52,9 @@ please follow these guidelines when contributing to this project. - Open an **Issue** before making any significant changes. Use it to describe your idea, get feedback, and confirm alignment with team priorities. - Create **Pull Requests (PRs)** linked to existing issues. Include clear descriptions -- and screenshots (if applicable). -- Every PR must be reviewed by at least **two team members** before it is merged - — this - ensures shared understanding, quality, and accountability. + and screenshots (if applicable). +- Every PR must be reviewed by at least **two team members** before it is merged. + This ensures shared understanding, quality, and accountability. - Use **Draft PRs** if your work is still in progress but you'd like early feedback. --- From c66252cd0b21c16bee1f0e10f5077c8eedac8b8b Mon Sep 17 00:00:00 2001 From: doctorbanu Date: Fri, 13 Jun 2025 15:18:02 -0400 Subject: [PATCH 42/70] docs: Rewrite CONTRIBUTING.md for clarity and structure - Completely reorganized the CONTRIBUTING.md file for better readability and navigation - Added collapsible sections and improved visual formatting - Updated and reworded content based on teammate feedback - Adjusted markdownlint rules for optimal appearance --- CONTRIBUTING.md | 230 ++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 193 insertions(+), 37 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d362b7418..4616852b3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,70 +1,226 @@ + + + + # CONTRIBUTING.md -Welcome to The Data Detectives, +Welcome to The Data Detectives! 👋 We are an international, interdisciplinary team working across time zones, cultures, and communication styles. To ensure respectful, inclusive, and effective collaboration, -please follow these guidelines when contributing to this project. +please follow these guidelines when contributing to this project. 👇 --- -## 🌍 Be Culturally Respectful +
+

🏗️ Repository Structure

 -- Assume good intent — different expressions or tones may reflect cultural habits, -not rudeness. -- Avoid idioms, slang, or region-specific references unless you explain them. -- Be mindful of cultural holidays and differing weekend schedules. +Please take a moment to get acquainted with the key directories and files in this repository: + +| Path | Description | +|-----------------------------------------|--------------------------------------------------------------------------------------| +| **/collaboration** | Materials for team communication, group norms, learning goals, constraints, and retrospectives. | +| **/notes** | Shared tools, guides, resources and useful references for the team. | +| **/0_domain_study → /6_final_presentation** | Project deliverables arranged by milestones | +| **README.md, CONTRIBUTING.md** | Core documentation for understanding and contributing to the project. | + +
+ +--- + +
+

🌍 Be Culturally Respectful

 + +- Assume positive intent — differences in expression or tone may reflect cultural backgrounds, not disrespect. +- Limit the use of idioms, slang, or culture-specific references, or explain them if used. +- Remember that holidays and weekends may vary across cultures and locations. + +
+ +--- + +
+

🕓 Respect Time Zones and Asynchronous Work

 + +- Don’t expect instant responses; allow time for team members to reply. +- Use clear dates and specify time zones when coordinating meetings or deadlines. +- Document any decisions so collaborators in other time zones stay in the loop. +- Assign and track tasks on the GitHub Project Board for team-wide visibility. + +
+ +--- + +
+

💬 Communicate Clearly

 + +- Keep your messages clear and to the point. +- Use lists, visuals, or brief summaries to break down complex ideas. +- Request clarification if you’re confused, and be patient with questions from others. + +
+ +--- + +
+

🎯 Contribute Inclusively

 + +- Invite participation from everyone, especially those less comfortable with language or tools. +- Value different working styles, speeds, and levels of experience. +- Use shared docs and GitHub Issues to ensure everyone can contribute and stay informed. + +
+ +--- + +
+

🛠 GitHub Workflow

 + +### 1. 🖇️ Cloning the Repository + +- You can either: + + - Use VSCode → "Clone Git Repository" + + - Or use terminal with following command: + +```bash +git clone https://github.com/MIT-Emerging-Talent/ET6-CDSP-group-19-repo.git +cd ET6-CDSP-group-19-repo +``` + +--- + +### 2. 🌿 Creating & Updating a Branch + +- Make a new branch for your feature or fix: + + ```bash + git checkout -b your_branch_name + ``` + + ✔ Use clear names: `docs-collaboration`, `bug-fix` + +- To keep your branch updated with main: + + ```bash + git checkout main + git pull origin main + git checkout your_branch_name + git merge main + ``` + +--- + +### 3. 🚀 Making & Pushing Changes + +- Only stage files you intend to change: + + ```bash + git add specific_file.py + git commit -m "feat: add milestone summary" + git push origin your_branch_name + ``` + + ❌ Avoid using 'git add .' + +--- + +### 4. 🧩 Working with Issues + +- Always check for an existing issue before creating a new one. +- Use issues for bugs, ideas, or questions; describe your suggestion, get feedback, and make sure it fits team priorities. +- Write clear titles and details. +- Assign yourself to an issue when you start. +- Reference issues in Pull Requests (e.g., `Closes #7`). --- -## 🕓 Respect Time Zones and Asynchronous Work +### 5. 📥 Creating a Pull Request (PR) + +- After pushing your branch: + + - **Option 1:** Click **Compare & Pull Request** on the repo homepage. + - **Option 2:** + 1. Go to the Pull Requests tab → New Pull Request + 2. Select your branch and `main` + 3. Click **Create Pull Request** -- Don’t expect immediate responses. Allow some time for replies. -- Use clear timestamps (with time zones) when proposing meetings or deadlines. -- Document decisions in writing so team members in other zones stay informed. -- Assign tasks through the GitHub Project Board so everyone can follow the workflow. +- Your PR should include: + + - What you changed & why + - Linked issue (e.g., `Closes #4`) + - Screenshots or notes if helpful + +❗ Every PR must be reviewed by **at least two members** before merging. --- -## 💬 Communicate Clearly +### 6. 🔁 Review & Merge -- Keep messages concise and easy to understand. -- Use bullet points, visuals, or summaries to make complex ideas easier to follow. -- Ask for clarification when something is unclear, and be patient when others do -the same. +- Assign reviewers and move your task to **Ready for Review** on the Project Board. +- After approval, click **Merge pull request → Confirm merge.** +- Move the corresponding card to **Done** on the Project Board. --- -## 🎯 Contribute Inclusively +### 7. ⚔️ Resolving Merge Conflicts + +- If your branch is behind `main`, follow these steps: + +```bash +git checkout main +git pull origin main +git checkout your_branch_name +git merge main +``` -- Encourage input from all team members, especially those who may feel less -confident due to language or experience. -- Respect different work styles, speeds, and levels of expertise. -- Use shared documents and GitHub Issues to promote transparency and equal -participation. +- If there are conflicts: + + - VSCode will highlight the conflicting areas (`<<<<<<<`) + - Manually edit files to resolve + +- After fixing each file: + +```bash +git add resolved_file.py +``` + +- Finalize the merge: + +```bash +git commit -m "resolve merge conflict with main" +``` + +❗If you're unsure, don’t hesitate to ask the team before committing. --- -## 🛠 GitHub Contribution Process +### 8. 📌 Using the Project Board + +- The GitHub Project Board helps us stay organized. +- Every task should begin as an **Issue**. +- Move tasks to **In Progress** when you start. +- Move to **Ready for Review** with an open PR. +- Move to **Done** after merging. +- Keep the board updated for async teamwork. -- Track tasks on the GitHub Project Board — this helps us coordinate across different -time zones and prevents duplicated effort. -- Open an **Issue** before making any significant changes. Use it to describe -your idea, get feedback, and confirm alignment with team priorities. -- Create **Pull Requests (PRs)** linked to existing issues. Include clear descriptions - and screenshots (if applicable). -- Every PR must be reviewed by at least **two team members** before it is merged. - This ensures shared understanding, quality, and accountability. -- Use **Draft PRs** if your work is still in progress but you'd like early feedback. +
--- -## 🚀 Let’s Build Together +## 🤝 Let’s Build Together This is a learning environment—everyone brings something valuable. -Let’s co-create a respectful and inclusive space where differences are strengths, -and feedback is welcomed as a tool for collective growth. +Let’s co-create a respectful and inclusive space where differences are strengths, and feedback is welcomed as a tool for collective growth. --- -Thank you for contributing 💙 +Thank you for contributing! 💙 From f2798daf1874cbf0c63a993affe953af0539ad38 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Sat, 14 Jun 2025 11:12:44 +0300 Subject: [PATCH 43/70] filled the retrospective file of domain study milestone --- .../1_problem_identification.md | 120 ++++++++++++++++++ 1 file changed, 120 insertions(+) diff --git a/collaboration/retrospectives/1_problem_identification.md b/collaboration/retrospectives/1_problem_identification.md index e69de29bb..28c267831 100644 --- a/collaboration/retrospectives/1_problem_identification.md +++ b/collaboration/retrospectives/1_problem_identification.md @@ -0,0 +1,120 @@ +# Milestone 1: Domain Study + +**Milestone dates:** June 3 – June 16 + +--- + +## Main goal of Milestone 1 + +The main goal of this milestone was to brainstorm research ideas +using divergent thinking and select one using convergent thinking. +The goal was also to conduct a background study of our research domain +to understand what is already known and identify gaps worth exploring. +Finally, we set out to define a research question that meets +the FRESCO criteria: **Feasible, Relevant, Ethical, Specific, Complex, and Original.** + +--- + +## 🔴 Stop Doing + +- Being inactive for long periods without informing the team in advance, which + can unintentionally disrupt collaboration. +- Accumulating work until near the deadline, +which increases stress and reduces quality. + +--- + +## 🟢 Continue Doing + +- Communicating clearly and respectfully across time zones and cultures. +- Collaborating effectively through synchronous work, where team members worked + on the same task at the same time professionally. +- Maintaining strong commitment to meeting times, with all active members attending + on time. + +--- + +## 🟡 Start Doing + +- Setting a meeting agenda in advance and making meetings more systematic +by discussing agenda items one by one, +ensuring a decision is made before moving on. +- Adding brief summaries after each meeting to ensure everyone is on the same page, + and creating a clear task list from what was agreed. + +--- + +## 💡 Lessons Learned + +Sometimes what appears to be a difference of opinion +is caused by misunderstanding each other’s points, +when in fact we already agree. This can lead to wasting time +discussing points we actually agree on. + +--- + +## 📊 Strategy vs. Board + +1️⃣ **What parts of our plan went as expected?** + +- Using divergent thinking and brainstorming to generate good research question ideas. +- Working synchronously, with team members collaborating on the same task at the + same time professionally. + +2️⃣ **What parts of our plan did not work out?** + +- Keeping a task list throughout the milestone for better task division. + +3️⃣ **Did you need to add things that weren’t in your strategy?** + +- Setting clear criteria to review questions before reflecting on them. + +4️⃣ **Or remove extra steps?** + +- No extra steps were removed. + +--- + +## 👤 Individual Retrospectives + +### Member_1 + +- Contributions +- Challenges +- Progress + +### Member_2 + +- Contributions +- Challenges +- Progress + +### Member_3 + +- Contributions +- Challenges +- Progress + +### Member_4 + +- Contributions +- Challenges +- Progress + +### Member_5 + +- Contributions +- Challenges +- Progress + +### Member_6 + +- Contributions +- Challenges +- Progress + +### Member_7 + +- Contributions +- Challenges +- Progress From 93618e0195d355a2c1c3be4dc30a5a053212c73a Mon Sep 17 00:00:00 2001 From: Gennadii Ershov Date: Sun, 15 Jun 2025 03:06:36 -0400 Subject: [PATCH 44/70] docs: add Research Process Overview to README --- 0_domain_study/README.md | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/0_domain_study/README.md b/0_domain_study/README.md index 308b71113..aa5d2e6d0 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -1 +1,22 @@ -# Domain Research +# Domain Study: Immigration Law & Juvenile Justice Systems (United States) + +## Research Process Overview + +Our team followed a **divergent → convergent** workflow: + +1. **Divergent phase** – +mapped multiple domains (education, climate, health, immigration). +2. **Background scanning** – +collected key papers, the EOIR dataset, NGO reports, and recent news. +3. **FRESCO scoring** – +ranked each draft question on +Feasibility, Relevance, Ethics, Specificity, Complexity, and Originality. +4. **Convergent phase** – +immigration & juvenile justice emerged as the top-scoring domain +(see full notes → +[Google Doc](https://docs.google.com/document/d/1Wo8sHQ3FvOEXaQ5oRqN3xzSI-P6H3Mz-ySBnWYSa9dc/edit?usp=sharing) +). +5. **Focus refinement** – +narrowed scope to *access to counsel* and *case outcomes* for immigrant juveniles. + +This process culminated in the research question below. From 835bef5817af86f84c4bde60de978d53ecbae377 Mon Sep 17 00:00:00 2001 From: Gennadii Ershov Date: Sun, 15 Jun 2025 03:27:06 -0400 Subject: [PATCH 45/70] docs: add Problem Statement to README --- 0_domain_study/README.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/0_domain_study/README.md b/0_domain_study/README.md index aa5d2e6d0..846e413bf 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -20,3 +20,23 @@ immigration & juvenile justice emerged as the top-scoring domain narrowed scope to *access to counsel* and *case outcomes* for immigrant juveniles. This process culminated in the research question below. + +## Problem Statement +> + +## Background Review + +| Source / Link | One-sentence takeaway | +|---------------|-----------------------| +| [Paper A](#) | … | +| [Dataset B](#) | … | +| … | … | + +## Group Understanding Summary + +Explain—in your own words—how the domain works and where the pain points are. +You can embed a diagram, bullet causal loops, or add a short narrative. + +## Research Question From 31d76a5bc22d1f892615f0b4856338cb34bb49a5 Mon Sep 17 00:00:00 2001 From: Gennadii Ershov Date: Sun, 15 Jun 2025 03:27:44 -0400 Subject: [PATCH 46/70] docs: add Background Review to README --- 0_domain_study/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0_domain_study/README.md b/0_domain_study/README.md index 846e413bf..8671f5f39 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -22,7 +22,7 @@ narrowed scope to *access to counsel* and *case outcomes* for immigrant juvenile This process culminated in the research question below. ## Problem Statement -> From 97b3ebe5aa25484313bc42d2fe0fea52bb4dc037 Mon Sep 17 00:00:00 2001 From: Gennadii Ershov Date: Sun, 15 Jun 2025 03:28:11 -0400 Subject: [PATCH 47/70] docs: add Group Understanding Summary to README --- 0_domain_study/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/0_domain_study/README.md b/0_domain_study/README.md index 8671f5f39..60d6812fd 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -37,6 +37,6 @@ This process culminated in the research question below. ## Group Understanding Summary Explain—in your own words—how the domain works and where the pain points are. -You can embed a diagram, bullet causal loops, or add a short narrative. +You can embed a diagram, bullet causal loops, or add a short narrative ## Research Question From 5d5daf2d8a22ea1afc57595a55c2328c1b75e7d6 Mon Sep 17 00:00:00 2001 From: Gennadii Ershov Date: Sun, 15 Jun 2025 03:28:47 -0400 Subject: [PATCH 48/70] docs: add Research Question to README --- 0_domain_study/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/0_domain_study/README.md b/0_domain_study/README.md index 60d6812fd..99820f865 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -40,3 +40,5 @@ Explain—in your own words—how the domain works and where the pain points are You can embed a diagram, bullet causal loops, or add a short narrative ## Research Question + +. From da8fe475e16e8cc8c3502f477d3867be7db940b8 Mon Sep 17 00:00:00 2001 From: Gennadii Ershov Date: Sun, 15 Jun 2025 03:41:52 -0400 Subject: [PATCH 49/70] docs: update Background Review section --- 0_domain_study/README.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/0_domain_study/README.md b/0_domain_study/README.md index 99820f865..2a55d343f 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -30,9 +30,12 @@ This process culminated in the research question below. | Source / Link | One-sentence takeaway | |---------------|-----------------------| -| [Paper A](#) | … | -| [Dataset B](#) | … | -| … | … | +| [EOIR Case Data – Data.gov](https://catalog.data.gov/dataset/eoir-case-data) | A comprehensive public dataset of U.S. immigration court cases, including juvenile proceedings since 2008. | +| [TRAC Immigration Reports](https://trac.syr.edu/immigration/) | Offers aggregated immigration court statistics, but typically does not disaggregate juvenile-specific data. | +| [Los Angeles Times – Legal funding cut](https://www.latimes.com/california/story/2025-03-21/migrant-children-legal-funding-trump) | Reports on the Trump administration’s cancellation of legal aid contracts for unaccompanied minors. | +| [CNN – Migrant children custody](https://www.cnn.com/2025/06/04/politics/migrant-children-families-government-custody) | Reveals ongoing child detentions and removals without adequate legal support. | +| [The Guardian – Children left alone](https://www.theguardian.com/us-news/ng-interactive/2025/jun/05/trumps-immigration-children-unaccompanied-minors) | Details the emotional and legal isolation faced by migrant children under hardline policies. | +| [The Imprint – Kids used as bait](https://imprintnews.org/top-stories/the-children-are-being-used-as-bait/261090) | Investigates how prolonged detention and policy shifts leave immigrant children without resolution or support. | ## Group Understanding Summary @@ -41,4 +44,6 @@ You can embed a diagram, bullet causal loops, or add a short narrative ## Research Question -. +“How do changes in U.S. immigration policy under the current administration +affect access to legal representation and outcomes +for immigrant juveniles seeking protection?” From f361b95b89103e84a4c9cfe385c95a9f3533e44d Mon Sep 17 00:00:00 2001 From: Gennadii Ershov Date: Sun, 15 Jun 2025 03:45:16 -0400 Subject: [PATCH 50/70] docs: update Readme --- 0_domain_study/README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/0_domain_study/README.md b/0_domain_study/README.md index 2a55d343f..242f5f3e2 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -39,8 +39,9 @@ This process culminated in the research question below. ## Group Understanding Summary -Explain—in your own words—how the domain works and where the pain points are. -You can embed a diagram, bullet causal loops, or add a short narrative +> ## Research Question From 6f17a177c9b03af87d76f37a7c361afd99c8d706 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Sun, 15 Jun 2025 12:17:17 +0300 Subject: [PATCH 51/70] added Banu's indivdual retrospectives --- .../1_problem_identification.md | 27 ++++++++++++++++--- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/collaboration/retrospectives/1_problem_identification.md b/collaboration/retrospectives/1_problem_identification.md index 28c267831..4b5402368 100644 --- a/collaboration/retrospectives/1_problem_identification.md +++ b/collaboration/retrospectives/1_problem_identification.md @@ -77,11 +77,30 @@ discussing points we actually agree on. ## 👤 Individual Retrospectives -### Member_1 +### Banu Ozyilmaz -- Contributions -- Challenges -- Progress +> Contributions + +- Took part in the domain search by exploring sources and suggesting topic ideas. +- Helped shape research directions through team meetings and brainstorming. +- Created and refined the content of the CONTRIBUTING.md file. +- Created a Git tag. + +> Challenges + +- It was hard to narrow down broad topics into clear, focused areas +- Because of different time zones, it was hard to find enough shared meeting time. +This limited time made it harder to clarify small differences in ideas. +- Being part of this kind of process for the first time +made it hard for me to know where to start, which caused some confusion in the beginning. + +> Progress + +- Improved at moving from general themes to specific research questions. +- Learned to share early ideas to get quicker feedback. +- Became more mindful of how even small misunderstandings can hide agreement. +- Learned to apply divergent and convergent thinking more effectively. +- Learned to use the FRESCO framework to improve the quality of a research question. ### Member_2 From 5f29208abb96022f556fdf0183d442a911c64f6b Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Sun, 15 Jun 2025 23:06:28 +0300 Subject: [PATCH 52/70] Added background summary and group systems thinking to domain study --- 0_domain_study/README.md | 74 +++++++++++++++++++++++++++++++++++++++- 1 file changed, 73 insertions(+), 1 deletion(-) diff --git a/0_domain_study/README.md b/0_domain_study/README.md index 242f5f3e2..5a9b8f03b 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -28,6 +28,19 @@ This process culminated in the research question below. ## Background Review +Immigrant juveniles in the U.S. face growing challenges +due to stricter immigration policies, especially under the Trump administration. +New rules make it harder for children in ORR custody to reunite with family +by imposing tough sponsor requirements like DNA tests and proof of income. +Legal aid funding cuts leave many children to face immigration courts alone, +reducing their chances of staying in the country. Increased involvement +of immigration enforcement in child welfare discourages families +from sponsoring these children. Together, these policies create +systemic barriers that prolong detention and increase the risk of deportation +for vulnerable immigrant youths. + +### Resources + | Source / Link | One-sentence takeaway | |---------------|-----------------------| | [EOIR Case Data – Data.gov](https://catalog.data.gov/dataset/eoir-case-data) | A comprehensive public dataset of U.S. immigration court cases, including juvenile proceedings since 2008. | @@ -37,7 +50,66 @@ This process culminated in the research question below. | [The Guardian – Children left alone](https://www.theguardian.com/us-news/ng-interactive/2025/jun/05/trumps-immigration-children-unaccompanied-minors) | Details the emotional and legal isolation faced by migrant children under hardline policies. | | [The Imprint – Kids used as bait](https://imprintnews.org/top-stories/the-children-are-being-used-as-bait/261090) | Investigates how prolonged detention and policy shifts leave immigrant children without resolution or support. | -## Group Understanding Summary +## Group Understanding & breakingdown of the background review + +We applied systems thinking to the topic domain and the four previously +cited articles, to understand the complex, interconnected issues +immigrant juveniles face in accessing legal representation and reuniting +with family in the U.S. These systemic challenges result +from evolving immigration policies, funding instability, enforcement practices, +and underlying beliefs about immigrant children and legal rights. +Below is an overview organized into events, patterns/trends, structural factors, +and mental models shaping this system: + +### Events + +- The Trump administration ended funding for legal representation +of nearly 26,000 unaccompanied migrant children, severely limiting access +to counsel. +- Children face prolonged detention due to new, restrictive sponsor eligibility +requirements, including DNA testing, proof of income, and biometric data. +- ICE and DHS conduct surprise “welfare checks” at potential sponsors’ homes, +deterring families from stepping forward. +- Deportation hearings are frequently fast-tracked, pressuring children +to represent themselves without adequate legal support. +- Legal aid organizations struggle with unstable funding and reduced capacity. + +### Patterns / Trends + +- A consistent rise in unrepresented immigrant juveniles correlates with stricter +immigration policies. +- Children without attorneys have much lower appearance rates in court +and higher deportation risks. +- Detention times have tripled on average, causing increased trauma and distress. +- Families increasingly avoid sponsoring due to fear of enforcement actions. +- Legal aid funding remains vulnerable to political shifts, +undermining long-term support. + +### Structure + +- Immigration courts do not guarantee legal representation for juveniles, +unlike criminal courts. +- Legal aid depends on federal contracts subject to abrupt termination, +limiting stability. +- Sponsor approval involves complex and invasive documentation requirements. +- Court systems use “rocket docket” procedures, rushing hearings +and disadvantaging unrepresented children. +- Support systems (non-profits, social services) lack capacity to respond quickly +to policy changes. + +### Mental Models + +- Legal representation for immigrant children is widely viewed as discretionary, +not a right. +- Child welfare is often deprioritized in favor of immigration enforcement. +- Assumptions persist that stricter enforcement deters migration, +even at children’s expense. +- Some policymakers and system actors believe children can self-represent +or do not deserve counsel. +- ***Our group hold that every child deserves protection, +fairness, and legal voice, regardless of immigration status.*** + +--- > +Immigrant juveniles navigating the U.S. immigration system face significant +and growing barriers, especially due to recent policy changes that +restrict access to legal representation and critical support services. Without +proper legal aid, court interpreters, or guidance, many children — often appearing +in court alone — are unable to effectively advocate for their protection and fair +treatment. This vulnerability is compounded by longer detention times, increased +court backlogs, and language barriers, all of which severely impact their +chances of securing safety and reunification. As displaced students and +community members familiar with these struggles, we recognize that these +systemic gaps disproportionately harm immigrant children, placing thousands at +risk of deportation and trauma. This project aims to shed light on these +challenges and advocate for urgent reforms to ensure equitable legal protection +for immigrant youth. ## Background Review From e0a05e6a84795b5edb18b1cc5cff1b64dd32f8a3 Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 14:17:50 +0300 Subject: [PATCH 54/70] main README --- README.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/README.md b/README.md index 97ffd98bc..9779534f3 100644 --- a/README.md +++ b/README.md @@ -10,6 +10,18 @@ Briefly describe the goal and scope of this project. For example: --- +## Problem Statement + +Immigrant juveniles in the U.S. face serious barriers to legal +representation, especially under recent changes in immigration policy. +These policies have increased case backlogs, limited access to legal aid, +and negatively affected outcomes for children seeking protection. +Our group aims to understand how these systemic issues shaped by shifting +policies, institutional structures, and public attitudes impact vulnerable +youth and what can be done to improve fairness and access to justice. + +For more details: [0_domain_study](README.md) + ## Stack / Technologies Used - [Programming Language / Version] @@ -20,6 +32,16 @@ Briefly describe the goal and scope of this project. For example: --- +## Understanding the problem domain + +We applied systems thinking to the topic domain and the four previously cited +articles, to understand the complex, interconnected issues immigrant juveniles +face in accessing legal representation and reuniting with family in the U.S. +These systemic challenges result from evolving immigration policies, funding +instability, enforcement practices, and underlying beliefs about immigrant +children and legal rights. Below is an overview organized into events, +patterns/trends, structural factors, and mental models shaping this system: [0_domain_study](README.md) + ## Data ### Dataset Source From 79f736f949b77ad9c527ed9f00837b1fdfe50ff8 Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 14:26:27 +0300 Subject: [PATCH 55/70] main README --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9779534f3..d48bf250d 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# [Project Title] +# Seeking Safety, Denied Support ## Project Overview From 6a4df507b907b3e3127194dbe1bdfad01c60a88f Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 14:31:11 +0300 Subject: [PATCH 56/70] readme-understanding the problem domain --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index d48bf250d..111cab3ea 100644 --- a/README.md +++ b/README.md @@ -34,9 +34,9 @@ For more details: [0_domain_study](README.md) ## Understanding the problem domain -We applied systems thinking to the topic domain and the four previously cited -articles, to understand the complex, interconnected issues immigrant juveniles -face in accessing legal representation and reuniting with family in the U.S. +We applied systems thinking to the topic domain to understand the complex, +interconnected issues immigrant juveniles face in accessing legal representation +and reuniting with family in the U.S. These systemic challenges result from evolving immigration policies, funding instability, enforcement practices, and underlying beliefs about immigrant children and legal rights. Below is an overview organized into events, From a7803e3a05ee1a0047b917c56cf60f2e48381fd8 Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 15:21:12 +0300 Subject: [PATCH 57/70] fixing-readme --- README.md | 9 +++++---- collaboration/learning_goals.md | 26 +++++++++++++++++++++++++- 2 files changed, 30 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 111cab3ea..3fdbe84ac 100644 --- a/README.md +++ b/README.md @@ -37,10 +37,11 @@ For more details: [0_domain_study](README.md) We applied systems thinking to the topic domain to understand the complex, interconnected issues immigrant juveniles face in accessing legal representation and reuniting with family in the U.S. -These systemic challenges result from evolving immigration policies, funding -instability, enforcement practices, and underlying beliefs about immigrant -children and legal rights. Below is an overview organized into events, -patterns/trends, structural factors, and mental models shaping this system: [0_domain_study](README.md) +These systemic challenges result from increasingly restrictive immigration +policies, funding instability, enforcement practices, and underlying beliefs +about immigrant children and legal rights. + + [0_domain_study](README.md) ## Data diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index 6ae6472d3..2cb1f75fe 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -59,4 +59,28 @@ so we can collaborate smoothly as a team. 2-communicating efficiently and putting in effort for the team’s success—not just individual progress. --Member6 +Milestone 1: Problem Identification + +-AmroMohamed: + +1.better understand the domain of our problem + +2.collaboration skills + +-AmmarIbrahim + +-MuhammadShahroz + +1.Enhance cross–time–zone coordination + +2.Improve time‑blocking and productivity + +-BanuÖzyılmaz + +-Gennadii + +1.Improve collaboration skills in diverse teams. + +2.Build a better understanding of product management and project ownership. + +-AzzaOmer From 3677c1c405fc19d35643fda26ecfff553d78ca01 Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 16:16:23 +0300 Subject: [PATCH 58/70] fixing-readme --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3fdbe84ac..cbbb97717 100644 --- a/README.md +++ b/README.md @@ -41,7 +41,9 @@ These systemic challenges result from increasingly restrictive immigration policies, funding instability, enforcement practices, and underlying beliefs about immigrant children and legal rights. - [0_domain_study](README.md) +For a more detailed breakdown of the system, including key events, trends, +structures, and underlying mental models, check out the full overview: +[0_domain_study](README.md) ## Data From 2de45405e88714377b79d4cd67c503a0e0ed205c Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 16:44:12 +0300 Subject: [PATCH 59/70] editing learning goals --- collaboration/learning_goals.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index 2cb1f75fe..ac05dde4a 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -77,6 +77,12 @@ Milestone 1: Problem Identification -BanuÖzyılmaz +1.Understand the basics and process clearly: + +2.Improve problem framing and Breaking down complex problems + +3.Build the habit of using FRESCO test + -Gennadii 1.Improve collaboration skills in diverse teams. From 0f8d9d319a470c5c5bde76726d4729388bdc3d8e Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 18:56:46 +0300 Subject: [PATCH 60/70] the project title --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cbbb97717..343299dca 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,6 @@ -# Seeking Safety, Denied Support +# Barriers to Justice + +How Immigration Policies Affect Immigrant Juveniles Seeking Protection ## Project Overview From c421b096b0efbdc6b6d02498b8ca4d62cb84f88d Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 19:07:02 +0300 Subject: [PATCH 61/70] the project overview --- README.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 343299dca..3cf09eeb2 100644 --- a/README.md +++ b/README.md @@ -4,11 +4,17 @@ How Immigration Policies Affect Immigrant Juveniles Seeking Protection ## Project Overview -Briefly describe the goal and scope of this project. For example: +The goal of this project is to explore how recent changes in U.S. immigration +policy under the current administration are affecting immigrant juveniles’ +access to legal representation and the outcomes of their protection cases. -- What problem are you trying to solve? -- What questions are you aiming to answer? -- Why is this analysis or application important? +Our key questions include: + +-How have recent policy shifts impacted access to legal aid for immigrant juveniles? + +-What are the trends in case outcomes for unrepresented versus represented youth? + +-What structural or systemic factors contribute to the legal gap? --- From 9e7f347090d30be95d55b7a49d964c8696425c49 Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 19:12:25 +0300 Subject: [PATCH 62/70] fixed the links in the main README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3cf09eeb2..1d180e6cc 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ Our group aims to understand how these systemic issues shaped by shifting policies, institutional structures, and public attitudes impact vulnerable youth and what can be done to improve fairness and access to justice. -For more details: [0_domain_study](README.md) +For more details: [0_domain_study](0_domain_study/README.md) ## Stack / Technologies Used @@ -51,7 +51,7 @@ about immigrant children and legal rights. For a more detailed breakdown of the system, including key events, trends, structures, and underlying mental models, check out the full overview: -[0_domain_study](README.md) +[0_domain_study](0_domain_study/README.md) ## Data From a41f15265a405041570aedaaa7e2c14c67ec85d0 Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 19:58:54 +0300 Subject: [PATCH 63/70] fixed the links in the main README --- collaboration/learning_goals.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index ac05dde4a..64f704e27 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -90,3 +90,9 @@ Milestone 1: Problem Identification 2.Build a better understanding of product management and project ownership. -AzzaOmer + +1.Understanding Problem Identification + +2.Formulating Research Question + +3.Applying FRESCO Methodology From 9cbd4954c8ff83b273fa8bd264e411ec94581581 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Mon, 16 Jun 2025 20:00:18 +0300 Subject: [PATCH 64/70] added Ammar's individual retrospectives and edited Banu's ones --- .../1_problem_identification.md | 25 ++++++++++++++++--- 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/collaboration/retrospectives/1_problem_identification.md b/collaboration/retrospectives/1_problem_identification.md index 4b5402368..020605c1d 100644 --- a/collaboration/retrospectives/1_problem_identification.md +++ b/collaboration/retrospectives/1_problem_identification.md @@ -85,6 +85,7 @@ discussing points we actually agree on. - Helped shape research directions through team meetings and brainstorming. - Created and refined the content of the CONTRIBUTING.md file. - Created a Git tag. +- Helped finalize the problem statement. > Challenges @@ -102,11 +103,27 @@ made it hard for me to know where to start, which caused some confusion in the b - Learned to apply divergent and convergent thinking more effectively. - Learned to use the FRESCO framework to improve the quality of a research question. -### Member_2 +### Ammar Osman -- Contributions -- Challenges -- Progress +> Contributions + +- Helped in writing the understanding of the problem by applying systems +thinking to the background resources, and by combining and summarizing the ideas. +- Helped in summarizing the problem statement to its final form. +- Wrote this retrospective file. + +> Challenges + +- Balancing multiple responsibilities while meeting project deadlines. +- Following up on all the feedback and discussions across different platforms +(GitHub, Slack). + +> Progress + +- Improved in applying systems thinking to structure and analyze complex problems. +- Became better at summarizing and refining collaborative work into clear, final +forms. +- Gained more confidence in dealing with GitHub workflows. ### Member_3 From 8e515f1f4279f7e7da9f915b2748dc29d16c9679 Mon Sep 17 00:00:00 2001 From: Elshikh-Amro Date: Mon, 16 Jun 2025 20:15:58 +0300 Subject: [PATCH 65/70] adding the actionabl reasarch question --- README.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/README.md b/README.md index 1d180e6cc..cb679c53a 100644 --- a/README.md +++ b/README.md @@ -53,6 +53,34 @@ For a more detailed breakdown of the system, including key events, trends, structures, and underlying mental models, check out the full overview: [0_domain_study](0_domain_study/README.md) +## Actionable Research Question + +How do changes in U.S. immigration policy under the current administration +affect access to legal representation and outcomes for immigrant juveniles +seeking protection? + +--- +Context & Constraints: + +-Domain: U.S. immigration law and policy, focused on juveniles (minors) seeking +legal protection (e.g., asylum, Special Immigrant Juvenile Status). + +-Realities: Immigration policy is dynamic and politically influenced; juvenile +immigrants face complex barriers navigating the legal system; access to legal +counsel is crucial for fair outcomes. + +--Constraints: + +-Data Availability: Data on representation and case outcomes may be fragmented + (court records, NGO data, government statistics). Policy changes may not be + immediately or transparently reflected in public data. + +-Ethical/Legal: Privacy concerns for minors; potential bias in available datasets. + +-Temporal/Geographical Scope: Defining the appropriate time window may be + required. The study can be nationwide or limited to areas with sufficient or + high-priority data. + ## Data ### Dataset Source From bc9a5046e344142ffde65c9d334962f98704f3fb Mon Sep 17 00:00:00 2001 From: Banu Ozyilmaz Date: Mon, 16 Jun 2025 13:39:33 -0400 Subject: [PATCH 66/70] docs: made minor formatting changes for improved readabiliy on main README --- README.md | 42 +++++++++++++++++++----------------------- 1 file changed, 19 insertions(+), 23 deletions(-) diff --git a/README.md b/README.md index cb679c53a..e92a1daba 100644 --- a/README.md +++ b/README.md @@ -10,11 +10,9 @@ access to legal representation and the outcomes of their protection cases. Our key questions include: --How have recent policy shifts impacted access to legal aid for immigrant juveniles? - --What are the trends in case outcomes for unrepresented versus represented youth? - --What structural or systemic factors contribute to the legal gap? +- How have recent policy shifts impacted access to legal aid for immigrant juveniles? +- What are the trends in case outcomes for unrepresented versus represented youth? +- What structural or systemic factors contribute to the legal gap? --- @@ -40,7 +38,7 @@ For more details: [0_domain_study](0_domain_study/README.md) --- -## Understanding the problem domain +## Understanding the Problem Domain We applied systems thinking to the topic domain to understand the complex, interconnected issues immigrant juveniles face in accessing legal representation @@ -55,32 +53,30 @@ structures, and underlying mental models, check out the full overview: ## Actionable Research Question -How do changes in U.S. immigration policy under the current administration -affect access to legal representation and outcomes for immigrant juveniles -seeking protection? +***"How do changes in U.S. immigration policy under the current administration +affect access to legal representation and outcomes for immigrant juveniles +seeking protection?"*** ---- -Context & Constraints: +#### Context & Constraints: --Domain: U.S. immigration law and policy, focused on juveniles (minors) seeking +- **Domain:** U.S. immigration law and policy, focused on juveniles (minors) seeking legal protection (e.g., asylum, Special Immigrant Juvenile Status). --Realities: Immigration policy is dynamic and politically influenced; juvenile +- **Realities:** Immigration policy is dynamic and politically influenced; juvenile immigrants face complex barriers navigating the legal system; access to legal counsel is crucial for fair outcomes. ---Constraints: - --Data Availability: Data on representation and case outcomes may be fragmented - (court records, NGO data, government statistics). Policy changes may not be - immediately or transparently reflected in public data. - --Ethical/Legal: Privacy concerns for minors; potential bias in available datasets. - --Temporal/Geographical Scope: Defining the appropriate time window may be - required. The study can be nationwide or limited to areas with sufficient or +- **Constraints:** + - **Data Availability:** Data on representation and case outcomes may be fragmented + (court records, NGO data, government statistics). Policy changes may not be + immediately or transparently reflected in public data. + - **Ethical/Legal:** Privacy concerns for minors; potential bias in available datasets. + - **Temporal/Geographical Scope:** Defining the appropriate time window may be + required. The study can be nationwide or limited to areas with sufficient or high-priority data. +--- + ## Data ### Dataset Source From b02019935c1b0d141647415bf1c946e2d26f03cc Mon Sep 17 00:00:00 2001 From: Banu Ozyilmaz Date: Mon, 16 Jun 2025 13:42:13 -0400 Subject: [PATCH 67/70] fix: fixed md formatting errors --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e92a1daba..a9c36883e 100644 --- a/README.md +++ b/README.md @@ -57,7 +57,7 @@ structures, and underlying mental models, check out the full overview: affect access to legal representation and outcomes for immigrant juveniles seeking protection?"*** -#### Context & Constraints: +### Context & Constraints - **Domain:** U.S. immigration law and policy, focused on juveniles (minors) seeking legal protection (e.g., asylum, Special Immigrant Juvenile Status). From 10b515b0c95006121af6013bc2c8352428428b16 Mon Sep 17 00:00:00 2001 From: AmmarIbrahim <3mmar2001@gmail.com> Date: Mon, 16 Jun 2025 23:38:09 +0300 Subject: [PATCH 68/70] added Amro's and Muhammad's Individual Retrospectives --- .../1_problem_identification.md | 42 +++++++++---------- 1 file changed, 21 insertions(+), 21 deletions(-) diff --git a/collaboration/retrospectives/1_problem_identification.md b/collaboration/retrospectives/1_problem_identification.md index 020605c1d..f5bb66533 100644 --- a/collaboration/retrospectives/1_problem_identification.md +++ b/collaboration/retrospectives/1_problem_identification.md @@ -103,7 +103,7 @@ made it hard for me to know where to start, which caused some confusion in the b - Learned to apply divergent and convergent thinking more effectively. - Learned to use the FRESCO framework to improve the quality of a research question. -### Ammar Osman +### Ammar Ibrahim > Contributions @@ -125,32 +125,32 @@ thinking to the background resources, and by combining and summarizing the ideas forms. - Gained more confidence in dealing with GitHub workflows. -### Member_3 +### Amro Mohamed -- Contributions -- Challenges -- Progress +> Contributions + +- helped by (sharing personal experiences / asking questions / doing research) -### Member_4 +> Progress -- Contributions -- Challenges -- Progress +- learned how policies, legal systems, and public beliefs are all connected -### Member_5 +### Muhammad Shahroz -- Contributions -- Challenges -- Progress +> Contributions -### Member_6 +- Tried to help refine the problem statement, but haven’t been +able to add much value yet. +- Shared some thoughts but didn’t contribute heavily in discussions or docs. -- Contributions -- Challenges -- Progress +> Challenges +> +- Struggled with managing time and learning the domain—all while dealing +with job work and timezone overlaps. +- Found it hard to stay up to date with feedback and next steps across +Slack and GitHub. -### Member_7 +> Progress -- Contributions -- Challenges -- Progress +- Realized I need to focus on understanding the project before +I can contribute more meaningfully. From 02f2171194ef7bc3b409f76881eeab5d8f2dec30 Mon Sep 17 00:00:00 2001 From: AzzaOmer1 <103028535+AzzaOmer1@users.noreply.github.com> Date: Tue, 17 Jun 2025 02:34:21 +0300 Subject: [PATCH 69/70] update --- collaboration/constraints.md | 58 ++++++++++++++++++++++++++++++++++++ 1 file changed, 58 insertions(+) diff --git a/collaboration/constraints.md b/collaboration/constraints.md index 85d581b98..692a90f35 100644 --- a/collaboration/constraints.md +++ b/collaboration/constraints.md @@ -35,6 +35,8 @@ real-time coordination difficult. --- +## Milestone 0 + ## ⚙️ Internal Involuntary Constraints These are constraints from within the team that are beyond individual control: @@ -64,3 +66,59 @@ technical and collaborative skills. an opportunity to grow. --- + +## Milestone 1 + +### 🧍‍♂️ Individual Constraints + +#### Constraints (Banu) + +- ⏳ **Time limitations**: +We have only two weeks to complete this milestone, +and progress is further challenged by differing time zones +and personal commitments that make synchronous collaboration difficult. +- 📘 **Limited knowledge and no prior experience**: +I have no prior experience in data science research, +which makes it harder to adapt to the process and slows down decision-making. +- 🧠 **Unfamiliarity with domain-specific thinking**: +Coming from a different academic background, +I find it challenging to approach problems using a data-driven mindset, +especially when it comes to identifying what makes a question suitable for research. + +#### Constraints (Gennadii) + +- ⏱️ **Time management**: +It’s been extremely challenging to fully commit to the project +while juggling other responsibilities. +- 🤝 **Collaboration**: +Team building can be difficult, +especially when working with people from different backgrounds and perspectives. +- 🧩 **Sharing responsibilities**: +Delegating tasks and ensuring balance within the team is +something I’m still working on. + +#### Constraints (Shahroz) + +- 🕒 **Job timing conflicts**: +My work hours often overlap with team meetings, +making it difficult to attend live collaboration sessions. +- 🌍 **Time zone differences**:Team members are spread across +multiple time zones, causing challenges in scheduling synchronous work. +- 📅 **Limited weekend availability**: +Although weekends are my main opportunity to focus, +personal commitments limit their flexibility. + +#### Constraints (Elshikh-Amro) + +- 📚 **Limited knowledge of the topics** +- ⏰ **Time management** +- 📌 **Divide the tasks** + +#### Constraints (Azza) + +- 📖 **Limited Background Knowledge**: +I have limited prior knowledge or experience regarding the specific problem area. +- 📊 **Time Management Challenges**: +It takes time to understand the project requirements, +align on goals, and brainstorm collectively, +which can affect the overall workflow and productivity. From ed3ac820a4d7669a2d14f5e5e0e2f6e2dc34e5a6 Mon Sep 17 00:00:00 2001 From: AzzaOmer1 <103028535+AzzaOmer1@users.noreply.github.com> Date: Tue, 17 Jun 2025 02:39:29 +0300 Subject: [PATCH 70/70] update it --- .vscode/settings.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.vscode/settings.json b/.vscode/settings.json index 252022b48..dd4fff61d 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -122,5 +122,6 @@ "source.fixAll.ruff": "explicit", "source.organizeImports.ruff": "explicit" } - } + }, + "cSpell.words": ["Amro", "Azza", "Banu", "Elshikh", "Gennadii", "Shahroz"] }