add Group Retrospective

collaboration/retrospective.md

@@ -4,20 +4,74 @@
 
 ## Stop Doing
 
+### Mistakes Made  
+
+- 🕒 Time Management:  
+  - Spending too much time organizing synchronous meetings instead of working asynchronously.
+  - Poor prioritization strategies and leaving most work for the last days.  
+- 🔄 Missed Steps:  
+  - Lack of early starts to provide opportunities for better knowledge sharing.
+  - No clear process for reassigning reviews if someone was unavailable.  
+  - The review process took longer than expected and needed better management.
+- 🗨️ Communication Issues:  
+  - Lack of asynchronous protocols like setting response times and deadlines
+  - Insufficient regular and short catch-up meetings.  
+  - No specific roles defined for team members, such as a team leader for task assignment.
+
+---
+
 ## Continue Doing
 
+### Successes to Maintain  
+
+- 🛠️ Tools and Practices:  
+  - Effective use of Slack for communication and GitHub project boards for organization.
+  - Recording meetings for those unable to attend.  
+  - Structured code review through GitHub pull request features.  
+- 🤝 Supportive Culture:  
+  - Team members were supportive, helping each other with questions or issues.  
+  - One-on-one quick meetings scheduled to resolve individual issues.  
+
+---
+
 ## Start Doing
 
+### New Ideas to Implement  
+
+- 📌 Create a pinned table in Slack with solutions to common errors.  
+- ⏳ Set deadlines for tasks to improve organization.  
+- 📆 Use a shared calendar for tracking task progress.
+- 📝 Introduce clearly defined roles for team members, such as assigning a team
+leader to oversee task assignment.  
+
+---
+
 ## Lessons Learned
 
-______________________________________________________________________
+### Key Takeaways  
+
+- Tools and Skills:  
+  - 💻 Better understanding of GitHub features and their application in teamwork.
+  - 📝 Importance of constructive feedback during code reviews.  
+- Teamwork and Communication:  
+  - 🔗 Asynchronous collaboration requires clear communication and coordination.
+  - 👀 "You can't see your mistakes until someone else points them out to you."
+
+---
 
 ## Strategy vs. Board
 
-### What parts of your plan went as expected?
+### Successes  
+
+- 🌈 Smooth progress without conflicting opinions.  
+- 🧩 Effective collaboration through Slack and GitHub's code review process.  
+
+### Challenges  
 
-### What parts of your plan did not work out?
+- 🕰️ Fixed meeting times were impractical due to varying paces of work.  
+- 🛑 Progress delays caused by task dependencies.  
 
-### Did you need to add things that weren't in your strategy?
+### Adjustments  
 
-### Or remove extra steps?
+- 💡 Encourage sharing of bug fixes or solutions on Slack.  
+- 🕒 Schedule quick weekly meetings to track progress.