Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 6 commits into from
Jan 12, 2025
Merged

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

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
5392fc1
[docs] Add sections for Stop Doing, Continue Doing, and Start Doing.
Urz1 Jan 11, 2025
3c76c0c
Merge branch 'main' into 75-finalize-collaborationretrospectivemd
Urz1 Jan 11, 2025
7b43deb
Add Ava retrospective.md
ciiyaa Jan 11, 2025
978379e
Add Ava stop doing point
ciiyaa Jan 11, 2025
4e673fb
Merge branch 'main' into 75-finalize-collaborationretrospectivemd
Urz1 Jan 11, 2025
53dd3ca
Merge branch 'main' into 75-finalize-collaborationretrospectivemd
ciiyaa Jan 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 1 addition & 16 deletions collaboration/retrospective.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,32 +11,25 @@ Here’s what we’ve learned and how we’ll evolve for the next project. 🚀

- ❌ Overwriting code during merge conflicts without resolving them
collaboratively.

- 🛠️ Working in isolation for too long without syncing progress
with the team.

- 🚫 Committing untested code, which led to integration issues.

---

## ✅ 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

- 🤝 Implementing a formal process for handling **merge conflicts** collaboratively.

- 📆 Scheduling more frequent sync sessions to review and integrate changes incrementally.

- 🔍 Conducting **mandatory code reviews** before merging changes into the main branch.

- 📚 Writing **modular and well-documented code** to ease collaboration.

---
Expand All @@ -45,13 +38,11 @@ with the team.

- 💡 **Communication is key** to preventing duplicated efforts and resolving
conflicts efficiently.

- 🛠️ Merge conflicts are manageable with proper workflows and proactive
resolution practices.

- 🔄 Regular integration reduces the chances of encountering large, complex conflicts.

- ✍️ Clear documentation helps the team understand and build on each other's work.
- 🤝 Always make sure that your teammates are on the same page with you.

---

Expand All @@ -60,27 +51,22 @@ with the team.
### ✅ 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?

- ⚡ Handling merge conflicts wasn’t planned adequately, causing delays.

- 🔇 Communication gaps led to duplicated work and inconsistencies in code integration.

---

### ➕ Did you need to add things that weren't in your strategy?

- 🛠️ Introduced a process for **resolving merge conflicts** collaboratively.

- 🤝 Added extra **sync sessions** for better coordination.

- 🔍 Established steps for **pull request reviews** and mandatory code reviews
before merging.

Expand All @@ -89,7 +75,6 @@ before merging.
### ➖ Or remove extra steps?

- 🚮 Removed redundant tasks that became unnecessary due to shifting priorities.

- ✂️ Simplified parts of the strategy to focus on **conflict resolution and integration**.

---
Expand Down
Loading