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"] } diff --git a/0_domain_study/README.md b/0_domain_study/README.md index 308b71113..1bf177030 100644 --- a/0_domain_study/README.md +++ b/0_domain_study/README.md @@ -1 +1,135 @@ -# 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. + +## Problem Statement +> +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 + +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. | +| [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 & 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.*** + +--- + +> + +## 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?” diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e69de29bb..4616852b3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -0,0 +1,226 @@ + + + + +# 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. 👇 + +--- + +
+

🏗️ Repository Structure

 + +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`). + +--- + +### 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** + +- 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. + +--- + +### 6. 🔁 Review & Merge + +- 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. + +--- + +### 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 +``` + +- 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. + +--- + +### 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. + +
+ +--- + +## 🤝 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! 💙 diff --git a/README.md b/README.md index e69de29bb..a9c36883e 100644 --- a/README.md +++ b/README.md @@ -0,0 +1,179 @@ +# Barriers to Justice + +How Immigration Policies Affect Immigrant Juveniles Seeking Protection + +## Project Overview + +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. + +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? + +--- + +## 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](0_domain_study/README.md) + +## Stack / Technologies Used + +- [Programming Language / Version] +- [Library / Framework] +- [Library / Framework] +- [Library / Framework] +- [Notebook / IDE] + +--- + +## 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 +and reuniting with family in the U.S. +These systemic challenges result from increasingly restrictive immigration +policies, funding instability, enforcement practices, and underlying beliefs +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](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 + +**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. diff --git a/collaboration/README.md b/collaboration/README.md index 20889b951..300fc30a1 100644 --- a/collaboration/README.md +++ b/collaboration/README.md @@ -1,5 +1,92 @@ # 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 🗃️ + +- [**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. + +- [**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. + +- [**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, +and flexible as the project evolves. 🚀 + +## Group Norms 📜 + +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 🤝 + +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. +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 🧑‍💻 + +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. diff --git a/collaboration/communication.md b/collaboration/communication.md index f9e2d0181..9ddc671ed 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,41 +13,60 @@ ## 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 we will 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. + +--- ## Availability ### Availability for calling/messaging -| Day | Mon | Tue | Wed | Thu | Fri | Sat | Sun | -|--------|:---:|:---:|:---:|:---:|:---:|:---:|:---:| -| _name_ | | | | | | | | + + + +| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | +|--------|:------:|:-------:|:---------:|:--------:|:------:|:--------:|:------:| +| 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 | +|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 -- name: _5h_ -- name: _6h_ -- name: _5h_ -- name: _4h_ -- name: _3h_ +- Ammar: _2h_ +- Banu: _2–3h_ +- Amro: _2–3h_ +- Azza: _2-3h and Emergency_ +- Muhammad: 2h + +--- ## 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 -3. _60+ min_: Tag your coaches in Slack, WhatsApp 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 diff --git a/collaboration/constraints.md b/collaboration/constraints.md index 24079505c..692a90f35 100644 --- a/collaboration/constraints.md +++ b/collaboration/constraints.md @@ -1,34 +1,124 @@ +# 🚧 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. + +--- + +## Milestone 0 + +## ⚙️ 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. + +--- + +## 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. diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md index 11c583d2b..64f704e27 100644 --- a/collaboration/learning_goals.md +++ b/collaboration/learning_goals.md @@ -1,5 +1,98 @@ # 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. + +-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. + +-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. + +-MuhammadShahroz + +1-Aim to work supportively and openly with teammates from diverse backgrounds, + +2-ensuring clear and respectful communication. + +-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. + +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 + +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. + +2.Build a better understanding of product management and project ownership. + +-AzzaOmer + +1.Understanding Problem Identification + +2.Formulating Research Question + +3.Applying FRESCO Methodology 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/1_problem_identification.md b/collaboration/retrospectives/1_problem_identification.md index e69de29bb..f5bb66533 100644 --- a/collaboration/retrospectives/1_problem_identification.md +++ b/collaboration/retrospectives/1_problem_identification.md @@ -0,0 +1,156 @@ +# 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 + +### Banu Ozyilmaz + +> 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. +- Helped finalize the problem statement. + +> 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. + +### Ammar Ibrahim + +> 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. + +### Amro Mohamed + +> Contributions + +- helped by (sharing personal experiences / asking questions / doing research) + +> Progress + +- learned how policies, legal systems, and public beliefs are all connected + +### Muhammad Shahroz + +> Contributions + +- 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. + +> 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. + +> Progress + +- Realized I need to focus on understanding the project before +I can contribute more meaningfully. diff --git a/collaboration/retrospectives/README.md b/collaboration/retrospectives/README.md index 08d9b0582..772d575a1 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.*