We will be using GitHub Issues to coordinate work in this project. To learn how to use Issues, read Mastering Issues.
- Weekly meetings.
- Weekly or bi-weekly Sprint Milestones.
- End meeting by adding Issues for the next Sprint, assign them to people.
- Start meeting by reviewing the finished Issues from the last milestone. Move old open issues to next Sprint, reassign if needed.
GitHub Issues Tips and Guidelines
- Use @username to get that user's attention, @josemvidal for me.
- Use our milestones
- Create your own weekly or bi-weekly sprint milestones
- Assign each issue to 1 person
- Explain why you are closing the Issue. Adding "Closes #1" to your commit comment (anywhere) will do this for you automatically.
- Child issues refer to parent using “for #1” or “child of #1”
- bug something that needs to be fixed.
- enhancement new feature. A thing that needs to get done.
- duplicate this is issue is this same as another one. Link to the other one. Close this one.
- question answer it. Author closes it.
- readme read it. Close it. Teachers will use this to provide feedback to you.
- wontfix not gonna do it. Close it.
- Add your own!
- If someone did not close an important Issue by the end of the sprint, un-assign them. Assign them to an issue that is not on the critical path. If it continues, fire them.
If you have a lot of open Issues, you might want to use a Project (aka Kanban board) to organize them into columns. See video below.
- Mastering GitHub Issues
- GitHub for Project Management Video is a 1-hour video from GitHub where they go into a lot of details on how to use Issues.
- The Five Dysfunctions of a Team: A Leadership Fable
- Intro to Agile Scrum in Under 10 Minutes - What is Scrum?