Sprint checklist

Sprint process

• 

Issue labels

• 

Development process

• Protect master branch: require pull requests, dismiss stale pull requests & include admins

• All team members clone the repository

• Create a new feature branch for making changes

• Commit to the feature branch & publish

• Create a pull request for review

• Get another team member to review and approve or deny

• Merge pull request into master & delete the feature branch online and locally

Milestone & deadline

• Create a new milestone named after the sprint (week) number, e.g. “Sprint 2”

• Add a description denoting the overall sprint goal

• Add a deadline: before class next week

Project board

• Create a new project board named after the sprint (week) number, e.g. “Sprint 2”

• Add a description denoting the overall sprint goal

• Use GitHub’s “Kanban (Automated)” template as a starter

• Create a new “In review” column:

  • Preset: “Done”
  • Check: “Move all closed Issues here”
  • Yes: “This rule will be removed from the Done column”
  • Move “In review” between “In progress” & “Done”

• Delete the sample cards

Create Issues

• It’s an Issue or it doesn’t exist.

• Determine what the product should look like by the end of the sprint

• Create Issues for each small task or use Issues from the product backlog

• Use Markdown task lists to further detail the Issue

• Label each issue categorically

• Assign each Issue to a single person

• Assign each Issue to the sprint’s milestone

• Assign each Issue to the sprint’s project board

Cleanup

• Make sure all complete Issues are closed

• Make sure all pull requests are approved & complete

• Remove all incomplete Issues from the sprint’s milestone

• Remove all incomplete Issues from the sprint’s board

• Close the sprint milestone

• Close the sprint project board

Review

• Make a new Issue, assigned to the sprint’s milestone & assigned to all the team members

• Assign this Issue the “product” label

• Give a quick overview of your progress so far as the Issue description

• Each team member must make a comment answering these questions:

  • How did you & the sprint succeed? What was positive?
  • How did you & the sprint fail? What was negative?

  Do not blame team members for anything. This reflection is all about you and what you contributed.

• Tag @thomasjbradley when all team members have contributed

• Close the Issue