Kanban Board Setup

[Bettenoch]

The following is a breakdown of how we have distributed the Kanban board activities:

Group Members:

1. @Graciano1997 (STUDENT A)
2. @Bettenoch (STUDENT B)

Find the github project link HERE

[Gambit142]

Hi @Bettenoch @Graciano1997 👋,

Good job so far!

Highlights

• Created Kanban Board ✔️
• Every Project requirement is represented by a card ✔️

You still need to work on some issues to go to the next project, but you are almost there!

Required Changes ♻️

• [ ] Kindly assign all cards to a member. Assigning cards to members helps the team know which member is responsible for building a feature and most times contains a detailed description of what that task is all about. 👍 💻 If a task is assigned, the avatar of the person(s) that the task was assigned to will be found in the bottom right corner of the card as shown in the screenshot below:

• [ ] After you assign all tasks to a member, it is important that the tasks are shared in an equal manner. Assigning tasks in an equal manner ensures that everyone is participating equally and nobody is overwhelmed with too many tasks. For example, you can assign all tasks for Team Member A to @Bettenoch and all tasks for Team Member B to @Graciano1997 or the other way around. Then the group tasks can either be assigned equally to each team member or you assign them to both of you. 👍 😎

Optional suggestions

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend considering them as they can improve your code.

You can also consider the following:

N/A

Cheers, and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

Please tag me in your question so I can receive the notification. You can tag me by typing @Gambit142

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 the code review was unfair, request a second opinion using this form.

[Qoosim]

Status: Approved :tada: :heavy_check_mark:

Hi @team,

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

Highlights

• Kanban board setup properly. :heavy_check_mark:
• Tasks shared fairly equal. :heavy_check_mark:

Optional suggestions

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.

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.

---

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.