Skip to content

Latest commit

 

History

History
28 lines (24 loc) · 2.14 KB

sdlc.md

File metadata and controls

28 lines (24 loc) · 2.14 KB

Hola hola,

This document is meant to provide a complete overview of the THT Software Development Lifecycle (SDLC) moving forward.

SDLC Overview

  1. Client Requirements are received and Tickets are created and added to the Backlog column of the relevant GitHub Project.
  2. Tickets receive tags: Android, iOS, Bug, Feature Request, Good First Task_, Severity 1, Severity 2, Severity 3, Needs More Info.
  3. Tickets are added to the Ready For Designs column.
  4. When the Designer is finished with the Ticket, or the Designer needs some guidance/feedback, the Ticket should be moved to the Needs Design QA/Feedback column.
  5. When Design QA/Feedback is finished, the Ticket should be moved to the Ready For Development column.
  6. When the Developer is finished with the Ticket, or the Developer needs some guindance/feedback, the Ticket should be moved to the Needs Dev QA/Feedback column.
  7. When Development QA/Feedback is finished, a PR should be opened to merge the solution into the dev branch and the Ticket should be moved to the PR Open column.
  8. When the PR has been tested, the PR should be merged into the dev branch.
  9. On Monday and Wednesday, a PR from the dev branch should be opened to merge recent updates to the staging branch.
  10. On Tuesday and Thursday, the open PR should be merged to the prod branch.
  11. All Tickets for the PR should be moved to the Done column.

Tags Explained

  • Android - Android should be included in the solution and QA
  • iOS - iOS should be included in the solution and QA
  • Bug - A feature is not behaving as it was intended to
  • Feature Request - This is a new feature and requires more dialog on a potential solution
  • Good First Task - This Ticket is estimated to be easier than most other Tickets and would be good for someone during onboarding or a Jr dev.
  • Severity 1 - This is negatively affecting the Users in a big way
  • Severity 2 - This needs to get done as soon as there is some bandwidth
  • Severity 3 - This can be done when someone is available
  • Needs More Info - This Ticket cannot progress until questions are answered