-
-
Notifications
You must be signed in to change notification settings - Fork 26
Home
We track our issues on the current sprint's project board. The Current Sprint Board has columns to show progress. As you work on the issue, move the issue into the correct column:
- ToDo - Items in the sprint that are scheduled to be done.
- InProgress - Items in the sprint that are being worked on actively.
- InTesting - Items that are code changes that require testing by the developer prior to being ready. Coding is done, testing is in progress.
- InReview - Code and Testing are done, but someone (second set of eyes) should review for quality, especially merge requests.
- Done - Any issue that is worked on and finished OR closed because needs change.
In general, you should try to only have one issue at a time and take issues that have downstream items that depend on them only if you can turn them around fairly fast.
**If you're done with an issue, **please leave a final comment in the issue along with any related pull request. Anyone in the team can feel free to do reviews of issues and then comment to that effect. Once an issue is reviewed, I (or another delegate team member) will expect to do the merge of the pull request or any other admin work.
Once you're done with an issue, you should feel free to grab an issue from the top (or near top) of the todo list that you think you can do with minimal help.
If you think an issue is not clear, please leave a comment and do a mention to me or the creator and we'll try to make it clear.
**If you're stuck on an issue, **reach out to other team mates if you think they can help using slack or comments. If you cannot get help for a period of time (1-2 days), then feel free to make a comment that the issue is blocked (with the reason). Then you can take another item from the list. If any decisions/information is developed, add/update documentation so the entire team has it available.
We're generally trying to make sure that all items are done at the end of the sprint, and most that have been taken are done at the end of Tuesday night each week. To that end, keep issues small (1-2 hours of work). If needed, add an item to the ticket that says "enter issue(s) to continue x". That is perfectly fine. If you think the ticket warrants a large issue, that is fine, but mark that as (BIG) in the title. As we groom each week, we'll get better at this.
If you think an issue is too big/hard/you cannot complete it, just write a comment in the issue and put it back in the todo list at the top. This should be rare. Only take an issue if you feel pretty confident you can do it yourself.
Resources for Onboarding to be added here.