Skip to content
This repository has been archived by the owner on Jun 22, 2022. It is now read-only.

Feedback from the coaches #53

Open
jovankomatovic opened this issue Mar 27, 2020 · 2 comments
Open

Feedback from the coaches #53

jovankomatovic opened this issue Mar 27, 2020 · 2 comments

Comments

@jovankomatovic
Copy link

The team made a big leap forward with having implemented (with proper tests) the "communication" with a drone and the real-time tracking of it.
For the next meetings, it would be good to avoid confusions with the demo and preferably one member of the team does the entire demo session.
Also, please mark finished stories and tasks as done, move stories from Product to Sprint Backlog, divide them into tasks and assign members of the team responsible for them.
There are not a lot of detailed reviews on PRs. You should spend more time reviewing other's code and thinking about potential improvements.

@SolalPirelli
Copy link

Week ending on 03.04

It looks like your app is coming together. After the UI is improved and "best-path" feature is completed, the app would represent something that can be used in a real life.
As we have already mentioned during the meeting, the demo presentation should be focused more on clients, with a goal to attract them with the useful features your app incorporates.
Other than this, code reviews should be done regularly. It a very important part of the development, so plan your time to include this, please.

@SolalPirelli
Copy link

Week ending on 24.04

Good job. The app already looks like something that can be used.
Also, we noticed that you started paying attention to the code reviews and that is extremely important.
We have two suggestions for the next time:

  1. As we already mentioned, try to present a demo with an incorporated story. Look at yourself as some guy who just found out about the app and is extremely excited about it.
  2. Try to assign yourself to new tasks even before our weekly meeting. This is something that does not take a huge amount of time, but gives an impression of a very team-oriented and organized group.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants