t the end of iteration 3, each team should conduct a review of the work performed by another team, covering the following points:
1. Code review. Pull the code from the source code repository, build it and analyze the source code. List the bugs you found, design issues, antipatterns, inefficient code, etc.
2. Installation test. From the source code, get the application up and running in your environment. Describe the problems you faced and propose solutions to ease the installation.
Code review. Pull the code from the source code repository, build it and analyze the source code. List the bugs you found, design issues, antipatterns, inefficient code, etc.
* not really a problem, but a suggestion: when making a new order the could be like a word that says that the fish is by the amount not in kilograms or something like that. (I was a little confused for a second). In the Orders pages there is nicely said that it is the amount of fish
Installation test. From the source code, get the application up and running in your environment. Describe the problems you faced and propose solutions to ease the installation.
* the map was kinda slow sometimes
Acceptance test. Taking requirements into account, check the functionality of the application and verify whether it corresponds to the requirements. Make sure what features are supposed to work in the version you are conducting tests upon, you might need to communicate with the reviewed team for this.
* maybe the delivered/done orders text could be more seeable, I almost didn't see the option to look at these orders US-18 **\[Order Organisation\]** As a courier, I want to be able to look at all previously completed orders so I can quickly reference previous orders.
After your project is reviewed by another team, take time to analyze the issues raised, determine if any action needs to be taken, and, if necessary, create the tasks in your issue tracker to address the most important issues identified during the peer review. At the end of iteration 4, you need to submit a "Peer review response" explaining which of the issues raised in the peer-review of your project have been addressed, and why you have decided not to address the remaining issues.
3. Acceptance test. Taking requirements into account, check the functionality of the application and verify whether it corresponds to the requirements. Make sure what features are supposed to work in the version you are conducting tests upon, you might need to communicate with the reviewed team for this.
* I am not sure but I didn't see a option to add urgency, the US is marked as could-have so maybe it is to implemented yet (US-5: **\[Route planning\]** As a courier, I want the system to calculate the optimal route considering the urgency and stage of orders so that I can follow the most time-sensitive schedule efficiently.)
The first step of the peer review process is to select a project that you want to review. For the selection of a project, work and decide collaboratively within your team, and take into account the following two preconditions:
* Similar to this the UC-5 Calculate route. The system calculates the shortest path between the order locations, taking into account the order (sequence) in which the orders are in the route plan. (how can I change the order ) The system displays key route information, including the estimated travel time and distance in kilometers. (Currently distance is only displayed)
* Is that working? US-14 **\[Order management\]** As a courier, I want the system to be linked to the POS, so that I don’t have to manually enter all the orders.
Choose a project which is not selected by another team
* this is also not implemented? but once again it is marked as could-have. US-16 **\[Order Organisation\]** As a courier, I want to be able to prioritise certain orders so that they’d show up at the top of the Delivery Planning View.
Choose a project of a team that did not select to review your project
* KONTROLLI SEDA!!!!! **\[Account management\]** As a courier, I want to be able to reset my password, so that I can regain access to the application if I forget my password. Priority: High
In this way, we expect that every team will select a different project (that is, no project will be selected by two or more teams), no project will stay unselected, and no dependencies will be developed between teams.
*
\ No newline at end of file
Your peer review and your response must be accessible from your Wiki's front page.
