V.A.P.E Meeting Minutes
V.A.P.E Dev links
Note:
This is an ongoing document, please keep this up to date
First meeting (Sep 15th 2019)
Agenda:
- Team norms
- How Sprint works
- User stories
- Definition of Done
- Project management tool
Main points:
- Two main branches on each repo,
master
anddevelop
. The former one should serve as stable/release branch, while the later is for constant development. - All code must be merged through pull requests to
develop
branch from a feature branch first prior tomaster
branch.e.g feature/kurtosis_interface -> develop -> master
. - pull requests to
develop
branch requires at least one approval review.master
branch would require all team members approval review. - Sprint interval is set to 2 weeks. At the end of each sprint, team will host sprint review and planning meeting (Sunday morning. Time TBD)
- User stories should represent a feature/functionality that are ideally small, easy to test and review.
- Unit testing is one of the acceptance criteria of User story
- Trello is the Agile management tool
- Team should review pull requests in an efficient manner to avoid merging conflicts
Tasks:
- Create user stories in the backlog
- Set up local develop enviornment
- Get familiar with the work flow (Github pull requests, merging to develop, master, etc) (Updating documentation for our Github Org is a good example)
- Get familiar with Trello]
Second Meeting (Sep 25th 2019)
First Spring planning meeting
Committed 14 stories, 38 points