Team Processes - department-of-veterans-affairs/abd-vro GitHub Wiki

Dependabot tickets

  • We will rotate who is taking the lead on Depandabots each sprint.
  • A ticket will be created at the start of each sprint during planning and assigned to one team member.
  • Any Dependabots for the sprint should be linked to in the sprints Dependabot ticket so that we can track our work.
  • The Dependabot Lead for the sprint can post in the Benefits-VRO-DevOps channel for any Dependabot tickets they may need help with.
  • Dependabot PRs need 2 reviewers: the Dependabot Lead + another teammate. The assignee is the Dependabot Lead but they also act as a reviewer since Dependabot is the author of the PR.
  • For more information see Dependabot.

Secrel issues

  • All of the teams engineers should monitor the Benefits-VRO-DevOps Slack channel for Secrel issues.
  • If a Secrel alert is for something that may have been caused by an engineers work, that engineer should indicate in the Slack alert that they are looking into the issue.
  • The person assigned to the Secrel monitoring ticket for a given sprint will indicate in the alert thread in Slack if they are looking into the alert or they will tag the engineer whose work may have caused the alert in the Slack thread.

Creating tickets

  • When someone other than the Product Manager creates a ticket for the backlog they should post a slack message in the team channel with a link to the ticket tagging the Product Manager. The ticket creator should indicate their opinion on the priority level of the ticket in the slack message. If the ticket creator feels the ticket should be worked on in the current sprint, they should state this in the slack message and seek agreement from the Product Manager before starting. Tickets should be created for most work that a team member performs that takes more than a half day of time so the team can get credit for the work completed.

Pull Requests (PRs)

  • PRs must be approved by a minimum of two reviewers.
  • Dependabot PRs are authored by Dependabot. This means that the two reviewers are the Dependabot Lead for the sprint, and another teammate.
  • For more information on PRs see Pull Requests