00. Program
Process
The PR-based development workflow every ticket follows, from estimate to close, across the Dev, Team Lead, and Tester roles.
Every ticket follows the same PR-based workflow with clear ownership. A Developer implements and self-tests the work, the Team Lead reviews the merge request, and a Tester verifies the result before the ticket is closed. The ticket status tells everyone exactly where the work is: Open → In Progress → Resolved → Testing → Closed.
Steps
| Step | Details | Status | Doer |
|---|---|---|---|
| Estimate | Estimate the ticket during Sprint Planning. | Open | — |
| Implement | Set the ticket to In Progress, branch off develop, and start coding on the feature branch. | In Progress | Dev |
| Self Test | After coding, self-test the output and create evidence (Figma, Storybook, compared image). | In Progress | Dev |
| Create PR | Open a PR from the feature branch to develop, ensure the pipeline passes, assign the TL. | In Progress | Dev |
| TL Review | The Team Lead reviews and comments directly on the PR. | In Progress | TL |
| Fix Comments | Address the review comments (if any). | In Progress | Dev |
| Merge PR | Approve and merge the PR into develop. | Resolved | Dev |
| Test | Test resolved tickets; if a bug is found, raise a Bug ticket as a sub-task. | Testing | Tester |
| Close | Close once all Bug tickets are closed, or no bug was found. | Closed | Tester |
Definition of Done
A ticket is only Closed when the code is merged to develop, the evidence is attached, the
pipeline is green, and the Tester has confirmed there are no open bugs. Any bug found in testing
loops the work straight back to In Progress.