nashville-software-school/server-side-python-curriculum

Create guidance document for completing a sprint

Opened this issue · 0 comments

Ending Your Sprint

  1. Conduct a retrospective ceremony on the last day of the sprint. Read the three sections of the Introduction to the Sprint Retrospective article for an overview.
  2. On the Thursday of the Sprint, the team should commit on a specific start and stop time for the retro on Friday.
  3. Your retro board will be another Github project that you can attach to your repository. Add the following columns.
    1. Start Doing
    2. Stop Doing
    3. Keep Doing
    4. Kudos
  4. Tickets should be team focused and not “I” focused
  5. Stop and Start columns should highlight specific, actionable items that your team can work on during the next sprint.