completed the retrospective file

collaboration/retrospective.md

@@ -4,20 +4,59 @@
 
 ## Stop Doing
 
+- Missing meetings.
+- Absence of effective communication.
+- Non-compliance with deadlines.
+- Not adhering to group norms strictly.
+
 ## Continue Doing
 
+- Collaborative work.
+- Access to support whenever needed. 
+- Open to learn and to ask.
+- Consistency with work.
+- Good and organized planning.
+
 ## Start Doing
 
+- Use the GitHub discussion section more frequently.
+- Peer programming.
+- Detailed documentation of work and activities.
+- Create a detailed project timeline.
+- Assign tasks and roles at the outset of the project.
+- Keep meetings shorter and on a fixed agreed-upon day.
+- Understand everyone’s strengths and weaknesses, then build a common ground.
+
 ## Lessons Learned
 
+- GitHub workflow.
+- Project management.
+- VScode workflow.
+- Navigating issues related to Python, GitHub, and VSCode.
+- Flexibility.
+- Clear communication is the key for asynchronous collaboration.
+
 ______________________________________________________________________
 
 ## Strategy vs. Board
 
 ### What parts of your plan went as expected?
 
+- Communication with the team.
+- Collaborating on GitHub.
+- The majority of team members were able to meet the project's main requirements
+before the final deadline.
+- All team members were cautious with the repository.
+
 ### What parts of your plan did not work out?
 
+- **Internal deadline:** Some team members missed it.
+- **Time management and availability:** Coordinating meetings with all team members
+was quite challenging.
+
 ### Did you need to add things that weren't in your strategy?
 
-### Or remove extra steps?
+- Include an alternative communication medium.
+- Ensure that everyone is on the same page and understands the workflow.
+- Utilize a task management tool such as **_Asana_** or **_Trello_** for more insights
+and details into the progress of each team member.