Meltrust
commented
1 year ago Hi @dgcuenca,
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!
To highlight:
- All tasks have been assignedβοΈ
Required Changes β»οΈ
According to the project requirements:
At the time of this review, however, these are the pointings:
@paulsaenzsucre 44 @Juank628 46 @gjuliao 46 @dgcuenca 32 @belaymit 6
The general rule is that nobody can have more than 5 points than any other team member. That includes the whole team.
As you can see, @dgcuenca has 32 points, which is a lot less than @gjuliao who has 46. Also, @belaymit has just 6 points.
Therefore:
- [x] Kindly, make sure no one in your team has more than 5 points than any other member.
That way, we will meet this particular requirement. πͺ
Tip: You could reassign tasks, move the numbers, change the values.
- [x] This task does not have any points:
Kindly add points to it. While on it, kindly remember that no team member may have more than 5 points than any other. π
Optional suggestions
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 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.
Juank628
lojacho
In this pull request, We were able to:
Set up a kanban board to manage our project tasks: By organizing our tasks into different stages and columns, we can better visualize our progress and plan our next steps more effectively.
Created a project to manage the entire scope of the project: By having a centralized location for our project files and documentation, we can ensure that everyone is on the same page and that nothing falls through the cracks.
Created two separate repositories for front-end and back-end development: By separating our code into two distinct repositories, we can better manage changes, dependencies, and version control.
Created issues and assigned them to the appropriate repositories: By breaking down our tasks into smaller, more manageable chunks and assigning them to specific team members, we can ensure that everyone is working on the right things at the right time.
Thanks for the review. We are a group of 5