Kanban Board

[2004-okari]

• Github Project: https://github.com/2004-okari/CATALOG/projects/1
• A team of 4 members
  • @Bhekisile Team member #1
  • @Wineshuga Team member #2
  • @2004-okari Team member #3
  • @mohammadnewton Team member #4

[zieeco]

STATUS: INVALID!!! :x: :x: :x:

Hi @Team,

While you made a great effort in this project, unfortunately, I cannot proceed to review your code, please make sure you implement the following changes before you resubmit for review.

Required Changes ♻️

Check the comments below.

• [ ] Kindly add the link to the project to your issue description

Cheers, and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request Does not count into the code reviews limit.

INVALID PROJECT

[mikethreels]

Hi Team,

Good job so far! There are some issues that you still need to work on to go to the next project but you are almost there!

Highlights

• good job creating the board

Required Changes ♻️

• [ ] the goal of this project is to make a kanban board with tasks and divide them between each team member, for example below you can see a print screen of the project requirements for the group tasks: in this case you can divide this in the following cards:
• Create Item class
• All Item class properties visible in the diagram should be defined and set up in the constructor method.
• Add all methods visible in the diagram.
• Implement methods
• Create a main.rb file
• Implement startup actions make sure to give points to each card and divide them evenly so each team member has more or less the same workload and make sure that each card has a description of that task.

Please make sure to do this for all the requirements the above is just an example of what the group tasks might look like.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.

Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

---

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

[topeogunleye]

Hi @Wineshuga, @mohammadnewton, @2004-okari,

Status: Approved ✔️

Excellent job on making the changes requested by the previous code reviewer. Keep it up 👏

Your project is complete! There is nothing else to say other than... it's time to merge it 💪 Congratulations! 🎉

To highlight :champagne:

Code Review Highlights 🌟

1. Organization & Clarity: The division of tasks into separate cards demonstrates great organization. This will surely enhance the clarity and understanding for each team member.

2. Alignment with Requirements: By adhering to the initial instructions and addressing the requested changes, you've ensured that the project aligns well with the core requirements.

3. Attention to Detail: Noting the need to set up the Item class properties in the constructor and ensuring all methods from the diagram are included shows meticulous attention to detail.

4. Efficiency: Implementing the methods as directed and ensuring the creation of a main.rb file demonstrates efficient task management.

5. Balanced Workload: The recommendation to evenly distribute points among the cards is commendable. This will help ensure that each team member shares a balanced workload.

6. Descriptive Tasks: Highlighting the need to provide a description for each card/task enhances clarity and ensures each member knows what's expected.

Keep up the good work and continue to ensure clarity and balanced distribution as the project progresses! 🚀

[Optional] suggestions:

• Nothing to mention.

  Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag @topeogunleye in your question so I can receive the notification.

---

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.