From 5392fc1c84fd255d69c42d865077d29a21e071ed Mon Sep 17 00:00:00 2001 From: urz1 Date: Sat, 11 Jan 2025 11:16:36 +0300 Subject: [PATCH 1/3] [docs] Add sections for Stop Doing, Continue Doing, and Start Doing. --- collaboration/retrospective.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/collaboration/retrospective.md b/collaboration/retrospective.md index ef1974f8f..042830af8 100644 --- a/collaboration/retrospective.md +++ b/collaboration/retrospective.md @@ -10,6 +10,14 @@ - Working in isolation for too long without syncing progress with the team. - Committing untested code, which led to integration issues. + +- 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 @@ -18,6 +26,12 @@ - Writing clear and descriptive commit messages to improve traceability. - Sharing updates during team check-ins to stay aligned. + +- Supporting each other through challenges. + +- Accomplishing tasks within the given time frame. + +- Respecting one another and valuing diverse perspectives. ## Start Doing @@ -29,6 +43,10 @@ - Conducting mandatory code reviews before merging changes into the main branch. - Writing modular and well-documented code to ease collaboration. + +- Actively engaging in discussions and project activities. + +- Collaborating more frequently and effectively. ## Lessons Learned @@ -44,6 +62,10 @@ - Clear documentation helps the entire team understand and build on each other's work. +- No pain, no gain — hard work is essential for success. + +- Sincerity and accountability are crucial for team success. + --- ## Strategy vs. Board @@ -55,6 +77,12 @@ - Milestones were met on time for specific deliverables. - Most team members followed the planned development workflow. + +- Collaborating effectively on shared files. + +- Solving problems effectively. + +- Conducting productive code reviews. ### What parts of your plan did not work out? From 7b43debc5ec78c0eec59aa03b2f370878f344cf8 Mon Sep 17 00:00:00 2001 From: ciiyaa Date: Sat, 11 Jan 2025 17:39:50 +0300 Subject: [PATCH 2/3] Add Ava retrospective.md --- collaboration/retrospective.md | 78 ++++++++++++---------------------- 1 file changed, 26 insertions(+), 52 deletions(-) diff --git a/collaboration/retrospective.md b/collaboration/retrospective.md index 042830af8..7d9da6851 100644 --- a/collaboration/retrospective.md +++ b/collaboration/retrospective.md @@ -1,108 +1,82 @@ -# Retrospective +# Retrospective -## Stop Doing +## Stop Doing - 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. - - 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 + +## 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. - - Supporting each other through challenges. - - Accomplishing tasks within the given time frame. - - Respecting one another and valuing diverse perspectives. - -## Start Doing + +## 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. - - Actively engaging in discussions and project activities. - - Collaborating more frequently and effectively. - -## Lessons Learned -- 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. - - Collaborating effectively on shared files. - - Solving problems effectively. - - Conducting productive code reviews. - -### What parts of your plan did not work out? + +### 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. --- From 978379e239ff76ed2d6c8be4e78d4f7f26c817b0 Mon Sep 17 00:00:00 2001 From: ciiyaa Date: Sat, 11 Jan 2025 17:45:47 +0300 Subject: [PATCH 3/3] Add Ava stop doing point --- collaboration/retrospective.md | 1 + 1 file changed, 1 insertion(+) diff --git a/collaboration/retrospective.md b/collaboration/retrospective.md index 7d9da6851..93dff4d62 100644 --- a/collaboration/retrospective.md +++ b/collaboration/retrospective.md @@ -4,6 +4,7 @@ ## Stop Doing +- Initiating and implementing ideas individually. - Overwriting code during merge conflicts without resolving them collaboratively. - Working in isolation for too long without syncing progress with the team.