Rules to Better Scrum using GitHub (Issues and Projects)
- GitHub Issues - Do you use Issue Templates?
- GitHub Projects - Do you know how to do Scrum?
- Backlog - Do you know how to create a Sprint Backlog?
- GitHub Issues - Do you create templates for Sprint Reviews/Retros/Forecasts?
- GitHub Issues – Do you customize your labels?
- GitHub Issues - Do you turn emails into Issues before starting work?
- Do you review PBIs and react with 👍 or 👎?
- Do you know how to handle Undone Work (aka V2 for PBIs)?
- Backlog - Does your Product Owner know how to maintain the backlog?
- GitHub Issues – Do you sync to Azure DevOps?
- Scrum – Do you know where to discuss the backlog?
- Do you escalate key updates and deliverables?
- Do you use tasklists in your PBIs?
- Do you close PBIs and tasks with context?
- GitHub Repos - Do you write nice commit messages?
- Do you avoid linking issues to PRs in GitHub?
- GitHub - Do you use GitHub teams for collaborator permissions?