27 add group name and readme profile

README.md

@@ -6,14 +6,15 @@ Welcome to our MIT Emerging Talent Collaborative Data Science Project repository
 
 This project explores how data science, collaboration, and domain expertise
 intersect to solve real-world problems. We are currently
-in **Milestone 0: Cross-Cultural Collaboration**, focused on building a solid
-foundation for effective teamwork.
+in **Milestone 1: Problem Identification**, focused on making an initial domain study
+and framing an actionable research question in our project domain,
+and within our groups’ constraints.
 
 ---
 
 ## 👋 Meet the Team
 
-We are Group 06 from the 2025 MIT Emerging Talent program. Our team brings
+We are **The Animus⚛️** from the 2025 MIT Emerging Talent program. Our team brings
 together diverse perspectives, technical backgrounds, and cultural experiences.
 Through this project, we hope to:
 
@@ -29,10 +30,10 @@ Our domain of interest will be defined in Milestone 1.
 ## 🔍 Project Overview
 
 - **Track:** Collaborative Data Science Project (CDSP)
-- **Team:** Group 06
-- **Domain of Interest:** _To be defined in Milestone 1_
+- **Team:** The Animus⚛️
+- **Domain of Interest:** Education
 - **Timeline:** May–August 2025
-- **Status:** 🚧 In progress (Milestone 0)
+- **Status:** 🚧 In progress (Milestone 1)
 
 ---
 
@@ -61,16 +62,16 @@ Our domain of interest will be defined in Milestone 1.
 - 🔹 [Communication Plan](collaboration/communication.md)
 - 🔹 [Constraints](collaboration/constraints.md)
 - 🔹 [Learning Goals](collaboration/learning_goals.md)
-- 🔹 [Retrospective (Milestone 0)](collaboration/retrospective.md)
+- 🔹 [Retrospective (Milestone 1)](collaboration/retrospectives)
 
 ---
 
 ## 🗓️ Project Milestones
 
 | Milestone | Focus                        | Status        | Due Date   |
 |----------|------------------------------|---------------|------------|
-| 0        | Cross-Cultural Collaboration | 🟡 In Progress | June 2     |
-| 1        | Problem Identification        | ⏳ Upcoming    | June 16    |
+| 0        | Cross-Cultural Collaboration | 🟢 Done | June 2     |
+| 1        | Problem Identification        | 🟡 In Progress    | June 16    |
 | 2        | Data Collection               | ⏳ Upcoming    | June 30    |
 | 3        | Data Analysis                 | ⏳ Upcoming    | July 21    |
 | 4        | Communicating Results         | ⏳ Upcoming    | August 11  |
@@ -85,22 +86,6 @@ git clone https://github.com/MIT-Emerging-Talent/ET6-CDSP-group-06-repo.git
 cd ET6-CDSP-group-06-repo
 ```
 
-## 🛠️ Development Workflow
-
-Create a new branch for your solution:
-
-```bash
-git checkout -b feature/challenge-name
-```
-
-- Implement your solution in the solutions directory.  
-- Add tests in the tests directory.  
-- Submit a pull request for review.  
-- Address review feedback.  
-- Merge after approval.
-- Read our [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.
-- CI checks must pass before merging to `main`.
-
 ---
 
 ## 👥 Team Members

collaboration/README.md

@@ -42,7 +42,8 @@ flexibility, and accountability allow us to grow together through this project.
 
 ## ✏️ Our Group Name
 
-**To be Announced Later** 🎵⚛️  
+**The Animus⚛️**= mind, spirit, soul — ties perfectly to insight
+identity, and the work we’re doing  
 
 ---
 

collaboration/retrospectives/0_cross_cultural_collaboration.md

@@ -0,0 +1,48 @@
+
+<!-- this template is for inspiration, feel free to change it however you like! -->
+
+# Retrospective
+
+## Stop Doing
+
+- Waiting until the last minute to merge code, this caused avoidable conflicts.
+
+- Using group chats to track tasks instead of a shared task board (led to confusion).
+
+## Continue Doing
+
+- Writing post-commit messages to explain major changes in GitHub.
+
+## Start Doing
+
+- When a branch has been merged and no longer needed, we should to delete it
+to make everything neat.
+
+- Always update the project board, and review available pull requests.
+
+## Lessons Learned
+
+- Group success depends more on communication than technical skill alone.
+
+- Developed better time management skills by respecting deadlines and the
+schedules of team members.
+
+---
+
+## Strategy vs. Board
+
+### What parts of your plan went as expected?
+
+### What parts of your plan did not work out?
+
+### Did you need to add things that weren't in your strategy?
+
+### Or remove extra steps?
+
+---
+
+## Individual Rerospectives
+
+### Name
+
+<!-- reflect on your contributions, challenges and progress in this milestone -->