Merge pull request #59 from MIT-Emerging-Talent/collaboration

merging the final version of the collaboration folder

collaboration/README.md

@@ -21,5 +21,5 @@ to delivering quality work while maintaining understanding of different prioriti
 7. Maintain open communication about progress and challenges.
 8. Create a welcoming and supportive environment.
 9. Address conflicts directly and respectfully.
-10. Escalating unresolved conflicts or issues as a team to a mentor for guidance
+10. Escalating unresolved conflicts or issues as a team to our mentor for guidance
  when they cannot be solved directly.

collaboration/communication.md

@@ -55,9 +55,9 @@ ______________________________________________________________________
 | **Abdallah** | 6 PM - 8 PM (2h)  | 6 PM - 8 PM (2h)  | 6 PM - 8 PM (2h)  |
 | **Kimya**    | 10 AM - 12 PM (2h)| 11 AM - 1 PM (2h) | 10 AM - 12 PM (2h)|
 | **Mohammad** | 2 PM - 4 PM (2h)  | 2 PM - 4 PM (2h)  | 7 PM - 10 PM (2h) |
-| **Shadi**    | 11 AM - 4 PM      | 11 AM - 4 PM      | 11 AM - 4 PM      |
-| **Member 6** | 5h                | 6h                | 5h                |
-| **Member 7** | 5h                | 6h                | 5h                |
+| **Norbert**  | 5 PM -  7PM (2h)  | 2 PM - 4 PM  (2h)  | 4 PM - 6 PM (2h) |
+| **Asia** | 2 PM -  4PM (2h)      | 2 PM - 4 PM (2h)  | 2 PM  - 4 PM (2h) |
+| **Zeinab** | 5h                | 6h                | 5h                |
 
 #### Thursday to Saturday
 
@@ -67,9 +67,9 @@ ______________________________________________________________________
 | **Abdallah** | 6 PM - 8 PM (2h)  | 6 PM - 8 PM (2h)  | 10 AM - 17 PM (7h)|
 | **Mohammad** | 10 AM - 12 PM (2h)| 9 AM - 11 PM (2h) | 12 PM - 2 PM (2h) |
 | **Kimya**    | 10 AM - 12 PM     | 11 AM -  1 PM     | 10 AM - 12 PM     |
-| **Shadi**    | 11 AM - 4 PM      | 11 AM - 4 PM      | 12 PM - 8 PM      |
-| **Member 6** | 4h                | 3h                | 5h                |
-| **Member 7** | 4h                | 3h                | 5h                |
+| **Norbert** | 12 PM - 2 PM (2h)  | 10 AM - 12 AM (2h) | 8 AM - 12 PM (2h) |
+| **Asia** | 2 PM - 4 PM (2h)      | 10 AM - 12 AM (2h) | 2 PM - 4 PM (2h) |
+| **Zeinab** | 4h                | 3h                | 5h                |
 
 #### Sunday
 
@@ -79,19 +79,19 @@ ______________________________________________________________________
 | **Abdallah** | 10 AM - 17 PM (7h)  |
 | **Mohammad** | 2 PM - 4 PM (2h)    |
 | **Kimya**    | 11 AM - 1 PM        |
-| **Shadi**    | 12 PM - 8 PM        |
-| **Member 6** | 4h                  |
-| **Member 7** | 4h                  |
+| **Norbert**  | 8 AM - 5 PM (9h)    |
+| **Asia** | 2 PM - 4 PM (2h)        |
+| **Zeinab** | 4h                  |
 
 ### How many hours everyone has per day
 
 - **Huda**: 2h
 - **Abdallah**: 2-3 hrs
 - **Mohammad**: 2h
 - **Kimya**: 2h
-- **Shadi**: 2h
-- **Member 6**: 5h
-- **Member 7**: 5h
+- **Norbert**: 2h
+- **Asia**: 2h
+- **Zeinab**: 5h
 
 ## Asking for Help
 

collaboration/constraints.md

@@ -22,6 +22,7 @@ Some boundaries around our project.
 | Mohammad   | Time management        |
 | Kimya      | Time management        |
 | Asia   | Internet connectivity and no laptop    |
+| Norbert   | Time management        |
 | Shadi  | Work, Internet connectivity|
 
 ## Internal: Involuntary
@@ -39,6 +40,7 @@ Some boundaries around our project.
 | Mohammad    | New to GitHub        |
 | Kimya   | New to Python and Github       |
 | Asia  | Using a phone to do a project      |
+| Norbert   | Newbie on Test Driven Development        |
 | Shadi  | New to Github & Python        |
 
 ## Internal: Voluntary
@@ -57,4 +59,5 @@ Some boundaries around our project.
 | Mohammad   | The code difficulty        |
 | Kimya   | The code difficulty      |
 | Asia  | The organization of the project      |
+| Norbert   | Python Formatting       |
 | Shadi   | The code difficulty        |

collaboration/learning_goals.md

@@ -44,6 +44,18 @@
   and potential in writing and reviewing code.
 - Enhance problem-solving skills by collaboration with team.
 
+### **Norbert**
+
+- Master the principles of documenting and testing,
+  with a focus on Test-Driven Development (TDD).
+- Enhance proficiency in Python programming and deepen understanding of its concepts.
+
+### **Asia**
+
+- Navigating a new platform.
+- Trying to fulfill requirements in spite of personal challenges.
+- Gain experience working with GitHub even if small.
+
 ### **Shadi**
 
 - Programming Proficiency

collaboration/retrospective.md

@@ -2,22 +2,101 @@
 
 # Retrospective
 
+*"The only real mistake is the one from which we learn nothing."*
+*— Henry Ford*
+
 ## Stop Doing
 
+- **Lack of Active Participation:** Due to some personal issues, some team members
+  were less active, which slowed down progress. In the future, we need
+  to ensure clearer communication regarding availability and constraints.
+
+- **Underestimating the Importance of the Project Board:** We didn’t fully
+  recognize the value of using the GitHub project board at the start. This resulted
+  in some miscommunication as some members had to ask about which solutions need
+  to be reviewed.
+
 ## Continue Doing
 
+- **Collaboration and Flexibility**: When some members struggled in dealing with
+  GitHub and Python, others where there to help which ensured successful
+  submission of solutions and reviews in time. Also, when some members didn’t
+  find solutions to review, others implemented additional solution to provide
+  challenges for teammates to review. **We should continue such actions to ensure
+  our success in the Certificate program.**
+
+- **Regular code reviews using GitHub:** Now since we have seen how better it
+  is to communicate about the code through Github,
+  all of us are focusing on developing this skill for better code management.
+
+- **Regular Check-ins:** Having meetings helped us stay connected and
+  clear on progress, despite some delays.
+
 ## Start Doing
 
+- **Deadlines, deadlines, deadlines**: We should've set clear deadlines for each
+  task. This would've ensured early successful submission of the project and
+  we will have enough to fix any last-minute errors/problems.
+
+- **Organized Project Board and Label Usage:** We need to use the GitHub project
+  board more efficiently. This would ensure effective communication and delivery.
+  Also, we need to write more about the code in the description of the PR/issue.
+  This is something we didn't stick to in this project as the solutions were simple.
+
+- **Clearer Role Definition:** It’s important that to define individual roles
+  and responsibilities more clearly from the first meeting. This will ensure
+  each member understands their specific contributions.
+
+- **Capabilities Discussion**: We have to discuss our capabilities of using the tools
+  that will be used in detail, not just saying "I'm beginner". This would help
+  making it clear from the beginning which members will need help the most.
+
 ## Lessons Learned
 
+- **Collaboration, collaboration, collaboration:** Team members on any project
+  should collaborate effectively with one another. This ensures not only the
+  successful delivery of the project but also that no individual is
+  burdened with more work than necessary.
+
+- **Marketing on GitHub**: Given that most programmers and companies worldwide
+  utilize GitHub, it's highly beneficial to start developing projects and
+  sharing them on this platform. At more advanced levels, contributing
+  to open-source projects can significantly enhance both experience
+  and professional portfolio.
+
+- **Reviews and feedback:** Do not assume your code is great or easily readable
+  unless your teammates confirm it. This isn't about doubting your abilities;
+  rather, clear comprehension in your mind doesn't guarantee others will
+  understand it similarly. **Therefore, CODE REVIEWS ARE CRUCIAL!**
+
 ______________________________________________________________________
 
 ## Strategy vs. Board
 
 ### What parts of your plan went as expected?
 
+- We successfully submitted all the solutions and reviews in time and
+  didn't have to deal with last-minute problems.
+- We have all learned the basics of Git and GitHub, along with the
+  essentials of testing and code reviewing. This is the start to a long journey!
+- Most members didn't have to change their strategies, it was more about the implementation.
+
 ### What parts of your plan did not work out?
 
+- Communication. Despite of the successful delivery of the project, this aspect
+  should be further enhanced.
+
 ### Did you need to add things that weren't in your strategy?
 
+- Some members had issues that prevented them from learning some Git and Github basics
+  in advance, therefore, we needed to conduct meetings to tackle this issue.
+
 ### Or remove extra steps?
+
+- We didn't have to remove any steps!
+
+______________________________________________________________________
+
+Last but not least, we believe that it's time to look for a new group
+name. We are not buggy after all since our solutions worked perfectly!
+Soooo, What about **The Bug Busters?**