[docs] Add sections for Stop Doing, Continue Doing, and Start Doing.

collaboration/retrospective.md

@@ -1,80 +1,83 @@
 <!-- this template is for inspiration, feel free to change it however you like! -->
 
-# Retrospective  
+# Retrospective
 
-## Stop Doing  
+## Stop Doing
 
+- Initiating and implementing ideas individually.
 - Overwriting code during merge conflicts without resolving
- them collaboratively.
-
+  them collaboratively.
 - Working in isolation for too long without syncing progress with the team.
-
 - Committing untested code, which led to integration issues.
-
-## Continue Doing  
+- Reviewing code carelessly without sufficient attention to detail.
+- Missing meetings without giving prior notice.
+- Interrupting discussions during meetings.
+- Deviating off-topic redundantly during meetings.
+
+## Continue Doing
 
 - Regularly using GitHub to track progress and organize tasks.
-
 - Writing clear and descriptive commit messages to improve traceability.
-
 - Sharing updates during team check-ins to stay aligned.
-
-## Start Doing  
+- Supporting each other through challenges.
+- Accomplishing tasks within the given time frame.
+- Respecting one another and valuing diverse perspectives.
+
+## Start Doing
 
 - Implementing a formal process for handling merge conflicts collaboratively.
-
 - Scheduling more frequent sync sessions to review and integrate changes
- incrementally.
-
+  incrementally.
 - Conducting mandatory code reviews before merging changes into the main branch.
-
 - Writing modular and well-documented code to ease collaboration.
-  
-## Lessons Learned  
+- Actively engaging in discussions and project activities.
+- Collaborating more frequently and effectively.
 
-- Communication is key to preventing duplicated efforts and resolving conflicts
- efficiently.
+## Lessons Learned
 
+- Communication is key to preventing duplicated efforts and resolving conflicts
+  efficiently.
 - Merge conflicts are manageable with proper workflows and proactive conflict
- resolution practices.
-
+  resolution practices.
 - Regular integration reduces the chances of encountering large, complex
- conflicts.
-
+  conflicts.
 - Clear documentation helps the entire team understand and build on each
- other's work.
+  other's work.
+- No pain, no gain — hard work is essential for success.
+- Sincerity and accountability are crucial for team success.
+- Always make sure that your teammates are on the same page with you.
 
 ---
 
-## Strategy vs. Board  
+## Strategy vs. Board
 
-### What parts of your plan went as expected?  
+### What parts of your plan went as expected?
 
 - Tasks were tracked and organized effectively using GitHub.
-
 - Milestones were met on time for specific deliverables.
-
 - Most team members followed the planned development workflow.
-
-### What parts of your plan did not work out?  
+- Collaborating effectively on shared files.
+- Solving problems effectively.
+- Conducting productive code reviews.
+
+### What parts of your plan did not work out?
 
 - Handling merge conflicts was not planned adequately and caused delays.
-
 - Communication gaps led to duplicated work and inconsistencies in code
- integration.  
+  integration.
 
-### Did you need to add things that weren't in your strategy?  
+### Did you need to add things that weren't in your strategy?
 
 - Introduced a process for resolving merge conflicts and added extra sync
- sessions for better coordination.  
+  sessions for better coordination.
 - Added steps to review pull requests and conduct code reviews before merging.
-  
-### Or remove extra steps?  
+
+### Or remove extra steps?
 
 - Removed redundant tasks that became unnecessary due to shifting project
- priorities.  
+  priorities.
 - Simplified parts of the strategy to focus more on conflict resolution
- and integration.  
+  and integration.
 
 ---