...
- Process requirements
- All commits must come in the form of pull-requests
- Pull-requests must source from individual GitHub branches
- Optional: name branches based on JIRA number, e.g. vivo-1234
- Each pull-request must reference a JIRA ticket
- The pull-request author must not merge their own pull-request
Attendees
Agenda
- Organize the plan and associated tickets for each Topic Objective
- Who is on each topic Objective team?
- All: create JIRA tickets
- All: identify objective task for today
- Sprint logistics
- Daily virtual "stand-up" (see below)
- Working GitHub branch:
develop
- Meetings:
- Friday, Oct 18th @11am ET
- Friday, Oct 25th - retrospective @1pm ET
- Pull-requests / reviews
Slack Standup Template
[APIVIVO AlignmentSprint Standup] Finished yesterday: {ticket titles and associated JIRA links} {AND please include brief textual description} Working on today: {ticket titles and associated JIRA links} {AND please include brief textual description} Blockers: {brief textual description}
Notes
...