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.

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

Update retrospective.md #59

Merged
merged 9 commits into from
Jan 10, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
3 changes: 1 addition & 2 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,6 @@ about: A template PR for code review with a checklist

- [ ] The function's name describes it's behavior
- [ ] The function's name matches the file name
- _It's ok to have extra helper functions if necessary, like with mergesort_
- [ ] The function has correct type annotations
- [ ] The function is not called at the top level of the function file
- _Recursive solutions **can** call the function from **inside** the function body_
Expand All @@ -69,7 +68,7 @@ about: A template PR for code review with a checklist

### Don'ts

- [ ] The function's strategy _is not_ described in any docstrings or tests
- [ ] The function's strategy _is not_ described in the documentation
- [ ] Comments explain the _strategy_, **not** the _implementation_
- [ ] The function _does not_ have more comments than code
- If it does, consider finding a new strategy or a simpler implementation
Expand Down
75 changes: 75 additions & 0 deletions collaboration/retrospective.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,75 @@
<!-- this template is for inspiration, feel free to change it however you like! -->

# Retrospective: Group 18 - Collaborative Work Activity

## Stop Doing

- **Inefficient Coordination:** Stop relying on informal communication
methods that cause misunderstandings or delays.

- **Overloading Tasks:** Avoid taking on excessive responsibilities
without proper delegation or prioritization.

- **Passive Participation:** Stop being a silent participant in discussions;
ensure to actively contribute to conversations.

## Continue Doing

- **Effective Teamwork:** Continue fostering collaboration by sharing ideas
openly and respecting diverse perspectives.

- **Timely Updates:** Maintain a habit of providing timely progress updates
to keep the team aligned.

- **Using Tools:** Keep leveraging collaborative tools
(e.g., shared documents, project management software) to enhance productivity.

## Start Doing

- **Structured Planning:** Begin creating more detailed action plans with
clear milestones and deadlines.

- **Feedback Loops:** Start implementing regular feedback sessions to
evaluate progress and address challenges early.

- **Skill Development:** Focus on improving specific skills related
to collaborative work and presentation to contribute more effectively.

## Lessons Learned

- Effective communication is crucial to avoid duplication of efforts and ensure alignment.

- Clear roles and responsibilities significantly enhance team productivity.

- Flexibility in strategy allows for better adaptation to unforeseen challenges.

- Regular check-ins help maintain momentum and ensure accountability.

______________________________________________________________________

## Strategy vs. Board

### What parts of your plan went as expected?

- Collaboration tools were effectively utilized to
share resources and coordinate tasks.

- The team successfully met initial deadlines for project deliverables.

- Team members demonstrated a willingness to support each other when challenges arose.

### What parts of your plan did not work out?

- Some tasks were delayed due to unclear task ownership.

- Miscommunication led to redundant efforts in certain areas.

- Time zone differences caused occasional scheduling conflicts.

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

- Yes, we added weekly synchronization meetings to
address miscommunications and ensure alignment.

- Included additional training sessions for team members to
improve tool usage efficiency.
8 changes: 4 additions & 4 deletions solutions/cumulative_sum.py
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
- cumulative_sum(numbers: list) -> list:
Computes and returns a list of cumulative sums from the input list.

Author: Falaq Youniss
Author: Falaq Youniss.
Date: 29/12/2024
"""

Expand Down Expand Up @@ -44,9 +44,9 @@ def cumulative_sum(numbers: list) -> list:
# Validate input
assert numbers is not None, "Input cannot be None."
assert isinstance(numbers, list), "Input must be a list of numeric values."
assert all(
isinstance(num, (int, float)) for num in numbers
), "All elements in the list must be numeric."
assert all(isinstance(num, (int, float)) for num in numbers), (
"All elements in the list must be numeric."
)
# Compute cumulative sums
cumulative_list = []
current_sum = 0
Expand Down
Loading