-
Notifications
You must be signed in to change notification settings - Fork 0
PV Week 4
Simmanz edited this page Oct 7, 2024
·
3 revisions
- Maintainers ? => 20 mins ago
- Branch preds => done
- readme => could be better. (other branch)
- Scrum board. Well documented, could add tags (epics).
- Epic is a grouping of tasks. Main goals/components of the app.
- Warning do not over-expand (one-two at a time but well done instead of many mid)
- Change epics tags (no use tech/misc => Auth, …)
- Add colour to the tags for better visibility.
- Issues :
- When a task is in production, make an issue out of it.
- Create a new branch for the issue => feature implementation branch
- Then can implement / test
- Finally PR request
- Scrum board workflow :
- User stories from backlog => sprint backlog
- Generate tasks in the “In Development” column
- Once all tasks related to one user story are done, move user stories to finished column
- Coverage :
- Privilege 80%+ Sonar coverage (better coverage than line-coverage from Jacoco)
- Example of conditional testing for coverage.
- Figma check
- Branch rules
- Product owner (chooses the user stories)
- Discussion with the scrum master.
As many as possible user stories
- Conditions (filling fields of a report sheet).
- Abstraction if important (do not talk about exact implementation)
- Good example : This API is not well documented which make it hard/blocking
- Monday / Wednesday or Tuesday / Thursday for instance. => better Wednesday overall (Thursday is merge day + issues fixing)
- Demo is about main (not in a branch)
- Do not need to show everything / a lot. Just show progress (that works !)
- Should not be buggy
- To be filled Thursday evening
- What did the team work on (sprint)
- What did not work
- What to improve
- Maybe also an individual sheet (will get info later)
- Think about the sprint => more time efficient for meeting with coaches
- Big team problems sheet (slackers, hate, talk too much)
- Like for the bootcamps, but for the app
- Can you build app APK
- Is CI good
- MVVM architecture
- Meaningful tests
- Figma
- Documentation is in individual grades (+PR requests / reviews. Make them meaningful) /!\ Not too big / too small. Leave meaningful comments (if great comment
- Cognitive complexity (probably milestone 3) => modularize (no ifs in ifs)
- Can be verified with peers that do not know the project
- Good naming conventions (be good to the assistants)
- Dependency injection (opt : look at automatic injection)
- Do not have to create object instances
- Dagger hilt for info
- Sonar : which time metrics for code coverage checks
- Use badges (CI passed, coverage ok, …) Not more than 4-5 though.
- PRs need to have 80% code coverage on NEW CODE.
- #1-2 PRs per week per person. (graded individually => do most of it (99%))
- PR need to be check by 1, if big 2.
- Fix the tasks in scrum board.
- Change Epic fields
- Fill the sheets next standup meeting.
- PV added to github.
- CI has two different code coverage (Jacoco vs SonarCloud)
- Risk planning (Warm Up pt 2)
- Google ML kit
- Overpass API
- Implementing a friend-adding feature (QR-code for instance)
- Finish preparing the sprint 1 for friday 4.10.2024
- Figma User stories for backlog
- Verifying whether the current Figma has good enough UX/UI (ensure minimum viable product)
- QR-code in profile takes a lot of space => might be inside add a friend
- Main menu for friend's activity (timeline / like twitter feed)
- Events tab (bottomNavigationMenu) to access local event
- Assign backlog tasks to devs (sprint backlog)
- Profile UI - Kemin
- Sign-IN (UI & Logic) - Simon
- Map UI - Malik
- Fetch parks Overpass API - Alvaro
- Park UI - Arthur
- Navigation - Alex
- Localization (GPS) - Paul